Document Metadata' Carolin Odebrecht Institut für deutsche Sprache und Linguistik, Humboldt-Universität zu Berlin carolin.odebrecht@hu-berlin.de (ed.) DFG - Deutsche Forschungsgemeinschaft

Editor: Carolin Odebrecht Institut für deutsche Sprache und Linguistik, Humboldt-Universität zu Berlin carolin.odebrecht@hu-berlin.de2015-06-08

Table of contents

1 Application for the TEI customizaiton

The LAUDATIO-Repository provides open access to historical text corpora. With the help of metadata such as

you will be able to chose your corpus of interest for your analysis or next preparation steps.

The TEI customization provides a metadata scheme for the LAUDATIO-Repository which enables a structured and uniform display and facetted and free-metadata search of such corpus metadata. The customization is based on a metadata model.

For each corpus in the repository the metadata are stored in TEI XML. There are three ODDs which specify the metadata for a corpus, the documents of the corpus and the annotation in the documents. This customization refers to the class 'corpus', see figure 1 below.

The TEI ODD is developed in the context of the LAUDATIO-Project in cooperation with the working groups of the Search and Visualization System ANNIS and the converter framework SaltNPepper.

1.1 Metadata model

The metadata model refers to all kinds of historical text corpora.

Figure 1. Metadata model
Metadata model

The metadata model defines a corpus as the sum of documents which are the sum of annotations. For each concept, there is a list of attributes which represent the metadata relevant for data retrieval in the repository. For example, the attribut 'title' is assigned to each concept but there is a difference between a title for the corpus, a title for a historical document within the corpus or the title of an annotation layer. with the help of the model, it will be clear which title is meant in which situation.

For detailed information, motivation and discussion see

1.2 Implementation of the metadata model

The TEI customization creates TEI scheme for the LAUDATIO metadata concepts 'Corpus', 'Document' and 'PreparationStep' by mapping the metadata model and TEI p5 header structure. The metadata model is realized with TEI p5 by using a subset of the TEI p5 and a TEI header for each conclascept:

Each TEI XML file contains fileDesc, encodingDesc and revisionDesc. The concepts 'Corpus' and 'Document' contain profileDesc because they refer to the language used in the data.

The header have relations to each other in the following way: The 'Corpus Header' provides lists of documents corresponding to the 'Document Header' and list of annotations corresponding to the 'PreparationStep Header'. Each 'Document Header' contains a list of annotation for each document in the corpus corresponding to the 'PreparationStep Header'.

2 TEI p5 customization for the concept 'Document'

The ODD combines the modules <core>, <header>, <textstructure>, <tagdocs>, <namesdates> and <msdescription> but removes most of the available elements and changes several attribute classes, e.g. add a TEI attribute to an element. Thus, the customization is very restricted and allows little variation in selecting elements and attributes.

3 Core structure

The <core> module is very restricted and only contains the elements corresponding to bibliographic metadata such as author, editor, date and title and more general structural element such as <list>, <item>, <label>, p and ref.

No class or general module modification were made. The TEI schema is only locally restricted. That means that no inheritance relations or module relations were changed, deleted or added. The customization is documented in the section 'Formal declaration'.

All encoded metadata refer to information addressing each document, e.g. the editors and authors of the document, the revision history and the available annotations.

4 Basic TEI header structure

LAUDATIO metadata schema for the concept 'Document' contains much more elements and modules comparing to standard TEI header which are usually used for the purpose of text encoding only. For validity, fileDesc, the profileDesc, encodingDesc and revisionDesc are required.

The fileDesc contains the following elements where the basic meaning are left untouched but are referred to the concept 'Document', meaning the element author refers to the author of the document, the element title refers to the title of a single document. Important elements used within teiHeader are:

<teiHeader type="DocumentHeader">
 <fileDesc>
  <titleStmt/>
  <extent type="...">...</extent>
 </fileDesc>
</teiHeader>
The publicationStmt refers to a printed publication either an edition or the first publication
<teiHeader type="DocumentHeader">
 <fileDesc>
  <titleStmt/>
  <publicationStmt>
   <idno>...</idno>
   <pubPlace>...</pubPlace>
   <publisher>...</publisher>
   <date when="...">...</date>
   <biblScope>...</biblScope>
  </publicationStmt>
 </fileDesc>
</teiHeader>
Publication may be published within series. seriesStmt provides information about the publication series of publication of the document.
<teiHeader type="DocumentHeader">
 <fileDesc>
  <titleStmt/>
  <publicationStmt/>
  <seriesStmt/>
  <sourceDesc n="...">
   <msDesc>
    <msIdentifier>
     <msName>...</msName>
     <altIdentifier>
      <repository>...</repository>
      <collection>...</collection>
      <idno>...</idno>
     </altIdentifier>
    </msIdentifier>
    <history>
     <origin>
      <objectType>...</objectType>
      <origDate notAfter-custom="..."
       notBefore-custom="...precision="medium">
...</origDate>
      <origPlace>...</origPlace>
      <title>...</title>
      <locus>...</locus>
     </origin>
    </history>
   </msDesc>
   <recordHist>
    <source facs="...">
     <ref target="...">...</ref>
    </source>
   </recordHist>
  </sourceDesc>
 </fileDesc>
</teiHeader>
msDesc shall only give a short overview over the publication history of each document of the corpus in order to use the view and search functions of the LAUDATIO-Repository. Thus, recordHist is used to provide repertory references where much more detailed information about the manuscript history is given.
The profileDesc only contains metadata concerning the language of the every single document.
<teiHeader type="DocumentHeader">
 <fileDesc/>
 <profileDesc>
  <langUsage>
   <language ident="...style="Language">...</language>
   <language ident="..."
    style="LanguageType">
...</language>
   <language ident="..."
    style="LanguageArea">
...</language>
  </langUsage>
 </profileDesc>
</teiHeader>
The encodingDesc contains a list of annotation keys sorted by rough linguistic categories:
<teiHeader type="DocumentHeader">
 <fileDesc/>
 <profileDesc/>
 <encodingDesc>
  <schemaSpec ident="AnnotationKey">
   <elementSpec ident="...">
    <valList>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
    </valList>
   </elementSpec>
  </schemaSpec>
  <schemaSpec ident="AnnotationKey">
   <elementSpec ident="...">
    <valList>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
    </valList>
   </elementSpec>
  </schemaSpec>
 </encodingDesc>
</teiHeader>
The ident of elementSpec contains a fixed list of categories as a rough division of annotations according to their functions: Transcription, Lexical, Syntactical, Morphological, Graphical, MarkUp, Meta and Other.
revisionDesc refers to the version history of the whole corpus. Corpora in the LAUDATIO-Repository may have several versions. The changes between these versions will be provided here with focus on the document.
<teiHeader type="DocumentHeader">
 <fileDesc/>
 <profileDesc/>
 <encodingDesc/>
 <revisionDesc>
  <change n="...type="...when="..."
   who="...">
