WIBARAB FeatureDB TEI Customization — Version 1.0.1

Table of contents

WIBARAB Feature DB: Functional Requirements and Data Specification

The purpose of this TEI customization is to formalise the data structures needed to implement the WIBARAB Feature DB application. Thus, we start with a brief introduction into the most important functionalities which the application is expected to provide in Part I, a discussion of the sources feeding the database in Part II, descriptions of the overall data model in Part III, the organization of the working files in Part IV, giving some details on tools applied in the production of the data in Part V and finally a presentation of the formal TEI customization in Part VI.

1. Part I: Functional Requirements of WIBARAB Feature DB

The WIBARAB Feature DB should allow researchers to explore and compare the different realizations of particular lingustic features in an array of Arabic vernaculars. Since the main objective of the project is to investigate the linguistic Bedouin-Sedentary split, the WIBARAB Feature DB focuses on those Arabic varieties spoken by traditionally nomadic communities and on varieties that have been classified as "Bedouin" both by the envolved communities as well as researchers. For comparative purposes, it also includes the better documented sedentary varieties. The database focuses on a set of linguistic features that are considered especially relevant for typological purposes, most of which have been reported on in previously published academic studies to be especially salient of the speech of Bedouin communities.

In this way, the WIBARAB Feature DB represents both a specialized archive gathering linguistic data from a wide range of Arabic varieties, and an analytical research tool. It should enable the WIBARAB team and other researchers to both confirm the existence of common linguistic trends among Bedouin communities across the Arab World, accurately identifying the common features and its respective realizations, and provide sufficient data to reject the currently prevailing Bedouin-Sedentary split hypothesis.

The term database in the name of the described resource has been chosen for pragmatic reasons and has to be understood in a very broad sense as an organized collection of semi-structured data electronically stored and accessible. The entire textual source of WIBARAB Feature DB is encoded in accordance with the Guidelines of the Text Encoding Initiative.

2. Part II: Sources

The data included in the WIBARAB Feature DB draws on three main types of sources:

The research library has been stored in the VICAV Zotero library the creation of which antedates the project by several years. This library has been built-up mainly by students and researchers of the Institute of Oriental Studies of the University of Vienna and has been used as part of the VICAV digital infrastructure by several projects (TUNICO, SHAWI, TUNOCENT, WIBARAB). It brings together research publications in the fields of Arabic dialectology and Arabic linguistics focusing on spoken varieties. All bibliographical items have been provided at least with information on the region dealt with in the publication, however many items also contain further information about content and type of the publication (e.g. dictionary, grammatical description, textbook etc.). Currently, the VICAV library contains more than 5,000 titles.

The name VICAV Zotero library refers to the software that has been used to collect the data, Zotero being a freely available up-to-date bibliographical tool which allows to collaboratively compile bibliographies. It also provides a number of export functions, most conveniently also one producing valid TEI conformant bibliographical records.

3. Part III: Data Model of Feature Documents

The data included in the database is supposed to describe a series of salient linguistic features . The criteria used for the selection of these features mainly rely on typological considerations and on previously reported high levels of sociolinguistic salience. The feature descriptions are organised in documents grouping together feature value observations pertaining to particular linguistic phenomena, such as e.g. all observations that pertain to the existential particle, observations that pertain the reflexes of Classical Arabic interdentals in the modern varieties etc.

Every linguistic feature has a set of feature values that indicates the different attested realizations of a specific feature in the studied varieties. The documentation of an occurrence of (a) specific feature value(s) in a specific location is accomplished via feature value observations . Every feature value observation specifies that one particular feature value occurs in a specific place and is produced by a specific speaker or group of speakers. When information about the speakers and their communities is available, the sociolinguistic profile of the speaker or the community of speakers is indicated via the personGrp element, which may specify values regarding the speakers' tribal affiliation, religious affiliation, age group, gender, and native language among others. When specific remarks that are not codifiable via previously explained elements are due, they are indicated in prose within the exception notes, constraint notes or general notes.

Some sources may group the combination of realizations of feature values and characterize them as a linguistic variety or dialect. These linguistic varieties may be labelled after the approximate location they are spoken at, and/or the community of speakers that use them. These common groupings or varieties are indicated via language Profiles and provide additional historical and linguistic information available regarding a specific variety according to one or more sources.

3.1. Header

The status of the working document is indicated in the status attribute of the <revisionDesc> element of the document. It can have the following values:

  • draft is set when the input of the feature value observations is still not complete, data collection is still ongoing.
  • done is used when the input of the feature value oservations is considered as completed by the responsible person which is encoded as the <author> of the document, implying that the major part of data input has been done and the document is ready to be validated.
  • validated indicates that the document has been validated and no changes are required/the document is valid.
  • needsRevision shows that after the validation the document has to be revised and corrected in order to be valid.
  • revised indicates that the necessary change have been made and the document is ready to be validated again.
  • completed indicates that this is the final version of the document and the file is ready to be published.

Regarding data input procedures, different geographical areas have been assigned to particular members of the team. The individual researchers are then responsible for the compilation and encoding of the data of a specific location. The name of this responsible person is codified in 2 or 3 capital letters: ex. Johanna Doppelbauer is JD, Ana Iriarte Diez is AID in accordance with the information given in wibarab_dmp.xml file.

3.2. Feature Values

Every document starts with a list of feature values which represents one of the results of the research carried out on the particular phenomenon.

<head>Feature Values</head> <list type="featureValues">  <item xml:id="pr_p1c_nihna">   <label>niḥna/nəḥna</label>  </item>  <item xml:id="pr_p1c_ihna">   <label>iḥna/əḥnä</label>  </item> ... </list>

3.3. Feature Value Observation

In their initial experiments, the working group made use of a highly abstracted system made up of typefied <fs> (feature structure) elements. However, after extensive discussions and consultations with experts, we remodelled the entire structure attempting to make use of more expressive existing TEI elements. To come up with a solution fitting our particular goals, we customized the TEI Schema attempting to reuse as many TEI elements as possible. So far, we managed to do with only one additional new element ( <featureValueObservation> ) which had emerged from our discussions and appeared to serve the particular purpose best. This element is centre piece of the customisation, all other elements exist in the Guidelines and appear to be applicable without twisting their originally intended semantics too much.

The newly introduced <featureValueObservation> element contains at least three pieces of information:

  • an indication of the linguistic phenomenon being described,
  • information on the location of the phenomenon,
  • and the source where the information comes from.

The specificities of the respective elements are descibed below.

To describe this kind of data we made use of the following mandatory elements. Each feature value observation is based on the occurence of a linguistic feature in a specific way, i.e., a feature realisation . These realisations are grouped into a set of feature values , hence the feature value observation shows how a source attests that a given feature is realised by a certain Feature Value at a specific location. The feature value observation can additionally include information on the person group for which this particular Feature Realisation is attested and it is linked to the language profile of the variety to which it is customarily assigned.

The occurrence of multiple values or of multiple sources for a specific place or variety will then result in the creation of additional <featureValueObservation> elements. Each <featureValueObservation> is identifiable by a unique xml:id attribute.

<wib:featureValueObservation xml:id="fv_0048"  status="doneresp="dmp:AID"    xmlns:wib="https://wibarab.acdh.oeaw.ac.at/langDesc">  <name type="featureValueref="#q_q"/>  <bibl corresp="zot:Younes2013"   type="publication"/>  <placeName ref="geo:wadi_khalid"/>  <lang target="..\profiles\vicav_profile_LBN-ATI.xml"/>  <personGrp role="tribe"   corresp="pgr:arab_al_atij"/>  <personGrp role="agecorresp="pgr:young"/>  <cit xml:id="ct_0028type="example">   <quote>qalīl</quote>   <cit type="translation">    <quote>a little</quote>   </cit>  </cit>  <note type="general"> Young speakers often use q in words realized with    /g/ or /ǧ/ by older speakers, ex. <foreign>gilīl</foreign> or  <foreign>ǧilīl</foreign> - <foreign>qalīl</foreign> «few,    little»</note> </wib:featureValueObservation>

3.3.1. Mandatory Elements

3.3.1.1. Feature Name

The feature description at the beginning of each document contains a list of feature values that allow to neatly group the observed linguistic phenomena under clearly identifiable labels. This information is referred to in each <featureValueObservation> in a <name> element with a ref attributing pointing to particular items of the list of feature names.

3.3.1.2. Place

Locations to anchor particular phenomena geographically are indicated via <placeName> elements and a ref attribute pointing to the VICAV Geodata File.

3.3.1.3. Source

Each <featureValueObservation> element needs to have at least one source indicating where the information comes from. The most common case is <bibl type="publication"> , the reference to the bibliography (Zotero file) being put in a corresp attribute. However, as mentioned above the <bibl> element can also contain a reference to a fieldwork campaign or personal communication (source file).

<wib:featureValueObservation xml:id="fv_0027"  status="doneresp="dmp:AID"    xmlns:wib="https://wibarab.acdh.oeaw.ac.at/langDesc">  <name type="featureValue"   ref="#pr_p1c_ihna"/>  <bibl corresp="zot:Behnstedt2019"   type="publication"/>  <placeName ref="geo:jurdeih"/> ... </wib:featureValueObservation>

3.3.1.4. Variety

Information on a particular linguistic variety can be specified in a VICAV language profile. A <lang> element contains a link to a VICAV profile. The language profile is a file which contains any extra information collected about the variety and the place where it is spoken. These Profiles are named after our internal naming System with a 3 letter countrycode, dash, variety code. Some Profiles have been generated from pre-existing data from VICAV. For varieties that do not have a profile, stubs have been created.

3.3.2. Optional Elements

Additionally, a <featureValueObservation> may contain a number of optional elements outlined below.

3.3.2.1. Person Group

Person Group describes any specific discernable group of people that have the realization of a feature in common such as tribal affiliation, religious affiliation, age group, gender, native language, etc. To encode this kind of informatin, we make use persGroup element(s) which are furnished with role attributes that specify tribe, age, religion, sociolinguistic perception and native language) that further specifies information about the speakers from whom the realization of a feature value has been observed or documented in the source.

3.3.2.2. Source Representation

In contrast to the normalized transciptions of the feature values, source representations allow the encoders to give the original representation as found in the sources, reflecting the literal information from the source quoted in its original form, i.e. in the source's transcription system.

This information is encoded making use of cit[@type="sourceRepresentation"]/quote constructs.

3.3.2.3. Examples

Examples can be used to illustrate a feature value. They are taken from original source and furnished with English translations. They are encoded with cit[@type="example"]/quote constructs which have been chosen in analogy to common lexicographic procedures.

3.3.2.4. Notes

Notes can be used to clarify specificities of a particular phenomenon, especially exceptions and constraints concerning the realization of a feature value.

<note type="general"> Rosenhouse (1984: 17) notes similar <foreign>ʔəḥna</foreign> and <foreign>ʔaḥna</foreign> forms of this pronoun for the north Israeli Bedouin without further specification </note>

3.4. Discussion Section

Each feature document can contain a section (<div type="description"> ) with a description of the linguistic feature it describes, which is located right after the feature value list.

In order to include a copy of the feature value list in the description, one may use the <divGen> element with an type attribute with the value featureValues.

4. Part IV: Working Files