...</change>
  <change n="...type="...when="..."
   who="...">
...</change>
 </revisionDesc>
</teiHeader>

5 Detailed TEI header structure

A full TEI structure with all required elements is given below:
<teiHeader type="DocumentHeader">
 <fileDesc>
  <titleStmt>
   <title>...</title>
   <editor>
    <persName>
     <forename>...</forename>
     <surname>...</surname>
    </persName>
   </editor>
   <author>
    <persName>
     <forename>...</forename>
     <surname>...</surname>
    </persName>
   </author>
  </titleStmt>
  <extent type="...">...</extent>
  <publicationStmt>
   <idno>...</idno>
   <pubPlace>...</pubPlace>
   <publisher>...</publisher>
   <date when="...">...</date>
   <biblScope>...</biblScope>
  </publicationStmt>
  <seriesStmt>
   <title>...</title>
   <editor>...</editor>
   <biblScope type="vol">...</biblScope>
  </seriesStmt>
  <sourceDesc n="...">
   <msDesc>
    <msIdentifier>
     <msName>...</msName>
     <altIdentifier>
      <repository>...</repository>
      <collection>...</collection>
      <idno>...</idno>
     </altIdentifier>
    </msIdentifier>
    <history>
     <origin>
      <objectType>...</objectType>
      <origDate notAfter-custom="..."
       notBefore-custom="...precision="medium">
...</origDate>
      <origPlace>...</origPlace>
      <title>...</title>
      <locus>...</locus>
     </origin>
    </history>
   </msDesc>
   <recordHist>
    <source facs="...">
     <ref target="...">...</ref>
    </source>
   </recordHist>
  </sourceDesc>
 </fileDesc>
 <profileDesc>
  <langUsage>
   <language ident="...style="Language">...</language>
   <language ident="..."
    style="LanguageType">
...</language>
   <language ident="..."
    style="LanguageArea">
...</language>
  </langUsage>
 </profileDesc>
 <encodingDesc>
  <schemaSpec ident="AnnotationKey">
   <elementSpec ident="...">
    <valList>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
    </valList>
   </elementSpec>
   <elementSpec ident="...">
    <valList>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
    </valList>
   </elementSpec>
   <elementSpec ident="...">
    <valList>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
     <valItem corresp="...ident="..."/>
    </valList>
   </elementSpec>
  </schemaSpec>
 </encodingDesc>
 <revisionDesc>
  <change n="...type="...when="..."
   who="...">
...</change>
  <change n="...type="...when="..."
   who="...">
...</change>
 </revisionDesc>
</teiHeader>

6 Formal declaration

Schema teiODD_LAUDATIODocument_S7: Elements

<altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
msdescription: msIdentifier
May contain
header: idno
msdescription: collection repository
Declaration
element altIdentifier
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   (
      model.placeNamePart_sequenceOptional,
      institution?,
      repository?,
      collection?,
      idno,
      note?
   )
}
Example
<altIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</altIdentifier>
Note

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

<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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
AttributesAttributesatt.global.responsibility (@cert, @resp)
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document. Sample values include:
Derived fromatt.global
Status Recommended
Datatype data.text
Sample values include:
Member of
Contained by
header: titleStmt
May contain
Declaration
element author
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute n { data.text }?,
   macro.phraseSeq
}
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>
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.

<biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp))
Contained by
header: seriesStmt
May contain
Declaration
element biblScope { att.global.attributes, macro.phraseSeq }
Example
<biblScope>pp 12–34</biblScope>
<biblScope from="12to="34unit="page"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>
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 should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.

<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.5. The Revision Description 2.4.1. Creation 11.7. Changes]
Moduleheader
AttributesAttributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
targetpoints to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Contained by
header: revisionDesc
msdescription: recordHist
May contain
Declaration
element change
{
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute target { list { data.pointer+ } }?,
   macro.specialPara
}
Example
<titleStmt>
 <title> ... </title>
 <editor xml:id="LDB">Lou Burnard</editor>
 <respStmt xml:id="BZ">
  <resp>copy editing</resp>
  <name>Brett Zamir</name>
 </respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
 <change status="publicwhen="2008-02-02"
  who="#BZ">
Finished chapter 23</change>
 <change status="draftwhen="2008-01-02"
  who="#BZ">
Finished chapter 2</change>
 <change n="P2.2when="1991-12-21"
  who="#LDB">
Added examples to section 3</change>
 <change when="1991-11-11who="#MSM">Deleted chapter 10</change>
</revisionDesc>
Example
<profileDesc>
 <creation>
  <listChange>
   <change xml:id="DRAFT1">First draft in pencil</change>
   <change notBefore="1880-12-09"
    xml:id="DRAFT2">
First revision, mostly
       using green ink</change>
   <change notBefore="1881-02-13"
    xml:id="DRAFT3">
Final corrections as
       supplied to printer.</change>
  </listChange>
 </creation>
</profileDesc>
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.

<collection>

<collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
May containCharacter data only
Declaration
element collection
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.xtext
}
Example
<msIdentifier>
 <country>USA</country>
 <region>California</region>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <collection>Ellesmere</collection>
 <idno>El 26 C 9</idno>
 <msName>The Ellesmere Chaucer</msName>
</msIdentifier>

<date>

<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.5. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Modulecore
AttributesAttributesatt.typed (subtype, @type)
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
Status Required
Datatype data.temporal.iso
Member of
Contained by
May contain
Declaration
element date
{
   att.typed.attribute.type,
   attribute when { data.temporal.iso },
   ( text | model.gLike | model.phrase | model.global )*
}
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>

<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.11.2.2. Titles, Authors, and Editors]
Modulecore
AttributesAttributesatt.global.responsibility (@cert, @resp)
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document. Sample values include:
Derived fromatt.global
Status Recommended
Datatype data.text
Sample values include:
Member of
Contained by
May contain
Declaration
element editor
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute n { data.text }?,
   macro.phraseSeq
}
Example
<editor>Eric Johnson</editor>
<editor role="illustrator">John Tenniel</editor>
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.

<elementSpec>

<elementSpec> (element specification) documents the structure, content, and purpose of a single element type. [22.4.4. Element Specifications 22. Documentation Elements]
Moduletagdocs
AttributesAttributesatt.global.responsibility (@cert, @resp) att.deprecated (@validUntil)
identsupplies the identifier by which this element may be referenced.
Derived fromatt.identified
Status Required
Datatype data.name
Legal values are:
Lexical
Syntactical
Morphological
MarkUp
Graphical
Transcription
Other
Meta
Member of
Contained by
core: p ref title
header: change
msdescription: origin source
tagdocs: schemaSpec
May contain
tagdocs: valList
Declaration
element elementSpec
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.deprecated.attribute.validUntil,
   attribute ident
   {
      "Lexical"
    | "Syntactical"
    | "Morphological"
    | "MarkUp"
    | "Graphical"
    | "Transcription"
    | "Other"
    | "Meta"
   },
   (
      ( model.glossLike | model.descLike )*,
      classes?,
      content?,
      valList?,
      constraintSpec*,
      attList?,
      exemplum*,
      remarks*,
      listRef*
   )
}
Example
<elementSpec ident="codemodule="tagdocs">
 <gloss/>
 <desc>contains literal code</desc>
 <classes>
  <memberOf key="model.emphLike"/>
 </classes>
 <content>
  <rng:text/>
 </content>
 <attList>
  <attDef ident="typeusage="opt">
   <desc>the language of the code</desc>
   <datatype>
    <rng:ref name="data.enumerated"/>
   </datatype>
  </attDef>
 </attList>
</elementSpec>

<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
AttributesAttributesatt.global (xml:id, n, xml:lang, @xml:base, @xml:space) att.global.rendition (style, rendition, @rend) att.global.responsibility (@cert, @resp)
Member of
Contained by
header: teiHeader
May contain
core: p
tagdocs: schemaSpec
Declaration
element encodingDesc
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( ( model.encodingDescPart | model.pLike )+ )
}
Example
<encodingDesc>
 <p>Basic encoding, capturing lexical information only. All
   hyphenation, punctuation, and variant spellings normalized. No
   formatting or layout information preserved.</p>
</encodingDesc>

<extent>

<extent> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Moduleheader
AttributesAttributesatt.global.responsibility (@cert, @resp) att.typed (type, @subtype)
type(You must indicate what type of extent you refere of) characterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Required
Datatype data.enumerated
Legal values are:
Tokens
(The size of the corpus is given in token.)
Words
(The size of the corpus is given in words.)
Contained by
header: fileDesc
May contain
Declaration
element extent
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.typed.attribute.subtype,
   attribute type { "Tokens" | "Words" },
   macro.phraseSeq
}
Example
<extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent>
<extent>ten 3.5 inch high density diskettes</extent>
Example

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

<extent>
 <measure quantity="4.2unit="MiB">About four megabytes</measure>
 <measure quantity="245unit="pages">245 pages of source
   material</measure>
</extent>

<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
AttributesAttributesatt.global (n, xml:lang, xml:base, xml:space, @xml:id) att.global.responsibility (@cert, @resp)
Contained by
header: teiHeader
May contain
Declaration
element fileDesc
{
   att.global.attribute.xmlid,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt?,
         notesStmt?
      ),
      sourceDesc+
   )
}
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>
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.

<forename>

<forename> contains a forename, given or baptismal name. [13.2.1. Personal Names]
Modulenamesdates
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
May contain
Declaration
element forename
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.phraseSeq
}
Example
<persName>
 <roleName>Ex-President</roleName>
 <forename>George</forename>
 <surname>Bush</surname>
</persName>

<history>

<history> groups elements describing the full history of a manuscript or manuscript part. [10.8. History]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
msdescription: msDesc
May contain
core: p
msdescription: origin
Declaration
element history
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( model.pLike+ | ( summary?, origin?, provenance*, acquisition? ) )
}
Example
<history>
 <origin>
  <p>Written in Durham during the mid twelfth
     century.</p>
 </origin>
 <provenance>
  <p>Recorded in two medieval
     catalogues of the books belonging to Durham Priory, made in 1391 and
     1405.</p>
 </provenance>
 <provenance>
  <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
     and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
     according to inscriptions on ff. 4v and 5.</p>
 </provenance>
 <acquisition>
  <p>Presented to Trinity College in 1738 by
     Thomas Gale and his son Roger.</p>
 </acquisition>
</history>

<idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Status Optional
Datatype data.enumerated
Member of
Contained by
May contain
header: idno
Declaration
element idno
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type { data.enumerated }?,
   ( text | model.gLike | idno )*
}
Example
<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
 <g ref="#sym"/>345
</idno>

In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.

Note

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

<language>

<language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader
AttributesAttributesatt.global (xml:id, xml:lang, xml:base, xml:space, @n) att.global.responsibility (@cert, @resp)
stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
Derived fromatt.global.rendition
Status Required
Datatype data.text
Legal values are:
Language
LanguageType
LanguageArea
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
Status Required
Datatype data.language
Contained by
header: langUsage
May contain
Declaration
element language
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute style { "Language" | "LanguageType" | "LanguageArea" },
   attribute ident { data.language },
   macro.phraseSeq.limited
}
Example
<langUsage>
 <language ident="en-USusage="75">modern American English</language>
 <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>
 <language ident="x-lapusage="05">Pig Latin</language>
</langUsage>
Note

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

<langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
Moduleheader
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
header: profileDesc
May contain
header: language
Declaration
element langUsage
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   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>

<locus>

<locus> defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
May containCharacter data only
Declaration
element locus
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.xtext
}
Example

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

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

<msItem>
 <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
 <bibl>
  <title>IMEV</title>
  <biblScope>1506</biblScope>
 </bibl>
</msItem>
Note

The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the first example above. To associate a locus element with a page image or other comparable representation, the global facs attribute should be used instead, as shown in the second example. Use of the target attribute to indicate an image is strongly deprecated. The facs attribute may be used to indicate one or more image files, as above, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone> element, <graphic>, or <binaryObject> elements.

Note

When the location being defined consists of a single page, use the from and to attributes with an identical value. When no clear endpoint is given the from attribute should be used without to. For example, if the manuscript description being transcribed has ‘p. 3ff’ as the locus.

<locusGrp>

<locusGrp> groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation. [10.3.5. References to Locations within a Manuscript]
Modulemsdescription
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp))
schemeidentifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
Status Optional
Datatype data.pointer
Member of
Contained by
May contain
msdescription: locus
Declaration
element locusGrp
{
   att.global.attributes,
   attribute scheme { data.pointer }?,
   locus+
}
Example
<msItem>
 <locusGrp>
  <locus from="13to="26">Bl. 13--26</locus>
  <locus from="37to="58">37--58</locus>
  <locus from="82to="96">82--96</locus>
 </locusGrp>
 <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note>
</msItem>

<msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object. [10.1. Overview]
Modulemsdescription
AttributesAttributes att.declaring (@decls) att.global.responsibility (@cert, @resp)
Member of
Contained by
core: p ref title
msdescription: origin source
May contain
core: p
msdescription: history msIdentifier
Declaration
element msDesc
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.declaring.attributes,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents?, physDesc?, history?, additional?, msPart* )
      )
   )
}
Example
<msDesc>
 <msIdentifier>
  <settlement>Oxford</settlement>
  <repository>Bodleian Library</repository>
  <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
 </msIdentifier>
 <msContents>
  <msItem>
   <author>Geoffrey Chaucer</author>
   <title>The Canterbury Tales</title>
  </msItem>
 </msContents>
 <physDesc>
  <objectDesc>
   <p>A parchment codex of 136 folios, measuring approx
       28 by 19 inches, and containing 24 quires.</p>
   <p>The pages are margined and ruled throughout.</p>
   <p>Four hands have been identified in the manuscript: the first 44
       folios being written in two cursive anglicana scripts, while the
       remainder is for the most part in a mixed secretary hand.</p>
  </objectDesc>
 </physDesc>