The information described in Part II and III above is organized and stored in different types of documents. The document type describing the linguistic features has an open number of representations. This category of files comprises the feature files and the language profiles. However, the feature files contain numerous links to reusable data stored in five external files. These `background´ files are used to compile the linguistic features and to document the sources:

4.1. The Feature Files

The feature files each describe one linguistic feature.

The feature value observations are stored according to different features in what has been dubbed in the project's internal nomenclature feature files . These files have names that consist in the prefix features_ and a concise title describing the contents of the documents. Document names must not contain special characters or whitespace. Hence, there is one file for every feature where the feature value observations of that particular feature are stored together. At the beginning of every feature file there is a prose description of the phenomenon at hand followed by an explanation of the feature values and its symbolic representation in the map.

4.2. The Language Profiles

The profiles each describe an arabic variety.

4.3. VICAV Geodata (vicav_geodata.xml)

The geodata file contains a list of all the referenced places. Wherever possible, the place listed in this document refers to respective entries in the GeoNames geographical database.

<place type="geoxml:id="aaouade">  <placeName>Aaouade</placeName>  <location>   <geo decls="#dms">34°37'34"N 36°22'38"E</geo>   <geo decls="#dd">34.62611 36.37722</geo>   <country key="LB">Lebanon</country>   <country/>  </location>  <idno type="geoNames">2266310</idno>  <note>Location for the ʕAṛaḅ al-ʕAtīǧ</note> </place>

4.4. VICAV Zotero file (vicav_biblio_tei_zotero.xml)

The biblio file contains all the sources found in the Zotero library. The export from the Zotero database is enriched with geo-locations making use of the above described geodata file. Furthermore, all publications used in the WIBARAB Feature datatabase include information about the period when the data the publication is based on was collected; the decade of data collection (doc). Whereever possible, this information was extracted from he publications in question and marked with a "level of certainty = high" tag. However, in the cases where the publication does not specify the decade of data collection this information is estimated by the following method: when the when the publication was published in the first half of a decade, the decade of data collection is estimated to be the previous decade, e.g. for a publication published in 1994, the decade of data collection is estimated to be the 1980s. When the publication was published in the second half of a decade, it is estimated that the data was collected in the same decade, e.g. for a publication published in 1995, the decade of data collection is estimated to be the 1990s. In order to let the database users know that this is merely an estimate, a "level of certainty = low" tag is added to these entries in Zotero.

4.5. WIBARAB Individual Contributors (wibarab_dmp.xml)

The Data Management Plan contains a description of the project including information about the researchers who contribute to the database. The Responsible Person attribute links to this list.

4.6. WIBARAB Campaigns (wibarab_sources.xml)

The sources file contains all sources that are not from Zotero, i.e., fieldwork campains and personal communications.

4.7. WIBARAB Person Groups (wibarab_PersonGroup.xml)

The PersonGroup list contains different person groups, such as religion, age, gender, native language, sociolinguistics and affiliation to a tribe.

5. Part V: Other Components of the Infrastructure

The Schema of the customisation ... ; namespace wib:

The TEI data has for the most part been created making use of ˂TEI˃Enricher, a freely available XML editor that has been developed at the ACDH-CH. This tool is geared to the use with TEI conformant data in research contexts.

Data visualisation during the editing process is accomplished through an XSL file tei_fs_2_html__001.xsl which has also been used to integrate the data stored in the various files described in Part IV.

6. Part VI: Formal Specification

6.1. Elements

6.1.1. <TEI>

<TEI> (TEI document) In the context of the WIBARAB Feature Database, each TEI feature document contains the description of one feature, the possible ways it can be realised ( ‘feature values’) in a <list type="features" > and documented observations of this specific feature in literature or in the data collected in the fieldwork of WIBARAB.In the context of the WIBARAB Feature Database, each TEI feature document contains the description of one feature, the possible ways it can be realised ( ‘feature values’) in a <list type="features" > and documented observations of this specific feature in literature or in the data collected in the fieldwork of WIBARAB. [4. Default Text Structure 16.1. Varieties of Composite Text]
Namespacehttp://www.tei-c.org/ns/1.0
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

Member of
Contained by
core: teiCorpus
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

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

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   tei_att.global.attributes,
   attribute version { text }?,
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

6.1.2. <abbr>

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

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

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

6.1.3. <abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributes
Contained by
May contain
Note

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

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

6.1.4. <activity>

<activity> (activity) contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything. [16.2.3. The Setting Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: setting
May contain
Note

For more fine-grained description of participant activities during a spoken text, the <event> element should be used.

Example
<activity>driving</activity>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element activity { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.5. <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.transcriptional.attributes,
   tei_macro.paraContent
}

6.1.6. <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
core: address
May contain
Note

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

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

6.1.7. <address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
rolespecifies further information about the purpose of the address.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
sender
the address of the sender of a piece of correspondence.
return
the address to which undeliverable mail should be returned.
recipient
the address of the intended recipient of a piece of correspondence.
work
the address to which work-related mail should be sent, typically that of the recipient’s employer.
home
the address to which non-work-related mail should be sent, typically the domicile of the recipient.
start
the address of the beginning of a route, for example of a race.
finish
the address of the end of a route, for example of a race.
pickup
the address at which a person or package is picked up, for example by a taxi or delivery service.
dropOff
the address at which a person or package is dropped off, for example by a taxi or delivery service.
Note

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

Member of
Contained by
May contain
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
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute role { list { + } }?,
   ( tei_model.global*, ( ( tei_model.addrPart, tei_model.global* )+ ) )
}

6.1.8. <affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.

Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for    the Humanities</name> </affiliation>
ExampleThis example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"  notBefore="1957-02-28">Paid up member of the <orgName>Australian Journalists Association</orgName> </affiliation>
ExampleThis example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.
<affiliation from="1902-01-01"  to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element affiliation
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.9. <age>

<age> (age) specifies the age of a person. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
valuesupplies a numeric code representing the age or age group.
StatusOptional
Datatypeteidata.count
Note

This attribute may be used to complement a more detailed discussion of a person's age in the content of the element

Member of
Contained by
namesdates: person personGrp
May contain
Note

As with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text.

Example
<age value="2notAfter="1986">under 20 in the early eighties</age>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element age
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute value { text }?,
   tei_macro.phraseSeq.limited
}

6.1.10. <analytic>

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

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

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate 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
{
   tei_att.global.attributes,
   (
      tei_author
    | tei_editor
    | tei_respStmt
    | tei_title
    | tei_model.ptrLike
    | tei_date
    | tei_textLang
    | idno
    | tei_availability
   )*
}

6.1.11. <appInfo>

<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>  <application 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 { tei_att.global.attributes, tei_model.applicationLike+ }

6.1.12. <application>

<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader
Attributes
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
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
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute ident { text },
   attribute version { text },
   ( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
}

6.1.13. <author>

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

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

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

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

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

6.1.14. <availability>

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

A consistent format should be adopted

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

6.1.15. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
Note

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

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

6.1.16. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
statusThis attribute is used to indicate references to bibl entries which need to be conrolled.
Derived fromatt.docStatus
StatusOptional
Datatypeteidata.enumerated
Sample values include:
CHECKME
The value of @corresp needs to be confirmed by the FVO's editor.
type
StatusOptional
Legal values are:
publication
Published written documents, recorded in the VICAV Zotero library
personalCommunication
Personal communication with native speakers of the variety or researchers via phone, e-mail or in person.
fieldwork
data from fieldwork conducted by members of the team indcluding both campaigns conducted within the project and prior to it.
Member of
Contained by
derived-module-featuredb: featureValueObservation
dictionaries: lang
linking: seg
textstructure: body div
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:bibl"/> </sch:pattern>
Content model
<content autoPrefix="true">
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="title" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="biblScope" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="note"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element bibl
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.source.attribute.source,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute corresp { list { + } },
   attribute status { text }?,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "publication" | "personalCommunication" | "fieldwork"
   }?,
   ( tei_title?, tei_biblScope?, tei_note* )
}

6.1.17. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

Example
<biblScope>pp 12–34</biblScope> <biblScope 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
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_macro.phraseSeq
}

6.1.18. <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Example
<biblStruct type="newspaper">  <analytic>   <author>    <forename>David</forename>    <surname>Barstow</surname>   </author>   <author>    <forename>Susanne</forename>    <surname>Craig</surname>   </author>   <author>    <forename>Russ</forename>    <surname>Buettner</surname>   </author>   <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>   <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>  </analytic>  <monogr>   <title level="j">The New York Times</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>A. G. Sulzberger</publisher>    <date when="2018-10-03">Wednesday, October 3, 2018</date>   </imprint>   <biblScope unit="volume">CLXVIII</biblScope>   <biblScope unit="issue">58,104</biblScope>   <biblScope unit="page">1</biblScope>  </monogr> </biblStruct>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:biblStruct"/> </sch:pattern>
Content model
<content>
 <sequence>
  <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
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.docStatus.attributes,
   (
      tei_analytic*,
      ( ( tei_monogr, tei_series* )+ ),
      (
         tei_model.noteLike
       | tei_model.ptrLike
       | tei_relatedItem
       | tei_citedRange
      )*
   )
}

6.1.19. <binaryObject>

<binaryObject> provides encoded binary data representing an inline graphic, audio, video or other object. [3.10. Graphics and Other Non-textual Components]
Modulecore
Attributes
encodingThe encoding used to encode the binary data. If not specified, this is assumed to be Base64.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May containCharacter data only
Example
<binaryObject mimeType="image/gif"> R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwy GHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ +5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnK PjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6 mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3u Nna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH hhx4dbgYKAAA7</binaryObject>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element binaryObject
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.media.attributes,
   tei_att.timed.attributes,
   attribute encoding { list { + } }?,
   text
}

6.1.20. <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element birth
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.21. <bloc>

<bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<bloc type="union">the European Union</bloc> <bloc type="continent">Africa</bloc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element bloc
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.22. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
derived-module-featuredb: featureValueObservation
textstructure: byline div
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </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 body
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      tei_model.global*,
      ( ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )? ),
      (
         ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?
      ),
      (
         (
            ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
         )
       | (
            (
               tei_model.div1Like,
               ( tei_model.global | tei_model.divGenLike )*
            )+
         )
       | (
            ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
            (
               (
                  (
                     tei_model.divLike,
                     ( tei_model.global | tei_model.divGenLike )*
                  )+
               )
             | (
                  (
                     tei_model.div1Like,
                     ( tei_model.global | tei_model.divGenLike )*
                  )+
               )
            )?
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

6.1.23. <byline>

<byline> (byline) contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]
Namespacehttp://www.tei-c.org/ns/1.0
Moduletextstructure
Attributes
Member of
Contained by
core: lg list
textstructure: back body div front
May containCharacter data only
Note

The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docAuthor> element.

Example
<byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline>
Example
<byline>Written from her own MEMORANDUMS</byline>
Example
<byline>By George Jones, Political Editor, in Washington</byline>
Example
<byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline>
Content model
<content autoPrefix="true">
 <textNode/>
</content>
    
Schema Declaration
element byline { tei_att.global.attributes, tei_att.cmc.attributes, text }

6.1.24. <catDesc>

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

6.1.25. <catRef>

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

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

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

6.1.26. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Namespacehttp://www.tei-c.org/ns/1.0
Moduleheader
Attributes
n
StatusRequired
Datatypeteidata.text
Contained by
May contain
core: desc gloss
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   attribute [http://www.tei-c.org/ns/1.0]n { text },
   (
      ( tei_catDesc+ | ( tei_model.descLike | equiv | tei_gloss )* ),
      tei_category*
   )
}

6.1.27. <cb>

<cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

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

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

6.1.28. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
Note

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

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

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change 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
{
   tei_att.global.attributes,
   tei_att.ascribed.attributes,
   tei_att.datable.attributes,
   tei_att.docStatus.attributes,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

6.1.29. <channel>

<channel> (primary channel) describes the medium or channel by which a text is delivered or experienced. For a written text, this might be print, manuscript, email, etc.; for a spoken one, radio, telephone, face-to-face, etc. [16.2.1. The Text Description]
Modulecorpus
Attributes
modespecifies the mode of this channel with respect to speech and writing.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
s
(spoken)
w
(written)
sw
(spoken to be written) e.g. dictation
ws
(written to be spoken) e.g. a script
m
(mixed)
x
(unknown or inapplicable) [Default]
Member of
Contained by
corpus: textDesc
May contain
Example
<channel mode="s">face-to-face conversation</channel>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element channel
{
   tei_att.global.attributes,
   attribute mode { "s" | "w" | "sw" | "ws" | "m" | "x" }?,
   tei_macro.phraseSeq.limited
}

6.1.30. <choice>

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

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

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

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

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

6.1.31. <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 10.3.5.1. Examples]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
sourcesource on <cit type="example"> documents the source an example is taken from. In case the value of it points to a <person> element, that means that the example is provided by an informant. When it's absent, the example is drawn from source indicated by the <bibl> element in the parent <featureValueObservation>.
StatusOptional
Datatypeteidata.pointer
type
StatusOptional
Legal values are:
example
sourceRepresentation
translation
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>
Example
<cit type="example">  <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>  <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"   mimeType="audio/wav"/>  <cit type="translation">   <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>  </cit>  <cit type="translation">   <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>  </cit> </cit>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:rule context="tei:cit[@type = 'example']"> <sch:assert test="tei:cit[@type='translation']"> An example should have a translation. </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.cmc.attributes,
   attribute [http://www.tei-c.org/ns/1.0]source { text }?,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "example" | "sourceRepresentation" | "translation"
   }?,
   (
      tei_model.biblLike
    | tei_model.egLike
    | tei_model.entryPart
    | tei_model.global
    | tei_model.graphicLike
    | tei_model.ptrLike
    | tei_model.attributable
    | pc
    | tei_q
   )+
}

6.1.32. <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Contained by
May contain
Note

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

Example
<citedRange>pp 12–13</citedRange> <citedRange 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
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_att.pointing.attributes,
   tei_macro.phraseSeq
}

6.1.33. <classCode>

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

6.1.34. <classDecl>

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

6.1.35. <constitution>

<constitution> (constitution) describes the internal composition of a text or text sample, for example as fragmentary, complete, etc. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: textDesc
May contain
Note

The function of this element seems to overlap with both the org attribute on <div> and the <samplingDecl> in the <encodingDesc>.

Example
<constitution type="frags">Prologues only.</constitution>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element constitution { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.36. <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

6.1.37. <correspAction>

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
Contained by
header: correspDesc
May contain
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   tei_att.global.attributes,
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

6.1.38. <correspContext>

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

6.1.39. <correspDesc>

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

6.1.40. <creation>

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

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

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

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

6.1.41. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.source.attribute.source,
   tei_att.calendarSystem.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.w3c.attribute.when,
   tei_att.datable.w3c.attribute.notBefore,
   tei_att.datable.w3c.attribute.notAfter,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

6.1.42. <death>

<death> (death) contains information about a person's death, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element death
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.43. <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

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

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

Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegiblequantity="5"   unit="character"/> </del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.transcriptional.attributes,
   tei_macro.paraContent
}

6.1.44. <derivation>

<derivation> (derivation) describes the nature and extent of originality of this text. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: textDesc
May contain
Note

For derivative texts, details of the ancestor may be included in the source description.

Example
<derivation type="original"/>
Example
<derivation type="translation"  source="#rosette"/> <!-- ... --> <!-- in the sourceDesc: --> <bibl xml:id="rosette">  <author>de Béranger, Pierre-Jean</author>. <date>1839</date>. "<title level="a">Rosette</title>". In <editor>H. Fournier</editor>, ed. <title level="m">Œuvres complètes de Béranger</title>. <biblScope unit="volume">Vol 2</biblScope> (p. <biblScope unit="page">29-30</biblScope>). </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element derivation { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.45. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

ExampleExample of a <desc> element inside a documentation element.
<dataSpec module="tei"  ident="teidata.point">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
ExampleExample of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
SchematronA <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.limitedContent
}

6.1.46. <distinct>

<distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
Modulecore
Attributes
timespecifies how the phrase is distinct diachronically.
StatusOptional
Datatypeteidata.text
spacespecifies how the phrase is distinct diatopically.
StatusOptional
Datatypeteidata.text
socialspecifies how the phrase is distinct diastratically.
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
Example
Next morning a boy in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct> keep secret.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distinct
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute time { text }?,
   attribute space { text }?,
   attribute social { text }?,
   tei_macro.phraseSeq
}

6.1.47. <distributor>

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

6.1.48. <district>

<district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<placeName>  <district type="ward">Jericho</district>  <settlement>Oxford</settlement> </placeName>
Example
<placeName>  <district type="area">South Side</district>  <settlement>Chicago</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element district
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.49. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Namespacehttp://www.tei-c.org/ns/1.0
Moduletextstructure
Attributes
type
StatusOptional
Legal values are:
description
featureDescription
featureValueObservations
Member of
Contained by
textstructure: back body div front
May contain
derived-module-featuredb: featureValueObservation
textstructure: byline div
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:rule context="tei:div[@type = 'description']"> <sch:assert test="child::tei:byline"> 'byline' element is required. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:div"> <sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <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>
 </sequence>
</content>
    
Schema Declaration
element div
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.divLike.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "description" | "featureDescription" | "featureValueObservations"
   }?,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.divLike | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
                  (
                     (
                        ( tei_model.divLike | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

6.1.50. <divGen>

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
type
StatusRequired
Legal values are:
featureValues
list of feature values
Member of
Contained by
textstructure: back body div front
May contain
core: head
Note

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

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

6.1.51. <domain>

<domain> (domain of use) describes the most important social context in which the text was realized or for which it is intended, for example private vs. public, education, religion, etc. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: textDesc
May contain
Note

Usually empty, unless some further clarification of the type attribute is needed, in which case it may contain running prose.

The list presented here is primarily for illustrative purposes.

Example
<domain type="domestic"/> <domain type="rel">religious broadcast</domain>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element domain { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.52. <edition>

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

6.1.53. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
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
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
}

6.1.54. <editor>

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

A consistent format should be adopted.

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

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

6.1.55. <education>

<education> (education) contains a description of the educational experience of a person. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01"  to="1990-06-30">Attended <name>Cherwell School</name> </education>
Example
<education notBefore="1685-07"  notAfter="1690-06">Anthony Hammond smuggled her into the University of Cambridge, where she was disguised as his male cousin, Jack. She remained there for some months learning grammar, logic, rhetoric, and ethics</education>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element education
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.56. <ellipsis>

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

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

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

6.1.57. <email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

6.1.58. <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
Attributes
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
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.written.attributes,
   tei_macro.paraContent
}

6.1.59. <encodingDesc>

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

6.1.60. <event>

<event> (event) contains data relating to anything of significance that happens in time. [14.3.1. Basic Principles]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <event when="1618-05-23"   xml:id="SecondDefPraguewhere="#Prague">   <eventName>1618 Defenestration of Prague</eventName>   <idno>https://www.wikidata.org/wiki/Q13365740</idno>   <listPerson type="defenstrated">    <person>     <persName>Jaroslav Bořita z Martinic</persName>     <idno type="GND">https://d-nb.info/gnd/116810998</idno>    </person>    <person>     <persName>Vilém Slavata z Chlumu a Košumberka</persName>     <idno type="GND">https://d-nb.info/gnd/1018376615</idno>    </person>    <person>     <persName>Filip Fabricius</persName>     <idno type="GND">https://d-nb.info/gnd/133946118</idno>    </person>   </listPerson>   <place xml:id="Prague">    <placeName>Prague</placeName>   </place>  </event>  <event from="1618to="1648"   xml:id="ThirtyYearsWar">   <eventName>Thirty Years’ War</eventName>   <idno>https://www.wikidata.org/wiki/Q2487</idno>   <event when="1643-03-19"    xml:id="BattleofRocroiwhere="#Rocroi">    <eventName>Battle of Rocroi</eventName>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>    <idno type="GND">https://d-nb.info/gnd/4202901-6</idno>    <place xml:id="Rocroi">     <placeName>Rocroi</placeName>     <location>      <geo decls="#WGS">49.926111 4.522222</geo>     </location>    </place>   </event>  </event> </listEvent>
Example
<person>  <event type="matwhen="1972-10-12">   <label>matriculation</label>  </event>  <event type="gradwhen="1975-06-23">   <label>graduation</label>  </event> </person>
Content model
<content>
 <sequence>
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <elementRef key="eventName"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="idno"/>
  </alternate>
  <classRef key="model.eventLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPerson"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPlace"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <classRef key="model.objectLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element event
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.locatable.attributes,
   tei_att.naming.attributes,
   (
      idno*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ | eventName+ ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_model.ptrLike
       | linkGrp
       | link
       | idno
      )*,
      tei_model.eventLike*,
      ( tei_model.personLike | tei_listPerson )*,
      ( tei_model.placeLike | tei_listPlace )*,
      tei_model.objectLike*,
      ( relation | listRelation )*
   )
}

6.1.61. <expan>

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

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

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

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

6.1.62. <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader
Attributes
Contained by
core: monogr
header: fileDesc
May contain
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
ExampleThe <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.
<extent>  <measure 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 { tei_att.global.attributes, tei_macro.phraseSeq }

6.1.63. <factuality>

<factuality> (factuality) describes the extent to which the text may be regarded as imaginative or non-imaginative, that is, as describing a fictional or a non-fictional world. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: textDesc
May contain
Note

Usually empty, unless some further clarification of the type attribute is needed, in which case it may contain running prose

For many literary texts, a simple binary opposition between ‘fiction’ and ‘fact’ is naïve in the extreme; this parameter is not intended for purposes of subtle literary analysis, but as a simple means of characterizing the claimed fictiveness of a given text. No claim is made that works characterized as ‘fact’ are in any sense ‘true’.

Example
<factuality type="fiction"/>
Example
<factuality type="mixed">contains a mixture of gossip and speculation about real people and events</factuality>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element factuality { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.64. <faith>

<faith> (faith) specifies the faith, religion, or belief set of a person. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element faith
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq
}

6.1.65. <featureValueObservation>

<featureValueObservation> (feature value observation) contains data gathered by a source about the realisation of a fiven feature
Namespacehttps://wibarab.acdh.oeaw.ac.at/langDesc
Modulederived-module-featuredb
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Member of
Contained by
header: change licence
namesdates: occupation
textstructure: body div
May contain
dictionaries: lang
namesdates: personGrp placeName
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="wib"  uri="https://wibarab.acdh.oeaw.ac.at/langDesc"/> <sch:rule context="wib:featureValueObservation"> <sch:assert test="count(tei:personGrp[@role='tribe']) <= 1"> There should only be one personGrp element with @role="tribe" per featureValueObservation. </sch:assert> </sch:rule>
Content model
<content autoPrefix="true">
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="name" maxOccurs="1"
   minOccurs="1"/>
  <elementRef key="bibl" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="placeName"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="lang" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="1"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="personGrp"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="cit" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="note" minOccurs="1"
    maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element featureValueObservation
{
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_att.docStatus.attributes,
   attribute xml:id { text },
   (
      tei_name,
      tei_bibl,
      tei_placeName+,
      tei_lang,
      tei_date?,
      ( tei_personGrp | tei_cit | tei_note )*
   )
}

6.1.66. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
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" maxOccurs="unbounded"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   tei_att.global.attributes,
   (
      (
         tei_titleStmt,
         tei_editionStmt?,
         tei_extent?,
         tei_publicationStmt,
         tei_seriesStmt*,
         tei_notesStmt?
      ),
      tei_sourceDesc+
   )
}

6.1.67. <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

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

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

6.1.68. <forename>

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

6.1.69. <front>

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

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

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

6.1.70. <funder>

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

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

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

6.1.71. <gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
reason(reason) gives the reason for omission.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
cancelled
(cancelled)
deleted
(deleted)
editorial
(editorial) for features omitted from transcription due to editorial policy
illegible
(illegible)
inaudible
(inaudible)
irrelevant
(irrelevant)
sampling
(sampling)
agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
(rubbing) damage results from rubbing of the leaf edges
mildew
(mildew) damage results from mildew on the leaf surface
smoke
(smoke) damage results from smoke
Member of
Contained by
May contain
core: desc
Note

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

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

Example
<gap quantity="4unit="chars"  reason="illegible"/>
Example
<gap quantity="1unit="essay"  reason="sampling"/>
Example
<del>  <gap atLeast="4atMost="8unit="chars"   reason="illegible"/> </del>
Example
<gap extent="several linesreason="lost"/>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element gap
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.timed.attributes,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
         )+
      }
   }?,
   attribute agent { text }?,
   ( tei_model.descLike | tei_model.certLike )*
}

6.1.72. <gb>

<gb> (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <gb> elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.

The type attribute may be used to further characterize the gathering in any respect.

Example
<gb n="iii"/> <pb n="2r"/> <!-- material from page 2 recto of gathering iii here --> <pb n="2v"/> <!-- material from page 2 verso of gathering iii here -->
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element gb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   empty
}

6.1.73. <genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Charles</forename>  <genName>II</genName> </persName>
Example
<persName>  <surname>Pitt</surname>  <genName>the Younger</genName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element genName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.personal.attributes,
   tei_macro.phraseSeq
}

6.1.74. <geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [14.3.4.1. Varieties of Location]
Modulenamesdates
Attributes
Member of
Contained by
May containCharacter data only
Note

Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Example
<geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl> <!-- ... --> <location>  <desc>A tombstone plus six lines of    Anglo-Saxon text, built into the west tower (on the south side    of the archway, at 8 ft. above the ground) of the    Church of St. Mary-le-Wigford in Lincoln.</desc>  <geo decls="#WGS">53.226658 -0.541254</geo>  <geo decls="#OS">SK 97481 70947</geo> </location>
Example
<geo>41.687142 -74.870109</geo>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element geo
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   text
}

6.1.75. <geoDecl>

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

6.1.76. <geogFeat>

<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<geogName>The <geogFeat>vale</geogFeat> of White Horse</geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geogFeat
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.77. <geogName>

<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<geogName>  <geogFeat>Mount</geogFeat>  <name>Sinai</name> </geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geogName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.78. <gloss>

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Modulecore
Attributes
Member of
Contained by
May contain
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
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.pointing.attributes,
   tei_macro.phraseSeq
}

6.1.79. <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
Note

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

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

Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<facsimile>  <surfaceGrp n="leaf1">   <surface>    <graphic url="page1.png"/>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>   </surface>  </surfaceGrp> </facsimile>
Example
<facsimile>  <surfaceGrp n="leaf1xml:id="spi001">   <surface xml:id="spi001r">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001r.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001r.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001v.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001v.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic type="normal"      subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>     <graphic type="normal"      subtype="low-res"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic type="normal"      subtype="high-res"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="low-res"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="high-res"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element graphic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.media.attributes,
   tei_att.resourced.attributes,
   tei_model.descLike*
}

6.1.80. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
ExampleThe <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

6.1.81. <headItem>

<headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headItem> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headItem { tei_att.global.attributes, tei_macro.phraseSeq }

6.1.82. <headLabel>

<headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headLabel> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headLabel { tei_att.global.attributes, tei_macro.phraseSeq }

6.1.83. <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.written.attributes,
   tei_macro.paraContent
}

6.1.84. <hyphenation>

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

6.1.85. <imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: monogr
May contain
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <sequence>
  <alternate 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
{
   tei_att.global.attributes,
   (
      ( tei_classCode | tei_catRef )*,
      (
         (
            ( tei_model.imprintPart | tei_model.dateLike ),
            tei_respStmt*,
            tei_model.global*
         )+
      )
   )
}

6.1.86. <index>

<index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
Modulecore
Attributes
indexNamea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), supplying a name to specify which index (of several) the index entry belongs to.
StatusOptional
Datatypeteidata.name
Note

This attribute makes it possible to create multiple indexes for a text.

Member of
Contained by
May contain
core: index term
Example
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term>Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES">  <term>Sura</term> </index> was David's own first cousin.
Content model
<content>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="term"/>
  <elementRef key="index" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element index
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.spanning.attributes,
   attribute indexName { text }?,
   ( ( tei_term, tei_index? )* )
}

6.1.87. <interaction>

<interaction> (interaction) describes the extent, cardinality and nature of any interaction among those producing and experiencing the text, for example in the form of response or interjection, commentary, etc. [16.2.1. The Text Description]
Modulecorpus
Attributes
activespecifies the number of active participants (or addressors) producing parts of the text.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
singular
a single addressor
plural
many addressors
corporate
a corporate addressor
unknown
number of addressors unknown or unspecifiable
passivespecifies the number of passive participants (or addressees) to whom a text is directed or in whose presence it is created or performed.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
self
text is addressed to the originator e.g. a diary
single
text is addressed to one other person e.g. a personal letter
many
text is addressed to a countable number of others e.g. a conversation in which all participants are identified
group
text is addressed to an undefined but fixed number of participants e.g. a lecture
world
text is addressed to an undefined and indeterminately large number e.g. a published book
Member of
Contained by
corpus: textDesc
May contain
Example
<interaction type="complete"  active="pluralpassive="many"/>
Example
<interaction type="noneactive="singular"  passive="group"/>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element interaction
{
   tei_att.global.attributes,
   attribute active { "singular" | "plural" | "corporate" | "unknown" }?,
   attribute passive { "self" | "single" | "many" | "group" | "world" }?,
   tei_macro.phraseSeq.limited
}

6.1.88. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

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

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:rule context="tei:item[parent::tei:list/@type = 'featureValues']"> <sch:report test="not(exists(@xml:id[.!='']))"> missing or empty xml:id on featureValue item </sch:report> <sch:report test="not(exists(tei:label[. != '']))"> missing label or empty xml:id on featureValue item </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item { tei_att.global.attributes, tei_macro.specialPara }

6.1.89. <keywords>

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

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

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

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

6.1.90. <l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]
Modulecore
Attributes
Member of
Contained by
dictionaries: lang
header: change licence
linking: seg
namesdates: occupation
textstructure: body div
May contain
Example
<l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron
<sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule>
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"/>
 </alternate>
</content>
    
Schema Declaration
element l
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.fragmentable.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

6.1.91. <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runon numbered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
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
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_macro.phraseSeq
}

6.1.92. <lang>

<lang> (language name) contains the name of a language mentioned in etymological or other linguistic discussion. [10.3.4. Etymological Information]
Moduledictionaries
Attributes
Member of
Contained by
May contain
Note

May contain character data mixed with phrase-level elements.

Example
<entry>  <form>   <orth>publish</orth> ... </form>  <etym>   <lang>ME.</lang>   <mentioned>publisshen</mentioned>,  <lang>F.</lang>   <mentioned>publier</mentioned>, <lang>L.</lang>   <mentioned>publicare,      publicatum</mentioned>. <xr>See <ref>public</ref>; cf. <ref>2d -ish</ref>.</xr>  </etym> </entry>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element lang
{
   tei_att.global.attributes,
   tei_att.lexicographic.attributes,
   tei_macro.paraContent
}

6.1.93. <langKnowledge>

<langKnowledge> (language knowledge) summarizes the state of a person's linguistic knowledge, either as prose or by a list of <langKnown> elements. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
tagssupplies one or more valid language tags for the languages specified.
StatusOptional
Datatype1–∞ occurrences of teidata.language separated by whitespace
Note

This attribute should be supplied only if the element contains no <langKnown> children. Its values are language ‘tags’ as defined in RFC 4646 or its successor

Member of
Contained by
namesdates: person personGrp
May contain
core: p
namesdates: langKnown
Example
<langKnowledge tags="en-GB fr">  <p>British English and French</p> </langKnowledge>
Example
<langKnowledge>  <langKnown tag="en-GBlevel="H">British English</langKnown>  <langKnown tag="frlevel="M">French</langKnown> </langKnowledge>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"/>
   <elementRef key="langKnown"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element langKnowledge
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute tags { list { + } }?,
   ( precision*, ( tei_model.pLike | tei_langKnown+ ) )
}

6.1.94. <langKnown>

<langKnown> (language known) summarizes the state of a person's linguistic competence, i.e., knowledge of a single language. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
tagsupplies a valid language tag for the language concerned.
StatusRequired
Datatypeteidata.language
Note

The value for this attribute should be a language ‘tag’ as defined in BCP 47.

levela code indicating the person's level of knowledge for this language.
StatusOptional
Datatypeteidata.word
Contained by
namesdates: langKnowledge
May contain
Example
<langKnown tag="en-GBlevel="H">British English</langKnown> <langKnown tag="frlevel="M">French</langKnown>
Example
<person sex="mrole="speaker collaborator"> <!-- other details omitted -->  <langKnowledge>   <langKnown tag="mix">Mixtepec-Mixtec</langKnown>   <langKnown tag="en">English</langKnown>   <langKnown tag="es">Spanish</langKnown>  </langKnowledge> </person>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element langKnown
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute tag { text },
   attribute level { text }?,
   tei_macro.phraseSeq.limited
}

6.1.95. <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Contained by
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:langUsage"/> </sch:pattern>
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
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | tei_language+ )
}

6.1.96. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Namespacehttp://www.tei-c.org/ns/1.0
Moduleheader
Attributes
ana
StatusOptional
Legal values are:
#bedouin
#sedentary
#mixed
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

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

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   tei_att.global.attributes,
   tei_att.scope.attributes,
   attribute [http://www.tei-c.org/ns/1.0]ana
   {
      "#bedouin" | "#sedentary" | "#mixed"
   }?,
   attribute ident { text },
   attribute usage { text }?,
   tei_macro.phraseSeq.limited
}

6.1.97. <lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.6. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <lb> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking the beginning of each new topographic line on a manuscript or printed page, at the point where it occurs; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.

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

ExampleThis example shows the encoding of the beginning of each new topographic line within a metrical line, indicating where it occurs in both the 1667 and 1674 editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
ExampleThis example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   empty
}

6.1.98. <lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]
Modulecore
Attributes
Member of
Contained by
dictionaries: lang
header: change licence
linking: seg
namesdates: occupation
textstructure: body div
May contain
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

Example
<lg type="free">  <l>Let me be my own fool</l>  <l>of my own making, the sum of it</l> </lg> <lg type="free">  <l>is equivocal.</l>  <l>One says of the drunken farmer:</l> </lg> <lg type="free">  <l>leave him lay off it. And this is</l>  <l>the explanation.</l> </lg>
Schematron
<sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.divLike.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_lg
      ),
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_model.global
       | tei_lg
      )*,
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

6.1.99. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
header: availability
May contain
Note

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

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence 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
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.pointing.attributes,
   tei_macro.specialPara
}

6.1.100. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
type
StatusRecommended
Legal values are:
featureValues
Feature Values
Member of
Contained by
May contain
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list 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 minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <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
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type { "featureValues" }?,
   (
      ( tei_model.divTop | tei_model.global | tei_desc* )*,
      (
         ( ( tei_item, tei_model.global* )+ )
       | (
            tei_headLabel?,
            tei_headItem?,
            ( ( tei_label, tei_model.global*, tei_item, tei_model.global* )+ )
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

6.1.101. <listBibl>

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

6.1.102. <listChange>

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

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

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

6.1.103. <listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [14.3.1. Basic Principles]
Modulenamesdates
Attributes
Member of
Contained by
May contain
core: desc head
namesdates: event listEvent
Example
<listEvent>  <head>Battles of the American Civil War: Kentucky</head>  <event xml:id="event01when="1861-09-19">   <label>Barbourville</label>   <desc>The Battle of Barbourville was one of the early engagements of      the American Civil War. It occurred September 19, 1861, in Knox      County, Kentucky during the campaign known as the Kentucky Confederate      Offensive. The battle is considered the first Confederate victory in      the commonwealth, and threw a scare into Federal commanders, who      rushed troops to central Kentucky in an effort to repel the invasion,      which was finally thwarted at the <ref target="#event02">Battle of        Camp Wildcat</ref> in October.</desc>  </event>  <event xml:id="event02when="1861-10-21">   <label>Camp Wild Cat</label>   <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp      Wild Cat) was one of the early engagements of the American Civil      War. It occurred October 21, 1861, in northern Laurel County, Kentucky      during the campaign known as the Kentucky Confederate Offensive. The      battle is considered one of the very first Union victories, and marked      the first engagement of troops in the commonwealth of Kentucky.</desc>  </event>  <event xml:id="event03from="1864-06-11"   to="1864-06-12">   <label>Cynthiana</label>   <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement      during the American Civil War that was fought on June 11 and 12, 1864,      in Harrison County, Kentucky, near the town of Cynthiana. A part of      Confederate Brigadier General John Hunt Morgan's 1864 Raid into      Kentucky, the battle resulted in a victory by Union forces over the      raiders and saved the town from capture.</desc>  </event> </listEvent>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:listEvent"/> </sch:pattern>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.eventLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listEvent
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( relation | listRelation )*,
      ( ( tei_model.eventLike+, ( relation | listRelation )* )+ )
   )
}

6.1.104. <listOrg>

<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
core: desc head
namesdates: listOrg org
Note

The type attribute may be used to distinguish lists of organizations of a particular type if convenient.

Example
<listOrg>  <head>Libyans</head>  <org>   <orgName>Adyrmachidae</orgName>   <desc>These people have, in most points, the same customs as the Egyptians, but      use the costume of the Libyans. Their women wear on each leg a ring made of      bronze [...]</desc>  </org>  <org>   <orgName>Nasamonians</orgName>   <desc>In summer they leave their flocks and herds upon the sea-shore, and go up      the country to a place called Augila, where they gather the dates from the      palms [...]</desc>  </org>  <org>   <orgName>Garamantians</orgName>   <desc>[...] avoid all society or intercourse with their fellow-men, have no      weapon of war, and do not know how to defend themselves. [...]</desc> <!-- ... -->  </org> </listOrg>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:listOrg"/> </sch:pattern>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="org" minOccurs="1"
     maxOccurs="1"/>
    <elementRef key="listOrg" minOccurs="1"
     maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listOrg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( relation | listRelation )*,
      ( ( ( tei_org | tei_listOrg )+, ( relation | listRelation )* )+ )
   )
}

6.1.105. <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of people of a particular type if convenient.

Example
<listPerson type="respondents">  <personGrp xml:id="PXXX"/>  <person xml:id="P1234sex="2age="mid"/>  <person xml:id="P4332sex="1age="mid"/>  <listRelation>   <relation type="personalname="spouse"    mutual="#P1234 #P4332"/>  </listRelation> </listPerson>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:listPerson"/> </sch:pattern>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.personLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPerson"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPerson
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( relation | listRelation )*,
      (
         (
            ( tei_model.personLike | tei_listPerson )+,
            ( relation | listRelation )*
         )+
      )
   )
}

6.1.106. <listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
May contain
core: desc head
namesdates: listPlace place
Example
<listPlace type="offshoreIslands">  <place>   <placeName>La roche qui pleure</placeName>  </place>  <place>   <placeName>Ile aux cerfs</placeName>  </place> </listPlace>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:listPlace"/> </sch:pattern>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.placeLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPlace"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPlace
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( relation | listRelation )*,
      (
         (
            ( tei_model.placeLike | tei_listPlace )+,
            ( relation | listRelation )*
         )+
      )
   )
}

6.1.107. <listPrefixDef>

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

6.1.108. <locale>

<locale> contains a brief informal description of the kind of place concerned, for example: a room, a restaurant, a park bench, etc. [16.2.3. The Setting Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: setting
May contain
Example
<locale>a fashionable restaurant</locale>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element locale { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.109. <location>

<location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<place>  <placeName>Abbey Dore</placeName>  <location>   <geo>51.969604 -2.893146</geo>  </location> </place>
Example
<place xml:id="BGbuildingtype="building">  <placeName>Brasserie Georges</placeName>  <location>   <country key="FR"/>   <settlement type="city">Lyon</settlement>   <district type="arrondissement">IIème</district>   <district type="quartier">Perrache</district>   <placeName type="street">    <num>30</num>, Cours de Verdun</placeName>  </location> </place>
Example
<place type="imaginary">  <placeName>Atlantis</placeName>  <location>   <offset>beyond</offset>   <placeName>The Pillars of <persName>Hercules</persName>   </placeName>  </location> </place>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="precision"/>
  <classRef key="model.labelLike"/>
  <classRef key="model.placeNamePart"/>
  <classRef key="model.offsetLike"/>
  <classRef key="model.measureLike"/>
  <classRef key="model.addressLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.biblLike"/>
 </alternate>
</content>
    
Schema Declaration
element location
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   (
      precision
    | tei_model.labelLike
    | tei_model.placeNamePart
    | tei_model.offsetLike
    | tei_model.measureLike
    | tei_model.addressLike
    | tei_model.noteLike
    | tei_model.biblLike
   )*
}

6.1.110. <measure>

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleThis example references a definition of a measurement unit declared in the TEI header:
<measure type="weight">  <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="merktype="area">    <label>merk</label>    <placeName ref="#Scotland"/>    <desc>A merk was an area of land determined variably by its agricultural        productivity.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure quantity="40unit="hogshead"  commodity="rum">2 score hh rum</measure> <measure quantity="12unit="count"  commodity="roses">1 doz. roses</measure> <measure quantity="1unit="count"  commodity="tulips">a yellow tulip</measure>
Example
<head>Long papers.</head> <p>Speakers will be given 30 minutes each: 20 minutes for presentation, 10 minutes for discussion. Proposals should not exceed <measure max="500unit="count"   commodity="words">500    words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element measure
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.measurement.attributes,
   tei_macro.phraseSeq
}

6.1.111. <measureGrp>

<measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [11.3.4. Dimensions]
Modulecore
Attributes
Member of
Contained by
May contain
namesdates: geo
character data
Example
<measureGrp type="leavesunit="mm">  <height scope="range">157-160</height>  <width quantity="105"/> </measureGrp> <measureGrp type="ruledAreaunit="mm">  <height scope="mostquantity="90"/>  <width scope="mostquantity="48"/> </measureGrp> <measureGrp type="boxunit="in">  <height quantity="12"/>  <width quantity="10"/>  <depth quantity="6"/> </measureGrp>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.measureLike"/>
 </alternate>
</content>
    
Schema Declaration
element measureGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.measurement.attributes,
   ( text | tei_model.gLike | tei_model.measureLike )*
}

6.1.112. <media>

<media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
Modulecore
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
Derived fromatt.internetMedia
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
core: desc
Note

The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

Example
<figure>  <media mimeType="image/pngurl="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<media mimeType="audio/wav"  url="dingDong.wavdur="PT10S">  <desc>Ten seconds of bellringing sound</desc> </media>
Example
<media mimeType="video/mp4"  url="clip45.mp4dur="PT45Mwidth="500px">  <desc>A 45 minute video clip to be displayed in a window 500    px wide</desc> </media>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element media
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.media.attribute.width,
   tei_att.media.attribute.height,
   tei_att.media.attribute.scale,
   tei_att.resourced.attributes,
   tei_att.timed.attributes,
   attribute mimeType { list { + } },
   tei_model.descLike*
}

6.1.113. <meeting>

<meeting> contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
Member of
Contained by
core: lg list monogr
textstructure: body div front
May contain
Example
<div>  <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,    June 1998.</meeting>  <list type="attendance">   <head>List of Participants</head>   <item>    <persName>...</persName>   </item>   <item>    <persName>...</persName>   </item> <!--...-->  </list>  <p>...</p> </div>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element meeting
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_macro.limitedContent
}

6.1.114. <mentioned>

<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mentioned
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

6.1.115. <milestone>

<milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

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

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

Example
<milestone n="23ed="Launit="Dreissiger"/> ... <milestone n="24ed="AVunit="verse"/> ...
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element milestone
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.milestoneUnit.attributes,
   tei_att.spanning.attributes,
   empty
}

6.1.116. <monogr>

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

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope 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
{
   tei_att.global.attributes,
   (
      (
         (
            ( tei_author | tei_editor | tei_meeting | tei_respStmt ),
            ( tei_author | tei_editor | tei_meeting | tei_respStmt )*,
            tei_title+,
            (
               tei_model.ptrLike
             | idno
             | tei_textLang
             | tei_editor
             | tei_respStmt
            )*
         )
       | (
            ( tei_title | tei_model.ptrLike | idno )+,
            (
               tei_textLang
             | tei_author
             | tei_editor
             | tei_meeting
             | tei_respStmt
            )*
         )
       | ( authority, idno )
      )?,
      tei_availability*,
      tei_model.noteLike*,
      (
         (
            tei_edition,
            (
               idno
             | tei_model.ptrLike
             | tei_editor
             | tei_sponsor
             | tei_funder
             | tei_respStmt
            )*
         )*
      ),
      tei_imprint,
      ( tei_imprint | tei_extent | tei_biblScope )*
   )
}

6.1.117. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
type
StatusRecommended
Legal values are:
variety
tribe
person
feature
featureValue
Member of
Contained by
May contain
Note

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

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="fn"  uri="http://www.w3.org/2005/xpath-function"/> <sch:ns prefix="wib"  uri="https://wibarab.acdh.oeaw.ac.at/langDesc"/> <sch:rule context="tei:name[@type = 'featureValue']/@ref"> <sch:extends rule="reference"/> </sch:rule> <sch:rule context="tei:placeName/@ref"> <sch:extends rule="reference"/> </sch:rule> <sch:rule context="tei:bibl/@corresp[not(.='zot:')]"> <sch:extends rule="reference"/> </sch:rule> <sch:rule context="tei:lang/@corresp"> <sch:extends rule="reference"/> </sch:rule> <sch:rule context="wib:featureValueObservation/@resp"> <sch:extends rule="reference"/> </sch:rule> <sch:rule context="tei:personGrp/@corresp"> <sch:extends rule="reference"/> </sch:rule> <sch:rule id="reference" abstract="true"> <sch:let name="idRef" value="."/> <sch:let name="localID"  value="if (matches($idRef,'^#')) then substring-after($idRef,'#') else ()"/> <sch:let name="prefixDefs"  value="root()//tei:prefixDef"/> <sch:let name="prefixRegex"  value="concat('^(',string-join($prefixDefs/@ident,'|'),'):(.+)$')"/> <sch:let name="prefixMatch"  value="if (exists($prefixDefs)) then analyze-string($idRef, $prefixRegex)//*:group[1] else ()"/> <sch:let name="referenceMatch"  value="if (exists($prefixDefs)) then analyze-string($idRef, $prefixRegex)//*:group[2] else ()"/> <sch:let name="prefixDef"  value="if (exists($prefixMatch)) then $prefixDefs[@ident = $prefixMatch] else ()"/> <sch:let name="prefixGroups"  value="if (exists($prefixMatch)) then analyze-string($referenceMatch, $prefixDef/@matchPattern)//*:group else ()"/> <sch:let name="grpr1"  value="if (exists($prefixGroups[@nr = '1'])) then replace($prefixDef/@replacementPattern,'\$1', $prefixGroups[@nr = '1']) else $prefixDef/@replacementPattern"/> <sch:let name="grpr2"  value="if (exists($prefixGroups[@nr = '2'])) then replace($grpr1,'\$2', $prefixGroups[@nr = '2']) else $grpr1"/> <sch:let name="grpr3"  value="if (exists($prefixGroups[@nr = '3'])) then replace($grpr2,'\$3', $prefixGroups[@nr = '3']) else $grpr2"/> <sch:let name="grpr4"  value="if (exists($prefixGroups[@nr = '4'])) then replace($grpr3,'\$4', $prefixGroups[@nr = '4']) else $grpr3"/> <sch:let name="grpr5"  value="if (exists($prefixGroups[@nr = '5'])) then replace($grpr4,'\$5', $prefixGroups[@nr = '5']) else $grpr4"/> <sch:let name="grpr6"  value="if (exists($prefixGroups[@nr = '6'])) then replace($grpr5,'\$6', $prefixGroups[@nr = '6']) else $grpr5"/> <sch:let name="grpr7"  value="if (exists($prefixGroups[@nr = '7'])) then replace($grpr6,'\$7', $prefixGroups[@nr = '7']) else $grpr6"/> <sch:let name="grpr8"  value="if (exists($prefixGroups[@nr = '8'])) then replace($grpr7,'\$8', $prefixGroups[@nr = '8']) else $grpr7"/> <sch:let name="grpr9"  value="if (exists($prefixGroups[@nr = '9'])) then replace($grpr8,'\$9', $prefixGroups[@nr = '9']) else $grpr8"/> <sch:let name="grpr10"  value="if (exists($prefixGroups[@nr = '10'])) then replace($grpr9,'\$10', $prefixGroups[@nr = '10']) else $grpr9"/> <sch:let name="targetRaw"  value="if ($localID != '') then $idRef else if (exists($prefixDef)) then $grpr10 else $idRef"/> <sch:let name="target"  value="translate($targetRaw,'\','/')"/> <sch:let name="targetResolves"  value="if ($localID != '' ) then exists(root()//*[@xml:id = $localID]) else if (matches($idRef,'^(http|https)')) then true() else doc-available(resolve-uri($target, base-uri($idRef)))"/> <sch:report test="$target = ''">unexpected target "<sch:value-of select="$idRef"/>" in reference <sch:value-of select="local-name($idRef)"/> </sch:report> <sch:assert test="$targetResolves">the target "<sch:value-of select="$target"/>" of pointer "<sch:value-of select="$idRef"/> " cannot be resolved </sch:assert> <sch:report test="count(tokenize($idRef,' ')) gt 1"> pointer " <sch:value-of select="$idRef"/> " contains more than one references (whitespace) </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.personal.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "variety" | "tribe" | "person" | "feature" | "featureValue"
   }?,
   tei_macro.phraseSeq
}

6.1.118. <namespace>

<namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
namespecifies the full formal name of the namespace concerned.
StatusRequired
Datatype0–1 occurrences of teidata.namespace separated by whitespace
Contained by
May containEmpty element
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" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element namespace
{
   tei_att.global.attributes,
   attribute name { ? },
   tagUsage+
}

6.1.119. <nationality>

<nationality> (nationality) contains an informal description of a person's present or past nationality or citizenship. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<nationality key="USnotBefore="1966"> Obtained US Citizenship in 1966</nationality>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element nationality
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.120. <normalization>

<normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:normalization"/> </sch:pattern>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element normalization
{
   tei_att.global.attributes,
   attribute method { "silent" | "markup" }?,
   tei_model.pLike+
}

6.1.121. <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
sourcesource on <cit type="example"> documents the source an example is taken from. In case the value of it points to a <person> element, that means that the example is provided by an informant. When it's absent, the example is drawn from source indicated by the <bibl> element in the parent <featureValueObservation>.
StatusOptional
Datatypeteidata.pointer
type
StatusOptional
Legal values are:
constraintNote
exceptionNote
general
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
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.anchoring.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.written.attributes,
   attribute [http://www.tei-c.org/ns/1.0]source { text }?,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "constraintNote" | "exceptionNote" | "general"
   }?,
   tei_macro.specialPara
}

6.1.122. <noteGrp>

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

6.1.123. <notesStmt>

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

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

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

6.1.124. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore
Attributes
valuesupplies the value of the number in standard form.
StatusOptional
Datatypeteidata.numeric
Valuesa numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
Contained by
May contain
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The <num> element is intended for use in simple applications.

Example
<p>I reached <num type="cardinalvalue="21">twenty-one</num> on my <num type="ordinalvalue="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>  </num> cm per second.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element num
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute value { text }?,
   tei_macro.phraseSeq
}

6.1.125. <occupation>

<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
StatusOptional
Datatypeteidata.pointer
codeidentifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
namesdates: person personGrp
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomy"  code="#acc">accountant</occupation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element occupation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   attribute scheme { text }?,
   attribute code { text }?,
   tei_macro.specialPara
}

6.1.126. <org>

<org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [14.3.3. Organizational Data]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the organization.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, familyGroup, or politicalParty, each of which should be associated with a definition. Such local definitions will typically be provided by a <desc> for each <valItem> element in the schema specification of the project's customization.

Member of
Contained by
May contain
Example
<org xml:id="JAMs">  <orgName>Justified Ancients of Mummu</orgName>  <desc>An underground anarchist collective spearheaded by  <persName>Hagbard Celine</persName>, who fight the Illuminati    from a golden submarine, the <name>Leif Ericson</name>  </desc>  <bibl>   <author>Robert Shea</author>   <author>Robert Anton Wilson</author>   <title>The Illuminatus! Trilogy</title>  </bibl> </org>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.nameLike"/>
    <classRef key="model.placeLike"/>
    <classRef key="model.orgPart"/>
    <classRef key="model.milestoneLike"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <classRef key="model.personLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element org
{
   tei_att.global.attributes,
   attribute role { list { + } }?,
   (
      tei_model.headLike*,
      (
         tei_model.pLike*
       | (
            tei_model.labelLike
          | tei_model.nameLike
          | tei_model.placeLike
          | tei_model.orgPart
          | tei_model.milestoneLike
         )*
      ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_model.ptrLike
       | linkGrp
       | link
      )*,
      tei_model.personLike*
   )
}

6.1.127. <orgName>

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

6.1.128. <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

6.1.129. <p>

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

6.1.130. <particDesc>

<particDesc> (participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata. [16.2. Contextual Information]
Modulecorpus
Attributes
Contained by
May contain
Note

May contain a prose description organized as paragraphs, or a structured list of persons and person groups, with an optional formal specification of any relationships amongst them.

Example
<particDesc>  <listPerson>   <person xml:id="P-1234sex="2age="mid">    <p>Female informant, well-educated, born in        Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently.        Socio-Economic status B2.</p>   </person>   <person xml:id="P-4332sex="1">    <persName>     <surname>Hancock</surname>     <forename>Antony</forename>     <forename>Aloysius</forename>     <forename>St John</forename>    </persName>    <residence notAfter="1959">     <address>      <street>Railway Cuttings</street>      <settlement>East Cheam</settlement>     </address>    </residence>    <occupation>comedian</occupation>   </person>   <listRelation>    <relation type="personalname="spouse"     mutual="#P-1234 #P-4332"/>   </listRelation>  </listPerson> </particDesc>
This example shows both a very simple person description, and a very detailed one, using some of the more specialized elements from the module for Names and Dates.
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:particDesc"/> </sch:pattern>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.personLike"/>
   <elementRef key="listPerson"/>
   <elementRef key="listOrg"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element particDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_model.personLike | tei_listPerson | tei_listOrg )+
   )
}

6.1.131. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

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

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

ExamplePage numbers may vary in different editions of a text.
<p> ... <pb n="145ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
ExampleA page beginning may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>  <pb n="1facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb n="2facs="page2.png"/> <!-- similarly, for page 2 -->  <p> <!-- ... -->  </p> </body>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element pb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   empty
}

6.1.132. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.personal.attributes,
   tei_macro.phraseSeq
}

6.1.133. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

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

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

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

genderspecifies the gender of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

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

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

Member of
Contained by
corpus: particDesc
namesdates: event listPerson org
May contain
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example
<person sex="Fage="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersexrole="god"  age="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01sex="Mrole="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
ExampleThe following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="arielgender="U">  <persName>Ariel</persName>  <note>Character in <title level="m">The Tempest</title>.</note> </person>
ExampleThis example demonstrates the use of a <ref> element to provide more information about a person. The private URI scheme lacy: is presumably declared in the <teiHeader> with a <prefixDef>.
<person age="G2role="author"  xml:id="W0212sex="F">  <birth when="1787"/>  <death when="1855"/>  <persName type="main">Mitford, Mary Russell (1787–1855)</persName>  <persName resp="#Nicoll">MITFORD, MARY RUSSELL</persName>  <listBibl type="lacyTitles">   <desc>Lacy's Acting Editions</desc>   <bibl>    <ref target="lacy:L1280">Foscari</ref>   </bibl>   <bibl>    <ref target="lacy:L1337">Rienzi</ref>   </bibl>  </listBibl>  <listRef type="seeAlso">   <ref target="https://www.victorianresearch.org/atcl/show_author.php?aid=1386">ATCL</ref>   <ref target="https://doi.org/10.1093/ref:odnb/18859">ODNB</ref>   <ref target="https://en.wikipedia.org/wiki/Mary_Russell_Mitford">Wikipedia</ref>   <ref target="https://digitalmitford.org">Digital Mitford</ref>  </listRef> </person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <classRef key="model.ptrLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element person
{
   tei_att.global.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   (
      tei_model.pLike+
    | ( tei_model.personPart | tei_model.global | tei_model.ptrLike )*
   )
}

6.1.134. <personGrp>

<personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [16.2.2. The Participant Description]
Namespacehttp://www.tei-c.org/ns/1.0
Modulenamesdates
Attributes
roledocuments speaker traits that are specified to be relevant sociolinguistically in the sources and therefore may be necessary for the correct and accurate interpretation of cerain featureValueObservations.
StatusRequired
Legal values are:
tribe
religion
ageGroup
gender
firstLanguage
socio
<name type="featureValue"  ref="#q_g_affr2"/> <personGrp role="tribe"  corresp="pgr:arab_maslax"/> <personGrp role="age"  corresp="pgr:old"/> <personGrp role="gender"  corresp="pgr:male"/>
For instance, in the example above the featureValue #q_g_affr2 has only been documented amongst old men that belong to the Arab Maslax tribe, which would exclude all the women of this tribe, as well as all the middle-age and young male speakers.
Note

The coexistence of several <personGrp> elements should be interpreted as a conjunction, i.e. combined by a logical "AND", this is, it should be interpreted as the combination of these two or more roles, and would therefore exclusive of all the other roles.

This attribute is (mis-)used as a ad-hoc short-cut for a more verbose markup construct using <trait> and <desc>.

In a final version, all <personGrp> elements within a <featureValueObservation> will be merged into one, with their content being transformed into <trait> elements.

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

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

genderspecifies the gender of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

agespecifies the age group of the participants.
StatusOptional
Datatypeteidata.enumerated
Note

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

sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
corpus: particDesc
derived-module-featuredb: featureValueObservation
namesdates: event listPerson org
May contain
Note

May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

Example
<personGrp xml:id="pg1role="audience"  sex="mixedsize="approx 50"/>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element personGrp
{
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]role
   {
      "tribe" | "religion" | "ageGroup" | "gender" | "firstLanguage" | "socio"
   },
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   attribute size { list { + } }?,
   ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
}

6.1.135. <place>

<place> (place) contains data about a geographic location. [14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
corpus: settingDesc
namesdates: event listPlace org place
May contain
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.placeStateLike"/>
    <classRef key="model.eventLike"/>
    <elementRef key="name"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="idno"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element place
{
   tei_att.global.attributes,
   (
      tei_model.headLike*,
      (
         tei_model.pLike*
       | (
            tei_model.labelLike
          | tei_model.placeStateLike
          | tei_model.eventLike
          | tei_name
         )*
      ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_model.ptrLike
       | idno
       | linkGrp
       | link
      )*,
      ( tei_model.placeLike | tei_listPlace )*
   )
}

6.1.136. <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.personal.attributes,
   tei_macro.phraseSeq
}

6.1.137. <population>

<population> (population) contains information about the population of a place. [14.3.4.3. States, Traits, and Events]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<population when="2001-04resp="#UKCensus">  <population type="white">   <desc>54153898</desc>  </population>  <population type="asian">   <desc>11811423</desc>  </population>  <population type="black">   <desc>1148738</desc>  </population>  <population type="mixed">   <desc>677117</desc>  </population>  <population type="chinese">   <desc>247403</desc>  </population>  <population type="other">   <desc>230615</desc>  </population> </population>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <alternate>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <classRef key="model.labelLike"
     minOccurs="1" maxOccurs="unbounded"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </sequence>
  <elementRef key="population"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element population
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   (
      precision*,
      tei_model.headLike*,
      (
         (
            ( tei_model.pLike+ | tei_model.labelLike+ ),
            ( tei_model.noteLike | tei_model.biblLike )*
         )?
      ),
      tei_population*
   )
}

6.1.138. <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.6.2. Addresses]
Modulecore
Attributes
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 { tei_att.global.attributes, text }

6.1.139. <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.6.2. Addresses]
Modulecore
Attributes
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 { tei_att.global.attributes, text }

6.1.140. <prefixDef>

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

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

Contained by
May contain
core: p
Note

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

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

6.1.141. <preparedness>

<preparedness> (preparedness) describes the extent to which a text may be regarded as prepared or spontaneous. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
corpus: textDesc
May contain
Example
<preparedness type="none"/>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element preparedness { tei_att.global.attributes, tei_macro.phraseSeq.limited }

6.1.142. <principal>

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

6.1.143. <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]
Namespacehttp://www.tei-c.org/ns/1.0
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
header: textClass
Note

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

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose 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 autoPrefix="true">
 <elementRef key="textClass" minOccurs="1"
  maxOccurs="1"/>
</content>
    
Schema Declaration
element profileDesc { tei_att.global.attributes, tei_textClass }

6.1.144. <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:projectDesc"/> </sch:pattern>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc { tei_att.global.attributes, tei_model.pLike+ }

6.1.145. <ptr>

<ptr> (pointer) pointer to one featureValue in the list of featureValues [3.7. Simple Links and Cross-References 17.1. Links]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

The target and cRef attributes are mutually exclusive.

Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   empty
}

6.1.146. <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.147. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
Content model
<content>
 <alternate>
  <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
{
   tei_att.global.attributes,
   (
      (
         (
            tei_model.publicationStmtPart.agency,
            tei_model.publicationStmtPart.detail*
         )+
      )
    | tei_model.pLike+
   )
}

6.1.148. <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element publisher
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq
}

6.1.149. <punctuation>

<punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
Moduleheader
Attributes
marksindicates whether or not punctation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no punctuation marks have been retained
some
some punctuation marks have been retained
all
all punctuation marks have been retained
placementindicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
internal
punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
external
punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:punctuation"/> </sch:pattern>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element punctuation
{
   tei_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   attribute placement { "internal" | "external" }?,
   tei_model.pLike*
}

6.1.150. <purpose>

<purpose> characterizes a single purpose or communicative function of the text. [16.2.1. The Text Description]
Modulecorpus
Attributes
degreespecifies the extent to which this purpose predominates.
StatusOptional
Datatypeteidata.certainty
Note

Values should be interpreted as follows.

high
this purpose is predominant
medium
this purpose is intermediate
low
this purpose is weak
unknown
extent unknown
Contained by
corpus: textDesc
May contain
Note

Usually empty, unless some further clarification of the type attribute is needed, in which case it may contain running prose

Example
<purpose type="persuadedegree="high"/> <purpose type="entertaindegree="low"/>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element purpose
{
   tei_att.global.attributes,
   attribute degree { text }?,
   tei_macro.phraseSeq.limited
}

6.1.151. <q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore
Attributes
type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
spoken
(spoken) representation of speech
thought
(thought) representation of thought, e.g. internal monologue
written
(written) quotation from a written source
soCalled
(so called) authorial distance
foreign
(foreign) foreign words
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(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
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   tei_macro.specialPara
}

6.1.152. <quotation>

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

6.1.153. <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_macro.specialPara
}

6.1.154. <rb>

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

6.1.155. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_macro.paraContent
}

6.1.156. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

6.1.157. <region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [14.2.3. Place Names]
Namespacehttp://www.tei-c.org/ns/1.0
Modulenamesdates
Attributes
ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Derived fromatt.canonical
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containCharacter data only
Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>
Content model
<content autoPrefix="true">
 <textNode/>
</content>
    
Schema Declaration
element region
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attribute.role,
   tei_att.naming.attribute.nymRef,
   attribute ref { list { + } },
   text
}

6.1.158. <relatedItem>

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Modulecore
Attributes
targetpoints to the related bibliographic element by means of an absolute or relative URI reference.
StatusOptional
Datatypeteidata.pointer
Contained by
header: notesStmt
May contain
Note

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

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

6.1.159. <residence>

<residence> (residence) describes a person's present or past places of residence. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: person personGrp
May contain
Example
<residence>Childhood in East Africa and long term resident of Glasgow, Scotland.</residence>
Example
<residence notAfter="1997">Mbeni estate, Dzukumura region, Matabele land</residence> <residence notBefore="1903notAfter="1996">  <placeName>   <settlement>Glasgow</settlement>   <region>Scotland</region>  </placeName> </residence>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element residence
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.160. <resp>

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

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

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

6.1.161. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Member of
Contained by
May contain
core: name note resp
namesdates: orgName 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>
  <alternate>
   <sequence>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   (
      (
         ( tei_resp+, tei_model.nameLike.agent+ )
       | ( tei_model.nameLike.agent+, tei_resp+ )
      ),
      tei_note*
   )
}

6.1.162. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
core: list
Note

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

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="listChange"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   tei_att.global.attributes,
   tei_att.docStatus.attributes,
   ( tei_list+ | tei_listChange+ | tei_change+ )
}

6.1.163. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

6.1.164. <rt>

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

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

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

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

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

6.1.165. <ruby>

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

6.1.166. <said>

<said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
Modulecore
Attributes
aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
StatusOptional
Datatypeteidata.xTruthValue
<p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;    I believe she would not accept him.</said> Celia felt that this was a pity. <!-- ... --> </p>
Note

The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
StatusOptional
Datatypeteidata.xTruthValue
Defaulttrue
<!-- in the header --><editorialDecl>  <quotation marks="none"/> </editorialDecl> <!-- ... --> <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>. The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>, but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said> </p>
Note

The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

Member of
Contained by
May contain
Example
<!-- in the header --><editorialDecl>  <quotation marks="all"/> </editorialDecl> <!-- ... --> <p>  <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and    gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill    his wine, and blunt his sword, and say his name begins with X, and in the end the Duke    will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O      rider of the sun!'</said>"</said> </p>
Example
<p>  <said aloud="truerend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear. <said aloud="truerend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see.    Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove    yourself, now that's interesting. … So where shall I put you?</said> </p> <p>Harry gripped the edges of the stool and thought, <said aloud="falserend="italic">Not    Slytherin, not Slytherin</said>.</p>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element said
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute aloud { text }?,
   attribute direct { text }?,
   tei_macro.specialPara
}

6.1.167. <samplingDecl>

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

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

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:samplingDecl"/> </sch:pattern>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl { tei_att.global.attributes, tei_model.pLike+ }

6.1.168. <seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.6. Speech Contents]
Namespacehttp://www.tei-c.org/ns/1.0
Modulelinking
Attributes
type
StatusOptional
Legal values are:
morph
Member of
Contained by
May contain
Note

The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

Example
<seg>When are you leaving?</seg> <seg>Tomorrow.</seg>
Example
<s>  <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield. </s>
Example
<seg type="preamble">  <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>  <seg>Sinfiotli was the eldest of his sons ...</seg>  <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element seg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.written.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type { "morph" }?,
   tei_macro.paraContent
}

6.1.169. <series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
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
{
   tei_att.global.attributes,
   (
      text
    | tei_model.gLike
    | tei_title
    | tei_model.ptrLike
    | tei_editor
    | tei_respStmt
    | tei_biblScope
    | idno
    | tei_textLang
    | tei_model.global
    | tei_availability
   )*
}

6.1.170. <seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:seriesStmt"/> </sch:pattern>
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
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_title+, ( tei_editor | tei_respStmt )*, ( idno | tei_biblScope )* )
   )
}

6.1.171. <setting>

<setting> describes one particular setting in which a language interaction takes place. [16.2.3. The Setting Description]
Modulecorpus
Attributes
Contained by
corpus: settingDesc
May contain
Note

If the who attribute is not supplied, the setting is assumed to be that of all participants in the language interaction.

Example
<setting>  <placeName>New York City, US</placeName>  <date>1989</date>  <locale>on a park bench</locale>  <activity>feeding birds</activity> </setting>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.nameLike.agent"/>
   <classRef key="model.dateLike"/>
   <classRef key="model.settingPart"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element setting
{
   tei_att.global.attributes,
   tei_att.ascribed.attributes,
   (
      tei_model.pLike+
    | ( tei_model.nameLike.agent | tei_model.dateLike | tei_model.settingPart )*
   )
}

6.1.172. <settingDesc>

<settingDesc> (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata. [16.2. Contextual Information 2.4. The Profile Description]
Modulecorpus
Attributes
Contained by
May contain
core: p
corpus: setting
namesdates: listPlace place
Note

May contain a prose description organized as paragraphs, or a series of <setting> elements. If used to record not settings of language interactions, but other places mentioned in the text, then <place> optionally grouped by <listPlace> inside <standOff> should be preferred.

Example
<settingDesc>  <p>Texts recorded in the    Canadian Parliament building in Ottawa, between April and November 1988 </p> </settingDesc>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:settingDesc"/> </sch:pattern>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="setting"/>
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element settingDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_setting | tei_model.placeLike | tei_listPlace )+
   )
}

6.1.173. <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [14.2.3. Place Names]
Namespacehttp://www.tei-c.org/ns/1.0
Modulenamesdates
Attributes
ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Derived fromatt.canonical
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attribute.role,
   tei_att.naming.attribute.nymRef,
   attribute ref { list { + } },
   tei_macro.phraseSeq
}

6.1.174. <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

6.1.175. <soCalled>

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call <soCalled>nuts</soCalled> to Scrooge.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element soCalled
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

6.1.176. <socecStatus>

<socecStatus> (socio-economic status) contains an informal description of a person's perceived social or economic status. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
schemeidentifies the classification system or taxonomy in use, for example by pointing to a locally-defined <taxonomy> element or by supplying a URI for an externally-defined system.
StatusOptional
Datatypeteidata.pointer
codeidentifies a status code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
namesdates: person personGrp
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<socecStatus scheme="#rgcode="#ab1"/>
Example
<socecStatus>Status AB1 in the RG Classification scheme</socecStatus>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element socecStatus
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   attribute scheme { text }?,
   attribute code { text }?,
   tei_macro.phraseSeq
}

6.1.177. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:sourceDesc"/> </sch:pattern>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
   )
}

6.1.178. <sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
Modulecore
Attributes
Member of
Contained by
header: change licence
namesdates: occupation
textstructure: body div
May contain
Note

The who attribute on this element may be used either in addition to the <speaker> element or as an alternative.

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

6.1.179. <speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
Modulecore
Attributes
Contained by
core: sp
May contain
Note

This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an <sp> element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used.

Example
<sp who="#ni #rsa">  <speaker>Nancy and Robert</speaker>  <stage type="delivery">(speaking simultaneously)</stage>  <p>The future? ...</p> </sp> <list type="speakers">  <item xml:id="ni"/>  <item xml:id="rsa"/> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element speaker
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_macro.phraseSeq
}

6.1.180. <sponsor>

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

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

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

6.1.181. <stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.5. Stage Directions]
Modulecore
Attributes
typeindicates the kind of stage direction.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
setting
describes a setting.
entrance
describes an entrance.
exit
describes an exit.
business
describes stage business.
novelistic
is a narrative, motivating stage direction.
delivery
describes how a character speaks.
modifier
gives some detail about a character.
location
describes a location.
mixed
more than one of the above
Note

If the value mixed is used, it must be the only value. Multiple values may however be supplied if a single stage direction performs multiple functions, for example is both an entrance and a modifier.

Member of
Contained by
dictionaries: lang
header: change licence
linking: seg
namesdates: occupation
textstructure: body div
May contain
Note

The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

Example
<stage type="setting">A curtain being drawn.</stage> <stage type="setting">Music</stage> <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage> <!-- Middleton : Yorkshire Tragedy --> <stage type="exit">Exit pursued by a bear.</stage> <stage type="business">He quickly takes the stone out.</stage> <stage type="delivery">To Lussurioso.</stage> <stage type="novelistic">Having had enough, and embarrassed for the family.</stage> <!-- Lorraine Hansbury : a raisin in in the sun --> <stage type="modifier">Disguised as Ansaldo.</stage> <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage> <!-- Middleton: The Widow --> <stage type="location">At a window.</stage> <stage rend="inlinetype="delivery">Aside.</stage>
Example
<l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when    straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on    two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the  <hi>Prologue</hi> was spoken, which being ended, they descended in    order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element stage
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   attribute type
   {
      list
      {
         (
            "setting"
          | "entrance"
          | "exit"
          | "business"
          | "novelistic"
          | "delivery"
          | "modifier"
          | "location"
          | "mixed"
         )+
      }
   }?,
   tei_macro.specialPara
}

6.1.182. <stdVals>

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

6.1.183. <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.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
core: address
May contain
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 { tei_att.global.attributes, tei_macro.phraseSeq }

6.1.184. <taxonomy>

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

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

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

6.1.185. <teiCorpus>

<teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more <TEI> elements, each containing a single text header and a text. [4. Default Text Structure 16.1. Varieties of Composite Text]
Modulecore
Attributes
version(version) specifies 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>.

Member of
Contained by
core: teiCorpus
May contain
core: teiCorpus
header: teiHeader
textstructure: TEI text
Note

Should contain one <teiHeader> for the corpus, and a series of <TEI> elements, one for each text.

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

Example
<teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- header for corpus -->  </teiHeader>  <TEI>   <teiHeader> <!-- header for first text -->   </teiHeader>   <text> <!-- content of first text -->   </text>  </TEI>  <TEI>   <teiHeader> <!-- header for second text -->   </teiHeader>   <text> <!-- content of second text -->   </text>  </TEI> <!-- more TEI elements here --> </teiCorpus>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.describedResource"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element teiCorpus
{
   tei_att.global.attributes,
   attribute version { text }?,
   ( tei_teiHeader, tei_model.resource*, tei_model.describedResource+ )
}

6.1.186. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Namespacehttp://www.tei-c.org/ns/1.0
Moduleheader
Attributes
Contained by
core: teiCorpus
textstructure: TEI
May contain
Note

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

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

6.1.187. <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term 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
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.declaring.attributes,
   tei_att.pointing.attributes,
   tei_macro.phraseSeq
}

6.1.188. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Member of
Contained by
core: teiCorpus
textstructure: TEI
May contain
Note

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

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

6.1.189. <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]
Namespacehttp://www.tei-c.org/ns/1.0
Moduleheader
Attributes
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>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:rule context="tei:catRef"> <sch:let name="target" value="@target"/> <sch:let name="prefix"  value="substring-before($target, ':')"/> <sch:let name="id"  value="substring-after($target, ':')"/> <sch:let name="prefixDef"  value="root()//tei:prefixDef[@ident = $prefix]"/> <sch:let name="replacementPattern"  value="$prefixDef/@replacementPattern"/> <sch:let name="resolvedTarget"  value="replace($replacementPattern, '\$1', $id)"/> <sch:let name="targetExists"  value="doc-available(resolve-uri($resolvedTarget, base-uri($target)))"/> <sch:assert test="$prefix = 'dmp'"> The prefix of the target " <sch:value-of select="$target"/>" should be "dmp"</sch:assert> <sch:assert test="$targetExists">The target "<sch:value-of select="$target"/>" of pointer "<sch:value-of select="$id"/> " cannot be resolved </sch:assert> </sch:rule>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:textClass"/> </sch:pattern>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   tei_att.global.attributes,
   ( tei_classCode | tei_catRef | tei_keywords )*
}

6.1.190. <textDesc>

<textDesc> (text description) provides a description of a text in terms of its situational parameters. [16.2.1. The Text Description]
Modulecorpus
Attributes
Member of
Contained by
header: catDesc
May contain
Example
<textDesc n="Informal domestic conversation">  <channel mode="s"/>  <constitution type="single"/>  <derivation type="original"/>  <domain type="domestic"/>  <factuality type="mixed"/>  <interaction type="complete"   active="pluralpassive="many"/>  <preparedness type="spontaneous"/>  <purpose type="entertaindegree="high"/>  <purpose type="informdegree="medium"/> </textDesc>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:textDesc"/> </sch:pattern>
Content model
<content>
 <sequence>
  <classRef key="model.textDescPart"
   expand="sequence"/>
  <elementRef key="purpose" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element textDesc
{
   tei_att.global.attributes,
   (
      tei_channel,
      tei_constitution,
      tei_derivation,
      tei_domain,
      tei_factuality,
      tei_interaction,
      tei_preparedness,
      tei_purpose+
   )
}

6.1.191. <textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems]
Modulecore
Attributes
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
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
Contained by
May contain
Note

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

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

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   tei_att.global.attributes,
   attribute mainLang { text }?,
   attribute otherLangs { list { * } }?,
   tei_macro.specialPara
}

6.1.192. <time>

<time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
Modulecore
Attributes
Member of
Contained by
May contain
Example
As he sat smiling, the quarter struck — <time when="11:45:00">the quarter to twelve</time>.
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 time
{
   tei_att.global.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

6.1.193. <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Namespacehttp://www.tei-c.org/ns/1.0
Modulecore
Attributes
type
StatusOptional
Legal values are:
main
sub
short
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
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
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.source.attribute.source,
   tei_att.cmc.attributes,
   tei_att.datable.attribute.period,
   attribute [http://www.tei-c.org/ns/1.0]type { "main" | "sub" | "short" }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   tei_macro.paraContent
}

6.1.194. <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
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
{
   tei_att.global.attributes,
   ( tei_title+, tei_model.respLike* )
}

6.1.195. <unclear>

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

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Note

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

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

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

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
         )+
      }
   }?,
   attribute agent { text }?,
   tei_macro.paraContent
}

6.1.196. <unit>

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

6.1.197. <unitDecl>

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

6.1.198. <unitDef>

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

6.2. Model classes

6.2.1. model.addrPart

6.2.2. model.addressLike

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

6.2.3. model.applicationLike

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

6.2.4. model.attributable

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

6.2.5. model.availabilityPart

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

6.2.6. model.biblLike

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

6.2.7. model.catDescPart

model.catDescPart groups component elements of the TEI header Category Description.
Moduletei
Used by
MemberstextDesc

6.2.8. model.choicePart

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

6.2.9. model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.cmc model.divPart[model.lLike[l] model.pLike[p] featureValueObservation lg sp] model.entryLike model.inter[model.attributable[model.quoteLike[cit quote] said] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike[desc label] model.listLike[list listEvent listOrg listPerson listPlace] model.oddDecl model.stageLike[stage]] q
Note

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

6.2.10. model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Moduletei
Used by
Membersmodel.addressLike[address affiliation email] model.dateLike[date time] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[forename genName] model.placeStateLike[model.placeNamePart[bloc district geogName placeName region settlement] location population] lang rs] note noteGrp

6.2.11. model.correspContextPart

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

6.2.12. model.correspDescPart

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

6.2.13. model.dateLike

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

6.2.14. model.descLike

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

6.2.15. model.describedResource

model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document. [1.3. The TEI Class System]
Moduletei
Used by
MembersTEI teiCorpus

6.2.16. model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersmodel.divBottomPart[address] model.divWrapper[byline meeting]

6.2.17. model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages]
Moduletei
Used by
Membersaddress

6.2.18. model.divGenLike

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

6.2.19. model.divLike

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

6.2.20. model.divPart

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

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

6.2.21. model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersmodel.divTopPart[model.headLike[head] address] model.divWrapper[byline meeting]

6.2.22. model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Moduletei
Used by
Membersmodel.headLike[head] address

6.2.23. model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersbyline meeting

6.2.24. model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membersdistinct emph foreign gloss mentioned soCalled term title

6.2.25. model.encodingDescPart

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

6.2.26. model.eventLike

model.eventLike groups elements which describe events.
Moduletei
Used by
Membersevent listEvent

6.2.27. model.frontPart

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

6.2.29. model.global.edit

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

6.2.30. model.global.meta

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

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

6.2.31. model.graphicLike

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

6.2.32. model.headLike

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

6.2.33. model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membershi q

6.2.34. model.highlighted

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

6.2.35. model.imprintPart

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

6.2.36. model.inter

6.2.37. model.lLike

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

6.2.38. model.labelLike

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

6.2.40. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
Memberslist listEvent listOrg listPerson listPlace

6.2.41. model.measureLike

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

6.2.42. model.milestoneLike

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

6.2.43. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike[geogFeat] model.persNamePart[forename genName] model.placeStateLike[model.placeNamePart[bloc district geogName placeName region settlement] location population] lang rs
Note

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

6.2.44. model.nameLike.agent

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

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

6.2.45. model.noteLike

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

6.2.46. model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name. [14.2.3. Place Names]
Moduletei
Used by
MembersgeogFeat

6.2.47. model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Moduletei
Used by
Membersmodel.eventLike[event listEvent] listOrg listPerson listPlace

6.2.49. model.pLike.front

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

6.2.51. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersmodel.pPart.editorial[abbr choice expan] model.pPart.transcriptional[add corr del orig reg sic unclear]

6.2.52. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersabbr choice expan

6.2.53. model.pPart.transcriptional

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

6.2.55. model.persNamePart

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

6.2.56. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei
Used by
Membersaffiliation age education faith langKnowledge nationality occupation persName residence socecStatus
Note

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

6.2.57. model.personLike

model.personLike groups elements which provide information about people and their relationships.
Moduletei
Used by
Membersorg person personGrp

6.2.60. model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Moduletei
Used by
Membersplace

6.2.61. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names]
Moduletei
Used by
Membersbloc district geogName placeName region settlement

6.2.62. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
Membersmodel.placeNamePart[bloc district geogName placeName region settlement] location population

6.2.63. model.ptrLike

6.2.64. model.publicationStmtPart.agency

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

6.2.65. model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Membersmodel.ptrLike[ptr ref] address availability date pubPlace
Note

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

See also model.publicationStmtPart.agency.

6.2.66. model.quoteLike

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

6.2.67. model.resource

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

6.2.68. model.respLike

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

6.2.69. model.segLike

model.segLike groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Moduletei
Used by
Membersseg
Note

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

6.2.70. model.settingPart

model.settingPart groups elements used to describe the setting of a linguistic interaction.
Moduletei
Used by
Membersactivity locale placeName

6.2.71. model.stageLike

model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]
Moduletei
Used by
Membersstage
Note

Stage directions are members of class inter: that is, they can appear between or within component-level elements.

6.2.72. model.textDescPart

model.textDescPart groups elements used to categorize a text for example in terms of its situational parameters.
Moduletei
Used by
Memberschannel constitution derivation domain factuality interaction preparedness

6.3. Attribute classes

6.3.1. att.anchoring

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

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

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

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

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

6.3.2. att.ascribed

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

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

6.3.3. att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Membersq said sp stage
Attributes
toWhomindicates the person, or group of people, to whom a speech act or action is directed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.
<castItem type="role">  <role xml:id="emil">Emilius.</role> </castItem> <castItem type="role">  <role xml:id="lov">Lovisa</role> </castItem> <castItem type="role">  <role xml:id="serv">A servant</role> </castItem> <!-- ... --> <sp who="#emil"  toWhom="#lov">  <speaker>Emil.</speaker>  <l n="1">My love!</l> </sp> <sp who="#lov"  toWhom="#emil">  <speaker>Lov.</speaker>  <l n="2">I have no Witness of my Noble Birth</l>  <stage who="emil"   toWhom="#serv">Pointing to her Woman.</stage>  <l>But that poor helpless wretch——</l> </sp>
Note

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

6.3.4. att.breaking

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

6.3.5. att.cReferencing

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

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

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

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

6.3.6. att.calendarSystem

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

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

6.3.7. att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming[att.personal[forename genName name orgName persName placeName] affiliation author birth bloc death district editor education event geogFeat geogName nationality occupation population pubPlace region residence rs settlement socecStatus] address bibl biblStruct catDesc correspDesc date distributor faith funder meeting principal publisher resp respStmt sponsor term time title unitDecl unitDef
Attributes
ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

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

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

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

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

6.3.8. att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei
MembersbiblScope citedRange
Attributes
unitidentifies the unit of information conveyed by the element.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(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

6.3.9. att.cmc

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

6.3.10. att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersaffiliation age application author birth bloc change creation date death district editor education event faith funder geogFeat geogName langKnowledge langKnown licence location meeting name nationality occupation orgName persName placeName population principal region residence resp settlement socecStatus sponsor time title unitDecl unitDef
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s, or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

6.3.11. att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersatt.datable[affiliation age application author birth bloc change creation date death district editor education event faith funder geogFeat geogName langKnowledge langKnown licence location meeting name nationality occupation orgName persName placeName population principal region residence resp settlement socecStatus sponsor time title unitDecl unitDef]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
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.

6.3.12. att.datcat

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

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

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

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

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

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

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

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

6.3.13. att.declaring

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

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

6.3.14. att.divLike

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

6.3.15. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl biblStruct change featureValueObservation revisionDesc
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change 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>

6.3.16. att.edition

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

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

6.3.17. att.fragmentable

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

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

6.3.18. att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abbr abstract activity add addrLine address affiliation age analytic appInfo application author availability back bibl biblScope biblStruct binaryObject birth bloc body byline catDesc catRef category cb change channel choice cit citedRange classCode classDecl constitution corr correspAction correspContext correspDesc creation date death del derivation desc distinct distributor district div divGen domain edition editionStmt editor education ellipsis email emph encodingDesc event expan extent factuality faith featureValueObservation fileDesc foreign forename front funder gap gb genName geo geoDecl geogFeat geogName gloss graphic head headItem headLabel hi hyphenation imprint index interaction item keywords l label lang langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listOrg listPerson listPlace listPrefixDef locale location measure measureGrp media meeting mentioned milestone monogr name namespace nationality normalization note noteGrp notesStmt num occupation org orgName orig p particDesc pb persName person personGrp place placeName population postBox postCode prefixDef preparedness principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation purpose q quotation quote rb ref reg region relatedItem residence resp respStmt revisionDesc rs rt ruby said samplingDecl seg series seriesStmt setting settingDesc settlement sic soCalled socecStatus sourceDesc sp speaker sponsor stage stdVals street taxonomy teiCorpus teiHeader term text textClass textDesc textLang time title titleStmt unclear unit unitDecl unitDef
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

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

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

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

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

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

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

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

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

6.3.19. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI abbr abstract activity add addrLine address affiliation age analytic appInfo application author availability back bibl biblScope biblStruct binaryObject birth bloc body byline catDesc catRef category cb change channel choice cit citedRange classCode classDecl constitution corr correspAction correspContext correspDesc creation date death del derivation desc distinct distributor district div divGen domain edition editionStmt editor education ellipsis email emph encodingDesc event expan extent factuality faith featureValueObservation fileDesc foreign forename front funder gap gb genName geo geoDecl geogFeat geogName gloss graphic head headItem headLabel hi hyphenation imprint index interaction item keywords l label lang langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listOrg listPerson listPlace listPrefixDef locale location measure measureGrp media meeting mentioned milestone monogr name namespace nationality normalization note noteGrp notesStmt num occupation org orgName orig p particDesc pb persName person personGrp place placeName population postBox postCode prefixDef preparedness principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation purpose q quotation quote rb ref reg region relatedItem residence resp respStmt revisionDesc rs rt ruby said samplingDecl seg series seriesStmt setting settingDesc settlement sic soCalled socecStatus sourceDesc sp speaker sponsor stage stdVals street taxonomy teiCorpus teiHeader term text textClass textDesc textLang time title titleStmt unclear unit unitDecl unitDef]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

6.3.20. att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global[TEI abbr abstract activity add addrLine address affiliation age analytic appInfo application author availability back bibl biblScope biblStruct binaryObject birth bloc body byline catDesc catRef category cb change channel choice cit citedRange classCode classDecl constitution corr correspAction correspContext correspDesc creation date death del derivation desc distinct distributor district div divGen domain edition editionStmt editor education ellipsis email emph encodingDesc event expan extent factuality faith featureValueObservation fileDesc foreign forename front funder gap gb genName geo geoDecl geogFeat geogName gloss graphic head headItem headLabel hi hyphenation imprint index interaction item keywords l label lang langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listOrg listPerson listPlace listPrefixDef locale location measure measureGrp media meeting mentioned milestone monogr name namespace nationality normalization note noteGrp notesStmt num occupation org orgName orig p particDesc pb persName person personGrp place placeName population postBox postCode prefixDef preparedness principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation purpose q quotation quote rb ref reg region relatedItem residence resp respStmt revisionDesc rs rt ruby said samplingDecl seg series seriesStmt setting settingDesc settlement sic soCalled socecStatus sourceDesc sp speaker sponsor stage stdVals street taxonomy teiCorpus teiHeader term text textClass textDesc textLang time title titleStmt unclear unit unitDecl unitDef]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr 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>

6.3.21. att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global[TEI abbr abstract activity add addrLine address affiliation age analytic appInfo application author availability back bibl biblScope biblStruct binaryObject birth bloc body byline catDesc catRef category cb change channel choice cit citedRange classCode classDecl constitution corr correspAction correspContext correspDesc creation date death del derivation desc distinct distributor district div divGen domain edition editionStmt editor education ellipsis email emph encodingDesc event expan extent factuality faith featureValueObservation fileDesc foreign forename front funder gap gb genName geo geoDecl geogFeat geogName gloss graphic head headItem headLabel hi hyphenation imprint index interaction item keywords l label lang langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listOrg listPerson listPlace listPrefixDef locale location measure measureGrp media meeting mentioned milestone monogr name namespace nationality normalization note noteGrp notesStmt num occupation org orgName orig p particDesc pb persName person personGrp place placeName population postBox postCode prefixDef preparedness principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation purpose q quotation quote rb ref reg region relatedItem residence resp respStmt revisionDesc rs rt ruby said samplingDecl seg series seriesStmt setting settingDesc settlement sic soCalled socecStatus sourceDesc sp speaker sponsor stage stdVals street taxonomy teiCorpus teiHeader term text textClass textDesc textLang time title titleStmt unclear unit unitDecl unitDef]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

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

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

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

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

6.3.22. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media[binaryObject graphic media] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

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

6.3.23. att.lexicographic

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

6.3.24. att.locatable

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

6.3.25. att.measurement

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

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

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

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

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

Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l> So weren't you gonna buy <measure quantity="0.5unit="gal"   commodity="ice cream">half    a gallon</measure>, baby</l> <l> So won't you go and buy <measure quantity="1.893unit="L"   commodity="ice cream">half    a gallon</measure>, baby?</l>

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

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

6.3.26. att.media

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

6.3.27. att.milestoneUnit

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

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

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

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

6.3.28. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms]
Moduletei
Membersatt.personal[forename genName name orgName persName placeName] affiliation author birth bloc death district editor education event geogFeat geogName nationality occupation population pubPlace region residence rs settlement socecStatus
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

6.3.29. att.notated

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

6.3.30. att.patternReplacement

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

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

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

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

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

6.3.31. att.personal

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

6.3.32. att.placement

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

6.3.33. att.pointing

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

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

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

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

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

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

6.3.34. att.resourced

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

6.3.35. att.scope

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

6.3.36. att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Moduletei
Membersseg
Attributes
function(function) characterizes the function of the segment.
StatusOptional
Datatypeteidata.enumerated
Note

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

6.3.37. att.spanning

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

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

6.3.38. att.timed

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

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

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

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

6.3.39. att.transcriptional

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

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

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

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

6.3.40. att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membersatt.transcriptional[add del rt] div emph head hi label note noteGrp p seg sp speaker stage text
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

6.4. Macros

6.4.1. macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
tei_macro.limitedContent =
   ( text | tei_model.limitedPhrase | tei_model.inter )*

6.4.2. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
tei_macro.paraContent = ( text | tei_model.paraPart )*

6.4.3. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

6.4.4. macro.phraseSeq.limited

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

6.4.5. macro.specialPara

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

6.5. Datatypes

6.5.1. teidata.certainty

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

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

6.5.2. teidata.count

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

Any positive integer value or zero is permitted

6.5.3. teidata.duration.iso

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

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

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

6.5.4. teidata.duration.w3c

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

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

For complete details, see the W3C specification.

6.5.5. teidata.enumerated

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

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

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

6.5.6. teidata.gender

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

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

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

6.5.7. teidata.language

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

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

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

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

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

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

Examples include

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

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

6.5.8. teidata.name

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

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

6.5.9. teidata.namespace

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

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

6.5.10. teidata.numeric

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

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

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

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

6.5.11. teidata.outputMeasurement

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

6.5.12. teidata.pattern

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

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

6.5.13. teidata.pointer

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

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

6.5.14. teidata.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
tei_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.

6.5.15. teidata.probCert

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

6.5.16. teidata.probability

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

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

6.5.17. teidata.replacement

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

6.5.18. teidata.sex

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

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

6.5.19. teidata.temporal.w3c

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

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

6.5.20. teidata.text

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

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

6.5.21. teidata.truthValue

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

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

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

6.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
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

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

6.5.23. teidata.versionNumber

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

6.5.24. teidata.word

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

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

6.5.25. teidata.xTruthValue

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

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

6.5.26. teidata.xpath

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

Any XPath expression using the syntax defined in 6.2..

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

Charly Mörth, Daniel Schopper, Ana Iriarte Díez, Ana Iriarte Díez, Veronika Engler, and Johanna Doppelbauer. Date: 2022