</msDesc>

<msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript being described. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
msdescription: msDesc
May contain
Declaration
element msIdentifier
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   (
      (
         model.placeNamePart_sequenceOptional,
         institution?,
         repository?,
         collection*,
         idno?
      ),
      ( msName | altIdentifier )*
   )
}
Schematron

<s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location of some type, or a manuscript name</s:report>
Example
<msIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</msIdentifier>

<msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
msdescription: msIdentifier
May containCharacter data only
Declaration
element msName
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.xtext
}
Example
<msName>The Vercelli Book</msName>

<objectType>

<objectType> contains a word or phrase describing the type of object being referred to. [10.3.2. Material and Object Type]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
May contain
Declaration
element objectType
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.phraseSeq
}
Example
<physDesc>
 <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p>
</physDesc>
Example
<physDesc>
 <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.
 </p>
</physDesc>
Note

The ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

<orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element orgName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
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>....

<origDate>

<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part. [10.3.1. Origination]
Modulemsdescription
AttributesAttributesatt.datable.custom (when-custom, from-custom, to-custom, datingPoint, datingMethod, @notBefore-custom, @notAfter-custom) att.dimensions (unit, quantity, extent, scope, @precision)
Member of
Contained by
May contain
Declaration
element origDate
{
   att.datable.custom.attribute.notBefore-custom,
   att.datable.custom.attribute.notAfter-custom,
   att.dimensions.attribute.precision,
   ( text | model.gLike | model.phrase | model.global )*
}
Example
<origDate notAfter="-0200"
 notBefore="-0300">
3rd century BCE</origDate>

<origin>

<origin> contains any descriptive or other information concerning the origin of a manuscript or manuscript part. [10.8. History]
Modulemsdescription
Contained by
msdescription: history
May contain
Declaration
element origin { macro.specialPara }
Example
<origin evidence="internalnotAfter="1845"
 notBefore="1802resp="#AMH">
Copied in <name type="origPlace">Derby</name>, probably from an
old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
</origin>

<origPlace>

<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript or manuscript part. [10.3.1. Origination]
Modulemsdescription
Member of
Contained by
May contain
Declaration
element origPlace { macro.phraseSeq }
Example
<origPlace>Birmingham</origPlace>
Note

The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.fragmentable (@part)
Member of
Contained by
May contain
Declaration
element p
{
   att.global.attributes,
   att.declaring.attributes,
   att.fragmentable.attributes,
   macro.paraContent
}
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>

<persName>

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

<profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader
AttributesAttributesatt.global (xml:id, n, xml:lang, @xml:base, @xml:space) att.global.rendition (style, rendition, @rend) att.global.responsibility (@cert, @resp)
Member of
Contained by
header: teiHeader
May contain
header: langUsage
Declaration
element profileDesc
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( model.profileDescPart* )
}
Example
<profileDesc>
 <langUsage>
  <language ident="fr">French</language>
 </langUsage>
 <textDesc n="novel">
  <channel mode="w">print; part issues</channel>
  <constitution type="single"/>
  <derivation type="original"/>
  <domain type="art"/>
  <factuality type="fiction"/>
  <interaction type="none"/>
  <preparedness type="prepared"/>
  <purpose degree="hightype="entertain"/>
  <purpose degree="mediumtype="inform"/>
 </textDesc>
 <settingDesc>
  <setting>
   <name>Paris, France</name>
   <time>Late 19th century</time>
  </setting>
 </settingDesc>
</profileDesc>
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.

In earlier versions of these Guidelines, it was required that the <creation> element appear first.

<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
AttributesAttributesatt.global (xml:id, n, xml:lang, @xml:base, @xml:space) att.global.rendition (style, rendition, @rend) att.global.responsibility (@cert, @resp)
Contained by
header: fileDesc
May contain
Declaration
element publicationStmt
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   (
      (
         ( model.publicationStmtPart.agency ),
         model.publicationStmtPart.detail*
      )+
    | model.pLike+
   )
}
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>
Note

Where a publication statement contains several members of the model.publicationStmtPart 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.

<publisher>

<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element publisher { att.global.attributes, macro.phraseSeq }
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
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

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
May contain
Declaration
element pubPlace
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>

<recordHist>

<recordHist> (recorded history) provides information about the source and revision status of the parent manuscript description itself. [10.9.1. Administrative Information]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
header: sourceDesc
May contain
core: p
header: change
msdescription: source
Declaration
element recordHist
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( model.pLike+ | ( source, change* ) )
}
Example
<recordHist>
 <source>
  <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research
     by P.M.W.Robinson</p>
 </source>
 <change when="1999-06-23">
  <name>LDB</name> (editor)
   checked examples against DTD version 3.6
 </change>
</recordHist>

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]
Modulecore
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate) att.internetMedia (@mimeType) att.typed (@type, @subtype) att.declaring (@decls) att.cReferencing (@cRef)
Member of
Contained by
May contain
Declaration
element ref
{
   att.global.attributes,
   att.pointing.attributes,
   att.internetMedia.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.cReferencing.attributes,
   macro.paraContent
}
Schematron

<s:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <s:name/></s:report>
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>.
Note

The target and cRef attributes are mutually exclusive.

<repository>

<repository> contains the name of a repository within which manuscripts are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
May containCharacter data only
Declaration
element repository
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.xtext
}
Example
<msIdentifier>
 <settlement>Oxford</settlement>
 <institution>University of Oxford</institution>
 <repository>Bodleian Library</repository>
 <idno>MS. Bodley 406</idno>
</msIdentifier>

<revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.5. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
AttributesAttributes att.docStatus (@status) att.global (xml:id, n, xml:lang, @xml:base, @xml:space) att.global.rendition (style, rendition, @rend) att.global.responsibility (@cert, @resp)
Contained by
header: teiHeader
May contain
header: change
Declaration
element revisionDesc
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.docStatus.attributes,
   ( list | listChange | change+ )
}
Example
<revisionDesc status="embargoed">
 <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
</revisionDesc>
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.

<schemaSpec>

<schemaSpec> (schema specification) generates a TEI-conformant schema and documentation for it. [2.3. The Encoding Description 22.2. Modules and Schemas 23.5.1. Making a Unified ODD]
Moduletagdocs
AttributesAttributesatt.global.responsibility (@cert, @resp) att.identified (predeclare, module, status, @ident) att.deprecated (@validUntil)
Member of
Contained by
msdescription: origin source
May contain
tagdocs: elementSpec
Declaration
element schemaSpec
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.identified.attribute.ident,
   att.deprecated.attribute.validUntil,
   ( ( model.glossLike | model.descLike )*, ( model.oddRef | model.oddDecl )* )
}
Example
<schemaSpec ident="testsvgprefix="TEI_"
 start="TEI svg">

 <moduleRef key="header"
  source="tei:current"/>

 <moduleRef key="core"/>
 <moduleRef key="drama"/>
 <moduleRef url="svg11.rng"/>
</schemaSpec>

This schema combines elements from the current versions of the drama and core modules, the current release version of the header module, and elements from an existing RELAXNG schema available from the URL indicated.

Note

A schemaSpec combines references to modules, individual element or macro declarations, and specification groups together to form a unified schema. The processing of the schemaSpec element must resolve any conflicts amongst the declarations it contains or references. Different ODD processors may generate schemas and documentation using different concrete syntaxes.

<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
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp))
Contained by
header: fileDesc
May contain
header: idno
Declaration
element seriesStmt
{
   att.global.attributes,
   ( model.pLike+ | ( title+, ( editor | respStmt )*, ( idno | biblScope )* ) )
}
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>

<source>

<source> describes the original source for the information contained with a manuscript description. [10.9.1.1. Record History]
Modulemsdescription
AttributesAttributesatt.global.responsibility (@cert, @resp)
facs
Status Required
Contained by
msdescription: recordHist
May contain
Declaration
element source
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute facs { text },
   macro.specialPara
}
Example
<source>Derived from <ref>Stanley (1960)</ref>
</source>

<sourceDesc>

<sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
Contained by
header: fileDesc
May contain
core: p
msdescription: msDesc recordHist
Declaration
element sourceDesc
{
   att.global.attributes,
   att.declarable.attributes,
   (
      model.pLike+
    | ( model.biblLike | model.sourceDescPart | model.listLike )+
   )
}
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>

<surname>

<surname> contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Modulenamesdates
AttributesAttributesatt.global.responsibility (@cert, @resp)
Member of
Contained by
May contain
Declaration
element surname
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.phraseSeq
}
Example
<surname type="combine">St John Stevas</surname>

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of TEI elements may be combined together to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp))
versionspecifies the major version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype data.version
Note

The major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the schemaSpec element. The current version is P5.

Contained by
May contain
header: teiHeader
textstructure: text
Declaration
element TEI
{
   att.global.attributes,
   attribute version { data.version }?,
   ( teiHeader, ( ( model.resourceLike+, text? ) | text ) )
}
Schematron

<s:ns prefix="tei"
 uri="http://www.tei-c.org/ns/1.0"/>

<s:ns prefix="xs"
 uri="http://www.w3.org/2001/XMLSchema"/>
Schematron

<s:ns prefix="rng"
 uri="http://relaxng.org/ns/structure/1.0"/>
Example
<TEI version="5.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 name space.</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="5.0" 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>
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

<teiHeader>

<teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Moduleheader
AttributesAttributesatt.global (xml:id, xml:lang, xml:base, xml:space, @n) att.global.rendition (rend, rendition, @style) att.global.responsibility (@cert, @resp)
type(You must identify the module of the LAUDATIO metada schema, e.g. CorpusHeader, DocumentHeader, PreparationHeader) specifies the kind of document to which the header is attached, for example whether it is a corpus or individual text.
Status Required
Datatype data.enumerated
Legal values are:
CorpusHeader
DocumentHeader
PreparationHeader
Contained by
textstructure: TEI
May contain
Declaration
element teiHeader
{
   att.global.attribute.n,
   att.global.rendition.attribute.style,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute type { "CorpusHeader" | "DocumentHeader" | "PreparationHeader" },
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}
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>
Note

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

<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 15.1. Varieties of Composite Text]
Moduletextstructure
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.typed (@type, @subtype)
Contained by
textstructure: TEI
May containEmpty element
Declaration
element text
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}
Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

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

<text>
 <front>
<!-- front matter for the whole group -->
 </front>
 <group>
  <text>
<!-- first text -->
  </text>
  <text>
<!-- second text -->
  </text>
 </group>
</text>
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.

<title>

<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
AttributesAttributesatt.global (xml:id, n, xml:lang, @xml:base, @xml:space) att.global.rendition (style, rendition, @rend) att.global.responsibility (@cert, @resp)
type(You must specify the exact reference to LAUDATIO metadata module schema 'Corpus'.) classifies the title according to some convenient typology.
Derived fromatt.typed
Status Recommended
Datatype data.enumerated
Legal values are:
Document
(The title only refers to the LAUDATIO metadata module 'Corpus')
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.

Member of
Contained by
May contain
Declaration
element title
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute type { "Document" }?,
   macro.paraContent
}
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>
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.

<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
AttributesAttributesatt.global.responsibility (@cert, @resp)
Contained by
header: fileDesc
May contain
Declaration
element titleStmt
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( title+, model.respLike* )
}
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>

<valItem>

<valItem> documents a single value in a predefined list of values. [22.4.5. Attribute List Specification]
Moduletagdocs
AttributesAttributesatt.global.responsibility (@cert, @resp) att.deprecated (@validUntil)
corresp
Status Required
identspecifies the value concerned.
Status Required
Datatype data.text
Contained by
tagdocs: valList
May containEmpty element
Declaration
element valItem
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.deprecated.attribute.validUntil,
   attribute corresp { text },
   attribute ident { data.text },
   ( model.descLike | model.glossLike )*
}
Example
<valItem ident="dub">
 <altIdent xml:lang="fr">dou</altIdent>
 <equiv name="unknown"/>
 <gloss>dubious</gloss>
 <desc>used when the application of this element is doubtful or uncertain</desc>
</valItem>

<valList>

<valList> (value list) contains one or more valItem elements defining possible values. [22.4.5. Attribute List Specification]
Moduletagdocs
AttributesAttributesatt.global.responsibility (@cert, @resp) att.deprecated (@validUntil)
Contained by
tagdocs: elementSpec
May contain
tagdocs: valItem
Declaration
element valList
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.deprecated.attribute.validUntil,
   valItem*
}
Example
<valList type="closed">
 <valItem ident="req">
  <gloss>required</gloss>
 </valItem>
 <valItem ident="rec">
  <gloss>recommended</gloss>
 </valItem>
 <valItem ident="opt">
  <gloss>optional</gloss>
 </valItem>
</valList>

Schema teiODD_LAUDATIODocument_S7: Model classes

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]
Moduletei
Used by
MembersmsDesc

model.dateLike

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

model.divPart

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

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

model.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
Memberstitle

model.encodingDescPart

model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times.
Moduletei
Used by
MembersschemaSpec

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.global.edit model.global.meta model.milestoneLike model.noteLike

model.highlighted

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

model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.biblLike [msDesc] model.egLike model.labelLike model.listLike model.oddDecl [elementSpec] model.qLike [model.quoteLike] model.stageLike

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.emphLike [title] model.hiLike model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [orgName persName] model.offsetLike model.persNamePart [forename surname] model.placeStateLike [model.placeNamePart] idno] ] model.pPart.editorial model.pPart.msdesc [locus locusGrp objectType origDate origPlace] model.phrase.xml model.ptrLike [ref]

model.nameLike

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

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

model.nameLike.agent

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

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

model.oddDecl

model.oddDecl groups elements which generate declarations in some markup language in ODD documents.
Moduletei
Used by
MemberselementSpec

model.persNamePart

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

model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.graphicLike model.highlighted [model.emphLike [title] model.hiLike] model.lPart model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [orgName persName] model.offsetLike model.persNamePart [forename surname] model.placeStateLike [model.placeNamePart] idno] ] model.pPart.edit [model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc [locus locusGrp objectType origDate origPlace] model.phrase.xml model.ptrLike [ref] model.segLike model.specDescLike
Note

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

model.placeStateLike

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

model.pLike

model.pLike groups paragraph-like elements.
Moduletei
Used by
Membersp

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
Membersmodel.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [orgName persName] model.offsetLike model.persNamePart [forename surname] model.placeStateLike [model.placeNamePart] idno]

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]
Moduletei
Used by
Membersmodel.pPart.editorial model.pPart.transcriptional

model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
Moduletei
Used by
Memberslocus locusGrp objectType origDate origPlace

model.profileDescPart

model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times.
Moduletei
Used by
MemberslangUsage

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]
Moduletei
Used by
Membersref

model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Memberspublisher
Note

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

See also model.publicationStmtPart.detail.

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
Membersdate idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membersmodel.quoteLike

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

model.sourceDescPart

model.sourceDescPart groups elements which may be used inside sourceDesc and appear multiple times.
Moduletei
Used by
MembersrecordHist

model.teiHeaderPart

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

Schema teiODD_LAUDATIODocument_S7: Attribute classes

att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Memberschange
AttributesAttributes
whoindicates the person, or group of people, to whom the element content is ascribed.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace

In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.

<castItem type="role">
 <role xml:id="Barnardo">Bernardo</role>
</castItem>
<castItem type="role">
 <role xml:id="Francisco">Francisco</role>
 <roleDesc>a soldier</roleDesc>
</castItem>
<!-- ... -->
<sp who="#Barnardo">
 <speaker>Bernardo</speaker>
 <l n="1">Who's there?</l>
</sp>
<sp who="#Francisco">
 <speaker>Francisco</speaker>
 <l n="2">Nay, answer me: stand, and unfold yourself.</l>
</sp>
Note

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

att.canonical

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Moduletei
Membersatt.naming [att.personal [orgName] pubPlace]
AttributesAttributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype data.text
<author>
 <name key="name 427308"
  type="organisation">
[New Zealand Parliament, Legislative Council]</name>
</author>
<author>
 <name key="Hugo, Victor (1802-1885)"
  ref="http://www.idref.fr/026927608">
Victor Hugo</name>
</author>
Note

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

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

ref(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated 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.

att.combinable

att.combinable provides attributes indicating how multiple references to the same object in a schema should be combined
Moduletagdocs
Membersatt.identified
AttributesAttributes att.deprecated (@validUntil)
modespecifies the effect of this declaration on its parent object.
Status Optional
Datatype data.enumerated
Legal values are:
add
this declaration is added to the current definitions [Default]
delete
if present already, the whole of the declaration for this object is removed from the current setup
change
this declaration changes the declaration of the same name in the current definition
replace
this declaration replaces the declaration of the same name in the current definition
Note

An ODD processor should handle the values for mode as follows:

add
the object should be created (processing any children in add mode); raise an error if an object with the same identifier already exists
replace
use this object in preference to any existing object with the same identifier, and ignore any children of that object; process any new children in replace mode
delete
do not process this object or any existing object with the same identifier; raise an error if any new children supplied
change
process this object, and process its children, and those of any existing object with the same identifier, in change mode

att.cReferencing

att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei
Membersref
AttributesAttributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
Status Optional
Datatype data.text
Note

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

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

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

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei
Memberschange orgName
AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
calendarindicates the system or calendar to which the date represented by the content of this element belongs.
Status Optional
Datatype data.pointer
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length(.) gt 0">@calendar indicates the system or calendar to which the date represented by the content of this element
belongs, but this <sch:name/> element has no textual content.</sch:assert></sch:rule>
He was born on <date calendar="#Gregorian">Feb. 22, 1732</date>
(<date calendar="#Julianwhen="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).
periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
Status Optional
Datatype data.pointer
Note

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

att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.6. Dates and Times]
Modulenamesdates
Membersatt.datable [change orgName]
AttributesAttributes
when-customsupplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace

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

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

Not all custom date formulations will have Gregorian equivalents.

The when-custom attribute and other custom dating are not contrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.

notBefore-customspecifies the earliest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
from-customindicates the starting point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
<event datingMethod="#julian"
 from-custom="1666-09-02to-custom="1666-09-05xml:id="FIRE1">

 <head>The Great Fire of London</head>
 <p>The Great Fire of London burned through a large part
   of the city of London.</p>
</event>
to-customindicates the ending point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Status Optional
Datatype data.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Datatype data.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne
eſtate, and deſcription of that Citie, written in the yeare
<date calendar="#julian"
 datingMethod="#julianwhen-custom="1598">
1598</date>. by Iohn Stow
Citizen of London.
Note

Here the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.

att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601 standard. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Modulenamesdates
Membersatt.datable [change orgName]
AttributesAttributes
when-isosupplies the value of a date or time in a standard form.
Status Optional
Datatype data.temporal.iso

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

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

All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.

He likes to be punctual. I said <q>
 <time when-iso="12">around noon</time>
</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.

notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.iso
from-isoindicates the starting point of the period in standard form.
Status Optional
Datatype data.temporal.iso
to-isoindicates the ending point of the period in standard form.
Status Optional
Datatype data.temporal.iso
Note

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

Note
If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date dur-iso="P8Dwhen-iso="2007-06-01"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei
Membersatt.datable [change orgName]
AttributesAttributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.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="#Julianwhen="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.
Status Optional
Datatype data.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
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.

att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
Moduletei
MemberssourceDesc
AttributesAttributes
defaultindicates whether or not this element is selected by default when its parent is selected.
Status Optional
Datatype data.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. [Default]
Note

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

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. [15.3. Associating Contextual Information with a Text]
Moduletei
MembersmsDesc p ref text
AttributesAttributes
declsidentifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Note

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

att.deprecated

att.deprecated provides attributes indicating how a deprecated feature will be treated in future releases.
Moduletagdocs
Membersatt.combinable [att.identified]
AttributesAttributes
validUntilprovides a date before which the construct being defined will not be removed.
Status Optional
Datatype xsd:date
Schematron

<sch:rule context="tei:*[@validUntil]">
<sch:assert test="@validUntil cast as xs:date ge current-date()">
 <sch:value-of select="if (@ident) then concat('The ',@ident) else concat('This ',local-name(.),' of ',ancestor::tei:*[@ident][1]/@ident)"/>
construct is outdated (as of <sch:value-of select="@validUntil"/>); ODD processors may ignore it, and its use is no longer supported</sch:assert>
<sch:assert role="nonfatal"
 test="@validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))">

 <sch:value-of select="if (@ident) then concat('The ',@ident) else concat('This ',local-name(.),' of ',ancestor::tei:*[@ident][1]/@ident)"/> construct becomes outdated on <sch:value-of select="@validUntil"/>
</sch:assert></sch:rule>
Note

The value of this attribute should represent a date (in standard yyyy-mm-dd format) which is later than the date on which the attribute is added to an ODD. Technically, this attribute asserts only the intent to leave a construct in future releases of the markup language being defined up to at least the specified date, and makes no assertion about what happens past that date. In practice, the expectation is that the construct will be removed from future releases of the markup language being defined sometime shortly after the validUntil date.

An ODD processor will typically not process a specification element which has a validUntil date that is in the past. An ODD processor will typically warn users about constructs which have a validUntil date that is in the future. E.g., the documentation for such a construct might include the phrase warning: deprecated in red.

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersatt.editLike [orgName]
AttributesAttributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
unitnames the unit used for the measurement Suggested values include: 1] cm(centimetres) ; 2] mm(millimetres) ; 3] in(inches) ; 4] lines; 5] chars(characters)
Status Optional
Datatype data.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
lines
lines of text
chars
(characters) characters of text
quantityspecifies the length in the units specified
Status Optional
Datatype data.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Status Optional
Datatype data.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
Status Optional
Datatype data.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement. Sample values include: 1] all; 2] most; 3] range
Status Optional
Datatype data.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Memberschange revisionDesc
AttributesAttributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated. Sample values include: 1] approved; 2] candidate; 3] cleared; 4] deprecated; 5] draft; 6] embargoed; 7] expired; 8] frozen; 9] galley; 10] proposed; 11] published; 12] recommendation; 13] submitted; 14] unfinished; 15] withdrawn
Status Optional
Datatype data.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">
 <change status="published"
  when="2010-10-21"/>

 <change status="clearedwhen="2010-10-02"/>
 <change status="embargoed"
  when="2010-08-02"/>

 <change status="frozenwhen="2010-05-01"
  who="#MSM"/>

 <change status="draftwhen="2010-03-01"
  who="#LB"/>

</revisionDesc>

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.4. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Moduletei
MembersorgName
AttributesAttributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.source (@source)
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation. Suggested values include: 1] internal; 2] external; 3] conjecture
Status Optional
Datatype 1–∞ occurrences of  data.enumeratedseparated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
Status Optional
Datatype data.xTruthValue
Default false
Note

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

Note

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

att.fragmentable

att.fragmentable groups structural elements which may be fragmented, usually as a consequence of some overlapping hierarchy.
Moduletei
Membersp
AttributesAttributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Datatype data.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) either the element is not fragmented, or no claim is made as to its completeness. [Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

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

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI biblScope change idno locusGrp orgName p pubPlace publisher ref seriesStmt sourceDesc text
AttributesAttributes att.global.rendition (@rend, @style, @rendition) att.global.responsibility (@cert, @resp)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype xsd:ID
Note

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

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

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

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

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

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

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.
Status Optional
Datatype data.pointer
<div type="bibl">
 <head>Bibliography</head>
 <listBibl xml:base="http://www.lib.ucdavis.edu/BWRP/Works/">
  <bibl>
   <author>
    <name>Landon, Letitia Elizabeth</name>
   </author>
   <ref target="LandLVowOf.sgm">
    <title>The Vow of the Peacock</title>
   </ref>
  </bibl>
  <bibl>
   <author>
    <name>Compton, Margaret Clephane</name>
   </author>
   <ref target="NortMIrene.sgm">
    <title>Irene, a Poem in Six Cantos</title>
   </ref>
  </bibl>
  <bibl>
   <author>
    <name>Taylor, Jane</name>
   </author>
   <ref target="TaylJEssay.sgm">
    <title>Essays in Rhyme on Morals and Manners</title>
   </ref>
  </bibl>
 </listBibl>
</div>
xml:spacesignals an intention about how white space should be managed by applications.
Status Optional
Datatype data.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

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

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global [TEI biblScope change idno locusGrp orgName p pubPlace publisher ref seriesStmt sourceDesc text]
AttributesAttributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
Status Optional
Datatype data.text
<head style="text-align: center; font-variant: small-caps">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>
Note

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

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

renditionpoints to a description of the rendering or presentation used for this element in the source text.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
<head rendition="#ac #sc">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi rendition="#normal">New Blazing-World</hi>.
</head>
<!-- elsewhere... -->
<rendition scheme="cssxml:id="sc">font-variant: small-caps</rendition>
<rendition scheme="cssxml:id="normal">font-variant: normal</rendition>
<rendition scheme="cssxml:id="ac">text-align: center</rendition>
Note

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

Where both rendition and rend are supplied, the latter is understood to override or complement the former.

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

att.global.responsibility

att.global.responsibility provides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global [TEI biblScope change idno locusGrp orgName p pubPlace publisher ref seriesStmt sourceDesc text]
AttributesAttributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype data.certainty
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Note

Note that a simple resp pointing to a person or organization is likely to be somewhat ambiguous with regard to the nature of the responsibility. For this reason, 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>placemakers</sic>
 <corr cert="highresp="#editor">peacemakers</corr>
</choice>: for they shall be called the children of God.
Example

<!-- in the <text> ... --><lg>
<!-- ... -->
 <l>Punkes, Panders, baſe extortionizing
   sla<choice>
   <sic>n</sic>
   <corr resp="#JENS1_transcriber">u</corr>
  </choice>es,</l>
<!-- ... -->
</lg>
<!-- in the <teiHeader> ... -->
<!-- ... -->
<respStmt xml:id="JENS1_transcriber">
 <resp when="2014">Transcriber</resp>
 <name>Janelle Jenstad</name>
</respStmt>

att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersref
AttributesAttributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
Example

In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.

<ref mimeType="application/tei+xml; charset=UTF-8"
 target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/>
Note

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

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. Referring Strings 13.3.5. Names and Nyms]
Moduletei
Membersatt.personal [orgName] pubPlace
AttributesAttributes att.canonical (@key, @ref)
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.
Status Optional
Datatype 1–∞ occurrences of  data.enumeratedseparated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Note

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

att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
Moduletei
MembersorgName
AttributesAttributes att.naming (@role, @nymRef) (att.canonical (@key, @ref))
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Datatype data.enumerated
Legal values are:
yes
the name component is spelled out in full. [Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sortspecifies the sort order of the name component in relation to others within the name.
Status Optional
Datatype data.count

att.pointing

att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.6. Simple Links and Cross-References]
Moduletei
Membersref
AttributesAttributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype data.language
Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="count(@target)">@targetLang can only be used if @target is specified.</sch:assert></sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
 <ptr target="pol/UDHR/text.xml#pol_txt_1-head"
  targetLang="pltype="tuvxml:id="pol-swh_aln_2.1.1-ptr"/>

 <ptr target="swh/UDHR/text.xml#swh_txt_1-head"
  targetLang="swtype="tuvxml:id="pol-swh_aln_2.1.2-ptr"/>

</linkGrp>

In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.

Note

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

targetspecifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated 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.

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

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

att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions [att.editLike [orgName] ]
AttributesAttributes
atLeastgives a minimum estimated value for the approximate measurement.
Status Optional
Datatype data.numeric
atMostgives a maximum estimated value for the approximate measurement.
Status Optional
Datatype data.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype data.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype data.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
Status Optional
Datatype data.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">
 <gap atLeast="1atMost="2"
  extent="one or two lettersreason="illegibleunit="chars"/>

</del> Philadelphia to the Graphic office, New York.

att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
Moduletei
Membersidno
AttributesAttributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
Status Optional
Datatype data.word
David's other principal backer, Josiah
ha-Kohen <index indexName="NAMES">
 <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
</index> b. Azarya, son of one of the last gaons of Sura was David's own first
cousin.
Note

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

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

att.source

att.source provides attributes for pointing to the source of a bibliographic reference. [3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.editLike [orgName]
AttributesAttributes
sourceprovides a pointer to the bibliographical source from which a quotation or citation is drawn.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
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>

att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.5.1. Referring Strings 3.6. Simple Links and Cross-References 3.5.5. Abbreviations and Their Expansions 3.12.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.4.4.2. RELAX NG Content Models 8.3. Elements Unique to Spoken Texts 23.3.1.4. Modification of Attribute and Attribute Value Lists]
Moduletei
Memberschange orgName ref text
AttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype data.enumerated
<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l></l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</l>
  <l></l>
 </lg>
</div>
Note

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

subtypeprovides a sub-categorization of the element, if needed
Status Optional
Datatype data.enumerated
Note

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

Schematron

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

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

Schema teiODD_LAUDATIODocument_S7: Macros

data.certainty

data.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
Declaration
data.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. For more precise indication, data.probability may be used instead or in addition.

data.count

data.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei
Used by
Declaration
data.count = xsd:nonNegativeInteger
Note

Only positive integer values (including zero) are permitted

data.duration.iso

data.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei
Used by
Declaration
data.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.

data.duration.w3c

data.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei
Used by
Declaration
data.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.

data.enumerated

data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei
Used by
Element:
Declaration
data.enumerated = data.word
Note

Attributes using this datatype must contain a single word matching the pattern defined for this datatype: for example it cannot include whitespace but may begin with digits.

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.

data.language

data.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:
Declaration
data.language = xsd:language | ""
Note

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

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

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

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

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

Examples include

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

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

data.name

data.name defines the range of attribute values expressed as an XML Name.
Moduletei
Used by
Element:
Declaration
data.name = xsd:Name
Note

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

data.namespace

data.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
Declaration
data.namespace = xsd:anyURI
Note

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

data.numeric

data.numeric defines the range of attribute values used for numeric values.
Moduletei
Used by
Declaration
data.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.

data.outputMeasurement

data.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei
Used by
Declaration
data.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
   }
Example
<figure>
 <head>The TEI Logo</head>
 <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
   background.</figDesc>
 <graphic height="600px"
  url="http://www.tei-c.org/logos/TEI-600.jpgwidth="600px"/>

</figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

data.pattern

data.pattern (regular expression pattern) defines attribute values which are expressed as a regular expression.
Moduletei
Used by
Declaration
data.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

data.pointer

data.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:
Declaration
data.pointer = xsd:anyURI
Note

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

data.probability

data.probability defines the range of attribute values expressing a probability.
Moduletei
Used by
Declaration
data.probability = xsd:double { minInclusive = "0" maxInclusive = "1" }
Note

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

data.replacement

data.replacement defines attribute values which contain a replacement template.
Moduletei
Used by
Declaration
data.replacement = text

data.temporal.iso

data.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Moduletei
Used by
Element:
Declaration
data.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

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

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

While ISO 8601 permits the use of both 00:00 and 24:00 to represent midnight, these Guidelines strongly recommend against the use of 24:00.

data.temporal.w3c

data.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
Declaration
data.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.

data.text

data.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:
Declaration
data.text = string
Note

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

data.truthValue

data.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Declaration
data.truthValue = xsd:boolean
Note

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

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

data.version

data.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei
Used by
Element:
Declaration
data.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

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

data.versionNumber

data.versionNumber defines the range of attribute values used for version numbers.
Moduletei
Used by
Declaration
data.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

data.word

data.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
Declaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
Note

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

data.xmlName

data.xmlName defines attribute values which contain an XML name.
Moduletei
Used by
Declaration
data.xmlName = xsd:NCName
Note

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

data.xTruthValue

data.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei
Used by
Declaration
data.xTruthValue = xsd:boolean | "unknown" | "inapplicable"
Note

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

macro.anyXML

macro.anyXML defines a content model within which any XML elements are permitted
Moduletagdocs
Used by
Declaration
macro.anyXML =
   element * - (tei:* | teix:egXML)
   {
      attribute * { text }*,
      ( text | macro.anyXML )*
   }

macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
Used by
Declaration
macro.paraContent =
   ( text | model.gLike | model.phrase | model.inter | model.global | lg | l )*

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
Declaration
macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )*

macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Moduletei
Used by
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Declaration
macro.specialPara =
   (
      text
    | model.gLikemodel.phrasemodel.intermodel.divPartmodel.global
   )*

macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei
Used by
Declaration
macro.xtext = ( text | model.gLike )*

7 Contact

Carolin Odebrecht,
Korpuslinguistik und Morphologie. Institut für deutsche Sprache und Linguistik, Humboldt-universität zu Berlin.
carolin.odebrecht@hu-berlin.de

LAUDATIO: Long-term Access and Usage of Deeply Annotated Information. The management and archiving of digital research data is an overlapping field for linguistics, library and information science (LIS) and computer science. These disciplines are cooperating in the LAUDATIO project. The name LAUDATIO is an abbreviation for Long-term Access and Usage of Deeply Annotated Information. The project is funded by the German Research Foundation from 2011-2014. The departments of Corpus Linguistics as well as Historical Linguistics, and the Computer and Media Service (CMS) at Humboldt-Universität zu Berlin and The National Institute for Research in Computer Science and Control (INRIA France) are project partners cooperating with the Berlin School of Library and Information Science (BSLIS).

8 Licence

The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence applies to this document.

Date: 2015-06-08