diff --git a/grobid-home/schemas/doc/Grobid_doc.html b/grobid-home/schemas/doc/Grobid_doc.html index 9c81319d37..38fb56668d 100644 --- a/grobid-home/schemas/doc/Grobid_doc.html +++ b/grobid-home/schemas/doc/Grobid_doc.html @@ -67,25 +67,25 @@ } } - -->

Grobid TEI result schemaPatrice Lopez.

Author: Patrice Lopez2024-02-08

Schema for structured documents resulting from the automatic extraction and restructuring realized by Grobid.

Schema Grobid: Elements

<abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributes
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
analysis: s
core: list p
derived-module-Grobid: trash
figures: formula table
namesdates: listObject
textstructure: div
Note

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

Example
<profileDesc>
 <abstract resp="#LB">
  <p>Good database design involves the acquisition and deployment of
     skills which have a wider relevance to the educational process. From
     a set of more or less instinctive rules of thumb a formal discipline
     or "methodology" of database design has evolved. Applying that
     methodology can be of great benefit to a very wide range of academic
     subjects: it requires fundamental skills of abstraction and
     generalisation and it provides a simple mechanism whereby complex
     ideas and information structures can be represented and manipulated,
     even without the use of a computer. </p>
 </abstract>
</profileDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <classRef key="model.divLike"/>
 </alternate>
</content>
Schema Declaration
+        -->
Grobid TEI result schemaPatrice Lopez. 
 Author: Patrice Lopez2024-02-09
Schema for structured documents resulting from the automatic extraction and restructuring realized by Grobid.
Schema Grobid: Elements
<abstract>
<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributes
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
analysis: s
core: list p
derived-module-Grobid: trash
figures: formula table
namesdates: listObject
textstructure: div
Note
This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a div within the front, as it should for a born-digital document.
Example
<profileDesc>
 <abstract resp="#LB">
  <p>Good database design involves the acquisition and deployment of
     skills which have a wider relevance to the educational process. From
     a set of more or less instinctive rules of thumb a formal discipline
     or "methodology" of database design has evolved. Applying that
     methodology can be of great benefit to a very wide range of academic
     subjects: it requires fundamental skills of abstraction and
     generalisation and it provides a simple mechanism whereby complex
     ideas and information structures can be represented and manipulated,
     even without the use of a computer. </p>
 </abstract>
</profileDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <classRef key="model.divLike"/>
 </alternate>
</content>
Schema Declaration
 element abstract
 {
    tei_att.global.attributes,
    ( tei_model.pLike | tei_model.listLike | tei_model.divLike )*
-}
<addName>
<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Frederick</forename>
 <addName type="epithet">the Great</addName>
 <roleName>Emperor of Prussia</roleName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}
<addName>
<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Frederick</forename>
 <addName type="epithet">the Great</addName>
 <roleName>Emperor of Prussia</roleName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element addName
 {
    tei_att.global.attributes,
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}
<address>
<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.addressLike model.publicationStmtPart.detail 
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence publicationStmt
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName orgName persName persPronouns region roleName settlement surname
May contain
core: addrLine ellipsis name note noteGrp postBox postCode street
figures: figure
header: idno
linking: anchor link
namesdates: addName country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
Note
This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as street, postCode etc.
Example
Using just the elements defined by the core module, an address could be represented as follows:
<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <name>Bologna</name>
 <name>Italy</name>
</address>
Example
When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name:
<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <settlement>Bologna</settlement>
 <country>Italy</country>
</address>
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL 60680</addrLine>
 <addrLine>USA</addrLine>
</address>
Example
<address>
 <country key="FR"/>
 <settlement type="city">Lyon</settlement>
 <postCode>69002</postCode>
 <district type="arrondissement">IIème</district>
 <district type="quartier">Perrache</district>
 <street>
  <num>30</num>, Cours de Verdun</street>
</address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}
<address>
<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.addressLike model.publicationStmtPart.detail 
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence publicationStmt
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName orgName persName persPronouns region roleName settlement surname
May contain
core: addrLine ellipsis lb name note noteGrp postBox postCode street
figures: figure
header: idno
linking: anchor link
namesdates: addName country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
Note
This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as street, postCode etc.
Example
Using just the elements defined by the core module, an address could be represented as follows:
<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <name>Bologna</name>
 <name>Italy</name>
</address>
Example
When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name:
<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <settlement>Bologna</settlement>
 <country>Italy</country>
</address>
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL 60680</addrLine>
 <addrLine>USA</addrLine>
</address>
Example
<address>
 <country key="FR"/>
 <settlement type="city">Lyon</settlement>
 <postCode>69002</postCode>
 <district type="arrondissement">IIème</district>
 <district type="quartier">Perrache</district>
 <street>
  <num>30</num>, Cours de Verdun</street>
</address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element address
 {
    tei_att.global.attributes,
    ( tei_model.global*, ( tei_model.addrPart, tei_model.global* )+ )
-}
<addrLine>
<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL</addrLine>
 <addrLine>60680 USA</addrLine>
</address>
Example
<addrLine>
 <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
-element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }
<affiliation>
<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
sponsor
recommend
discredit
pledged
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.addressLike model.persStateLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
If included, the name of an organization may be tagged using either the name element as above, or the more specific orgName element.
Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for
   the Humanities</name>
</affiliation>
Example
This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"
 notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation>
Example
This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.
<affiliation from="1902-01-01"
 to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}
<addrLine>
<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL</addrLine>
 <addrLine>60680 USA</addrLine>
</address>
Example
<addrLine>
 <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }
<affiliation>
<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
sponsor
recommend
discredit
pledged
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.addressLike model.persStateLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
If included, the name of an organization may be tagged using either the name element as above, or the more specific orgName element.
Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for
   the Humanities</name>
</affiliation>
Example
This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"
 notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation>
Example
This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.
<affiliation from="1902-01-01"
 to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element affiliation
 {
    tei_att.global.attributes,
@@ -96,7 +96,7 @@
    attribute type { teidata.enumerated }?,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}
<analytic>
<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
core: biblStruct
May contain
core: author date editor ptr ref title
header: availability idno
Note
May contain titles and statements of responsibility (author, editor, or other), in any order.
The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item.
Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope>377–380</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
+}
<analytic>
<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
core: biblStruct
May contain
core: author date editor ptr ref title
header: availability idno
Note
May contain titles and statements of responsibility (author, editor, or other), in any order.
The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item.
Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope>377–380</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
 element analytic
 {
    tei_att.global.attributes,
@@ -111,9 +111,9 @@
     | tei_idno
     | tei_availability
    )*
-}
<anchor>
<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]
Modulelinking
Attributes
Member of
model.milestoneLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email head hi imprint item label list name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May containEmpty element
Note
On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.
Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/>
</s>
Content model
<content>
 <empty/>
</content>
Schema Declaration
-element anchor { tei_att.global.attributes, tei_att.typed.attributes, empty }
<annotation>
<annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
Status Required
Datatype ID
targetspecifies the destination of the reference by supplying one or more URI References
Derived fromatt.pointing
Status Required
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
motivation
Status Optional
Datatype  1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
assessing
intent is to assess the target resource in some way, rather than simply make a comment about it
bookmarking
intent is to create a bookmark to the target or part thereof
classifying
intent is to classify the target in some way
commenting
intent is to comment about the target
describing
intent is to describe the target, rather than (for example) comment on it
editing
intent is to request an edit or a change to the target resource
highlighting
intent is to highlight the target resource or a segment thereof
identifying
intent is to assign an identity to the target
linking
intent is to link to a resource related to the target
moderating
intent is to assign some value or quality to the target
questioning
intent is to ask a question about the target
replying
intent is to reply to a previous statement, either an annotation or another resource
tagging
intent is to associate a tag with the target
Note
For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.
As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.
Member of
model.annotationLike
Contained by
linking: listAnnotation standOff
May contain
core: note ptr ref
header: licence revisionDesc
Example
<annotation motivation="linking"
 target="#Gallia" xml:id="ann1">
<!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and 
-             https://www.w3.org/TR/annotation-model/#agents -->
 <respStmt xml:id="fred">
  <resp>creator</resp>
  <persName>Fred Editor</persName>
 </respStmt>
 <revisionDesc>
  <change status="created"
   when="2020-05-21T13:59:00Z" who="#fred"/>
  <change status="modified"
   when="2020-05-21T19:48:00Z" who="#fred"/>
 </revisionDesc>
<!-- See https://www.w3.org/TR/annotation-model/#rights-information -->
 <licence target="http://creativecommons.org/licenses/by/3.0/"/>
<!-- Multiple bodies -->
<!-- Pointers to sections of text in the same document -->
 <ptr target="#string-range(c1p1s1,0,6)"/>
 <ptr target="#string-range(c1p1s6,19,7)"/>
</annotation>
Example
<annotation motivation="commenting"
 target="#line1" xml:id="TheCorrectTitle">
 <note>The correct title of this specification, and the correct full name of XML, is
   "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.
   However, the abbreviation "XML" is not only correct but, appearing as it does in the title
   of the specification, an official name of the Extensible Markup Language. </note>
</annotation>
Content model
<content>
 <sequence>
  <elementRef key="respStmt"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="revisionDesc"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="licence"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.annotationPart.body"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
+}
<anchor>
<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]
Modulelinking
Attributes
Member of
model.milestoneLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email gloss head hi imprint item label list name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May containEmpty element
Note
On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.
Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/>
</s>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+element anchor { tei_att.global.attributes, tei_att.typed.attributes, empty }
<annotation>
<annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
Status Required
Datatype ID
targetspecifies the destination of the reference by supplying one or more URI References
Derived fromatt.pointing
Status Required
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
motivation
Status Optional
Datatype  1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
assessing
intent is to assess the target resource in some way, rather than simply make a comment about it
bookmarking
intent is to create a bookmark to the target or part thereof
classifying
intent is to classify the target in some way
commenting
intent is to comment about the target
describing
intent is to describe the target, rather than (for example) comment on it
editing
intent is to request an edit or a change to the target resource
highlighting
intent is to highlight the target resource or a segment thereof
identifying
intent is to assign an identity to the target
linking
intent is to link to a resource related to the target
moderating
intent is to assign some value or quality to the target
questioning
intent is to ask a question about the target
replying
intent is to reply to a previous statement, either an annotation or another resource
tagging
intent is to associate a tag with the target
Note
For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.
As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.
Member of
model.annotationLike
Contained by
linking: listAnnotation standOff
May contain
core: note ptr ref
header: licence revisionDesc
Example
<annotation motivation="linking"
 target="#Gallia" xml:id="ann1">
<!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and 
+             https://www.w3.org/TR/annotation-model/#agents -->
 <respStmt xml:id="fred">
  <resp>creator</resp>
  <persName>Fred Editor</persName>
 </respStmt>
 <revisionDesc>
  <change status="created"
   when="2020-05-21T13:59:00Z" who="#fred"/>
  <change status="modified"
   when="2020-05-21T19:48:00Z" who="#fred"/>
 </revisionDesc>
<!-- See https://www.w3.org/TR/annotation-model/#rights-information -->
 <licence target="http://creativecommons.org/licenses/by/3.0/"/>
<!-- Multiple bodies -->
<!-- Pointers to sections of text in the same document -->
 <ptr target="#string-range(c1p1s1,0,6)"/>
 <ptr target="#string-range(c1p1s6,19,7)"/>
</annotation>
Example
<annotation motivation="commenting"
 target="#line1" xml:id="TheCorrectTitle">
 <note>The correct title of this specification, and the correct full name of XML, is
   "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.
   However, the abbreviation "XML" is not only correct but, appearing as it does in the title
   of the specification, an official name of the Extensible Markup Language. </note>
</annotation>
Content model
<content>
 <sequence>
  <elementRef key="respStmt"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="revisionDesc"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="licence"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.annotationPart.body"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
 element annotation
 {
    tei_att.global.attribute.coords,
@@ -169,8 +169,8 @@
       tei_licence*,
       tei_model.annotationPart.body*
    )
-}
<appInfo>
<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader
Attributes
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>
 <application ident="Xaira" version="1.24">
  <label>XAIRA Indexer</label>
  <ptr target="#P1"/>
 </application>
</appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
-element appInfo { tei_att.global.attributes, tei_model.applicationLike+ }
<application>
<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
identsupplies an identifier for the application, independent of its version number or display name.
Status Required
Datatype teidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
Status Required
Datatype token
Member of
model.applicationLike
Contained by
header: appInfo
May contain
analysis: s
core: desc label p ptr ref
derived-module-Grobid: trash
figures: formula
Example
<appInfo>
 <application ident="ImageMarkupTool1"
  notAfter="2006-06-01" version="1.5">
  <label>Image Markup Tool</label>
  <ptr target="#P1"/>
  <ptr target="#P2"/>
 </application>
</appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two ptr elements.
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.labelLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.ptrLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
+}
<appInfo>
<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader
Attributes
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>
 <application ident="Xaira" version="1.24">
  <label>XAIRA Indexer</label>
  <ptr target="#P1"/>
 </application>
</appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
+element appInfo { tei_att.global.attributes, tei_model.applicationLike+ }
<application>
<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
identsupplies an identifier for the application, independent of its version number or display name.
Status Required
Datatype teidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
Status Required
Datatype token
Member of
model.applicationLike
Contained by
header: appInfo
May contain
analysis: s
core: desc label p ptr ref
derived-module-Grobid: trash
figures: formula
Example
<appInfo>
 <application ident="ImageMarkupTool1"
  notAfter="2006-06-01" version="1.5">
  <label>Image Markup Tool</label>
  <ptr target="#P1"/>
  <ptr target="#P2"/>
 </application>
</appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two ptr elements.
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.labelLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.ptrLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
 element application
 {
    tei_att.global.attributes,
@@ -180,7 +180,7 @@
    attribute ident { teidata.name },
    attribute version { token { pattern = "[0-9a-zA-Z\.\-_]+" } },
    ( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
-}
<author>
<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.respLike
Contained by
core: analytic bibl monogr
header: editionStmt titleStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.
In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.
Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.
Example
<author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
 <persName>Beaumont, Francis</persName> and
<persName>John Fletcher</persName>
</author>
<author>
 <orgName key="BBC">British Broadcasting
   Corporation</orgName>: Radio 3 Network
</author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}
<author>
<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.respLike
Contained by
core: analytic bibl monogr
header: editionStmt titleStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.
In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.
Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.
Example
<author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
 <persName>Beaumont, Francis</persName> and
<persName>John Fletcher</persName>
</author>
<author>
 <orgName key="BBC">British Broadcasting
   Corporation</orgName>: Radio 3 Network
</author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element author
 {
    tei_att.global.attributes,
@@ -188,7 +188,7 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}
<availability>
<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived fromatt.global.responsibility
Status Optional
Datatype string
Legal values are:
authors
Copyrights owner of the document are the authors
publisher
Copyrights owner of the document is the publisher
status(status) supplies a code identifying the current availability of the text.
Status Optional
Datatype teidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
model.biblPart model.publicationStmtPart.detail 
Contained by
core: analytic bibl monogr series
header: publicationStmt
May contain
analysis: s
core: p
derived-module-Grobid: trash
figures: formula
header: licence
Note
A consistent format should be adopted
Example
<availability status="restricted">
 <p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
 <p>In the public domain</p>
</availability>
<availability status="restricted">
 <p>Available under licence from the publishers.</p>
</availability>
Example
<availability>
 <licence target="http://opensource.org/licenses/MIT">
  <p>The MIT License
     applies to this document.</p>
  <p>Copyright (C) 2011 by The University of Victoria</p>
  <p>Permission is hereby granted, free of charge, to any person obtaining a copy
     of this software and associated documentation files (the "Software"), to deal
     in the Software without restriction, including without limitation the rights
     to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     copies of the Software, and to permit persons to whom the Software is
     furnished to do so, subject to the following conditions:</p>
  <p>The above copyright notice and this permission notice shall be included in
     all copies or substantial portions of the Software.</p>
  <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
     IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
     FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
     AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
     THE SOFTWARE.</p>
 </licence>
</availability>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
Schema Declaration
+}
<availability>
<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived fromatt.global.responsibility
Status Optional
Datatype string
Legal values are:
authors
Copyrights owner of the document are the authors
publisher
Copyrights owner of the document is the publisher
status(status) supplies a code identifying the current availability of the text.
Status Optional
Datatype teidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
model.biblPart model.publicationStmtPart.detail 
Contained by
core: analytic bibl monogr series
header: publicationStmt
May contain
analysis: s
core: p
derived-module-Grobid: trash
figures: formula
header: licence
Note
A consistent format should be adopted
Example
<availability status="restricted">
 <p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
 <p>In the public domain</p>
</availability>
<availability status="restricted">
 <p>Available under licence from the publishers.</p>
</availability>
Example
<availability>
 <licence target="http://opensource.org/licenses/MIT">
  <p>The MIT License
     applies to this document.</p>
  <p>Copyright (C) 2011 by The University of Victoria</p>
  <p>Permission is hereby granted, free of charge, to any person obtaining a copy
     of this software and associated documentation files (the "Software"), to deal
     in the Software without restriction, including without limitation the rights
     to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     copies of the Software, and to permit persons to whom the Software is
     furnished to do so, subject to the following conditions:</p>
  <p>The above copyright notice and this permission notice shall be included in
     all copies or substantial portions of the Software.</p>
  <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
     IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
     FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
     AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
     THE SOFTWARE.</p>
 </licence>
</availability>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
Schema Declaration
 element availability
 {
    tei_att.global.attribute.coords,
@@ -217,7 +217,7 @@
    attribute resp { "authors" | "publisher" }?,
    attribute status { "free" | "unknown" | "restricted" }?,
    ( tei_model.availabilityPart | tei_model.pLike )+
-}
<back>
<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
analysis: s
core: ellipsis head list listBibl note noteGrp p
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Note
Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical.
Example
<back>
 <div type="appendix">
  <head>The Golden Dream or, the Ingenuous Confession</head>
  <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets
     and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she
     had like to have been, too fond of Money 
<!-- .... -->
  </p>
 </div>
<!-- ... -->
 <div type="epistle">
  <head>A letter from the Printer, which he desires may be inserted</head>
  <salute>Sir.</salute>
  <p>I have done with your Copy, so you may return it to the Vatican, if you please;
  
<!-- ... -->
  </p>
 </div>
 <div type="advert">
  <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
     Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
  <list>
   <item n="1">The Christmas Box, Price 1d.</item>
   <item n="2">The History of Giles Gingerbread, 1d.</item>
<!-- ... -->
   <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
       10 Vol, Pr. bound 1l.</item>
  </list>
 </div>
 <div type="advert">
  <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.
     Paul's Church-Yard.</head>
  <list>
   <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.
       6d</item>
   <item n="2">Dr. Hooper's Female Pills, 1s.</item>
<!-- ... -->
  </list>
 </div>
</back>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0">
   <classRef key="model.divBottomPart"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}
<back>
<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
analysis: s
core: ellipsis head lb list listBibl note noteGrp p
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Note
Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical.
Example
<back>
 <div type="appendix">
  <head>The Golden Dream or, the Ingenuous Confession</head>
  <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets
     and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she
     had like to have been, too fond of Money 
<!-- .... -->
  </p>
 </div>
<!-- ... -->
 <div type="epistle">
  <head>A letter from the Printer, which he desires may be inserted</head>
  <salute>Sir.</salute>
  <p>I have done with your Copy, so you may return it to the Vatican, if you please;
  
<!-- ... -->
  </p>
 </div>
 <div type="advert">
  <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
     Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
  <list>
   <item n="1">The Christmas Box, Price 1d.</item>
   <item n="2">The History of Giles Gingerbread, 1d.</item>
<!-- ... -->
   <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
       10 Vol, Pr. bound 1l.</item>
  </list>
 </div>
 <div type="advert">
  <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.
     Paul's Church-Yard.</head>
  <list>
   <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.
       6d</item>
   <item n="2">Dr. Hooper's Female Pills, 1s.</item>
<!-- ... -->
  </list>
 </div>
</back>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0">
   <classRef key="model.divBottomPart"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element back
 {
    tei_att.global.attributes,
@@ -245,7 +245,7 @@
          ( tei_model.divBottomPart | tei_model.global )*
       )?
    )
-}
<bibl>
<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike model.biblPart
Contained by
core: bibl desc head hi item listBibl meeting note p ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: body div
May contain
analysis: s
core: address author bibl biblScope date editor ellipsis email hi meeting name note noteGrp ptr pubPlace publisher ref series term title unit
figures: figure
header: availability edition idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectIdentifier objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Contains phrase-level elements, together with any combination of elements from the model.biblPart class
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
 1990)</bibl>
Example
<bibl>
 <title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
 <date>1968</date>. 
</bibl>
Example
<bibl subtype="book_chapter" type="article"
 xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
+}
<bibl>
<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike model.biblPart
Contained by
core: bibl desc head hi item listBibl meeting note p quote ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: body div
May contain
analysis: s
core: address author bibl biblScope date editor ellipsis email gloss hi lb meeting name note noteGrp ptr pubPlace publisher ref series term title unit
figures: figure
header: availability edition idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectIdentifier objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
Contains phrase-level elements, together with any combination of elements from the model.biblPart class
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
 1990)</bibl>
Example
<bibl>
 <title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
 <date>1968</date>. 
</bibl>
Example
<bibl subtype="book_chapter" type="article"
 xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
 element bibl
 {
    tei_att.global.attributes,
@@ -264,13 +264,13 @@
     | tei_model.biblPart
     | tei_model.global
    )*
-}
<biblScope>
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
model.imprintPart 
Contained by
core: bibl imprint monogr series
header: seriesStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.
It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.
Example
<biblScope>pp 12–34</biblScope>
<biblScope from="12" to="34" unit="page"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}
<biblScope>
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
model.imprintPart 
Contained by
core: bibl imprint monogr series
header: seriesStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.
It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.
Example
<biblScope>pp 12–34</biblScope>
<biblScope from="12" to="34" unit="page"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element biblScope
 {
    tei_att.global.attributes,
    tei_att.citing.attributes,
    tei_macro.phraseSeq
-}
<biblStruct>
<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike
Contained by
core: desc head hi item listBibl meeting note p ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: body div
May contain
core: analytic monogr note noteGrp ptr ref series
header: idno
Example
<biblStruct>
 <monogr>
  <author>Blain, Virginia</author>
  <author>Clements, Patricia</author>
  <author>Grundy, Isobel</author>
  <title>The Feminist Companion to Literature in English: women writers from the middle ages
     to the present</title>
  <edition>first edition</edition>
  <imprint>
   <publisher>Yale University Press</publisher>
   <pubPlace>New Haven and London</pubPlace>
   <date>1990</date>
  </imprint>
 </monogr>
</biblStruct>
Example
<biblStruct type="newspaper">
 <analytic>
  <author>
   <forename>David</forename>
   <surname>Barstow</surname>
  </author>
  <author>
   <forename>Susanne</forename>
   <surname>Craig</surname>
  </author>
  <author>
   <forename>Russ</forename>
   <surname>Buettner</surname>
  </author>
  <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
  <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
 </analytic>
 <monogr>
  <title level="j">The New York Times</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>A. G. Sulzberger</publisher>
   <date when="2018-10-03">Wednesday, October 3, 2018</date>
  </imprint>
  <biblScope unit="volume">CLXVIII</biblScope>
  <biblScope unit="issue">58,104</biblScope>
  <biblScope unit="page">1</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="analytic"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
   <elementRef key="idno"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
+}
<biblStruct>
<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike
Contained by
core: desc head hi item listBibl meeting note p quote ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: body div
May contain
core: analytic monogr note noteGrp ptr ref series
header: idno
Example
<biblStruct>
 <monogr>
  <author>Blain, Virginia</author>
  <author>Clements, Patricia</author>
  <author>Grundy, Isobel</author>
  <title>The Feminist Companion to Literature in English: women writers from the middle ages
     to the present</title>
  <edition>first edition</edition>
  <imprint>
   <publisher>Yale University Press</publisher>
   <pubPlace>New Haven and London</pubPlace>
   <date>1990</date>
  </imprint>
 </monogr>
</biblStruct>
Example
<biblStruct type="newspaper">
 <analytic>
  <author>
   <forename>David</forename>
   <surname>Barstow</surname>
  </author>
  <author>
   <forename>Susanne</forename>
   <surname>Craig</surname>
  </author>
  <author>
   <forename>Russ</forename>
   <surname>Buettner</surname>
  </author>
  <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
  <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
 </analytic>
 <monogr>
  <title level="j">The New York Times</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>A. G. Sulzberger</publisher>
   <date when="2018-10-03">Wednesday, October 3, 2018</date>
  </imprint>
  <biblScope unit="volume">CLXVIII</biblScope>
  <biblScope unit="issue">58,104</biblScope>
  <biblScope unit="page">1</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="analytic"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
   <elementRef key="idno"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
 element biblStruct
 {
    tei_att.global.attributes,
@@ -289,7 +289,7 @@
        | tei_idno
       )*
    )
-}
<body>
<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
analysis: s
core: bibl biblStruct desc ellipsis head label list listBibl meeting note noteGrp p
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Example
<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.divLike"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.div1Like"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}
<body>
<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
analysis: s
core: bibl biblStruct desc ellipsis head label lb list listBibl meeting note noteGrp p quote
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Example
<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.divLike"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.div1Like"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element body
 {
    tei_att.global.attributes,
@@ -317,13 +317,13 @@
       ),
       ( tei_model.divBottom, tei_model.global* )*
    )
-}
<cell>
<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
Modulefigures
Attributes
Contained by
figures: row
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp p ptr ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<row>
 <cell role="label">General conduct</cell>
 <cell role="data">Not satisfactory, on account of his great unpunctuality
   and inattention to duties</cell>
</row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
+}
<cell>
<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
Modulefigures
Attributes
Contained by
figures: row
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<row>
 <cell role="label">General conduct</cell>
 <cell role="data">Not satisfactory, on account of his great unpunctuality
   and inattention to duties</cell>
</row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
 element cell
 {
    tei_att.global.attributes,
    tei_att.tableDecoration.attributes,
    tei_macro.specialPara
-}
<change>
<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
target(target) points to one or more elements that belong to this change.
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp p ptr ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.
It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.
Example
<titleStmt>
 <title> ... </title>
 <editor xml:id="LDB">Lou Burnard</editor>
 <respStmt xml:id="BZ">
  <resp>copy editing</resp>
  <name>Brett Zamir</name>
 </respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
 <change status="public" when="2008-02-02"
  who="#BZ">Finished chapter 23</change>
 <change status="draft" when="2008-01-02"
  who="#BZ">Finished chapter 2</change>
 <change n="P2.2" when="1991-12-21"
  who="#LDB">Added examples to section 3</change>
 <change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc>
Example
<profileDesc>
 <creation>
  <listChange>
   <change xml:id="DRAFT1">First draft in pencil</change>
   <change notBefore="1880-12-09"
    xml:id="DRAFT2">First revision, mostly
       using green ink</change>
   <change notBefore="1881-02-13"
    xml:id="DRAFT3">Final corrections as
       supplied to printer.</change>
  </listChange>
 </creation>
</profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
+}
<change>
<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
target(target) points to one or more elements that belong to this change.
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.
It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.
Example
<titleStmt>
 <title> ... </title>
 <editor xml:id="LDB">Lou Burnard</editor>
 <respStmt xml:id="BZ">
  <resp>copy editing</resp>
  <name>Brett Zamir</name>
 </respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
 <change status="public" when="2008-02-02"
  who="#BZ">Finished chapter 23</change>
 <change status="draft" when="2008-01-02"
  who="#BZ">Finished chapter 2</change>
 <change n="P2.2" when="1991-12-21"
  who="#LDB">Added examples to section 3</change>
 <change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc>
Example
<profileDesc>
 <creation>
  <listChange>
   <change xml:id="DRAFT1">First draft in pencil</change>
   <change notBefore="1880-12-09"
    xml:id="DRAFT2">First revision, mostly
       using green ink</change>
   <change notBefore="1881-02-13"
    xml:id="DRAFT3">Final corrections as
       supplied to printer.</change>
  </listChange>
 </creation>
</profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
 element change
 {
    tei_att.ascribed.attributes,
@@ -334,14 +334,14 @@
    attribute calendar { list { teidata.pointer+ } }?,
    attribute target { list { teidata.pointer+ } }?,
    tei_macro.specialPara
-}
<citeData>
<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Moduleheader
Attributes
property(property) A URI indicating a property definition.
Status Required
Datatype teidata.pointer
Contained by
header: citeStructure
May containEmpty element
Example
<citeStructure match="//body/div"
 unit="book" use="@n">
 <citeData property="http://purl.org/dc/terms/title"
  use="head"/>
</citeStructure>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+}
<citeData>
<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Moduleheader
Attributes
property(property) A URI indicating a property definition.
Status Required
Datatype teidata.pointer
Contained by
header: citeStructure
May containEmpty element
Example
<citeStructure match="//body/div"
 unit="book" use="@n">
 <citeData property="http://purl.org/dc/terms/title"
  use="head"/>
</citeStructure>
Content model
<content>
 <empty/>
</content>
Schema Declaration
 element citeData
 {
    tei_att.global.attributes,
    tei_att.citeStructurePart.attributes,
    attribute property { teidata.pointer },
    empty
-}
<citeStructure>
<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Moduleheader
Attributes
delim(delimiter) supplies a delimiting string preceding the structural component.
Status Optional
Datatype string
Note
delim must contain at least one character.
match(match) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a citeStructure without a citeStructure parent must be an absolute XPath. If it is relative, its context is set by the match of the parent citeStructure.
Status Required
Datatype teidata.xpath
Schematron

<sch:rule context="tei:citeStructure[not(parent::tei:citeStructure)]">
<sch:assert test="starts-with(@match,'/')">An XPath in @match on the outer <sch:name/> must start with '/'.</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:citeStructure[parent::tei:citeStructure]">
<sch:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <sch:name/>.</sch:assert>
</sch:rule>
unit(unit) describes the structural unit indicated by the citeStructure.
Status Optional
Datatype teidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
header: citeStructure
May contain
core: desc
header: citeData citeStructure
Example
<citeStructure match="//body/div"
 unit="book" use="@n">
 <citeStructure delim=" " match="div"
  unit="chapter" use="position()">
  <citeStructure delim=":" match="div"
   unit="verse" use="position()"/>
 </citeStructure>
</citeStructure>
Content model
<content>
 <sequence>
  <elementRef key="citeData"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="citeStructure"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.descLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
+}
<citeStructure>
<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Moduleheader
Attributes
delim(delimiter) supplies a delimiting string preceding the structural component.
Status Optional
Datatype string
Note
delim must contain at least one character.
match(match) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a citeStructure without a citeStructure parent must be an absolute XPath. If it is relative, its context is set by the match of the parent citeStructure.
Status Required
Datatype teidata.xpath
Schematron

<sch:rule context="tei:citeStructure[not(parent::tei:citeStructure)]">
<sch:assert test="starts-with(@match,'/')">An XPath in @match on the outer <sch:name/> must start with '/'.</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:citeStructure[parent::tei:citeStructure]">
<sch:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <sch:name/>.</sch:assert>
</sch:rule>
unit(unit) describes the structural unit indicated by the citeStructure.
Status Optional
Datatype teidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
header: citeStructure
May contain
core: desc
header: citeData citeStructure
Example
<citeStructure match="//body/div"
 unit="book" use="@n">
 <citeStructure delim=" " match="div"
  unit="chapter" use="position()">
  <citeStructure delim=":" match="div"
   unit="verse" use="position()"/>
 </citeStructure>
</citeStructure>
Content model
<content>
 <sequence>
  <elementRef key="citeData"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="citeStructure"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.descLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
 element citeStructure
 {
    tei_att.global.attributes,
@@ -350,13 +350,13 @@
    attribute match { teidata.xpath },
    attribute unit { teidata.enumerated }?,
    ( tei_citeData*, tei_citeStructure*, tei_model.descLike* )
-}
<classCode>
<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
Status Required
Datatype teidata.pointer
Contained by
core: imprint
header: textClass
May contain
core: address date ellipsis email hi name note noteGrp ptr ref term title unit
figures: figure
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
+}
<classCode>
<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
Status Required
Datatype teidata.pointer
Contained by
core: imprint
header: textClass
May contain
core: address date ellipsis email gloss hi lb name note noteGrp ptr ref term title unit
figures: figure
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
 element classCode
 {
    tei_att.global.attributes,
    attribute scheme { teidata.pointer },
    tei_macro.phraseSeq.limited
-}
<conversion>
<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
Status Required
Datatype teidata.pointer
toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
Status Required
Datatype teidata.pointer
Contained by
header: unitDef
May containEmpty element
Note
The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.
Example
<conversion formula="$fromUnit * 12"
 from="1707" fromUnit="#shilling" to="1971"
 toUnit="#pence"/>
Example
<conversion formula="$fromUnit * 20"
 from="1701" fromUnit="#pound" to="1971"
 toUnit="#shilling"/>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+}
<conversion>
<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
Status Required
Datatype teidata.pointer
toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
Status Required
Datatype teidata.pointer
Contained by
header: unitDef
May containEmpty element
Note
The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.
Example
<conversion formula="$fromUnit * 12"
 from="1707" fromUnit="#shilling" to="1971"
 toUnit="#pence"/>
Example
<conversion formula="$fromUnit * 20"
 from="1701" fromUnit="#pound" to="1971"
 toUnit="#shilling"/>
Content model
<content>
 <empty/>
</content>
Schema Declaration
 element conversion
 {
    tei_att.global.attributes,
@@ -367,7 +367,7 @@
    attribute fromUnit { teidata.pointer },
    attribute toUnit { teidata.pointer },
    empty
-}
<correspAction>
<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
typedescribes the nature of the action.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
model.correspDescPart
Contained by
header: correspDesc
May contain
analysis: s
core: address date email name note noteGrp p
derived-module-Grobid: trash
figures: formula
header: idno
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
Example
<correspAction type="sent">
 <persName>Adelbert von Chamisso</persName>
 <settlement>Vertus</settlement>
 <date when="1807-01-29"/>
</correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
+}
<correspAction>
<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
typedescribes the nature of the action.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
model.correspDescPart
Contained by
header: correspDesc
May contain
analysis: s
core: address date email name note noteGrp p
derived-module-Grobid: trash
figures: formula
header: idno
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
Example
<correspAction type="sent">
 <persName>Adelbert von Chamisso</persName>
 <settlement>Vertus</settlement>
 <date when="1807-01-29"/>
</correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
 element correspAction
 {
    tei_att.global.attributes,
@@ -383,12 +383,12 @@
     | teidata.enumerated
    }?,
    ( tei_model.correspActionPart+ | tei_model.pLike+ )
-}
<correspContext>
<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
model.correspDescPart
Contained by
header: correspDesc
May contain
analysis: s
core: note noteGrp p ptr ref
derived-module-Grobid: trash
figures: formula
Example
<correspContext>
 <ptr subtype="toAuthor"
  target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh" type="next"/>
 <ptr subtype="fromAuthor"
  target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen" type="prev"/>
</correspContext>
Example
<correspContext>
 <ref target="http://weber-gesamtausgabe.de/A040962"
  type="prev"> Previous letter of
 <persName>Carl Maria von Weber</persName> to
 <persName>Caroline Brandt</persName>:
 <date when="1816-12-30">December 30, 1816</date>
 </ref>
 <ref target="http://weber-gesamtausgabe.de/A041003"
  type="next"> Next letter of
 <persName>Carl Maria von Weber</persName> to
 <persName>Caroline Brandt</persName>:
 <date when="1817-01-05">January 5, 1817</date>
 </ref>
</correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
+}
<correspContext>
<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
model.correspDescPart
Contained by
header: correspDesc
May contain
analysis: s
core: note noteGrp p ptr ref
derived-module-Grobid: trash
figures: formula
Example
<correspContext>
 <ptr subtype="toAuthor"
  target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh" type="next"/>
 <ptr subtype="fromAuthor"
  target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen" type="prev"/>
</correspContext>
Example
<correspContext>
 <ref target="http://weber-gesamtausgabe.de/A040962"
  type="prev"> Previous letter of
 <persName>Carl Maria von Weber</persName> to
 <persName>Caroline Brandt</persName>:
 <date when="1816-12-30">December 30, 1816</date>
 </ref>
 <ref target="http://weber-gesamtausgabe.de/A041003"
  type="next"> Next letter of
 <persName>Carl Maria von Weber</persName> to
 <persName>Caroline Brandt</persName>:
 <date when="1817-01-05">January 5, 1817</date>
 </ref>
</correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
 element correspContext
 {
    tei_att.global.attributes,
    tei_model.correspContextPart+
-}
<correspDesc>
<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
analysis: s
core: note noteGrp p
derived-module-Grobid: trash
figures: formula
header: correspAction correspContext
Example
<correspDesc>
 <correspAction type="sent">
  <persName>Carl Maria von Weber</persName>
  <settlement>Dresden</settlement>
  <date when="1817-06-23">23 June 1817</date>
 </correspAction>
 <correspAction type="received">
  <persName>Caroline Brandt</persName>
  <settlement>Prag</settlement>
 </correspAction>
 <correspContext>
  <ref target="http://www.weber-gesamtausgabe.de/A041209"
   type="prev">Previous letter of
  <persName>Carl Maria von Weber</persName> 
     to <persName>Caroline Brandt</persName>:
  <date from="1817-06-19" to="1817-06-20">June 19/20, 1817</date>
  </ref>
  <ref target="http://www.weber-gesamtausgabe.de/A041217"
   type="next">Next letter of
  <persName>Carl Maria von Weber</persName> to
  <persName>Caroline Brandt</persName>:
  <date when="1817-06-27">June 27, 1817</date>
  </ref>
 </correspContext>
</correspDesc>
Content model
<content>
 <alternate>
  <classRef key="model.correspDescPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
+}
<correspDesc>
<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
analysis: s
core: note noteGrp p
derived-module-Grobid: trash
figures: formula
header: correspAction correspContext
Example
<correspDesc>
 <correspAction type="sent">
  <persName>Carl Maria von Weber</persName>
  <settlement>Dresden</settlement>
  <date when="1817-06-23">23 June 1817</date>
 </correspAction>
 <correspAction type="received">
  <persName>Caroline Brandt</persName>
  <settlement>Prag</settlement>
 </correspAction>
 <correspContext>
  <ref target="http://www.weber-gesamtausgabe.de/A041209"
   type="prev">Previous letter of
  <persName>Carl Maria von Weber</persName> 
     to <persName>Caroline Brandt</persName>:
  <date from="1817-06-19" to="1817-06-20">June 19/20, 1817</date>
  </ref>
  <ref target="http://www.weber-gesamtausgabe.de/A041217"
   type="next">Next letter of
  <persName>Carl Maria von Weber</persName> to
  <persName>Caroline Brandt</persName>:
  <date when="1817-06-27">June 27, 1817</date>
  </ref>
 </correspContext>
</correspDesc>
Content model
<content>
 <alternate>
  <classRef key="model.correspDescPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
 element correspDesc
 {
    tei_att.declarable.attributes,
@@ -396,7 +396,7 @@
    tei_att.global.attributes,
    tei_att.typed.attributes,
    ( tei_model.correspDescPart+ | tei_model.pLike+ )
-}
<country>
<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
The recommended source for codes to represent coded country names is ISO 3166.
Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}
<country>
<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype  1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
 systems or calendars to which the date represented by the content of this element belongs,
 but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
The recommended source for codes to represent coded country names is ISO 3166.
Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element country
 {
    tei_att.global.attributes,
@@ -405,7 +405,7 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}
<date>
<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Modulecore
Attributes
Member of
model.dateLike model.publicationStmtPart.detail
Contained by
analysis: s
core: addrLine analytic author bibl biblScope date desc editor email head hi imprint item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence publicationStmt
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day
 of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
 the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
+}
<date>
<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Modulecore
Attributes
Member of
model.dateLike model.publicationStmtPart.detail
Contained by
analysis: s
core: addrLine analytic author bibl biblScope date desc editor email gloss head hi imprint item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence publicationStmt
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day
 of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
 the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
 element date
 {
    tei_att.global.attributes,
@@ -417,14 +417,14 @@
    tei_att.typed.attributes,
    ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
 }
<desc>
<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented.  [22.4.1. Description of Components]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
deprecationInfo
(deprecation
-          information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec ident="teidata.point"
 module="tei" validUntil="2050-02-25">
 <desc type="deprecationInfo"
  versionDate="2018-09-14" xml:lang="en">Several standards bodies, including NIST in the USA,
   strongly recommend against ending the representation of a number
   with a decimal point. So instead of <q>3.</q> use either <q>3</q>
   or <q>3.0</q>.</desc>
<!-- ... -->
</dataSpec>
Member of
model.descLike model.labelLike 
Contained by
core: desc ellipsis graphic head hi item list meeting note noteGrp p ref title
figures: cell figDesc figure
header: application change citeStructure licence schemaRef unitDef
linking: listAnnotation
namesdates: listObject org state
textstructure: body div
transcr: surface
May contain
core: address bibl biblStruct date desc email hi label list listBibl name ptr ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note
When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.
Example
Example of a desc element inside a documentation element.
<dataSpec ident="teidata.point"
 module="tei">
 <desc versionDate="2010-10-17"
  xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
 <content>
  <dataRef name="token"
   restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
 </content>
<!-- ... -->
</dataSpec>
Example
Example of a desc element in a non-documentation element.
<place xml:id="KERG2">
 <placeName>Kerguelen Islands</placeName>
<!-- ... -->
 <terrain>
  <desc>antarctic tundra</desc>
 </terrain>
<!-- ... -->
</place>
SchematronA desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
 deprecation should only be present in a specification element
 that is being deprecated: that is, only an element that has a
 @validUntil attribute should have a child <desc
 type="deprecationInfo">.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
+          information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec ident="teidata.point"
 module="tei" validUntil="2050-02-25">
 <desc type="deprecationInfo"
  versionDate="2018-09-14" xml:lang="en">Several standards bodies, including NIST in the USA,
   strongly recommend against ending the representation of a number
   with a decimal point. So instead of <q>3.</q> use either <q>3</q>
   or <q>3.0</q>.</desc>
<!-- ... -->
</dataSpec>
Member of
model.descLike model.labelLike
Contained by
core: desc ellipsis graphic head hi item list meeting note noteGrp p quote ref title
figures: cell figDesc figure
header: application change citeStructure licence schemaRef unitDef
linking: listAnnotation
namesdates: listObject org state
textstructure: body div
transcr: surface
May contain
core: address bibl biblStruct date desc email gloss hi label list listBibl name ptr quote ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example

Example of a desc element inside a documentation element.

<dataSpec ident="teidata.point"
 module="tei">
 <desc versionDate="2010-10-17"
  xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
 <content>
  <dataRef name="token"
   restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
 </content>
<!-- ... -->
</dataSpec>
Example

Example of a desc element in a non-documentation element.

<place xml:id="KERG2">
 <placeName>Kerguelen Islands</placeName>
<!-- ... -->
 <terrain>
  <desc>antarctic tundra</desc>
 </terrain>
<!-- ... -->
</place>
SchematronA desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
 element desc
 {
    tei_att.global.attributes,
    tei_att.typed.attribute.subtype,
    attribute type { "deprecationInfo" | teidata.enumerated }?,
    tei_macro.limitedContent
-}

<div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
model.divLike
Contained by
figures: figDesc
header: abstract
textstructure: back body div front
May contain
analysis: s
core: bibl biblStruct desc ellipsis head label list listBibl meeting note noteGrp p
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Example
<body>
 <div type="part">
  <head>Fallacies of Authority</head>
  <p>The subject of which is Authority in various shapes, and the object, to repress all
     exercise of the reasoning faculty.</p>
  <div n="1" type="chapter">
   <head>The Nature of Authority</head>
   <p>With reference to any proposed measures having for their object the greatest
       happiness of the greatest number [...]</p>
   <div n="1.1" type="section">
    <head>Analysis of Authority</head>
    <p>What on any given occasion is the legitimate weight or influence to be attached to
         authority [...] </p>
   </div>
   <div n="1.2" type="section">
    <head>Appeal to Authority, in What Cases Fallacious.</head>
    <p>Reference to authority is open to the charge of fallacy when [...] </p>
   </div>
  </div>
 </div>
</body>
Schematron

<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
Schematron

<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <alternate maxOccurs="1"
       minOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="0">
      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
model.divLike
Contained by
figures: figDesc
header: abstract
textstructure: back body div front
May contain
analysis: s
core: bibl biblStruct desc ellipsis head label lb list listBibl meeting note noteGrp p quote
derived-module-Grobid: trash
figures: figure formula table
linking: anchor link
namesdates: listObject
textstructure: div
Example
<body>
 <div type="part">
  <head>Fallacies of Authority</head>
  <p>The subject of which is Authority in various shapes, and the object, to repress all
     exercise of the reasoning faculty.</p>
  <div n="1" type="chapter">
   <head>The Nature of Authority</head>
   <p>With reference to any proposed measures having for their object the greatest
       happiness of the greatest number [...]</p>
   <div n="1.1" type="section">
    <head>Analysis of Authority</head>
    <p>What on any given occasion is the legitimate weight or influence to be attached to
         authority [...] </p>
   </div>
   <div n="1.2" type="section">
    <head>Appeal to Authority, in What Cases Fallacious.</head>
    <p>Reference to authority is open to the charge of fallacy when [...] </p>
   </div>
  </div>
 </div>
</body>
Schematron

<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
Schematron

<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <alternate maxOccurs="1"
       minOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="0">
      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element div
 {
    tei_att.global.attributes,
@@ -448,13 +448,13 @@
          ( tei_model.divBottom, tei_model.global* )*
       )?
    )
-}

<edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
model.biblPart
Contained by
core: bibl monogr
header: editionStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
-element edition { tei_att.global.attributes, tei_macro.phraseSeq }

<editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: author editor meeting p
derived-module-Grobid: trash
figures: formula
header: edition
Example
<editionStmt>
 <edition n="S2">Students' edition</edition>
 <respStmt>
  <resp>Adapted by </resp>
  <name>Elizabeth Kirk</name>
 </respStmt>
</editionStmt>
Example
<editionStmt>
 <p>First edition, <date>Michaelmas Term, 1991.</date>
 </p>
</editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </alternate>
</content>
Schema Declaration
+}

<edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
model.biblPart
Contained by
core: bibl monogr
header: editionStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+element edition { tei_att.global.attributes, tei_macro.phraseSeq }

<editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: author editor meeting p
derived-module-Grobid: trash
figures: formula
header: edition
Example
<editionStmt>
 <edition n="S2">Students' edition</edition>
 <respStmt>
  <resp>Adapted by </resp>
  <name>Elizabeth Kirk</name>
 </respStmt>
</editionStmt>
Example
<editionStmt>
 <p>First edition, <date>Michaelmas Term, 1991.</date>
 </p>
</editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </alternate>
</content>
Schema Declaration
 element editionStmt
 {
    tei_att.global.attributes,
    ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
-}

<editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.respLike
Contained by
core: analytic bibl monogr series
header: editionStmt seriesStmt titleStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

A consistent format should be adopted.

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

Example
<editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.respLike
Contained by
core: analytic bibl monogr series
header: editionStmt seriesStmt titleStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

A consistent format should be adopted.

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

Example
<editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element editor
 {
    tei_att.global.attributes,
@@ -462,20 +462,20 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<ellipsis>

<ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
model.global.edit
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email head hi imprint item label list name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May contain
core: desc
Note

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

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

<ellipsis>

<ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
model.global.edit
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email gloss head hi imprint item label list name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May contain
core: desc
Note

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

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

<email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addressLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

<encodingDesc>

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

<email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addressLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

<encodingDesc>

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

<eventName>

<eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [13.2.4. Event Names]
Modulenamesdates
Attributes
Member of
model.nameLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<listEvent>
 <event from="1939-09-01" to="1945-09-02">
  <eventName xml:lang="de">Zweiter Weltkrieg</eventName>
  <eventName xml:lang="en">World War II</eventName>
  <idno type="GND">https://d-nb.info/gnd/4079167-1</idno>
  <idno type="Wikidata">https://www.wikidata.org/wiki/Q362</idno>
  <event from="1939-09-01" to="1939-10-06"
   xml:id="UeberfallAufPolen">
   <eventName xml:lang="de">Überfall auf Polen</eventName>
   <eventName xml:lang="en">Invasion of Poland</eventName>
   <idno type="GND">https://d-nb.info/gnd/4175002-0</idno>
   <idno type="LOC">https://id.loc.gov/authorities/sh85148341</idno>
   <listPlace type="affected">
    <place>
     <placeName xml:lang="pl">Gdańsk</placeName>
     <location>
      <geo>54.350556, 18.652778</geo>
     </location>
    </place>
   </listPlace>
  </event>
  <event from="1941-06-22" to="1945-05-09">
   <eventName xml:lang="de">Deutsch-Sowjetischer Krieg</eventName>
   <eventName xml:lang="ru">Великая Отечественная война</eventName>
   <idno type="GND">https://d-nb.info/gnd/4076906-9</idno>
   <idno type="Wikidata">https://www.wikidata.org/wiki/Q189266</idno>
  </event>
 </event>
</listEvent>
Example
<p>On <date when="1719-03-19">Monday</date>, <rs type="person">she</rs> was writing about the
<eventName ref="#SecondDefPrague">1618 Defenestration of Prague</eventName> which initiated the
<rs ref="#ThirtyYearsWar" type="event">long war</rs>.</p>
Example
<event from="2019-09-16" to="2019-09-20"
 xml:id="tei2019graz">
 <eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>
 <eventName type="short">TEI 2019</eventName>
 <note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.
   Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the
 <ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.
 </note>
 <listPerson type="LocalOrganizers">
  <person>
   <persName>
    <surname>Raunig</surname>
    <forename>Elisabeth</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Scholger</surname>
    <forename>Martina</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Scholger</surname>
    <forename>Walter</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Steiner</surname>
    <forename>Elisabeth</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Vogeler</surname>
    <forename>Georg</forename>
   </persName>
  </person>
 </listPerson>
 <place xml:lang="de">
  <placeName>Universität Graz</placeName>
  <location>
   <address>
    <addrLine>ReSoWi Gebäude</addrLine>
    <addrLine>Universitätsstraße 15</addrLine>
    <postCode>8010</postCode>
    <settlement>Graz</settlement>
    <country>Österreich</country>
   </address>
   <geo>15.451651587656 47.078215112534</geo>
  </location>
 </place>
 <listRelation>
  <relation active="#tei2019graz"
   name="P31_is_instance_of" passive="#AnnualTEIConference"
   ref="https://www.wikidata.org/wiki/Property:P31" type="CRM"/>
 </listRelation>
</event>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<eventName>

<eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [13.2.4. Event Names]
Modulenamesdates
Attributes
Member of
model.nameLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<listEvent>
 <event from="1939-09-01" to="1945-09-02">
  <eventName xml:lang="de">Zweiter Weltkrieg</eventName>
  <eventName xml:lang="en">World War II</eventName>
  <idno type="GND">https://d-nb.info/gnd/4079167-1</idno>
  <idno type="Wikidata">https://www.wikidata.org/wiki/Q362</idno>
  <event from="1939-09-01" to="1939-10-06"
   xml:id="UeberfallAufPolen">
   <eventName xml:lang="de">Überfall auf Polen</eventName>
   <eventName xml:lang="en">Invasion of Poland</eventName>
   <idno type="GND">https://d-nb.info/gnd/4175002-0</idno>
   <idno type="LOC">https://id.loc.gov/authorities/sh85148341</idno>
   <listPlace type="affected">
    <place>
     <placeName xml:lang="pl">Gdańsk</placeName>
     <location>
      <geo>54.350556, 18.652778</geo>
     </location>
    </place>
   </listPlace>
  </event>
  <event from="1941-06-22" to="1945-05-09">
   <eventName xml:lang="de">Deutsch-Sowjetischer Krieg</eventName>
   <eventName xml:lang="ru">Великая Отечественная война</eventName>
   <idno type="GND">https://d-nb.info/gnd/4076906-9</idno>
   <idno type="Wikidata">https://www.wikidata.org/wiki/Q189266</idno>
  </event>
 </event>
</listEvent>
Example
<p>On <date when="1719-03-19">Monday</date>, <rs type="person">she</rs> was writing about the
<eventName ref="#SecondDefPrague">1618 Defenestration of Prague</eventName> which initiated the
<rs ref="#ThirtyYearsWar" type="event">long war</rs>.</p>
Example
<event from="2019-09-16" to="2019-09-20"
 xml:id="tei2019graz">
 <eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>
 <eventName type="short">TEI 2019</eventName>
 <note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.
   Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the
 <ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.
 </note>
 <listPerson type="LocalOrganizers">
  <person>
   <persName>
    <surname>Raunig</surname>
    <forename>Elisabeth</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Scholger</surname>
    <forename>Martina</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Scholger</surname>
    <forename>Walter</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Steiner</surname>
    <forename>Elisabeth</forename>
   </persName>
  </person>
  <person>
   <persName>
    <surname>Vogeler</surname>
    <forename>Georg</forename>
   </persName>
  </person>
 </listPerson>
 <place xml:lang="de">
  <placeName>Universität Graz</placeName>
  <location>
   <address>
    <addrLine>ReSoWi Gebäude</addrLine>
    <addrLine>Universitätsstraße 15</addrLine>
    <postCode>8010</postCode>
    <settlement>Graz</settlement>
    <country>Österreich</country>
   </address>
   <geo>15.451651587656 47.078215112534</geo>
  </location>
 </place>
 <listRelation>
  <relation active="#tei2019graz"
   name="P31_is_instance_of" passive="#AnnualTEIConference"
   ref="https://www.wikidata.org/wiki/Property:P31" type="CRM"/>
 </listRelation>
</event>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element eventName
 {
    tei_att.global.attributes,
@@ -484,7 +484,7 @@
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
Moduletranscr
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: graphic
figures: formula
textstructure: back front
transcr: surface
Example
<facsimile>
 <graphic url="page1.png"/>
 <surface>
  <graphic url="page2-highRes.png"/>
  <graphic url="page2-lowRes.png"/>
 </surface>
 <graphic url="page3.png"/>
 <graphic url="page4.png"/>
</facsimile>
Example
<facsimile>
 <surface lrx="200" lry="300" ulx="0" uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Schematron

<sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
<sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
transcribed text should not be present within it.
</sch:report>
</sch:rule>
Content model
<content>
 <sequence>
  <elementRef key="front" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.graphicLike"/>
   <elementRef key="surface"/>
   <elementRef key="surfaceGrp"/>
  </alternate>
  <elementRef key="back" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
+}

<facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
Moduletranscr
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: graphic
figures: formula
textstructure: back front
transcr: surface
Example
<facsimile>
 <graphic url="page1.png"/>
 <surface>
  <graphic url="page2-highRes.png"/>
  <graphic url="page2-lowRes.png"/>
 </surface>
 <graphic url="page3.png"/>
 <graphic url="page4.png"/>
</facsimile>
Example
<facsimile>
 <surface lrx="200" lry="300" ulx="0" uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Schematron

<sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
<sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
transcribed text should not be present within it.
</sch:report>
</sch:rule>
Content model
<content>
 <sequence>
  <elementRef key="front" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.graphicLike"/>
   <elementRef key="surface"/>
   <elementRef key="surfaceGrp"/>
  </alternate>
  <elementRef key="back" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
 element facsimile
 {
    tei_att.global.attributes,
@@ -494,12 +494,12 @@
       ( tei_model.graphicLike | tei_surface | surfaceGrp )+,
       tei_back?
    )
-}

<figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Contained by
figures: figure
May contain
core: address bibl biblStruct date desc email hi label list listBibl name ptr ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
textstructure: div
character data
Note

This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Example
<figure>
 <graphic url="emblem1.png"/>
 <head>Emblemi d'Amore</head>
 <figDesc>A pair of naked winged cupids, each holding a
   flaming torch, in a rural setting.</figDesc>
</figure>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divLike"/>
 </alternate>
</content>
Schema Declaration
+}

<figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Contained by
figures: figure
May contain
core: address bibl biblStruct date desc email gloss hi label list listBibl name ptr quote ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
textstructure: div
character data
Note

This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Example
<figure>
 <graphic url="emblem1.png"/>
 <head>Emblemi d'Amore</head>
 <figDesc>A pair of naked winged cupids, each holding a
   flaming torch, in a rural setting.</figDesc>
</figure>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divLike"/>
 </alternate>
</content>
Schema Declaration
 element figDesc
 {
    tei_att.global.attributes,
    ( text | tei_model.limitedPhrase | tei_model.inter | tei_model.divLike )*
-}

<figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Member of
model.global
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email head hi imprint item label list name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May contain
analysis: s
core: bibl biblStruct desc ellipsis graphic head label list listBibl meeting note noteGrp p
derived-module-Grobid: trash
figures: figDesc figure formula table
linking: anchor link
namesdates: listObject
Example
<figure>
 <head>The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
 <graphic scale="0.5"
  url="http://www.example.org/fig1.png"/>
</figure>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
Schema Declaration
+}

<figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Member of
model.global
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email gloss head hi imprint item label list name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May contain
analysis: s
core: bibl biblStruct desc ellipsis graphic head label lb list listBibl meeting note noteGrp p quote
derived-module-Grobid: trash
figures: figDesc figure formula table
linking: anchor link
namesdates: listObject
Example
<figure>
 <head>The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
 <graphic scale="0.5"
  url="http://www.example.org/fig1.png"/>
</figure>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
Schema Declaration
 element figure
 {
    tei_att.global.attributes,
@@ -514,7 +514,7 @@
     | tei_model.global
     | tei_model.divBottom
    )*
-}

<fileDesc>

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

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

Example
<fileDesc>
 <titleStmt>
  <title>The shortest possible TEI document</title>
 </titleStmt>
 <publicationStmt>
  <p>Distributed as part of TEI P5</p>
 </publicationStmt>
 <sourceDesc>
  <p>No print source exists: this is an original digital text</p>
 </sourceDesc>
</fileDesc>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
Schema Declaration
+}

<fileDesc>

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

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

Example
<fileDesc>
 <titleStmt>
  <title>The shortest possible TEI document</title>
 </titleStmt>
 <publicationStmt>
  <p>Distributed as part of TEI P5</p>
 </publicationStmt>
 <sourceDesc>
  <p>No print source exists: this is an original digital text</p>
 </sourceDesc>
</fileDesc>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
Schema Declaration
 element fileDesc
 {
    tei_att.global.attributes,
@@ -529,14 +529,14 @@
       ),
       tei_sourceDesc+
    )
-}

<forename>

<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <roleName>Ex-President</roleName>
 <forename>George</forename>
 <surname>Bush</surname>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<forename>

<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <roleName>Ex-President</roleName>
 <forename>George</forename>
 <surname>Bush</surname>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element forename
 {
    tei_att.global.attributes,
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<formula>

<formula> (formula) contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Modulefigures
Attributes
Member of
model.graphicLike model.pLike
Contained by
analysis: s
core: addrLine author biblScope date editor email head hi item label name note p pubPlace publisher rb ref rt street term title unit
figures: cell figure formula table
header: abstract application availability change correspAction correspContext correspDesc edition editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front
transcr: facsimile surface
May contain
core: graphic hi label
figures: formula
character data
Example
<formula notation="mathml">
 <m:math>
  <m:mi>E</m:mi>
  <m:mo>=</m:mo>
  <m:mi>m</m:mi>
  <m:msup>
   <m:mrow>
    <m:mi>c</m:mi>
   </m:mrow>
   <m:mrow>
    <m:mn>2</m:mn>
   </m:mrow>
  </m:msup>
 </m:math>
</formula>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="label"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.hiLike"/>
  <elementRef key="mathml.math"/>
 </alternate>
</content>
Schema Declaration
+}

<formula>

<formula> (formula) contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Modulefigures
Attributes
Member of
model.graphicLike model.pLike
Contained by
analysis: s
core: addrLine author biblScope date editor email gloss head hi item label name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figure formula table
header: abstract application availability change correspAction correspContext correspDesc edition editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front
transcr: facsimile surface
May contain
core: graphic hi label
figures: formula
character data
Example
<formula notation="mathml">
 <m:math>
  <m:mi>E</m:mi>
  <m:mo>=</m:mo>
  <m:mi>m</m:mi>
  <m:msup>
   <m:mrow>
    <m:mi>c</m:mi>
   </m:mrow>
   <m:mrow>
    <m:mn>2</m:mn>
   </m:mrow>
  </m:msup>
 </m:math>
</formula>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="label"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.hiLike"/>
  <elementRef key="mathml.math"/>
 </alternate>
</content>
Schema Declaration
 element formula
 {
    tei_att.typed.attributes,
@@ -549,7 +549,7 @@
     | tei_model.hiLike
     | mathml.math
    )*
-}

<front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
analysis: s
core: ellipsis head listBibl meeting note noteGrp p
derived-module-Grobid: trash
figures: figure formula
linking: anchor link
textstructure: div
Note

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

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

<front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
transcr: facsimile
May contain
analysis: s
core: ellipsis head lb listBibl meeting note noteGrp p
derived-module-Grobid: trash
figures: figure formula
linking: anchor link
textstructure: div
Note

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

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

<gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
valuesupplies a coded value for gender identity
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

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

Member of
model.persStateLike
Contained by
namesdates: persona
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
valuesupplies a coded value for gender identity
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

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

Member of
model.persStateLike
Contained by
namesdates: persona
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element gender
 {
    tei_att.global.attributes,
@@ -585,14 +585,23 @@
    attribute calendar { list { teidata.pointer+ } }?,
    attribute value { list { teidata.gender+ } }?,
    tei_macro.phraseSeq
-}

<genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Charles</forename>
 <genName>II</genName>
</persName>
Example
<persName>
 <surname>Pitt</surname>
 <genName>the Younger</genName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Charles</forename>
 <genName>II</genName>
</persName>
Example
<persName>
 <surname>Pitt</surname>
 <genName>the Younger</genName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element genName
 {
    tei_att.global.attributes,
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
Modulecore
Attributes
Member of
model.graphicLike
Contained by
analysis: s
core: addrLine author biblScope date editor email head hi item label name note p pubPlace publisher rb ref rt street term title unit
figures: cell figure formula table
header: change edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
transcr: facsimile surface
May contain
core: desc
Note

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

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

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

<gloss>

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components]
Modulecore
Attributes
Member of
model.emphLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

The target and cRef attributes are mutually exclusive.

Example
We may define <term rend="sc" xml:id="tdpv">discoursal point of view</term> as
<gloss target="#tdpv">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+element gloss
+{
+   tei_att.global.attributes,
+   tei_att.declaring.attributes,
+   tei_att.typed.attributes,
+   tei_att.pointing.attributes,
+   tei_att.cReferencing.attributes,
+   tei_macro.phraseSeq
+}

<graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
Modulecore
Attributes
Member of
model.graphicLike
Contained by
analysis: s
core: addrLine author biblScope date editor email gloss head hi item label name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figure formula table
header: change edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
transcr: facsimile surface
May contain
core: desc
Note

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

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

Example
<figure>
 <graphic url="fig1.png"/>
 <head>Figure One: The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
</figure>
Example
<facsimile>
 <surfaceGrp n="leaf1">
  <surface>
   <graphic url="page1.png"/>
  </surface>
  <surface>
   <graphic url="page2-highRes.png"/>
   <graphic url="page2-lowRes.png"/>
  </surface>
 </surfaceGrp>
</facsimile>
Example
<facsimile>
 <surfaceGrp n="leaf1" xml:id="spi001">
  <surface xml:id="spi001r">
   <graphic subtype="thumbnail"
    type="normal" url="spi/thumb/001r.jpg"/>
   <graphic subtype="low-res" type="normal"
    url="spi/normal/lowRes/001r.jpg"/>
   <graphic subtype="high-res"
    type="normal" url="spi/normal/highRes/001r.jpg"/>
   <graphic subtype="low-res"
    type="high-contrast" url="spi/contrast/lowRes/001r.jpg"/>
   <graphic subtype="high-res"
    type="high-contrast" url="spi/contrast/highRes/001r.jpg"/>
  </surface>
  <surface xml:id="spi001v">
   <graphic subtype="thumbnail"
    type="normal" url="spi/thumb/001v.jpg"/>
   <graphic subtype="low-res" type="normal"
    url="spi/normal/lowRes/001v.jpg"/>
   <graphic subtype="high-res"
    type="normal" url="spi/normal/highRes/001v.jpg"/>
   <graphic subtype="low-res"
    type="high-contrast" url="spi/contrast/lowRes/001v.jpg"/>
   <graphic subtype="high-res"
    type="high-contrast" url="spi/contrast/highRes/001v.jpg"/>
   <zone xml:id="spi001v_detail01">
    <graphic subtype="thumbnail"
     type="normal" url="spi/thumb/001v-detail01.jpg"/>
    <graphic subtype="low-res"
     type="normal"
     url="spi/normal/lowRes/001v-detail01.jpg"/>
    <graphic subtype="high-res"
     type="normal"
     url="spi/normal/highRes/001v-detail01.jpg"/>
    <graphic subtype="low-res"
     type="high-contrast"
     url="spi/contrast/lowRes/001v-detail01.jpg"/>
    <graphic subtype="high-res"
     type="high-contrast"
     url="spi/contrast/highRes/001v-detail01.jpg"/>
   </zone>
  </surface>
 </surfaceGrp>
</facsimile>
Content model
<content>
 <classRef key="model.descLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
Schema Declaration
 element graphic
 {
    tei_att.global.attributes,
@@ -601,7 +610,7 @@
    tei_att.declaring.attributes,
    tei_att.typed.attributes,
    tei_model.descLike*
-}
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Member of
model.headLike model.pLike.front
Contained by
core: list
figures: figure table
linking: listAnnotation
namesdates: listObject object org state
textstructure: back body div front
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp ptr ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example

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

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

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

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

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

With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
 <head>Connectives</head>
 <item>above</item>
 <item>accordingly</item>
 <item>across from</item>
 <item>adjacent to</item>
 <item>again</item>
 <item>
<!-- ... -->
 </item>
</list>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
+}
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Member of
model.headLike model.pLike.front
Contained by
core: list
figures: figure table
linking: listAnnotation
namesdates: listObject object org state
textstructure: back body div front
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp ptr quote ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example

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

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

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

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

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

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

<hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
model.hiLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc formula
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp ptr ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
+}

<hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
model.hiLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc formula
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp ptr quote ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
 element hi
 {
    tei_att.global.attributes,
    tei_att.written.attributes,
    tei_macro.paraContent
-}

<idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
Attributes
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
ISBN
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike model.personPart model.publicationStmtPart.detail
Contained by
analysis: s
core: addrLine address analytic author bibl biblScope biblStruct date desc editor email head hi item label meeting monogr name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figDesc
header: change classCode correspAction edition idno licence publicationStmt seriesStmt
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
header: idno
character data
Note

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

Example
<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
 <g ref="#sym"/>345
</idno>

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

Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
Schema Declaration
+}

<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. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
Attributes
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
ISBN
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike model.personPart model.publicationStmtPart.detail
Contained by
analysis: s
core: addrLine address analytic author bibl biblScope biblStruct date desc editor email gloss head hi item label meeting monogr name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figDesc
header: change classCode correspAction edition idno licence publicationStmt seriesStmt
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
header: idno
character data
Note

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

Example
<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
 <g ref="#sym"/>345
</idno>

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

Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
Schema Declaration
 element idno
 {
    tei_att.global.attributes,
@@ -643,7 +652,7 @@
    }?,
    attribute calendar { list { teidata.pointer+ } }?,
    ( text | tei_model.gLike | tei_idno )*
-}

<imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: monogr
May contain
core: biblScope date ellipsis note noteGrp pubPlace publisher
figures: figure
header: classCode
linking: anchor link
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: monogr
May contain
core: biblScope date ellipsis lb note noteGrp pubPlace publisher
figures: figure
header: classCode
linking: anchor link
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element imprint
 {
    tei_att.global.attributes,
@@ -655,19 +664,19 @@
          tei_model.global*
       )*
    )
-}

<item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
Contained by
core: list
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp p ptr ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

May contain simple prose or a sequence of chunks.

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

Example
<list rend="numbered">
 <head>Here begin the chapter headings of Book IV</head>
 <item n="4.1">The death of Queen Clotild.</item>
 <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
 <item n="4.3">The wives and children of Lothar.</item>
 <item n="4.4">The Counts of the Bretons.</item>
 <item n="4.5">Saint Gall the Bishop.</item>
 <item n="4.6">The priest Cato.</item>
 <item> ...</item>
</list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
+}

<item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
Contained by
core: list
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

May contain simple prose or a sequence of chunks.

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

Example
<list rend="numbered">
 <head>Here begin the chapter headings of Book IV</head>
 <item n="4.1">The death of Queen Clotild.</item>
 <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
 <item n="4.3">The wives and children of Lothar.</item>
 <item n="4.4">The Counts of the Bretons.</item>
 <item n="4.5">Saint Gall the Bishop.</item>
 <item n="4.6">The priest Cato.</item>
 <item> ...</item>
</list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
 element item
 {
    tei_att.global.attributes,
    tei_att.sortable.attributes,
    tei_macro.specialPara
-}

<keywords>

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

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

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

Example
<keywords scheme="http://classificationweb.net">
 <term>Babbage, Charles</term>
 <term>Mathematicians - Great Britain - Biography</term>
</keywords>
Example
<keywords>
 <term>Fermented beverages</term>
 <term>Central Andes</term>
 <term>Schinus molle</term>
 <term>Molle beer</term>
 <term>Indigenous peoples</term>
 <term>Ethnography</term>
 <term>Archaeology</term>
</keywords>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="0">
  <textNode/>
  <elementRef key="term"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="list"/>
 </alternate>
</content>
Schema Declaration
+}

<keywords>

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

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

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

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

<label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
model.labelLike
Contained by
core: desc head hi item list meeting note p ref title
figures: cell figDesc figure formula
header: application change licence unitDef
linking: listAnnotation
namesdates: org state
textstructure: body div
transcr: surface
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

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

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

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

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

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

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

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

Example

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

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

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

If so desired the type attribute may be used to distinguish different categories of label.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
model.labelLike
Contained by
core: desc head hi item list meeting note p quote ref title
figures: cell figDesc figure formula
header: application change licence unitDef
linking: listAnnotation
namesdates: org state
textstructure: body div
transcr: surface
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

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

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

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

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

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

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

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

Example

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

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

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

If so desired the type attribute may be used to distinguish different categories of label.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element label
 {
    tei_att.global.attributes,
@@ -675,7 +684,17 @@
    tei_att.placement.attributes,
    tei_att.written.attributes,
    tei_macro.phraseSeq
-}

<licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.availabilityPart
Contained by
header: availability
linking: annotation
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp p ptr ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence>
Example
<availability>
 <licence notBefore="2013-01-01"
  target="http://creativecommons.org/licenses/by/3.0/">
  <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
     applies to this document.</p>
  <p>The licence was added on January 1, 2013.</p>
 </licence>
</availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
+}

<lb>

<lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone +Elements 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
model.milestoneLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email gloss head hi imprint item label list name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May containEmpty element
Note

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

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

Example

This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example

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

<titlePart>
 <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+element lb
+{
+   tei_att.global.attributes,
+   tei_att.typed.attributes,
+   tei_att.edition.attributes,
+   tei_att.spanning.attributes,
+   tei_att.breaking.attributes,
+   empty
+}

<licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.availabilityPart
Contained by
header: availability
linking: annotation
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence>
Example
<availability>
 <licence notBefore="2013-01-01"
  target="http://creativecommons.org/licenses/by/3.0/">
  <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
     applies to this document.</p>
  <p>The licence was added on January 1, 2013.</p>
 </licence>
</availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
 element licence
 {
    tei_att.global.attributes,
@@ -683,14 +702,14 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.specialPara
-}
<link> (link) defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements. [16.1. Links]
Modulelinking
Attributes
Member of
model.global.meta
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email head hi imprint item label list name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
linking: standOff
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May containEmpty element
Note

This element should only be used to encode associations not otherwise provided for by more specific elements.

The location of this element within a document has no significance, unless it is included within a <linkGrp>, in which case it may inherit the value of the type attribute from the value given on the <linkGrp>.

Example
<s n="1">The state Supreme Court has refused to release <rs xml:id="R1">
  <rs xml:id="R2">Rahway State Prison</rs> inmate</rs>
 <rs xml:id="R3">James Scott</rs> on bail.</s>
<s n="2">
 <rs xml:id="R4">The fighter</rs> is serving 30-40 years
for a 1975 armed robbery conviction in <rs xml:id="R5">the penitentiary</rs>.
</s>
<!-- ... -->
<linkGrp type="periphrasis">
 <link target="#R1 #R3 #R4"/>
 <link target="#R2 #R5"/>
</linkGrp>
Schematron

<sch:assert test="contains(normalize-space(@target),' ')">You must supply at least two values for @target or on <sch:name/>
</sch:assert>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+}
<link> (link) defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements. [16.1. Links]
Modulelinking
Attributes
Member of
model.global.meta
Contained by
analysis: s
core: addrLine address author bibl biblScope date editor email gloss head hi imprint item label list name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode edition licence
linking: standOff
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement surname
textstructure: back body div front text
transcr: surface
May containEmpty element
Note

This element should only be used to encode associations not otherwise provided for by more specific elements.

The location of this element within a document has no significance, unless it is included within a <linkGrp>, in which case it may inherit the value of the type attribute from the value given on the <linkGrp>.

Example
<s n="1">The state Supreme Court has refused to release <rs xml:id="R1">
  <rs xml:id="R2">Rahway State Prison</rs> inmate</rs>
 <rs xml:id="R3">James Scott</rs> on bail.</s>
<s n="2">
 <rs xml:id="R4">The fighter</rs> is serving 30-40 years
for a 1975 armed robbery conviction in <rs xml:id="R5">the penitentiary</rs>.
</s>
<!-- ... -->
<linkGrp type="periphrasis">
 <link target="#R1 #R3 #R4"/>
 <link target="#R2 #R5"/>
</linkGrp>
Schematron

<sch:assert test="contains(normalize-space(@target),' ')">You must supply at least two values for @target or on <sch:name/>
</sch:assert>
Content model
<content>
 <empty/>
</content>
Schema Declaration
 element link
 {
    tei_att.global.attributes,
    tei_att.pointing.attributes,
    tei_att.typed.attributes,
    empty
-}

<list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
type(type) describes the nature of the items in the list.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
gloss
(gloss) each list item glosses some term or concept, which is given by a label element preceding the list item.
index
(index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
(instructions) each list item is a step in a sequence of instructions, as in a recipe.
litany
(litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
(syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
Note

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

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

Member of
model.listLike
Contained by
core: desc head hi item meeting note p ref title
figures: cell figDesc figure
header: abstract change keywords licence revisionDesc sourceDesc
linking: standOff
textstructure: back body div
May contain
core: desc ellipsis head item label meeting note noteGrp
figures: figure
linking: anchor link
Note

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

Example
<list rend="numbered">
 <item>a butcher</item>
 <item>a baker</item>
 <item>a candlestick maker, with
 <list rend="bulleted">
   <item>rings on his fingers</item>
   <item>bells on his toes</item>
  </list>
 </item>
</list>
Example
<list rend="bulleted" type="syllogism">
 <item>All Cretans are liars.</item>
 <item>Epimenides is a Cretan.</item>
 <item>ERGO Epimenides is a liar.</item>
</list>
Example
<list rend="simple" type="litany">
 <item>God save us from drought.</item>
 <item>God save us from pestilence.</item>
 <item>God save us from wickedness in high places.</item>
 <item>Praise be to God.</item>
</list>
Example

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

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

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

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

<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="item"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence>
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="label"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
type(type) describes the nature of the items in the list.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
gloss
(gloss) each list item glosses some term or concept, which is given by a label element preceding the list item.
index
(index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
(instructions) each list item is a step in a sequence of instructions, as in a recipe.
litany
(litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
(syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
Note

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

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

Member of
model.listLike
Contained by
core: desc head hi item meeting note p quote ref title
figures: cell figDesc figure
header: abstract change keywords licence revisionDesc sourceDesc
linking: standOff
textstructure: back body div
May contain
core: desc ellipsis head item label lb meeting note noteGrp
figures: figure
linking: anchor link
Note

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

Example
<list rend="numbered">
 <item>a butcher</item>
 <item>a baker</item>
 <item>a candlestick maker, with
 <list rend="bulleted">
   <item>rings on his fingers</item>
   <item>bells on his toes</item>
  </list>
 </item>
</list>
Example
<list rend="bulleted" type="syllogism">
 <item>All Cretans are liars.</item>
 <item>Epimenides is a Cretan.</item>
 <item>ERGO Epimenides is a liar.</item>
</list>
Example
<list rend="simple" type="litany">
 <item>God save us from drought.</item>
 <item>God save us from pestilence.</item>
 <item>God save us from wickedness in high places.</item>
 <item>Praise be to God.</item>
</list>
Example

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

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

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

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

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

<listAnnotation>

<listAnnotation> contains a list of annotations, typically encoded as annotation, <annotationBlock>, or note, possibly organized with nested listAnnotation elements. [16.10. The standOff Container]
Modulelinking
Attributes
Member of
model.standOffPart
Contained by
linking: listAnnotation standOff
May contain
core: desc head label note
linking: annotation listAnnotation
Note

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

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

<listAnnotation>

<listAnnotation> contains a list of annotations, typically encoded as annotation, <annotationBlock>, or note, possibly organized with nested listAnnotation elements. [16.10. The standOff Container]
Modulelinking
Attributes
Member of
model.standOffPart
Contained by
linking: listAnnotation standOff
May contain
core: desc head label note
linking: annotation listAnnotation
Note

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

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

<listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike model.frontPart
Contained by
core: desc head hi item listBibl meeting note p ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: back body div front
May contain
core: bibl biblStruct listBibl
Example
<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>
Content model
<content>
 <classRef key="model.biblLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
Schema Declaration
+}

<listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore
Attributes
Member of
model.biblLike model.frontPart
Contained by
core: desc head hi item listBibl meeting note p quote ref title
figures: cell figDesc figure
header: change licence sourceDesc
linking: standOff
namesdates: object org persona state
textstructure: back body div front
May contain
core: bibl biblStruct listBibl
Example
<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>
Content model
<content>
 <classRef key="model.biblLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
Schema Declaration
 element listBibl
 {
    tei_att.global.attributes,
@@ -737,7 +756,7 @@
    tei_att.declarable.attributes,
    tei_att.typed.attributes,
    tei_model.biblLike*
-}

<listObject>

<listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [13.3.6. Objects]
Modulenamesdates
Attributes
Member of
model.listLike model.objectLike
Contained by
core: desc head hi item meeting note p ref title
figures: cell figDesc figure
header: abstract change licence sourceDesc
linking: standOff
namesdates: listObject
textstructure: back body div
May contain
core: desc head
namesdates: listObject object
Note

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

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

<listObject>

<listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [13.3.6. Objects]
Modulenamesdates
Attributes
Member of
model.listLike model.objectLike
Contained by
core: desc head hi item meeting note p quote ref title
figures: cell figDesc figure
header: abstract change licence sourceDesc
linking: standOff
namesdates: listObject
textstructure: back body div
May contain
core: desc head
namesdates: listObject object
Note

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

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

<meeting>

<meeting> contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.divWrapper model.respLike
Contained by
core: bibl list monogr
figures: figure table
header: editionStmt titleStmt
textstructure: body div front
May contain
core: address bibl biblStruct date desc email hi label list listBibl name ptr ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<div>
 <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,
   June 1998.</meeting>
 <list type="attendance">
  <head>List of Participants</head>
  <item>
   <persName>...</persName>
  </item>
  <item>
   <persName>...</persName>
  </item>
<!--...-->
 </list>
 <p>...</p>
</div>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
+}

<meeting>

<meeting> contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.divWrapper model.respLike
Contained by
core: bibl list monogr
figures: figure table
header: editionStmt titleStmt
textstructure: body div front
May contain
core: address bibl biblStruct date desc email gloss hi label list listBibl name ptr quote ref term title unit
figures: table
header: idno
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<div>
 <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,
   June 1998.</meeting>
 <list type="attendance">
  <head>List of Participants</head>
  <item>
   <persName>...</persName>
  </item>
  <item>
   <persName>...</persName>
  </item>
<!--...-->
 </list>
 <p>...</p>
</div>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
 element meeting
 {
    tei_att.global.attributes,
@@ -758,7 +777,7 @@
    tei_att.canonical.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.limitedContent
-}

<monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
core: biblStruct
May contain
core: author biblScope editor imprint meeting note noteGrp ptr ref title
header: availability edition idno
Note

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope from="377" to="380" unit="page">377–380</biblScope>
 </monogr>
</biblStruct>
Example
<biblStruct type="book">
 <monogr>
  <author>
   <persName>
    <forename>Leo Joachim</forename>
    <surname>Frachtenberg</surname>
   </persName>
  </author>
  <title level="m" type="main">Lower Umpqua Texts</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Columbia University Press</publisher>
   <date>1914</date>
  </imprint>
 </monogr>
 <series>
  <title level="s" type="main">Columbia University Contributions to
     Anthropology</title>
  <biblScope unit="volume">4</biblScope>
 </series>
</biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.respLike"/>
  <elementRef key="imprint"/>
  <elementRef key="authority"/>
  <classRef key="model.noteLike"/>
  <elementRef key="biblScope"/>
  <elementRef key="extent"/>
  <elementRef key="edition"/>
  <elementRef key="availability"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="title"/>
 </alternate>
</content>
Schema Declaration
+}

<monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
core: biblStruct
May contain
core: author biblScope editor imprint meeting note noteGrp ptr ref title
header: availability edition idno
Note

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope from="377" to="380" unit="page">377–380</biblScope>
 </monogr>
</biblStruct>
Example
<biblStruct type="book">
 <monogr>
  <author>
   <persName>
    <forename>Leo Joachim</forename>
    <surname>Frachtenberg</surname>
   </persName>
  </author>
  <title level="m" type="main">Lower Umpqua Texts</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Columbia University Press</publisher>
   <date>1914</date>
  </imprint>
 </monogr>
 <series>
  <title level="s" type="main">Columbia University Contributions to
     Anthropology</title>
  <biblScope unit="volume">4</biblScope>
 </series>
</biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.respLike"/>
  <elementRef key="imprint"/>
  <elementRef key="authority"/>
  <classRef key="model.noteLike"/>
  <elementRef key="biblScope"/>
  <elementRef key="extent"/>
  <elementRef key="edition"/>
  <elementRef key="availability"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="title"/>
 </alternate>
</content>
Schema Declaration
 element monogr
 {
    tei_att.global.attributes,
@@ -776,7 +795,7 @@
     | tei_model.ptrLike
     | tei_title
    )*
-}

<name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent model.personPart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name ref="#HOC001" type="person">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent model.personPart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name ref="#HOC001" type="person">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element name
 {
    tei_att.global.attributes,
@@ -786,7 +805,7 @@
    tei_att.typed.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Modulecore
Attributes
Member of
model.annotationLike model.annotationPart.body model.correspActionPart model.correspContextPart model.correspDescPart model.noteLike
Contained by
analysis: s
core: addrLine address author bibl biblScope biblStruct date editor email head hi imprint item label list monogr name note noteGrp p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode correspAction correspContext correspDesc edition licence notesStmt
linking: annotation listAnnotation standOff
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front text
transcr: surface
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp p ptr ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

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

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

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

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

Example

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

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="true" n="126"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann.

However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
+}

<note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Modulecore
Attributes
Member of
model.annotationLike model.annotationPart.body model.correspActionPart model.correspContextPart model.correspDescPart model.noteLike
Contained by
analysis: s
core: addrLine address author bibl biblScope biblStruct date editor email gloss head hi imprint item label list monogr name note noteGrp p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode correspAction correspContext correspDesc edition licence notesStmt
linking: annotation listAnnotation standOff
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front text
transcr: surface
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

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

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

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

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

Example

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

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="true" n="126"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann.

However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
 element note
 {
    tei_att.global.attributes,
@@ -796,7 +815,7 @@
    tei_att.written.attributes,
    tei_att.anchoring.attributes,
    tei_macro.specialPara
-}

<noteGrp>

<noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes]
Modulecore
Attributes
Member of
model.correspActionPart model.correspContextPart model.correspDescPart model.noteLike
Contained by
analysis: s
core: addrLine address author bibl biblScope biblStruct date editor email head hi imprint item label list monogr name note noteGrp p pubPlace publisher rb ref rt series street term title unit
figures: cell figure table
header: change classCode correspAction correspContext correspDesc edition licence notesStmt
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front text
transcr: surface
May contain
core: desc note noteGrp
Example

In the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:

<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus
<noteGrp>
  <note xml:lang="en">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday)
     falling on each of the quarters of the year. In the first quarter they were called Cinerum
     (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis
     (after the Exaltation of the Holy Cross, September 14th), and Luciae
     in the fourth (after the feast of St. Lucia, December 13th).
  </note>
  <note xml:lang="pl">Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota)
     przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum
     (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis
     (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae
     (po dniu św. Łucji 13 grudnia).
  </note>
 </noteGrp>
totaliter expediui.
</p>
Content model
<content>
 <sequence>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="note"/>
   <elementRef key="noteGrp"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
+}

<noteGrp>

<noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes]
Modulecore
Attributes
Member of
model.correspActionPart model.correspContextPart model.correspDescPart model.noteLike
Contained by
analysis: s
core: addrLine address author bibl biblScope biblStruct date editor email gloss head hi imprint item label list monogr name note noteGrp p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figure table
header: change classCode correspAction correspContext correspDesc edition licence notesStmt
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front text
transcr: surface
May contain
core: desc note noteGrp
Example

In the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:

<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus
<noteGrp>
  <note xml:lang="en">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday)
     falling on each of the quarters of the year. In the first quarter they were called Cinerum
     (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis
     (after the Exaltation of the Holy Cross, September 14th), and Luciae
     in the fourth (after the feast of St. Lucia, December 13th).
  </note>
  <note xml:lang="pl">Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota)
     przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum
     (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis
     (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae
     (po dniu św. Łucji 13 grudnia).
  </note>
 </noteGrp>
totaliter expediui.
</p>
Content model
<content>
 <sequence>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="note"/>
   <elementRef key="noteGrp"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
 element noteGrp
 {
    tei_att.global.attributes,
@@ -806,12 +825,12 @@
    tei_att.written.attributes,
    tei_att.anchoring.attributes,
    ( tei_desc*, ( tei_note | tei_noteGrp )+ )
-}

<notesStmt>

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

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

Example
<notesStmt>
 <note>Historical commentary provided by Mark Cohen</note>
 <note>OCR scanning done at University of Toronto</note>
</notesStmt>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.noteLike"/>
  <elementRef key="relatedItem"/>
 </alternate>
</content>
Schema Declaration
+}

<notesStmt>

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

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

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

<object>

<object> contains a description of a single identifiable physical object. [13.3.6. Objects]
Modulenamesdates
Attributes
Member of
model.objectLike
Contained by
namesdates: listObject object
May contain
analysis: s
core: bibl biblStruct head listBibl note noteGrp p
derived-module-Grobid: trash
figures: formula
linking: link
namesdates: object objectIdentifier
Note

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

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

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

<object>

<object> contains a description of a single identifiable physical object. [13.3.6. Objects]
Modulenamesdates
Attributes
Member of
model.objectLike
Contained by
namesdates: listObject object
May contain
analysis: s
core: bibl biblStruct head listBibl note noteGrp p
derived-module-Grobid: trash
figures: formula
linking: link
namesdates: object objectIdentifier
Note

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

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

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

<objectIdentifier>

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

<objectIdentifier>

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

<objectName>

<objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [13.2.5. Object Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<p>
The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
<objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
   Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<objectName>

<objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [13.2.5. Object Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<p>
The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
<objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
   Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element objectName
 {
    tei_att.datable.attributes,
@@ -852,7 +871,7 @@
    tei_att.typed.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<org>

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

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

Member of
model.personLike
Contained by
namesdates: org
May contain
analysis: s
core: bibl biblStruct desc head label listBibl name note noteGrp p ptr
derived-module-Grobid: trash
figures: formula
header: idno
linking: anchor link
namesdates: addName country eventName forename genName objectName org orgName persName persPronouns region roleName settlement state surname
Example
<org xml:id="JAMs">
 <orgName>Justified Ancients of Mummu</orgName>
 <desc>An underground anarchist collective spearheaded by
 <persName>Hagbard Celine</persName>, who fight the Illuminati
   from a golden submarine, the <name>Leif Ericson</name>
 </desc>
 <bibl>
  <author>Robert Shea</author>
  <author>Robert Anton Wilson</author>
  <title>The Illuminatus! Trilogy</title>
 </bibl>
</org>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate>
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.labelLike"/>
    <classRef key="model.nameLike"/>
    <classRef key="model.placeLike"/>
    <classRef key="model.orgPart"/>
    <classRef key="model.milestoneLike"/>
   </alternate>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.personLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
+}

<org>

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

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

Member of
model.personLike
Contained by
namesdates: org
May contain
analysis: s
core: bibl biblStruct desc head label lb listBibl name note noteGrp p ptr
derived-module-Grobid: trash
figures: formula
header: idno
linking: anchor link
namesdates: addName country eventName forename genName objectName org orgName persName persPronouns region roleName settlement state surname
Example
<org xml:id="JAMs">
 <orgName>Justified Ancients of Mummu</orgName>
 <desc>An underground anarchist collective spearheaded by
 <persName>Hagbard Celine</persName>, who fight the Illuminati
   from a golden submarine, the <name>Leif Ericson</name>
 </desc>
 <bibl>
  <author>Robert Shea</author>
  <author>Robert Anton Wilson</author>
  <title>The Illuminatus! Trilogy</title>
 </bibl>
</org>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate>
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.labelLike"/>
    <classRef key="model.nameLike"/>
    <classRef key="model.placeLike"/>
    <classRef key="model.orgPart"/>
    <classRef key="model.milestoneLike"/>
   </alternate>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.personLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
 element org
 {
    tei_att.global.attributes,
@@ -881,7 +900,7 @@
       )*,
       tei_model.personLike*
    )
-}

<orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
 <placeName key="PEN">Pennsyla.</placeName> Abolition Society
</orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
 <placeName key="PEN">Pennsyla.</placeName> Abolition Society
</orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element orgName
 {
    tei_att.global.attributes,
@@ -891,7 +910,7 @@
    tei_att.typed.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
model.pLike
Contained by
core: item note
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: object org persona state
textstructure: back body div front
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp ptr ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
   done?</q>
</p>
<p>
 <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
 <q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
 <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p>
Schematron

<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText +}

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
model.pLike
Contained by
core: item note quote
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: object org persona state
textstructure: back body div front
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp ptr quote ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
   done?</q>
</p>
<p>
 <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
 <q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
 <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p>
Schematron

<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
</sch:report>
Schematron

<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText @@ -903,7 +922,7 @@ tei_att.fragmentable.attributes, tei_att.written.attributes, tei_macro.paraContent -}

<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
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent model.persStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Edward</forename>
 <forename>George</forename>
 <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
 <placeName>Knebworth</placeName>
 </roleName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<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
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.nameLike.agent model.persStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<persName>
 <forename>Edward</forename>
 <forename>George</forename>
 <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
 <placeName>Knebworth</placeName>
 </roleName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element persName
 {
    tei_att.global.attributes,
@@ -913,7 +932,7 @@
    tei_att.typed.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<persona>

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

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

sexspecifies the sex of the persona.
Status Optional
Datatype 1–∞ occurrences of teidata.sex separated by whitespace
Note

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

genderspecifies the gender of the persona.
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

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

agespecifies an age group for the persona.
Status Optional
Datatype teidata.enumerated
Note

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

Member of
model.persStateLike
Contained by
namesdates: persona
May contain
analysis: s
core: bibl biblStruct ellipsis listBibl name note noteGrp p
derived-module-Grobid: trash
figures: figure formula
header: idno
linking: anchor link
namesdates: affiliation gender persName persPronouns persona state
Note

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

Example
<person age="adult" sex="M">
 <persona sex="M">
  <persName>Dr Henry Jekyll</persName>
 </persona>
 <persona age="youth" sex="M">
  <persName>Edward Hyde</persName>
 </persona>
</person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
Schema Declaration
+}

<persona>

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

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

sexspecifies the sex of the persona.
Status Optional
Datatype 1–∞ occurrences of teidata.sex separated by whitespace
Note

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

genderspecifies the gender of the persona.
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

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

agespecifies an age group for the persona.
Status Optional
Datatype teidata.enumerated
Note

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

Member of
model.persStateLike
Contained by
namesdates: persona
May contain
analysis: s
core: bibl biblStruct ellipsis lb listBibl name note noteGrp p
derived-module-Grobid: trash
figures: figure formula
header: idno
linking: anchor link
namesdates: affiliation gender persName persPronouns persona state
Note

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

Example
<person age="adult" sex="M">
 <persona sex="M">
  <persName>Dr Henry Jekyll</persName>
 </persona>
 <persona age="youth" sex="M">
  <persName>Edward Hyde</persName>
 </persona>
</person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
Schema Declaration
 element persona
 {
    tei_att.global.attributes,
@@ -924,7 +943,7 @@
    attribute gender { list { teidata.gender+ } }?,
    attribute age { teidata.enumerated }?,
    ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
-}

<persPronouns>

<persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
evidence(evidence) indicates support for the listed personal pronouns.
Status Recommended
Datatype teidata.enumerated
Suggested values include:
conjecture
(conjecture) The given value was selected based on assumptions by someone besides the person to whom this pronoun applies. As a result, the value may be erroneous.
selfIdentification
(self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
trustedThirdParty
(trusted third party) The given value has been supplied by another individual trusted by the encoder to know the preferences of the person to whom this pronoun applies.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
value(value) supplies a regularized value for personal pronouns.
Status Recommended
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
e
(e) e/eirs
he
(he) he/him/his
she
(she) she/her/hers
they
(they) they/them/theirs
Note

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

Member of
model.persNamePart model.persStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<person>
 <persName>
  <forename>SUE</forename>
  <addName>the T. rex</addName>
 </persName>
 <residence>The Field Museum. Chicago, Illinois, United States.</residence>
 <sex value="0"/>
 <persPronouns value="they">they/them</persPronouns>
 <note>
  <cit>
   <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex
       Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>
   </quote>
   <bibl>SUEtheTrex, Twitter biography.
   <ptr target="https://twitter.com/SUEtheTrex"/>.
       Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>
  </cit>
 </note>
</person>
Example
<docAuthor>
 <persName>Lal Zimman</persName>
 <persPronouns value="he">(he/him/his)</persPronouns>
 <ref target="#Name">(FAQ)</ref>
 <persName type="IPA">[lɑɫ ˈzimn̩]</persName>
 <email>zimman at ucsb dot edu</email>
 <roleName>Assistant Professor of Linguistics</roleName>
 <roleName>Affiliated Faculty in Feminist Studies</roleName>
 <address>
  <addrLine>South Hall 3518</addrLine>
  <addrLine>University of California, Santa Barbara</addrLine>
 </address>
</docAuthor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<persPronouns>

<persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
evidence(evidence) indicates support for the listed personal pronouns.
Status Recommended
Datatype teidata.enumerated
Suggested values include:
conjecture
(conjecture) The given value was selected based on assumptions by someone besides the person to whom this pronoun applies. As a result, the value may be erroneous.
selfIdentification
(self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
trustedThirdParty
(trusted third party) The given value has been supplied by another individual trusted by the encoder to know the preferences of the person to whom this pronoun applies.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
value(value) supplies a regularized value for personal pronouns.
Status Recommended
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
e
(e) e/eirs
he
(he) he/him/his
she
(she) she/her/hers
they
(they) they/them/theirs
Note

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

Member of
model.persNamePart model.persStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<person>
 <persName>
  <forename>SUE</forename>
  <addName>the T. rex</addName>
 </persName>
 <residence>The Field Museum. Chicago, Illinois, United States.</residence>
 <sex value="0"/>
 <persPronouns value="they">they/them</persPronouns>
 <note>
  <cit>
   <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex
       Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>
   </quote>
   <bibl>SUEtheTrex, Twitter biography.
   <ptr target="https://twitter.com/SUEtheTrex"/>.
       Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>
  </cit>
 </note>
</person>
Example
<docAuthor>
 <persName>Lal Zimman</persName>
 <persPronouns value="he">(he/him/his)</persPronouns>
 <ref target="#Name">(FAQ)</ref>
 <persName type="IPA">[lɑɫ ˈzimn̩]</persName>
 <email>zimman at ucsb dot edu</email>
 <roleName>Assistant Professor of Linguistics</roleName>
 <roleName>Affiliated Faculty in Feminist Studies</roleName>
 <address>
  <addrLine>South Hall 3518</addrLine>
  <addrLine>University of California, Santa Barbara</addrLine>
 </address>
</docAuthor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element persPronouns
 {
    tei_att.global.attributes,
@@ -940,10 +959,10 @@
    attribute calendar { list { teidata.pointer+ } }?,
    attribute value { list { teidata.enumerated+ } }?,
    tei_macro.phraseSeq
-}

<postBox>

<postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May containCharacter data only
Note

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

Example
<postBox>P.O. Box 280</postBox>
Example
<postBox>Postbus 532</postBox>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
-element postBox { tei_att.global.attributes, text }

<postCode>

<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May containCharacter data only
Note

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

Example
<postCode>HR1 3LR</postCode>
Example
<postCode>60142-7</postCode>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
-element postCode { tei_att.global.attributes, text }

<profileDesc>

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

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

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

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
Member of
model.annotationPart.body model.ptrLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope biblStruct date desc editor email head hi item label meeting monogr name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figDesc
header: application change classCode correspContext edition licence publicationStmt
linking: annotation
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May containEmpty element
Example
<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>
Schematron

<sch:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+}

<postBox>

<postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May containCharacter data only
Note

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

Example
<postBox>P.O. Box 280</postBox>
Example
<postBox>Postbus 532</postBox>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
+element postBox { tei_att.global.attributes, text }

<postCode>

<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May containCharacter data only
Note

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

Example
<postCode>HR1 3LR</postCode>
Example
<postCode>60142-7</postCode>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
+element postCode { tei_att.global.attributes, text }

<profileDesc>

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

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

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

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
Member of
model.annotationPart.body model.ptrLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope biblStruct date desc editor email gloss head hi item label meeting monogr name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figDesc
header: application change classCode correspContext edition licence publicationStmt
linking: annotation
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May containEmpty element
Example
<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>
Schematron

<sch:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Content model
<content>
 <empty/>
</content>
Schema Declaration
 element ptr
 {
    tei_att.cReferencing.attributes,
@@ -953,7 +972,7 @@
    tei_att.pointing.attributes,
    tei_att.typed.attributes,
    empty
-}

<publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: address date p ptr pubPlace publisher ref
derived-module-Grobid: trash
figures: formula
header: availability idno
Note

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

Example
<publicationStmt>
 <publisher>C. Muquardt </publisher>
 <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
 <date when="1846"/>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Chadwyck Healey</publisher>
 <pubPlace>Cambridge</pubPlace>
 <availability>
  <p>Available under licence only</p>
 </availability>
 <date when="1992">1992</date>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Zea Books</publisher>
 <pubPlace>Lincoln, NE</pubPlace>
 <date>2017</date>
 <availability>
  <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
 </availability>
 <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt>
Content model
<content>
 <alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
+}

<publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: address date p ptr pubPlace publisher ref
derived-module-Grobid: trash
figures: formula
header: availability idno
Note

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

Example
<publicationStmt>
 <publisher>C. Muquardt </publisher>
 <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
 <date when="1846"/>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Chadwyck Healey</publisher>
 <pubPlace>Cambridge</pubPlace>
 <availability>
  <p>Available under licence only</p>
 </availability>
 <date when="1992">1992</date>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Zea Books</publisher>
 <pubPlace>Lincoln, NE</pubPlace>
 <date>2017</date>
 <availability>
  <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
 </availability>
 <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt>
Content model
<content>
 <alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
 element publicationStmt
 {
    tei_att.global.attributes,
@@ -964,25 +983,32 @@
       )+
     | tei_model.pLike+
    )
-}

<publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Member of
model.imprintPart model.publicationStmtPart.agency
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Member of
model.imprintPart model.publicationStmtPart.agency
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.imprintPart model.publicationStmtPart.detail
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
model.imprintPart model.publicationStmtPart.detail
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element pubPlace
 {
    tei_att.global.attributes,
    tei_att.naming.attributes,
    tei_macro.phraseSeq
-}

<rb>

<rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
Modulecore
Attributes
Contained by
core: ruby
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

The word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.

<p xml:lang="zh">
<!--...-->
 <ruby>
  <rb>你</rb>
  <rt place="above">nǐ</rt>
 </ruby>
 <ruby>
  <rb>好</rb>
  <rt place="above">hǎo</rt>
 </ruby>
<!--...-->
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
Member of
model.quoteLike
Contained by
analysis: s
core: addrLine author biblScope desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc figure
header: change edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
textstructure: body div
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp p ptr quote ref ruby term title unit
derived-module-Grobid: trash
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

<rb>

<rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
Modulecore
Attributes
Contained by
core: ruby
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

The word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.

<p xml:lang="zh">
<!--...-->
 <ruby>
  <rb>你</rb>
  <rt place="above">nǐ</rt>
 </ruby>
 <ruby>
  <rb>好</rb>
  <rt place="above">hǎo</rt>
 </ruby>
<!--...-->
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element rb
 {
    tei_att.global.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
Member of
model.annotationPart.body model.ptrLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope biblStruct date desc editor email head hi item label meeting monogr name note p pubPlace publisher rb ref rt series street term title unit
derived-module-Grobid: trash
figures: cell figDesc
header: application change classCode correspContext edition licence publicationStmt
linking: annotation
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp ptr ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

The target and cRef attributes are mutually exclusive.

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

<sch:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <sch:name/>
</sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
+}

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Modulecore
Attributes
Member of
model.annotationPart.body model.ptrLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope biblStruct date desc editor email gloss head hi item label meeting monogr name note p pubPlace publisher quote rb ref rt series street term title unit
derived-module-Grobid: trash
figures: cell figDesc
header: application change classCode correspContext edition licence publicationStmt
linking: annotation
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp ptr quote ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

The target and cRef attributes are mutually exclusive.

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

<sch:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <sch:name/>
</sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
 element ref
 {
    tei_att.cReferencing.attributes,
@@ -992,7 +1018,7 @@
    tei_att.pointing.attributes,
    tei_att.typed.attributes,
    tei_macro.paraContent
-}

<region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<placeName>
 <region n="IL" type="state">Illinois</region>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<placeName>
 <region n="IL" type="state">Illinois</region>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element region
 {
    tei_att.global.attributes,
@@ -1001,26 +1027,26 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<revisionDesc>

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

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

Example
<revisionDesc status="embargoed">
 <change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
</revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="listChange"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="change"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration
+}

<revisionDesc>

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

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

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

<roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

A roleName may be distinguished from an addName by virtue of the fact that, like a title, it typically exists independently of its holder.

Example
<persName>
 <forename>William</forename>
 <surname>Poulteny</surname>
 <roleName>Earl of Bath</roleName>
</persName>
Example
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
including the Supreme Court justices, required by statute to be “learned in the law.”</p>
Example
<p>
 <persName ref="#NJF">
  <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
representing the administration, asserted in rebuttal that there was nothing to disavow (...)
<persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
alike, have repeatedly said they must honor.
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

A roleName may be distinguished from an addName by virtue of the fact that, like a title, it typically exists independently of its holder.

Example
<persName>
 <forename>William</forename>
 <surname>Poulteny</surname>
 <roleName>Earl of Bath</roleName>
</persName>
Example
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
including the Supreme Court justices, required by statute to be “learned in the law.”</p>
Example
<p>
 <persName ref="#NJF">
  <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
representing the administration, asserted in rebuttal that there was nothing to disavow (...)
<persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
alike, have repeatedly said they must honor.
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element roleName
 {
    tei_att.global.attributes,
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<row>

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

<row>

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

<rt>

<rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
Modulecore
Attributes
targetsupplies a pointer to the base being glossed by this ruby text.
Status Optional
Datatype teidata.pointer
SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.

<sch:report test="../@from | ../@to">When target= is
present, neither from= nor to= should be.</sch:report>
Note

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

frompoints to the starting point of the span of text being glossed by this ruby text.
Status Optional
Datatype teidata.pointer
SchematronEnforce the presence of to iff there is a from.

<sch:assert test="../@to">When from= is present, the to=
attribute of <sch:name/> is required.</sch:assert>
topoints to the ending point of the span of text being glossed.
Status Optional
Datatype teidata.pointer
SchematronEnforce the presence of from iff there is a to.

<sch:assert test="../@from">When to= is present, the from=
attribute of <sch:name/> is required.</sch:assert>
Contained by
core: ruby
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example

The word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.

<p style="writing-mode: vertical-rl"
 xml:lang="ja">
<!--...-->
 <ruby>
  <rb>大</rb>
  <rt place="right">だい</rt>
 </ruby>
 <ruby>
  <rb>統</rb>
  <rt place="right">とう</rt>
 </ruby>
 <ruby>
  <rb>領</rb>
  <rt place="right">りょう</rt>
 </ruby>
<!--...-->
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<rt>

<rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
Modulecore
Attributes
targetsupplies a pointer to the base being glossed by this ruby text.
Status Optional
Datatype teidata.pointer
SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.

<sch:report test="../@from | ../@to">When target= is
present, neither from= nor to= should be.</sch:report>
Note

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

frompoints to the starting point of the span of text being glossed by this ruby text.
Status Optional
Datatype teidata.pointer
SchematronEnforce the presence of to iff there is a from.

<sch:assert test="../@to">When from= is present, the to=
attribute of <sch:name/> is required.</sch:assert>
topoints to the ending point of the span of text being glossed.
Status Optional
Datatype teidata.pointer
SchematronEnforce the presence of from iff there is a to.

<sch:assert test="../@from">When to= is present, the from=
attribute of <sch:name/> is required.</sch:assert>
Contained by
core: ruby
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example

The word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.

<p style="writing-mode: vertical-rl"
 xml:lang="ja">
<!--...-->
 <ruby>
  <rb>大</rb>
  <rt place="right">だい</rt>
 </ruby>
 <ruby>
  <rb>統</rb>
  <rt place="right">とう</rt>
 </ruby>
 <ruby>
  <rb>領</rb>
  <rt place="right">りょう</rt>
 </ruby>
<!--...-->
</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element rt
 {
    tei_att.global.attributes,
@@ -1031,13 +1057,13 @@
    attribute from { teidata.pointer }?,
    attribute to { teidata.pointer }?,
    tei_macro.phraseSeq
-}

<ruby>

<ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
Modulecore
Attributes
Member of
model.phrase
Contained by
analysis: s
core: addrLine author biblScope date editor email head hi item label name note p pubPlace publisher rb ref rt street term title unit
figures: cell
header: change edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
core: rb rt
Example

The word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.

<p xml:lang="ja">
<!--...-->
 <ruby>
  <rb>入学試験</rb>
  <rt place="above">にゅうがくしけん</rt>
 </ruby>
<!--...-->
</p>
Example

This fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.

<ruby>
 <rb>T</rb>
 <rt>ti:</rt>
</ruby>
<ruby>
 <rb>E</rb>
 <rt>i:</rt>
</ruby>
<ruby>
 <rb>I</rb>
 <rt>aɪ</rt>
</ruby>
Content model
<content>
 <sequence>
  <elementRef key="rb" maxOccurs="1"
   minOccurs="1"/>
  <elementRef key="rt"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
Schema Declaration
+}

<ruby>

<ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
Modulecore
Attributes
Member of
model.phrase
Contained by
analysis: s
core: addrLine author biblScope date editor email gloss head hi item label name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell
header: change edition licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
core: rb rt
Example

The word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.

<p xml:lang="ja">
<!--...-->
 <ruby>
  <rb>入学試験</rb>
  <rt place="above">にゅうがくしけん</rt>
 </ruby>
<!--...-->
</p>
Example

This fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.

<ruby>
 <rb>T</rb>
 <rt>ti:</rt>
</ruby>
<ruby>
 <rb>E</rb>
 <rt>i:</rt>
</ruby>
<ruby>
 <rb>I</rb>
 <rt>aɪ</rt>
</ruby>
Content model
<content>
 <sequence>
  <elementRef key="rb" maxOccurs="1"
   minOccurs="1"/>
  <elementRef key="rt"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
Schema Declaration
 element ruby
 {
    tei_att.global.attributes,
    tei_att.typed.attributes,
    ( tei_rb, tei_rt+ )
-}

<s>

<s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]
Moduleanalysis
Attributes
Member of
model.pLike model.segLike
Contained by
analysis: s
core: addrLine author bibl biblScope date editor email head hi item label name note p pubPlace publisher rb ref rt street term title unit
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc edition editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the <seg> should be used instead.

The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

Example
<head>
 <s>A short affair</s>
</head>
<s>When are you leaving?</s>
<s>Tomorrow.</s>
Schematron

<sch:report test="tei:s">You may not nest one s element within
another: use seg instead</sch:report>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<s>

<s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]
Moduleanalysis
Attributes
Member of
model.segLike
Contained by
analysis: s
core: addrLine author bibl biblScope date editor email gloss head hi item label name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc edition editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: addName affiliation country eventName forename genName gender object objectName org orgName persName persPronouns persona region roleName settlement state surname
textstructure: back body div front
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the <seg> should be used instead.

The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

Example
<head>
 <s>A short affair</s>
</head>
<s>When are you leaving?</s>
<s>Tomorrow.</s>
Schematron

<sch:report test="tei:s">You may not nest one s element within
another: use seg instead</sch:report>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element s
 {
    tei_att.global.attributes,
@@ -1045,7 +1071,7 @@
    tei_att.typed.attributes,
    tei_att.notated.attributes,
    tei_macro.phraseSeq
-}

<schemaRef>

<schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.10. The Schema Specification]
Moduleheader
Attributes
keythe identifier used for the customization or schema
Status Optional
Datatype teidata.xmlName
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
core: desc
Example
<schemaRef type="interchangeODD"
 url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/>
<schemaRef type="interchangeRNG"
 url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/>
<schemaRef type="projectODD"
 url="file:///schema/project.odd"/>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
Schema Declaration
+}

<schemaRef>

<schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.10. The Schema Specification]
Moduleheader
Attributes
keythe identifier used for the customization or schema
Status Optional
Datatype teidata.xmlName
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
core: desc
Example
<schemaRef type="interchangeODD"
 url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/>
<schemaRef type="interchangeRNG"
 url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/>
<schemaRef type="projectODD"
 url="file:///schema/project.odd"/>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
Schema Declaration
 element schemaRef
 {
    tei_att.global.attributes,
@@ -1053,7 +1079,7 @@
    tei_att.resourced.attributes,
    attribute key { teidata.xmlName }?,
    tei_model.descLike?
-}

<series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Member of
model.biblPart
Contained by
core: bibl biblStruct
May contain
core: biblScope editor ellipsis note noteGrp ptr ref title
figures: figure
header: availability idno
linking: anchor link
character data
Example
<series xml:lang="de">
 <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
 <respStmt>
  <resp>Herausgegeben von</resp>
  <name type="person">Manfred Thaller</name>
  <name type="org">Max-Planck-Institut für Geschichte</name>
 </respStmt>
 <title level="s">Serie A: Historische Quellenkunden</title>
 <biblScope>Band 11</biblScope>
</series>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
+}

<series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Member of
model.biblPart
Contained by
core: bibl biblStruct
May contain
core: biblScope editor ellipsis lb note noteGrp ptr ref title
figures: figure
header: availability idno
linking: anchor link
character data
Example
<series xml:lang="de">
 <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
 <respStmt>
  <resp>Herausgegeben von</resp>
  <name type="person">Manfred Thaller</name>
  <name type="org">Max-Planck-Institut für Geschichte</name>
 </respStmt>
 <title level="s">Serie A: Historische Quellenkunden</title>
 <biblScope>Band 11</biblScope>
</series>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
 element series
 {
    tei_att.global.attributes,
@@ -1070,7 +1096,7 @@
     | tei_model.global
     | tei_availability
    )*
-}

<seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: biblScope editor p title
derived-module-Grobid: trash
figures: formula
header: idno
Example
<seriesStmt>
 <title>Machine-Readable Texts for the Study of Indian Literature</title>
 <respStmt>
  <resp>ed. by</resp>
  <name>Jan Gonda</name>
 </respStmt>
 <biblScope unit="volume">1.2</biblScope>
 <idno type="ISSN">0 345 6789</idno>
</seriesStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="title"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
Schema Declaration
+}

<seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: biblScope editor p title
derived-module-Grobid: trash
figures: formula
header: idno
Example
<seriesStmt>
 <title>Machine-Readable Texts for the Study of Indian Literature</title>
 <respStmt>
  <resp>ed. by</resp>
  <name>Jan Gonda</name>
 </respStmt>
 <biblScope unit="volume">1.2</biblScope>
 <idno type="ISSN">0 345 6789</idno>
</seriesStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="title"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
Schema Declaration
 element seriesStmt
 {
    tei_att.global.attributes,
@@ -1079,7 +1105,7 @@
       tei_model.pLike+
     | ( tei_title+, ( tei_editor | respStmt )*, ( tei_idno | tei_biblScope )* )
    )
-}

<settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<placeName>
 <settlement type="town">Glasgow</settlement>
 <region>Scotland</region>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.placeNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectIdentifier objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<placeName>
 <settlement type="town">Glasgow</settlement>
 <region>Scotland</region>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element settlement
 {
    tei_att.global.attributes,
@@ -1088,7 +1114,7 @@
    tei_att.datable.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_macro.phraseSeq
-}

<sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: bibl biblStruct list listBibl p
derived-module-Grobid: trash
figures: formula table
namesdates: listObject
Example
<sourceDesc>
 <bibl>
  <title level="a">The Interesting story of the Children in the Wood</title>. In
 <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
 <publisher>OUP</publisher>
  <date>1968</date>. </bibl>
</sourceDesc>
Example
<sourceDesc>
 <p>Born digital: no previous source exists.</p>
</sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
Schema Declaration
+}

<sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
header: fileDesc
May contain
analysis: s
core: bibl biblStruct list listBibl p
derived-module-Grobid: trash
figures: formula table
namesdates: listObject
Example
<sourceDesc>
 <bibl>
  <title level="a">The Interesting story of the Children in the Wood</title>. In
 <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
 <publisher>OUP</publisher>
  <date>1968</date>. </bibl>
</sourceDesc>
Example
<sourceDesc>
 <p>Born digital: no previous source exists.</p>
</sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
Schema Declaration
 element sourceDesc
 {
    tei_att.global.attributes,
@@ -1097,14 +1123,14 @@
       tei_model.pLike+
     | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
    )
-}

<standOff>

<standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container]
Modulelinking
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: bibl biblStruct list listBibl note
figures: table
linking: annotation link listAnnotation
namesdates: listObject
Example

This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- ... -->
 </teiHeader>
 <text>
  <body>
<!-- ... -->
   <p>
    <w xml:id="w51">I</w>
    <w xml:id="w52">wanna</w>
    <w xml:id="w53">put</w>
    <w xml:id="w54">up</w>
    <w xml:id="w55">new</w>
    <w xml:id="w56">wallpaper</w>
    <pc>.</pc>
   </p>
<!-- ... -->
  </body>
 </text>
 <standOff type="morphosyntax">
  <spanGrp type="wordForm">
   <span ana="#fs01" target="#w51"/>
   <span ana="#fs02" target="#w52"/>
   <span ana="#fs03" target="#w52"/>
   <span ana="#fs04" target="#w53 #w54"/>
   <span ana="#fs05" target="#w55"/>
   <span ana="#fs06" target="#w56"/>
  </spanGrp>
  <fs xml:id="fs01">
   <f name="lemma">
    <string>I</string>
   </f>
   <f name="pos">
    <symbol value="PP"/>
   </f>
  </fs>
  <fs xml:id="fs02">
   <f name="lemma">
    <string>want</string>
   </f>
   <f name="pos">
    <symbol value="VBP"/>
   </f>
  </fs>
  <fs xml:id="fs03">
   <f name="lemma">
    <string>to</string>
   </f>
   <f name="pos">
    <symbol value="TO"/>
   </f>
  </fs>
  <fs xml:id="fs04">
   <f name="lemma">
    <string>put up</string>
   </f>
   <f name="pos">
    <symbol value="VB"/>
   </f>
  </fs>
  <fs xml:id="fs05">
   <f name="lemma">
    <string>new</string>
   </f>
   <f name="pos">
    <symbol value="JJ"/>
   </f>
  </fs>
  <fs xml:id="fs06">
   <f name="lemma">
    <string>wallpaper</string>
   </f>
   <f name="pos">
    <symbol value="NN"/>
   </f>
  </fs>
 </standOff>
</TEI>
Example

This example shows an encoding of contextual information which is referred to from the main text.

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- ... -->
 </teiHeader>
 <standOff>
  <listPlace>
   <place xml:id="LATL">
    <placeName>Atlanta</placeName>
    <location>
     <region key="US-GA">Georgia</region>
     <country key="USA">United States of America</country>
     <geo>33.755 -84.39</geo>
    </location>
    <population quantity="489359"
     source="https://www.biggestuscities.com/city/atlanta-georgia" type="interpolatedCensus" when="1963"/>
   </place>
   <place xml:id="LBHM">
    <placeName>Birmingham</placeName>
    <location>
     <region key="US-AL">Alabama</region>
     <country key="USA">United States of America</country>
     <geo>33.653333 -86.808889</geo>
    </location>
    <population quantity="332891"
     source="https://www.biggestuscities.com/city/birmingham-alabama" type="interpolatedCensus" when="1963"/>
   </place>
  </listPlace>
 </standOff>
 <text>
  <body>
<!-- ... -->
   <p>Moreover, I am <choice>
     <sic>congnizant</sic>
     <corr>cognizant</corr>
    </choice> of the interrelatedness of all communities and
   <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens
   <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We
   <lb/>are caught in an inescapable network of mutuality, tied in a single garment
   <lb/>of destiny. Whatever affects one directly affects all indirectly. Never
   <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>
    <lb/>idea. Anyone who lives inside the United States can never be considered
   <lb/>an outsider anywhere in this country.</p>
<!-- ... -->
  </body>
 </text>
</TEI>
Schematron

<sch:assert test="@type or not(ancestor::tei:standOff)">This
<sch:name/> element must have a @type attribute, since it is
nested inside a <sch:name/>
</sch:assert>
Content model
<content>
 <classRef key="model.standOffPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
+}

<standOff>

<standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container]
Modulelinking
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: bibl biblStruct list listBibl note
figures: table
linking: annotation link listAnnotation
namesdates: listObject
Example

This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- ... -->
 </teiHeader>
 <text>
  <body>
<!-- ... -->
   <p>
    <w xml:id="w51">I</w>
    <w xml:id="w52">wanna</w>
    <w xml:id="w53">put</w>
    <w xml:id="w54">up</w>
    <w xml:id="w55">new</w>
    <w xml:id="w56">wallpaper</w>
    <pc>.</pc>
   </p>
<!-- ... -->
  </body>
 </text>
 <standOff type="morphosyntax">
  <spanGrp type="wordForm">
   <span ana="#fs01" target="#w51"/>
   <span ana="#fs02" target="#w52"/>
   <span ana="#fs03" target="#w52"/>
   <span ana="#fs04" target="#w53 #w54"/>
   <span ana="#fs05" target="#w55"/>
   <span ana="#fs06" target="#w56"/>
  </spanGrp>
  <fs xml:id="fs01">
   <f name="lemma">
    <string>I</string>
   </f>
   <f name="pos">
    <symbol value="PP"/>
   </f>
  </fs>
  <fs xml:id="fs02">
   <f name="lemma">
    <string>want</string>
   </f>
   <f name="pos">
    <symbol value="VBP"/>
   </f>
  </fs>
  <fs xml:id="fs03">
   <f name="lemma">
    <string>to</string>
   </f>
   <f name="pos">
    <symbol value="TO"/>
   </f>
  </fs>
  <fs xml:id="fs04">
   <f name="lemma">
    <string>put up</string>
   </f>
   <f name="pos">
    <symbol value="VB"/>
   </f>
  </fs>
  <fs xml:id="fs05">
   <f name="lemma">
    <string>new</string>
   </f>
   <f name="pos">
    <symbol value="JJ"/>
   </f>
  </fs>
  <fs xml:id="fs06">
   <f name="lemma">
    <string>wallpaper</string>
   </f>
   <f name="pos">
    <symbol value="NN"/>
   </f>
  </fs>
 </standOff>
</TEI>
Example

This example shows an encoding of contextual information which is referred to from the main text.

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- ... -->
 </teiHeader>
 <standOff>
  <listPlace>
   <place xml:id="LATL">
    <placeName>Atlanta</placeName>
    <location>
     <region key="US-GA">Georgia</region>
     <country key="USA">United States of America</country>
     <geo>33.755 -84.39</geo>
    </location>
    <population quantity="489359"
     source="https://www.biggestuscities.com/city/atlanta-georgia" type="interpolatedCensus" when="1963"/>
   </place>
   <place xml:id="LBHM">
    <placeName>Birmingham</placeName>
    <location>
     <region key="US-AL">Alabama</region>
     <country key="USA">United States of America</country>
     <geo>33.653333 -86.808889</geo>
    </location>
    <population quantity="332891"
     source="https://www.biggestuscities.com/city/birmingham-alabama" type="interpolatedCensus" when="1963"/>
   </place>
  </listPlace>
 </standOff>
 <text>
  <body>
<!-- ... -->
   <p>Moreover, I am <choice>
     <sic>congnizant</sic>
     <corr>cognizant</corr>
    </choice> of the interrelatedness of all communities and
   <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens
   <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We
   <lb/>are caught in an inescapable network of mutuality, tied in a single garment
   <lb/>of destiny. Whatever affects one directly affects all indirectly. Never
   <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>
    <lb/>idea. Anyone who lives inside the United States can never be considered
   <lb/>an outsider anywhere in this country.</p>
<!-- ... -->
  </body>
 </text>
</TEI>
Schematron

<sch:assert test="@type or not(ancestor::tei:standOff)">This
<sch:name/> element must have a @type attribute, since it is
nested inside a <sch:name/>
</sch:assert>
Content model
<content>
 <classRef key="model.standOffPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
 element standOff
 {
    tei_att.global.attributes,
    tei_att.typed.attributes,
    tei_att.declaring.attributes,
    tei_model.standOffPart+
-}

<state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.persStateLike model.placeStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement state surname
May contain
analysis: s
core: bibl biblStruct desc head label listBibl note noteGrp p
derived-module-Grobid: trash
figures: formula
namesdates: state
Note

Where there is confusion between <trait> and state the more general purpose element state should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The state element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<state ref="#SCHOL" type="status">
 <label>scholar</label>
</state>
Example
<org>
 <orgName notAfter="1960">The Silver Beetles</orgName>
 <orgName notBefore="1960">The Beatles</orgName>
 <state from="1960-08" to="1962-05"
  type="membership">
  <desc>
   <persName>John Lennon</persName>
   <persName>Paul McCartney</persName>
   <persName>George Harrison</persName>
   <persName>Stuart Sutcliffe</persName>
   <persName>Pete Best</persName>
  </desc>
 </state>
 <state notBefore="1963" type="membership">
  <desc>
   <persName>John Lennon</persName>
   <persName>Paul McCartney</persName>
   <persName>George Harrison</persName>
   <persName>Ringo Starr</persName>
  </desc>
 </state>
</org>
Content model
<content>
 <sequence>
  <elementRef key="precision"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate>
   <elementRef key="state"
    maxOccurs="unbounded" minOccurs="1"/>
   <sequence>
    <classRef key="model.headLike"
     maxOccurs="unbounded" minOccurs="0"/>
    <classRef key="model.pLike"
     maxOccurs="unbounded" minOccurs="1"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
Schema Declaration
+}

<state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.persStateLike model.placeStateLike
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns persona region roleName settlement state surname
May contain
analysis: s
core: bibl biblStruct desc head label listBibl note noteGrp p
derived-module-Grobid: trash
figures: formula
namesdates: state
Note

Where there is confusion between <trait> and state the more general purpose element state should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The state element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<state ref="#SCHOL" type="status">
 <label>scholar</label>
</state>
Example
<org>
 <orgName notAfter="1960">The Silver Beetles</orgName>
 <orgName notBefore="1960">The Beatles</orgName>
 <state from="1960-08" to="1962-05"
  type="membership">
  <desc>
   <persName>John Lennon</persName>
   <persName>Paul McCartney</persName>
   <persName>George Harrison</persName>
   <persName>Stuart Sutcliffe</persName>
   <persName>Pete Best</persName>
  </desc>
 </state>
 <state notBefore="1963" type="membership">
  <desc>
   <persName>John Lennon</persName>
   <persName>Paul McCartney</persName>
   <persName>George Harrison</persName>
   <persName>Ringo Starr</persName>
  </desc>
 </state>
</org>
Content model
<content>
 <sequence>
  <elementRef key="precision"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate>
   <elementRef key="state"
    maxOccurs="unbounded" minOccurs="1"/>
   <sequence>
    <classRef key="model.headLike"
     maxOccurs="unbounded" minOccurs="0"/>
    <classRef key="model.pLike"
     maxOccurs="unbounded" minOccurs="1"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
Schema Declaration
 element state
 {
    tei_att.global.attributes,
@@ -1126,8 +1152,8 @@
        | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
       )
    )
-}

<street>

<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<street>via della Faggiola, 36</street>
Example
<street>
 <name>Duntaggin</name>, 110 Southmoor Road
</street>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
-element street { tei_att.global.attributes, tei_macro.phraseSeq }

<surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr
Attributes
attachmentdescribes the method by which this surface is or was connected to the main surface
Status Optional
Datatype teidata.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
Status Optional
Datatype teidata.truthValue
Contained by
transcr: facsimile surface
May contain
core: desc ellipsis graphic label note noteGrp
figures: figure formula
linking: anchor link
transcr: surface
Note

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

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

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

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

Example
<facsimile>
 <surface lrx="200" lry="300" ulx="0" uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <alternate>
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<street>

<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
Modulecore
Attributes
Member of
model.addrPart
Contained by
core: address
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<street>via della Faggiola, 36</street>
Example
<street>
 <name>Duntaggin</name>, 110 Southmoor Road
</street>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+element street { tei_att.global.attributes, tei_macro.phraseSeq }

<surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr
Attributes
attachmentdescribes the method by which this surface is or was connected to the main surface
Status Optional
Datatype teidata.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
Status Optional
Datatype teidata.truthValue
Contained by
transcr: facsimile surface
May contain
core: desc ellipsis graphic label lb note noteGrp
figures: figure formula
linking: anchor link
transcr: surface
Note

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

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

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

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

Example
<facsimile>
 <surface lrx="200" lry="300" ulx="0" uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <alternate>
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element surface
 {
    tei_att.global.attributes,
@@ -1140,14 +1166,14 @@
       ( tei_model.global | tei_model.labelLike | tei_model.graphicLike )*,
       ( ( zone | line | path | tei_surface | surfaceGrp ), tei_model.global* )*
    )
-}

<surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
model.persNamePart
Contained by
analysis: s
core: addrLine address author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode correspAction edition licence
namesdates: addName affiliation country eventName forename genName gender objectName org orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element surname
 {
    tei_att.global.attributes,
    tei_att.personal.attributes,
    tei_att.typed.attributes,
    tei_macro.phraseSeq
-}

<table>

<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
Modulefigures
Attributes
rows(rows) indicates the number of rows in the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of rows.

Rows should be presented from top to bottom.

cols(columns) indicates the number of columns in each row of the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of columns.

Within each row, columns should be presented left to right.

Member of
model.listLike
Contained by
core: desc head hi item meeting note p ref title
figures: cell figDesc figure
header: abstract change licence sourceDesc
linking: standOff
textstructure: back body div
May contain
core: ellipsis graphic head meeting note noteGrp
figures: figure formula row
linking: anchor link
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Example
<table cols="4" rows="4">
 <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
 <row role="label">
  <cell role="data"/>
  <cell role="data">Dossing Cribs or Lodging Houses</cell>
  <cell role="data">Beds</cell>
  <cell role="data">Needys or Nightly Lodgers</cell>
 </row>
 <row role="data">
  <cell role="label">Bury St Edmund's</cell>
  <cell role="data">5</cell>
  <cell role="data">8</cell>
  <cell role="data">128</cell>
 </row>
 <row role="data">
  <cell role="label">Thetford</cell>
  <cell role="data">3</cell>
  <cell role="data">6</cell>
  <cell role="data">36</cell>
 </row>
 <row role="data">
  <cell role="label">Attleboro'</cell>
  <cell role="data">3</cell>
  <cell role="data">5</cell>
  <cell role="data">20</cell>
 </row>
 <row role="data">
  <cell role="label">Wymondham</cell>
  <cell role="data">1</cell>
  <cell role="data">11</cell>
  <cell role="data">22</cell>
 </row>
</table>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="row"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<table>

<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
Modulefigures
Attributes
rows(rows) indicates the number of rows in the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of rows.

Rows should be presented from top to bottom.

cols(columns) indicates the number of columns in each row of the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of columns.

Within each row, columns should be presented left to right.

Member of
model.listLike
Contained by
core: desc head hi item meeting note p quote ref title
figures: cell figDesc figure
header: abstract change licence sourceDesc
linking: standOff
textstructure: back body div
May contain
core: ellipsis graphic head lb meeting note noteGrp
figures: figure formula row
linking: anchor link
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Example
<table cols="4" rows="4">
 <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
 <row role="label">
  <cell role="data"/>
  <cell role="data">Dossing Cribs or Lodging Houses</cell>
  <cell role="data">Beds</cell>
  <cell role="data">Needys or Nightly Lodgers</cell>
 </row>
 <row role="data">
  <cell role="label">Bury St Edmund's</cell>
  <cell role="data">5</cell>
  <cell role="data">8</cell>
  <cell role="data">128</cell>
 </row>
 <row role="data">
  <cell role="label">Thetford</cell>
  <cell role="data">3</cell>
  <cell role="data">6</cell>
  <cell role="data">36</cell>
 </row>
 <row role="data">
  <cell role="label">Attleboro'</cell>
  <cell role="data">3</cell>
  <cell role="data">5</cell>
  <cell role="data">20</cell>
 </row>
 <row role="data">
  <cell role="label">Wymondham</cell>
  <cell role="data">1</cell>
  <cell role="data">11</cell>
  <cell role="data">22</cell>
 </row>
</table>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="row"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element table
 {
    tei_att.global.attributes,
@@ -1162,19 +1188,19 @@
       ),
       ( tei_model.divBottom, tei_model.global* )*
    )
-}

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype teidata.version
Note

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

Contained by
—
May contain
header: teiHeader
linking: standOff
textstructure: text
transcr: facsimile
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a namespace.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <text>
  <body>
   <p>This is about the shortest TEI document imaginable.</p>
  </body>
 </text>
</TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>
Schematron

<sch:ns prefix="tei"
 uri="http://www.tei-c.org/ns/1.0"/>
<sch:ns prefix="xs"
 uri="http://www.w3.org/2001/XMLSchema"/>
Schematron

<sch:ns prefix="rng"
 uri="http://relaxng.org/ns/structure/1.0"/>
<sch:ns prefix="rna"
 uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Schematron

<sch:ns prefix="sch"
 uri="http://purl.oclc.org/dsdl/schematron"/>
<sch:ns prefix="sch1x"
 uri="http://www.ascc.net/xml/schematron"/>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
+}

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype teidata.version
Note

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

Contained by
—
May contain
header: teiHeader
linking: standOff
textstructure: text
transcr: facsimile
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a namespace.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <text>
  <body>
   <p>This is about the shortest TEI document imaginable.</p>
  </body>
 </text>
</TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>
Schematron

<sch:ns prefix="tei"
 uri="http://www.tei-c.org/ns/1.0"/>
<sch:ns prefix="xs"
 uri="http://www.w3.org/2001/XMLSchema"/>
Schematron

<sch:ns prefix="rng"
 uri="http://relaxng.org/ns/structure/1.0"/>
<sch:ns prefix="rna"
 uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Schematron

<sch:ns prefix="sch"
 uri="http://purl.oclc.org/dsdl/schematron"/>
<sch:ns prefix="sch1x"
 uri="http://www.ascc.net/xml/schematron"/>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration
 element TEI
 {
    tei_att.global.attributes,
    tei_att.typed.attributes,
    attribute version { teidata.version }?,
    ( tei_teiHeader, tei_model.resource* )
-}

<teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
textstructure: TEI
May contain
header: encodingDesc fileDesc profileDesc revisionDesc xenoData
Note

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

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

<teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
textstructure: TEI
May contain
header: encodingDesc fileDesc profileDesc revisionDesc xenoData
Note

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

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

<term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore
Attributes
Member of
model.emphLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode edition keywords licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

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

Example
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term rend="sc" xml:id="TDPV1">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+}

<term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore
Attributes
Member of
model.emphLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode edition keywords licence
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

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

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

Example
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term rend="sc" xml:id="TDPV1">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element term
 {
    tei_att.global.attributes,
@@ -1185,7 +1211,7 @@
    tei_att.sortable.attributes,
    tei_att.cReferencing.attributes,
    tei_macro.phraseSeq
-}

<text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: ellipsis note noteGrp
figures: figure
linking: anchor link
textstructure: back body front
Note

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

Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

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

<text>
 <front>
<!-- front matter for the whole group -->
 </front>
 <group>
  <text>
<!-- first text -->
  </text>
  <text>
<!-- second text -->
  </text>
 </group>
</text>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
+}

<text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: ellipsis lb note noteGrp
figures: figure
linking: anchor link
textstructure: back body front
Note

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

Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

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

<text>
 <front>
<!-- front matter for the whole group -->
 </front>
 <group>
  <text>
<!-- first text -->
  </text>
  <text>
<!-- second text -->
  </text>
 </group>
</text>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration
 element text
 {
    tei_att.global.attributes,
@@ -1199,13 +1225,13 @@
       tei_model.global*,
       ( tei_back, tei_model.global* )?
    )
-}

<textClass>

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

<textClass>

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

<title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note

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

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Datatype teidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

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

Member of
model.emphLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope date desc editor email head hi item label meeting monogr name note p pubPlace publisher rb ref rt series street term title unit
figures: cell figDesc
header: change classCode edition licence seriesStmt titleStmt
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email graphic hi label list listBibl name note noteGrp ptr ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>
Example
<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
+}

<title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note

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

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Datatype teidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

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

Member of
model.emphLike
Contained by
analysis: s
core: addrLine analytic author bibl biblScope date desc editor email gloss head hi item label meeting monogr name note p pubPlace publisher quote rb ref rt series street term title unit
figures: cell figDesc
header: change classCode edition licence seriesStmt titleStmt
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address bibl biblStruct date desc ellipsis email gloss graphic hi label lb list listBibl name note noteGrp ptr quote ref ruby term title unit
figures: figure formula table
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName listObject objectName orgName persName persPronouns region roleName settlement state surname
character data
Note

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

Example
<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>
Example
<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
 element title
 {
    tei_att.global.attributes,
@@ -1216,12 +1242,12 @@
    attribute calendar { list { teidata.pointer+ } }?,
    attribute level { "a" | "m" | "j" | "s" | "u" }?,
    tei_macro.paraContent
-}

<titleStmt>

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

<titleStmt>

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

<trash>

<trash> (Trash) contains noise information to be ignored, typically from vectoriel images
Modulederived-module-Grobid
Attributes
Member of
model.pLike
Contained by
core: item note
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: object org persona state
textstructure: back body div front
May contain
core: ref
character data
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="ref"/>
 </alternate>
</content>
Schema Declaration
+}

<trash>

<trash> (Trash) contains noise information to be ignored, typically from vectoriel images
Modulederived-module-Grobid
Attributes
Member of
model.pLike
Contained by
core: item note quote
figures: cell figure
header: abstract application availability change correspAction correspContext correspDesc editionStmt encodingDesc licence publicationStmt seriesStmt sourceDesc
namesdates: object org persona state
textstructure: back body div front
May contain
core: ref
character data
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="ref"/>
 </alternate>
</content>
Schema Declaration
 element trash
 {
    tei_att.editLike.attributes,
@@ -1229,14 +1255,14 @@
    tei_att.naming.attributes,
    ( text | tei_ref )*
 }

<unit>

<unit> contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. [3.6.3. Numbers and -Measures]
Modulecore
Attributes
Member of
model.measureLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email head hi item label meeting name note p pubPlace publisher rb ref rt street term title unit
figures: cell figDesc
header: change classCode edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email graphic hi name note noteGrp ptr ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

Here is an example of a unit element holding a unitRef attribute that points to a definition of the unit in the TEI header.

<measure>
 <num>3</num>
 <unit unitRef="#ell">ells</unit>
</measure>
<!-- In the TEI Header: -->
<encodingDesc>
 <unitDecl>
  <unitDef xml:id="ell">
   <label>ell</label>
   <placeName ref="#iceland"/>
   <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>
  </unitDef>
 </unitDecl>
</encodingDesc>
Example
<measure>
 <num>2</num>
 <unit>kg</unit>
</measure>
Example
<measure type="value">
 <num>3</num>
 <unit type="time" unit="min">minute</unit>
</measure>
Example
<measure type="interval">
 <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>
 <unit type="velocity" unit="km/h">km/h</unit>
</measure>
Example
<p>Light travels at <num value="3E10">3×10^10</num>
 <unit type="rate" unit="cm/s">
  <unit type="space">cm</unit> per <unit type="time">second</unit>
 </unit>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
+Measures]
Modulecore
Attributes
Member of
model.measureLike
Contained by
analysis: s
core: addrLine author bibl biblScope date desc editor email gloss head hi item label meeting name note p pubPlace publisher quote rb ref rt street term title unit
figures: cell figDesc
header: change classCode edition licence unitDef
namesdates: addName affiliation country eventName forename genName gender objectName orgName persName persPronouns region roleName settlement surname
May contain
analysis: s
core: address date ellipsis email gloss graphic hi lb name note noteGrp ptr quote ref ruby term title unit
figures: figure formula
header: idno
linking: anchor link
namesdates: addName affiliation country eventName forename genName objectName orgName persName persPronouns region roleName settlement state surname
character data
Example

Here is an example of a unit element holding a unitRef attribute that points to a definition of the unit in the TEI header.

<measure>
 <num>3</num>
 <unit unitRef="#ell">ells</unit>
</measure>
<!-- In the TEI Header: -->
<encodingDesc>
 <unitDecl>
  <unitDef xml:id="ell">
   <label>ell</label>
   <placeName ref="#iceland"/>
   <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>
  </unitDef>
 </unitDecl>
</encodingDesc>
Example
<measure>
 <num>2</num>
 <unit>kg</unit>
</measure>
Example
<measure type="value">
 <num>3</num>
 <unit type="time" unit="min">minute</unit>
</measure>
Example
<measure type="interval">
 <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>
 <unit type="velocity" unit="km/h">km/h</unit>
</measure>
Example
<p>Light travels at <num value="3E10">3×10^10</num>
 <unit type="rate" unit="cm/s">
  <unit type="space">cm</unit> per <unit type="time">second</unit>
 </unit>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
 element unit
 {
    tei_att.global.attributes,
    tei_att.typed.attributes,
    tei_att.measurement.attributes,
    tei_macro.phraseSeq
-}

<unitDecl>

<unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
header: unitDef
Example
<unitDecl>
 <unitDef type="weight" xml:id="斤">
  <label xml:lang="ja">斤</label>
  <label xml:lang="ja-Latn">kin</label>
  <conversion formula="16" fromUnit="#両"
   toUnit="#斤"/>
 </unitDef>
 <unitDef type="weight" xml:id="両">
  <label xml:lang="ja">両</label>
  <label xml:lang="ja-Latn">ryo</label>
  <conversion formula="4" fromUnit="#分"
   toUnit="#両"/>
 </unitDef>
 <unitDef type="weight" xml:id="分">
  <label xml:lang="ja">分</label>
  <label xml:lang="ja-Latn">Bu</label>
  <conversion formula="6" fromUnit="#銖"
   toUnit="#分"/>
 </unitDef>
 <unitDef type="weight" xml:id="銖">
  <label xml:lang="ja">銖</label>
  <label xml:lang="ja-Latn">Shu</label>
 </unitDef>
</unitDecl>
Content model
<content>
 <elementRef key="unitDef"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
+}

<unitDecl>

<unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
header: unitDef
Example
<unitDecl>
 <unitDef type="weight" xml:id="斤">
  <label xml:lang="ja">斤</label>
  <label xml:lang="ja-Latn">kin</label>
  <conversion formula="16" fromUnit="#両"
   toUnit="#斤"/>
 </unitDef>
 <unitDef type="weight" xml:id="両">
  <label xml:lang="ja">両</label>
  <label xml:lang="ja-Latn">ryo</label>
  <conversion formula="4" fromUnit="#分"
   toUnit="#両"/>
 </unitDef>
 <unitDef type="weight" xml:id="分">
  <label xml:lang="ja">分</label>
  <label xml:lang="ja-Latn">Bu</label>
  <conversion formula="6" fromUnit="#銖"
   toUnit="#分"/>
 </unitDef>
 <unitDef type="weight" xml:id="銖">
  <label xml:lang="ja">銖</label>
  <label xml:lang="ja-Latn">Shu</label>
 </unitDef>
</unitDecl>
Content model
<content>
 <elementRef key="unitDef"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration
 element unitDecl
 {
    tei_att.canonical.attributes,
@@ -1244,7 +1270,7 @@
    tei_att.global.attributes,
    attribute calendar { list { teidata.pointer+ } }?,
    tei_unitDef+
-}

<unitDef>

<unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Contained by
header: unitDecl
May contain
core: desc label unit
header: conversion
namesdates: country region settlement
Example
<unitDecl>
 <unitDef type="length" xml:id="pechys">
  <label>πῆχυς</label>
  <placeName ref="#athens"/>
  <conversion formula="$fromUnit div 24"
   fromUnit="#daktylos" toUnit="#pechys"/>
  <desc>Equivalent to a cubit or 24 daktyloi.</desc>
 </unitDef>
 <unitDef type="length" xml:id="daktylos">
  <label>δάκτυλος</label>
  <placeName ref="#athens"/>
  <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>
 </unitDef>
</unitDecl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.labelLike"
   minOccurs="1"/>
  <classRef key="model.placeNamePart"
   minOccurs="0"/>
  <elementRef key="conversion"
   minOccurs="0"/>
  <elementRef key="unit" minOccurs="0"/>
 </alternate>
</content>
Schema Declaration
+}

<unitDef>

<unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
Contained by
header: unitDecl
May contain
core: desc label unit
header: conversion
namesdates: country region settlement
Example
<unitDecl>
 <unitDef type="length" xml:id="pechys">
  <label>πῆχυς</label>
  <placeName ref="#athens"/>
  <conversion formula="$fromUnit div 24"
   fromUnit="#daktylos" toUnit="#pechys"/>
  <desc>Equivalent to a cubit or 24 daktyloi.</desc>
 </unitDef>
 <unitDef type="length" xml:id="daktylos">
  <label>δάκτυλος</label>
  <placeName ref="#athens"/>
  <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>
 </unitDef>
</unitDecl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.labelLike"
   minOccurs="1"/>
  <classRef key="model.placeNamePart"
   minOccurs="0"/>
  <elementRef key="conversion"
   minOccurs="0"/>
  <elementRef key="unit" minOccurs="0"/>
 </alternate>
</content>
Schema Declaration
 element unitDef
 {
    tei_att.global.attributes,
@@ -1258,7 +1284,7 @@
     | tei_conversion?
     | tei_unit?
    )+
-}

<when>

<when> indicates a point in time either relative to other elements in the same timeline tag, or absolutely. [16.4.2. Placing Synchronous Events in Time]
Modulelinking
Attributes
absolutesupplies an absolute value for the time.
Status Optional
Datatype teidata.temporal.w3c
Note

This attribute should always be specified on a when element which serves as the target for the origin attribute of a <timeline>.

unitspecifies the unit of time in which the interval value is expressed, if this is not inherited from the parent <timeline>.
Status Optional
Datatype teidata.enumerated
Suggested values include:
d
(days)
h
(hours)
min
(minutes)
s
(seconds)
ms
(milliseconds)
intervalspecifies a time interval either as a number or as one of the keywords defined by the datatype teidata.interval
Status Optional
Datatype teidata.interval
sinceidentifies the reference point for determining the time of the current when element, which is obtained by adding the interval to the time of the reference point.
Status Optional
Datatype teidata.pointer
Note

This attribute should point to another when element in the same <timeline>. If no value is supplied, and the absolute attribute is also unspecified, then the reference point is understood to be the origin of the enclosing <timeline> tag.

Contained by
—
May containEmpty element
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for this point in time. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

Example
<when interval="20" since="#w2" xml:id="TW3"/>
Content model
<content>
 <empty/>
</content>
Schema Declaration
+}

<when>

<when> indicates a point in time either relative to other elements in the same timeline tag, or absolutely. [16.4.2. Placing Synchronous Events in Time]
Modulelinking
Attributes
absolutesupplies an absolute value for the time.
Status Optional
Datatype teidata.temporal.w3c
Note

This attribute should always be specified on a when element which serves as the target for the origin attribute of a <timeline>.

unitspecifies the unit of time in which the interval value is expressed, if this is not inherited from the parent <timeline>.
Status Optional
Datatype teidata.enumerated
Suggested values include:
d
(days)
h
(hours)
min
(minutes)
s
(seconds)
ms
(milliseconds)
intervalspecifies a time interval either as a number or as one of the keywords defined by the datatype teidata.interval
Status Optional
Datatype teidata.interval
sinceidentifies the reference point for determining the time of the current when element, which is obtained by adding the interval to the time of the reference point.
Status Optional
Datatype teidata.pointer
Note

This attribute should point to another when element in the same <timeline>. If no value is supplied, and the absolute attribute is also unspecified, then the reference point is understood to be the origin of the enclosing <timeline> tag.

Contained by
—
May containEmpty element
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for this point in time. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

Example
<when interval="20" since="#w2" xml:id="TW3"/>
Content model
<content>
 <empty/>
</content>
Schema Declaration
 element when
 {
    tei_att.global.attributes,
@@ -1267,7 +1293,7 @@
    attribute interval { teidata.interval }?,
    attribute since { teidata.pointer }?,
    empty
-}

<xenoData>

<xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
Moduleheader
Attributes
Member of
model.teiHeaderPart
Contained by
header: teiHeader
May containANY
Example

This example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second xenoData block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the xenoData block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [ID SG-id in TEI Guidelines]). Do note, however, that if the contents of the xenoData block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.

<xenoData>
 <rdf:RDF>
  <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
   <dc:title>The description of a new world, called the blazing-world</dc:title>
   <dc:creator>The Duchess of Newcastle</dc:creator>
   <dc:date>1667</dc:date>
   <dc:identifier>British Library, 8407.h.10</dc:identifier>
   <dc:subject>utopian fiction</dc:subject>
  </rdf:Description>
 </rdf:RDF>
</xenoData>
<xenoData>
 <rdf:RDF>
  <rdf:Description rdf:about="">
   <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
   <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
   <dc:publisher>Women Writers Project</dc:publisher>
   <dc:date>2002-02-12</dc:date>
   <dc:subject>utopian fiction</dc:subject>
  </rdf:Description>
 </rdf:RDF>
</xenoData>
Example

In this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.

<xenoData>
 <rdf:RDF>
  <cc:Work rdf:about="">
   <dc:title>Applied Software Project Management - review</dc:title>
   <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
   <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>
  </cc:Work>
  <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
   <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
   <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
   <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>
  </cc:License>
 </rdf:RDF>
</xenoData>
Example

In this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.

<xenoData>
 <oai_dc:dc>
  <dc:title>The colonial despatches of Vancouver Island and British
     Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.
     Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>
  <dc:date>1858-11-12</dc:date>
  <dc:creator>Trevelyan</dc:creator>
  <dc:publisher>University of Victoria Humanities Computing and Media
     Centre, and UVic Libraries</dc:publisher>
  <dc:type>InteractiveResource</dc:type>
  <dc:format>application/xhtml+xml</dc:format>
  <dc:type>text</dc:type>
  <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
  <dc:rights>This document is licensed under a Creative Commons …</dc:rights>
  <dc:language>(SCHEME=ISO639) en</dc:language>
  <dc:source>Transcribed from microfilm and/or original documents, and
     marked up in TEI P5 XML. The interactive XHTML resource is generated
     from the XHTML using XQuery and XSLT.</dc:source>
  <dc:source>repository: CO</dc:source>
  <dc:source>coNumber: 60</dc:source>
  <dc:source>coVol: 2</dc:source>
  <dc:source>page: 291</dc:source>
  <dc:source>coRegistration: 11566</dc:source>
  <dc:source>received: received 13 November</dc:source>
  <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
  <dc:subject>Merivale, Herman</dc:subject>
  <dc:subject>Elliot, T. Frederick</dc:subject>
  <dc:subject>Moody, Colonel Richard Clement</dc:subject>
  <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
  <dc:subject>Jadis, Vane</dc:subject>
  <dc:subject>Carnarvon, Earl</dc:subject>
  <dc:subject>British Columbia</dc:subject>
  <dc:description>British Columbia correspondence: Public Offices
     document (normally correspondence between government
     departments)</dc:description>
 </oai_dc:dc>
</xenoData>
Example

In this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.

<xenoData>
 <mods:mods>
  <mods:titleInfo>
   <mods:title>Academic adaptation and cross-cultural
       learning experiences of Chinese students at American
       universities</mods:title>
   <mods:subTitle>a narrative inquiry</mods:subTitle>
  </mods:titleInfo>
  <mods:name authority="local"
   type="personal">
   <mods:namePart/>
   <mods:role>
    <mods:roleTerm authority="marcrelator"
     type="text">Author</mods:roleTerm>
   </mods:role>
   <mods:affiliation>Northeastern University</mods:affiliation>
   <mods:namePart type="given">Hong</mods:namePart>
   <mods:namePart type="family">Zhang</mods:namePart>
  </mods:name>
  <mods:name authority="local"
   type="personal">
   <mods:namePart/>
   <mods:role>
    <mods:roleTerm authority="local"
     type="text">Advisor</mods:roleTerm>
   </mods:role>
   <mods:namePart type="given">Liliana</mods:namePart>
   <mods:namePart type="family">Meneses</mods:namePart>
  </mods:name>
  
<!-- ... -->
  <mods:typeOfResource>text</mods:typeOfResource>
  <mods:genre>doctoral theses</mods:genre>
  <mods:originInfo>
   <mods:place>
    <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>
   </mods:place>
   <mods:publisher>Northeastern University</mods:publisher>
   <mods:copyrightDate encoding="w3cdtf"
    keyDate="yes">2013</mods:copyrightDate>
  </mods:originInfo>
  <mods:language>
   <mods:languageTerm authority="iso639-2b"
    type="code">eng</mods:languageTerm>
  </mods:language>
  <mods:physicalDescription>
   <mods:form authority="marcform">electronic</mods:form>
   <mods:digitalOrigin>born digital</mods:digitalOrigin>
  </mods:physicalDescription>
<!-- ... -->
 </mods:mods>
</xenoData>
Example

This example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.

<xenoData xml:space="preserve"> +}

<xenoData>

<xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
Moduleheader
Attributes
Member of
model.teiHeaderPart
Contained by
header: teiHeader
May containANY
Example

This example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second xenoData block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the xenoData block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [ID SG-id in TEI Guidelines]). Do note, however, that if the contents of the xenoData block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.

<xenoData>
 <rdf:RDF>
  <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
   <dc:title>The description of a new world, called the blazing-world</dc:title>
   <dc:creator>The Duchess of Newcastle</dc:creator>
   <dc:date>1667</dc:date>
   <dc:identifier>British Library, 8407.h.10</dc:identifier>
   <dc:subject>utopian fiction</dc:subject>
  </rdf:Description>
 </rdf:RDF>
</xenoData>
<xenoData>
 <rdf:RDF>
  <rdf:Description rdf:about="">
   <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
   <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
   <dc:publisher>Women Writers Project</dc:publisher>
   <dc:date>2002-02-12</dc:date>
   <dc:subject>utopian fiction</dc:subject>
  </rdf:Description>
 </rdf:RDF>
</xenoData>
Example

In this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.

<xenoData>
 <rdf:RDF>
  <cc:Work rdf:about="">
   <dc:title>Applied Software Project Management - review</dc:title>
   <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
   <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>
  </cc:Work>
  <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
   <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
   <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
   <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
   <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>
  </cc:License>
 </rdf:RDF>
</xenoData>
Example

In this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.

<xenoData>
 <oai_dc:dc>
  <dc:title>The colonial despatches of Vancouver Island and British
     Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.
     Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>
  <dc:date>1858-11-12</dc:date>
  <dc:creator>Trevelyan</dc:creator>
  <dc:publisher>University of Victoria Humanities Computing and Media
     Centre, and UVic Libraries</dc:publisher>
  <dc:type>InteractiveResource</dc:type>
  <dc:format>application/xhtml+xml</dc:format>
  <dc:type>text</dc:type>
  <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
  <dc:rights>This document is licensed under a Creative Commons …</dc:rights>
  <dc:language>(SCHEME=ISO639) en</dc:language>
  <dc:source>Transcribed from microfilm and/or original documents, and
     marked up in TEI P5 XML. The interactive XHTML resource is generated
     from the XHTML using XQuery and XSLT.</dc:source>
  <dc:source>repository: CO</dc:source>
  <dc:source>coNumber: 60</dc:source>
  <dc:source>coVol: 2</dc:source>
  <dc:source>page: 291</dc:source>
  <dc:source>coRegistration: 11566</dc:source>
  <dc:source>received: received 13 November</dc:source>
  <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
  <dc:subject>Merivale, Herman</dc:subject>
  <dc:subject>Elliot, T. Frederick</dc:subject>
  <dc:subject>Moody, Colonel Richard Clement</dc:subject>
  <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
  <dc:subject>Jadis, Vane</dc:subject>
  <dc:subject>Carnarvon, Earl</dc:subject>
  <dc:subject>British Columbia</dc:subject>
  <dc:description>British Columbia correspondence: Public Offices
     document (normally correspondence between government
     departments)</dc:description>
 </oai_dc:dc>
</xenoData>
Example

In this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.

<xenoData>
 <mods:mods>
  <mods:titleInfo>
   <mods:title>Academic adaptation and cross-cultural
       learning experiences of Chinese students at American
       universities</mods:title>
   <mods:subTitle>a narrative inquiry</mods:subTitle>
  </mods:titleInfo>
  <mods:name authority="local"
   type="personal">
   <mods:namePart/>
   <mods:role>
    <mods:roleTerm authority="marcrelator"
     type="text">Author</mods:roleTerm>
   </mods:role>
   <mods:affiliation>Northeastern University</mods:affiliation>
   <mods:namePart type="given">Hong</mods:namePart>
   <mods:namePart type="family">Zhang</mods:namePart>
  </mods:name>
  <mods:name authority="local"
   type="personal">
   <mods:namePart/>
   <mods:role>
    <mods:roleTerm authority="local"
     type="text">Advisor</mods:roleTerm>
   </mods:role>
   <mods:namePart type="given">Liliana</mods:namePart>
   <mods:namePart type="family">Meneses</mods:namePart>
  </mods:name>
  
<!-- ... -->
  <mods:typeOfResource>text</mods:typeOfResource>
  <mods:genre>doctoral theses</mods:genre>
  <mods:originInfo>
   <mods:place>
    <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>
   </mods:place>
   <mods:publisher>Northeastern University</mods:publisher>
   <mods:copyrightDate encoding="w3cdtf"
    keyDate="yes">2013</mods:copyrightDate>
  </mods:originInfo>
  <mods:language>
   <mods:languageTerm authority="iso639-2b"
    type="code">eng</mods:languageTerm>
  </mods:language>
  <mods:physicalDescription>
   <mods:form authority="marcform">electronic</mods:form>
   <mods:digitalOrigin>born digital</mods:digitalOrigin>
  </mods:physicalDescription>
<!-- ... -->
 </mods:mods>
</xenoData>
Example

This example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.

<xenoData xml:space="preserve"> <![CDATA[ {     "features": [ @@ -1347,15 +1373,16 @@ tei_att.declarable.attributes, tei_att.typed.attributes, ( text | anyElement_xenoData_1 ) -}

Schema Grobid: Model classes

model.addressLike

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

model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
Moduletei
Used by
address
Membersmodel.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] addrLine postBox postCode street

model.annotationLike

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

model.annotationPart.body

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

model.applicationLike

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

model.attributable

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

model.availabilityPart

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

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
listBibl model.inter model.personPart model.standOffPart object org sourceDesc state
Membersbibl biblStruct listBibl

model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
bibl
Membersmodel.imprintPart [biblScope pubPlace publisher] model.respLike [author editor meeting] availability bibl edition objectIdentifier series

model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
body div figure
Membersmodel.divPart [model.lLike model.pLike [formula p s trash] ] model.inter [model.attributable [model.quoteLike] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike]
Note

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

model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Moduletei
Used by
correspAction
Membersmodel.addressLike [address affiliation email] model.dateLike [date] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] note noteGrp

model.correspContextPart

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

model.correspDescPart

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

model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Used by
imprint model.correspActionPart model.pPart.data
Membersdate

model.descLike

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

model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
body div figure front list table
Membersmodel.divBottomPart model.divWrapper [meeting]

model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei
Used by
abstract back body div figDesc front
Membersdiv

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
macro.specialPara model.common
Membersmodel.lLike model.pLike [formula p s trash]
Note

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

model.divTop

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

model.divTopPart

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

model.divWrapper

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

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
model.highlighted model.limitedPhrase
Membersterm title

model.encodingDescPart

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

model.frontPart

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

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei
Used by
address back bibl body date div figure front head imprint list macro.phraseSeq macro.phraseSeq.limited macro.specialPara model.paraPart persona series surface table text
Membersmodel.global.edit [ellipsis] model.global.meta [link] model.milestoneLike [anchor] model.noteLike [note noteGrp] figure

model.global.edit

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

model.global.meta

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

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

model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Moduletei
Used by
facsimile figure formula model.phrase surface table
Membersformula graphic

model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
figure listAnnotation listObject model.divTopPart object org state table
Membershead

model.highlighted

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

model.hiLike

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

model.imprintPart

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

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
figDesc head macro.limitedContent macro.specialPara model.common model.paraPart
Membersmodel.attributable [model.quoteLike] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike

model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
application listAnnotation model.inter org state surface unitDef
Membersdesc label

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei
Used by
figDesc macro.limitedContent macro.phraseSeq.limited
Membersmodel.emphLike [term title] model.hiLike [hi] model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref]

model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
abstract back model.inter model.standOffPart sourceDesc
Memberslist listObject table

model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and +}

Schema Grobid: Model classes

model.addressLike

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

model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
Moduletei
Used by
address
Membersmodel.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] addrLine postBox postCode street

model.annotationLike

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

model.annotationPart.body

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

model.applicationLike

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

model.attributable

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

model.availabilityPart

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

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
listBibl model.inter model.personPart model.standOffPart object org sourceDesc state
Membersbibl biblStruct listBibl

model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
bibl
Membersmodel.imprintPart [biblScope pubPlace publisher] model.respLike [author editor meeting] availability bibl edition objectIdentifier series

model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
body div figure
Membersmodel.divPart [model.lLike model.pLike [model.segLike [s] formula p trash] ] model.inter [model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike]
Note

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

model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Moduletei
Used by
correspAction
Membersmodel.addressLike [address affiliation email] model.dateLike [date] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] note noteGrp

model.correspContextPart

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

model.correspDescPart

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

model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Used by
imprint model.correspActionPart model.pPart.data
Membersdate

model.descLike

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

model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
body div figure front list table
Membersmodel.divBottomPart model.divWrapper [meeting]

model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei
Used by
abstract back body div figDesc front
Membersdiv

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
macro.specialPara model.common
Membersmodel.lLike model.pLike [model.segLike [s] formula p trash]
Note

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

model.divTop

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

model.divTopPart

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

model.divWrapper

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

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
model.highlighted model.limitedPhrase
Membersgloss term title

model.encodingDescPart

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

model.frontPart

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

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei
Used by
address back bibl body date div figure front head imprint list macro.phraseSeq macro.phraseSeq.limited macro.specialPara model.paraPart persona series surface table text
Membersmodel.global.edit [ellipsis] model.global.meta [link] model.milestoneLike [anchor lb] model.noteLike [note noteGrp] figure

model.global.edit

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

model.global.meta

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

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

model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Moduletei
Used by
facsimile figure formula model.phrase surface table
Membersformula graphic

model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
figure listAnnotation listObject model.divTopPart object org state table
Membershead

model.highlighted

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

model.hiLike

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

model.imprintPart

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

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
figDesc head macro.limitedContent macro.specialPara model.common model.paraPart
Membersmodel.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike

model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
application listAnnotation model.inter org state surface unitDef
Membersdesc label

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei
Used by
figDesc macro.limitedContent macro.phraseSeq.limited
Membersmodel.emphLike [gloss term title] model.hiLike [hi] model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref]

model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
abstract back model.inter model.standOffPart sourceDesc
Memberslist listObject table

model.measureLike

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

model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone -Elements]
Moduletei
Used by
model.global org
Membersanchor

model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
model.addrPart model.correspActionPart model.pPart.data org
Membersmodel.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName
Note

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

model.nameLike.agent

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

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

model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Moduletei
Used by
biblStruct model.global monogr notesStmt object org state
Membersnote noteGrp

model.objectLike

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

model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Moduletei
Used by
org
Membersmodel.eventLike

model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
Moduletei
Used by
macro.paraContent
Membersmodel.gLike model.global [model.global.edit [ellipsis] model.global.meta [link] model.milestoneLike [anchor] model.noteLike [note noteGrp] figure] model.inter [model.attributable [model.quoteLike] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike] model.lLike model.phrase [model.graphicLike [formula graphic] model.highlighted [model.emphLike [term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.edit [model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref] model.segLike [s] model.specDescLike ruby]

model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Modulenamesdates
Used by
model.nameLike
MembersaddName forename genName persPronouns roleName surname

model.personLike

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

model.personPart

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

model.persStateLike

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

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

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
date head macro.phraseSeq macro.specialPara model.paraPart
Membersmodel.graphicLike [formula graphic] model.highlighted [model.emphLike [term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.edit [model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref] model.segLike [s] model.specDescLike ruby
Note

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

model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Moduletei
Used by
model.placeStateLike objectIdentifier unitDef
Memberscountry region settlement

model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
model.nameLike
Membersmodel.placeNamePart [country region settlement] state

model.pLike

model.pLike groups paragraph-like elements.
Moduletei
Used by
abstract application availability back correspAction correspDesc editionStmt encodingDesc front model.correspContextPart model.divPart object org persona publicationStmt seriesStmt sourceDesc state
Membersformula p s trash

model.pLike.front

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

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
bibl model.limitedPhrase model.phrase
Membersmodel.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName]

model.pPart.edit

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

model.profileDescPart

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

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Moduletei
Used by
analytic application bibl biblStruct model.correspContextPart model.limitedPhrase model.phrase model.publicationStmtPart.detail monogr series
Membersptr ref

model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
publicationStmt
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
publicationStmt
Membersmodel.ptrLike [ptr ref] address availability date idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

model.resource

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

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
editionStmt model.biblPart monogr titleStmt
Membersauthor editor meeting

model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Moduletei
Used by
bibl model.phrase
Memberss
Note

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

model.standOffPart

model.standOffPart groups elements which may be used as children of standOff.
Moduletei
Used by
standOff
Membersmodel.annotationLike [annotation note] model.biblLike [bibl biblStruct listBibl] model.global.meta [link] model.listLike [list listObject table] listAnnotation

model.teiHeaderPart

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

Schema Grobid: Attribute classes

att.anchoring

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

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

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

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

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

att.ascribed

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

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

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

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

att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersdate
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian" when="1732-02-22">Feb. 11, 1731/32,
O.S.</date>).
He was born on <date calendar="#gregorian #julian"
 when="1732-02-22">Feb. 22, 1732
(Feb. 11, 1731/32, O.S.)</date>.
Note

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

att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming [att.personal [addName eventName forename genName name objectName orgName persName roleName surname] affiliation author country editor pubPlace region settlement state trash] correspDesc date meeting object publisher term title unitDecl unitDef
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>
 <name key="Hugo, Victor (1802-1885)"
  ref="http://www.idref.fr/026927608">Victor Hugo</name>
</author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project.

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

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

Example

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

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

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

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

Note

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

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

att.citeStructurePart

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

att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei
MembersbiblScope
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Status Optional
Datatype teidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word

att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Moduletranscr
Memberssurface
Attributes
startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
Status Optional
Datatype teidata.pointer
ulxgives the x coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
pointsidentifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
Status Optional
Datatype 3–∞ occurrences of teidata.point separated by whitespace

att.cReferencing

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

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 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.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersaffiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, dates or <event>s) within which the datable item is understood to have occurred.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
Modulenamesdates
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace

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

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

Not all custom date formulations will have Gregorian equivalents.

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

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

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

<date datingMethod="#creationOfWorld"
 when="1382-06-28" when-custom="6890-06-20"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

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

Note

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

att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Modulenamesdates
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
when-isosupplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso

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

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

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

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

The second 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 teidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

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

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

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

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso

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

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

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

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

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

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

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

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

att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
Moduletei
Membersatt.segLike [s]
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example

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

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

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

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

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

If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [ID FS in TEI Guidelines].
<fs>
 <f fVal="#commonNoun" name="POS"/>
<!-- ... -->
</fs>

The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of text or a child of encodingDesc; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.

The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  value="NN" xml:id="commonNoun"/>
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
  value="NP" xml:id="properNoun"/>
<!-- ... -->
</fvLib>

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

Example

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

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

This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.

Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.

Example

The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.

<encodingDesc>
<!-- ... -->
 <classDecl>
<!-- ... -->
  <taxonomy datcat="https://universaldependencies.org/u/dep/index.html"
   xml:id="UD-SYN">
   <desc>
    <term>UD syntactic relations</term>
   </desc>
   <category valueDatcat="https://universaldependencies.org/u/dep/acl.html"
    xml:id="acl">
    <catDesc>
     <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>
   </category>
   <category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"
    xml:id="acl_relcl">
    <catDesc>
     <term>acl:relcl</term>: relative clause modifier</catDesc>
   </category>
   <category valueDatcat="https://universaldependencies.org/u/dep/advcl.html"
    xml:id="advcl">
    <catDesc>
     <term>advcl</term>: Adverbial clause modifier</catDesc>
   </category>
<!-- ... -->
  </taxonomy>
 </classDecl>
</encodingDesc>

The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.

Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.

Example

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

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

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

Example

The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.


<!-- in the dictionary header --><encodingDesc>
 <classDecl>
  <taxonomy xml:id="domains">
<!--...-->
   <category xml:id="domain.medical_and_health_sciences">
    <catDesc xml:lang="en">Medical and Health Sciences</catDesc>
    <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>
    <category valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"
     xml:id="domain.medical_and_health_sciences.medicine">
     <catDesc xml:lang="en">
      <term>Medicine</term>
      <gloss>
<!--...-->
      </gloss>
     </catDesc>
     <catDesc xml:lang="pt">
      <term>Medicina</term>
      <gloss>
<!--...-->
      </gloss>
     </catDesc>
    </category>
   </category>
<!--...-->
  </taxonomy>
 </classDecl>
</encodingDesc>
<!-- +Elements]
Moduletei
Used by
model.global org
Membersanchor lb

model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
model.addrPart model.correspActionPart model.pPart.data org
Membersmodel.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName
Note

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

model.nameLike.agent

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

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

model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Moduletei
Used by
biblStruct model.global monogr notesStmt object org state
Membersnote noteGrp

model.objectLike

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

model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Moduletei
Used by
org
Membersmodel.eventLike

model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
Moduletei
Used by
macro.paraContent
Membersmodel.gLike model.global [model.global.edit [ellipsis] model.global.meta [link] model.milestoneLike [anchor lb] model.noteLike [note noteGrp] figure] model.inter [model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl] model.egLike model.labelLike [desc label] model.listLike [list listObject table] model.oddDecl model.stageLike] model.lLike model.phrase [model.graphicLike [formula graphic] model.highlighted [model.emphLike [gloss term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.edit [model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref] model.segLike [s] model.specDescLike ruby]

model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Modulenamesdates
Used by
model.nameLike
MembersaddName forename genName persPronouns roleName surname

model.personLike

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

model.personPart

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

model.persStateLike

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

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

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
date head macro.phraseSeq macro.specialPara model.paraPart
Membersmodel.graphicLike [formula graphic] model.highlighted [model.emphLike [gloss term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName] ] model.pPart.edit [model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike [ptr ref] model.segLike [s] model.specDescLike ruby
Note

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

model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Moduletei
Used by
model.placeStateLike objectIdentifier unitDef
Memberscountry region settlement

model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
model.nameLike
Membersmodel.placeNamePart [country region settlement] state

model.pLike

model.pLike groups paragraph-like elements.
Moduletei
Used by
abstract application availability back correspAction correspDesc editionStmt encodingDesc front model.correspContextPart model.divPart object org persona publicationStmt seriesStmt sourceDesc state
Membersmodel.segLike [s] formula p trash

model.pLike.front

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

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
bibl model.limitedPhrase model.phrase
Membersmodel.addressLike [address affiliation email] model.dateLike [date] model.measureLike [unit] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [country region settlement] state] eventName idno objectName]

model.pPart.edit

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

model.profileDescPart

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

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Moduletei
Used by
analytic application bibl biblStruct model.correspContextPart model.limitedPhrase model.phrase model.publicationStmtPart.detail monogr series
Membersptr ref

model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
publicationStmt
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
publicationStmt
Membersmodel.ptrLike [ptr ref] address availability date idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei
Used by
model.attributable
Membersquote

model.resource

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

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
editionStmt model.biblPart monogr titleStmt
Membersauthor editor meeting

model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Moduletei
Used by
bibl model.pLike model.phrase
Memberss
Note

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

model.standOffPart

model.standOffPart groups elements which may be used as children of standOff.
Moduletei
Used by
standOff
Membersmodel.annotationLike [annotation note] model.biblLike [bibl biblStruct listBibl] model.global.meta [link] model.listLike [list listObject table] listAnnotation

model.teiHeaderPart

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

Schema Grobid: Attribute classes

att.anchoring

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

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

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

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

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

att.ascribed

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

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

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

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

att.breaking

att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone +Elements]
Moduletei
Memberslb
Attributes
breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
Status Recommended
Datatype teidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.

In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.

<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt .
leodum la<lb break="no"/> ðost ærþan ichim lifes
ƿeȝ rihtne ȝerymde reord be<lb break="no"/>
rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer...
</ab>

att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersdate
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian" when="1732-02-22">Feb. 11, 1731/32,
O.S.</date>).
He was born on <date calendar="#gregorian #julian"
 when="1732-02-22">Feb. 22, 1732
(Feb. 11, 1731/32, O.S.)</date>.
Note

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

att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming [att.personal [addName eventName forename genName name objectName orgName persName roleName surname] affiliation author country editor pubPlace region settlement state trash] correspDesc date meeting object publisher term title unitDecl unitDef
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>
 <name key="Hugo, Victor (1802-1885)"
  ref="http://www.idref.fr/026927608">Victor Hugo</name>
</author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project.

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

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

Example

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

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

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

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

Note

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

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

att.citeStructurePart

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

att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei
MembersbiblScope
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Status Optional
Datatype teidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word

att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Moduletranscr
Memberssurface
Attributes
startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
Status Optional
Datatype teidata.pointer
ulxgives the x coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
pointsidentifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
Status Optional
Datatype 3–∞ occurrences of teidata.point separated by whitespace

att.cReferencing

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

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 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.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersaffiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, dates or <event>s) within which the datable item is understood to have occurred.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
Modulenamesdates
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace

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

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

Not all custom date formulations will have Gregorian equivalents.

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

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

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

<date datingMethod="#creationOfWorld"
 when="1382-06-28" when-custom="6890-06-20"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

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

Note

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

att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Modulenamesdates
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
when-isosupplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso

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

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

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

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

The second 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 teidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

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

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

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

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
Moduletei
Membersatt.datable [affiliation application author change conversion country date editor eventName gender idno licence meeting name objectName orgName persName persPronouns region settlement state title trash unitDecl unitDef]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso

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

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

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

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

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

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

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

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

att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
Moduletei
Membersatt.segLike [s]
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example

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

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

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

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

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

If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [ID FS in TEI Guidelines].
<fs>
 <f fVal="#commonNoun" name="POS"/>
<!-- ... -->
</fs>

The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of text or a child of encodingDesc; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.

The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  value="NN" xml:id="commonNoun"/>
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
  value="NP" xml:id="properNoun"/>
<!-- ... -->
</fvLib>

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

Example

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

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

This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.

Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.

Example

The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.

<encodingDesc>
<!-- ... -->
 <classDecl>
<!-- ... -->
  <taxonomy datcat="https://universaldependencies.org/u/dep/index.html"
   xml:id="UD-SYN">
   <desc>
    <term>UD syntactic relations</term>
   </desc>
   <category valueDatcat="https://universaldependencies.org/u/dep/acl.html"
    xml:id="acl">
    <catDesc>
     <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>
   </category>
   <category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"
    xml:id="acl_relcl">
    <catDesc>
     <term>acl:relcl</term>: relative clause modifier</catDesc>
   </category>
   <category valueDatcat="https://universaldependencies.org/u/dep/advcl.html"
    xml:id="advcl">
    <catDesc>
     <term>advcl</term>: Adverbial clause modifier</catDesc>
   </category>
<!-- ... -->
  </taxonomy>
 </classDecl>
</encodingDesc>

The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.

Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.

Example

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

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

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

Example

The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.


<!-- in the dictionary header --><encodingDesc>
 <classDecl>
  <taxonomy xml:id="domains">
<!--...-->
   <category xml:id="domain.medical_and_health_sciences">
    <catDesc xml:lang="en">Medical and Health Sciences</catDesc>
    <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>
    <category valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"
     xml:id="domain.medical_and_health_sciences.medicine">
     <catDesc xml:lang="en">
      <term>Medicine</term>
      <gloss>
<!--...-->
      </gloss>
     </catDesc>
     <catDesc xml:lang="pt">
      <term>Medicina</term>
      <gloss>
<!--...-->
      </gloss>
     </catDesc>
    </category>
   </category>
<!--...-->
  </taxonomy>
 </classDecl>
</encodingDesc>
<!-- inside an <entry> element: -->
<usg type="domain"
 valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>

In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).

Note

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

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

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

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

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

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

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

att.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
Membersavailability bibl biblStruct correspDesc listBibl listObject seriesStmt sourceDesc textClass xenoData
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
Status Optional
Datatype teidata.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
Membersback body div facsimile front graphic listAnnotation object p ptr ref standOff surface term text
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersdate ellipsis state
Attributes
unitnames the unit used for the measurement
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
Status Optional
Datatype teidata.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 teidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Datatype teidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

att.divLike

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

att.docStatus

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

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersatt.transcriptional [rt] affiliation date eventName gender name objectName org orgName persName persPronouns persona state trash
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
Status Optional
Datatype teidata.xTruthValue
Default false
Note

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

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

att.formula

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

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

att.fragmentable

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

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

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype ID
Note

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

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

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

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

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

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

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

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

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

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

att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
Moduleanalysis
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
changepoints to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
Moduletranscr
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<group>
 <text xml:id="t1-g1-t1" xml:lang="mi">
  <body xml:id="t1-g1-t1-body1">
   <div type="chapter">
    <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
 <text xml:id="t1-g1-t2" xml:lang="en">
  <body corresp="#t1-g1-t1-body1"
   xml:id="t1-g1-t2-body1">
   <div type="chapter">
    <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
</group>

In this example a <group> contains two texts, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.


<!-- In a placeography called "places.xml" --><place corresp="people.xml#LOND2 people.xml#GENI1"
 xml:id="LOND1">
 <placeName>London</placeName>
 <desc>The city of London...</desc>
</place>
<!-- In a literary personography called "people.xml" -->
<person corresp="places.xml#LOND1 #GENI1"
 xml:id="LOND2">
 <persName type="lit">London</persName>
 <note>
  <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
 </note>
</person>
<person corresp="places.xml#LOND1 #LOND2"
 xml:id="GENI1">
 <persName type="lit">London’s Genius</persName>
 <note>
  <p>Personification of London’s genius. Appears as an
     allegorical character in mayoral shows.
  </p>
 </note>
</person>

In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

synch(synchronous) points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOfpoints to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

nextpoints to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

excludepoints to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>
Note

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

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 teidata.text
<head style="text-align: center; font-variant: small-caps">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>
Note

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

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

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

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

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

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. 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 agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 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 abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

Example
Blessed are the
<choice>
 <sic>cheesemakers</sic>
 <corr cert="high" resp="#editor">peacemakers</corr>
</choice>: for they shall be called the children of God.
Example

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

att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender graphic head hi idno imprint item keywords label licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@source]">
<sch:let name="srcs"
 value="tokenize( normalize-space(@source),' ')"/>
<sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | +Information with a Text]
Moduletei
Membersback body div facsimile front gloss graphic listAnnotation object p ptr ref standOff surface term text
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersdate ellipsis state
Attributes
unitnames the unit used for the measurement
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
Status Optional
Datatype teidata.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 teidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Datatype teidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

att.divLike

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

att.docStatus

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

att.edition

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

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersatt.transcriptional [rt] affiliation date eventName gender name objectName org orgName persName persPronouns persona state trash
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
Status Optional
Datatype teidata.xTruthValue
Default false
Note

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

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

att.formula

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

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

att.fragmentable

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

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

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype ID
Note

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

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

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

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

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

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

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

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

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

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

att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
Moduleanalysis
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
changepoints to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
Moduletranscr
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<group>
 <text xml:id="t1-g1-t1" xml:lang="mi">
  <body xml:id="t1-g1-t1-body1">
   <div type="chapter">
    <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
 <text xml:id="t1-g1-t2" xml:lang="en">
  <body corresp="#t1-g1-t1-body1"
   xml:id="t1-g1-t2-body1">
   <div type="chapter">
    <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
</group>

In this example a <group> contains two texts, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.


<!-- In a placeography called "places.xml" --><place corresp="people.xml#LOND2 people.xml#GENI1"
 xml:id="LOND1">
 <placeName>London</placeName>
 <desc>The city of London...</desc>
</place>
<!-- In a literary personography called "people.xml" -->
<person corresp="places.xml#LOND1 #GENI1"
 xml:id="LOND2">
 <persName type="lit">London</persName>
 <note>
  <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
 </note>
</person>
<person corresp="places.xml#LOND1 #LOND2"
 xml:id="GENI1">
 <persName type="lit">London’s Genius</persName>
 <note>
  <p>Personification of London’s genius. Appears as an
     allegorical character in mayoral shows.
  </p>
 </note>
</person>

In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

synch(synchronous) points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOfpoints to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

nextpoints to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

excludepoints to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>
Note

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

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 teidata.text
<head style="text-align: center; font-variant: small-caps">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>
Note

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

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

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

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

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

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. 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 agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 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 abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

Example
Blessed are the
<choice>
 <sic>cheesemakers</sic>
 <corr cert="high" resp="#editor">peacemakers</corr>
</choice>: for they shall be called the children of God.
Example

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

att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global [TEI abstract addName addrLine address affiliation analytic anchor annotation appInfo application author availability back bibl biblScope biblStruct body cell change citeData citeStructure classCode conversion correspAction correspContext correspDesc country date desc div edition editionStmt editor ellipsis email encodingDesc eventName facsimile figDesc figure fileDesc forename formula front genName gender gloss graphic head hi idno imprint item keywords label lb licence link list listAnnotation listBibl listObject meeting monogr name note noteGrp notesStmt object objectIdentifier objectName org orgName p persName persPronouns persona postBox postCode profileDesc ptr pubPlace publicationStmt publisher quote rb ref region revisionDesc roleName row rt ruby s schemaRef series seriesStmt settlement sourceDesc standOff state street surface surname table teiHeader term text textClass title titleStmt unit unitDecl unitDef when xenoData]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

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

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

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

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

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

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

</bibl>
Example
<elementRef key="p" source="tei:2.0.1"/>

Include in the schema an element named p available from the TEI P5 2.0.1 release.

Example
<schemaSpec ident="myODD"
 source="mycompiledODD.xml">
<!-- further declarations specifying the components required -->
</schemaSpec>

Create a schema using components taken from the file mycompiledODD.xml.

att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media [graphic] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of teidata.word separated 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="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

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

att.locatable

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

att.measurement

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

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

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

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

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

Schematron

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

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

att.media

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

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms]
Moduletei
Membersatt.personal [addName eventName forename genName name objectName orgName persName roleName surname] affiliation author country editor pubPlace region settlement state trash
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
Membersformula listAnnotation s
Attributes
notationnames the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

att.personal

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

att.placement

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

att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Membersannotation licence link note noteGrp ptr ref term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
</sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
 <ptr target="pol/UDHR/text.xml#pol_txt_1-head"
  targetLang="pl" type="tuv" xml:id="pol-swh_aln_2.1.1-ptr"/>
 <ptr target="swh/UDHR/text.xml#swh_txt_1-head"
  targetLang="sw" type="tuv" xml:id="pol-swh_aln_2.1.2-ptr"/>
</linkGrp>

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

Note

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

targetspecifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

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

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

att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions [date ellipsis state]
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.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 teidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">
 <gap atLeast="1" atMost="2"
  extent="one or two letters" reason="illegible" unit="chars"/>
</del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern
Europe since 1986, and since 1992 has provided <measure atLeast="120000000"
 commodity="currency" unit="USD">more than
$120m</measure> in aid to Ukrainians.

att.resourced

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

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Moduletei
Memberss
Attributes
function(function) characterizes the function of the segment.
Status Optional
Datatype teidata.enumerated
Note

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

att.sortable

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

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

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

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music]
Modulefigures
Memberscell row
Attributes
role(role) indicates the kind of information held in this cell or in each cell of this row.
Status Optional
Datatype teidata.enumerated
Suggested values include:
label
labelling or descriptive information only.
data
data values. [Default]
Note

When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent row element.

rows(rows) indicates the number of rows occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.

cols(columns) indicates the number of columns occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
Moduletei
Membersellipsis
Attributes
startindicates the location within a temporal alignment at which this element begins.
Status Optional
Datatype teidata.pointer
Note

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

endindicates the location within a temporal alignment at which this element ends.
Status Optional
Datatype teidata.pointer
Note

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

att.transcriptional

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

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

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

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

att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
MembersTEI addName affiliation anchor application bibl biblStruct change correspAction correspDesc country date desc div eventName figure forename formula genName gender graphic head idno label link list listAnnotation listBibl listObject name note noteGrp object objectName org orgName persName persPronouns ptr rb ref region roleName rt ruby s schemaRef settlement standOff state surface surname table term text title unit unitDef xenoData
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype teidata.enumerated
<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l>…</l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</l>
  <l>…</l>
 </lg>
</div>
Note

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

subtype(subtype) provides a sub-categorization of the element, if needed
Status Optional
Datatype teidata.enumerated
Note

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

Schematron

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

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

att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membersatt.transcriptional [rt] div figure head hi label note noteGrp p text
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Status Optional
Datatype teidata.pointer

Schema Grobid: Datatypes

teidata.certainty

+ and $srcs[2]"> When used on a schema description element (like
<sch:value-of select="name(.)"/>), the @source attribute
should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.)
</sch:report>
</sch:rule>
teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
teidata.probCert
Note

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

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

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

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

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

</bibl>
Example
<elementRef key="p" source="tei:2.0.1"/>

Include in the schema an element named p available from the TEI P5 2.0.1 release.

Example
<schemaSpec ident="myODD"
 source="mycompiledODD.xml">
<!-- further declarations specifying the components required -->
</schemaSpec>

Create a schema using components taken from the file mycompiledODD.xml.

att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media [graphic] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of teidata.word separated 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="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

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

att.locatable

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

att.measurement

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

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

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

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

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

Schematron

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

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

att.media

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

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms]
Moduletei
Membersatt.personal [addName eventName forename genName name objectName orgName persName roleName surname] affiliation author country editor pubPlace region settlement state trash
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
Membersformula listAnnotation quote s
Attributes
notationnames the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

att.personal

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

att.placement

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

att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Membersannotation gloss licence link note noteGrp ptr ref term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
</sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
 <ptr target="pol/UDHR/text.xml#pol_txt_1-head"
  targetLang="pl" type="tuv" xml:id="pol-swh_aln_2.1.1-ptr"/>
 <ptr target="swh/UDHR/text.xml#swh_txt_1-head"
  targetLang="sw" type="tuv" xml:id="pol-swh_aln_2.1.2-ptr"/>
</linkGrp>

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

Note

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

targetspecifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

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

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

att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions [date ellipsis state]
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.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 teidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">
 <gap atLeast="1" atMost="2"
  extent="one or two letters" reason="illegible" unit="chars"/>
</del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern
Europe since 1986, and since 1992 has provided <measure atLeast="120000000"
 commodity="currency" unit="USD">more than
$120m</measure> in aid to Ukrainians.

att.resourced

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

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Moduletei
Memberss
Attributes
function(function) characterizes the function of the segment.
Status Optional
Datatype teidata.enumerated
Note

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

att.sortable

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

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

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

att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
Moduletei
Memberslb
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
Status Optional
Datatype teidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element

<sch:rule context="tei:*[@spanTo]">
<sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
</sch:assert>
</sch:rule>
Note

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

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music]
Modulefigures
Memberscell row
Attributes
role(role) indicates the kind of information held in this cell or in each cell of this row.
Status Optional
Datatype teidata.enumerated
Suggested values include:
label
labelling or descriptive information only.
data
data values. [Default]
Note

When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent row element.

rows(rows) indicates the number of rows occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.

cols(columns) indicates the number of columns occupied by this cell or row.
Status Optional
Datatype teidata.count
Default 1
Note

A value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
Moduletei
Membersellipsis
Attributes
startindicates the location within a temporal alignment at which this element begins.
Status Optional
Datatype teidata.pointer
Note

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

endindicates the location within a temporal alignment at which this element ends.
Status Optional
Datatype teidata.pointer
Note

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

att.transcriptional

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

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

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

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

att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
MembersTEI addName affiliation anchor application bibl biblStruct change correspAction correspDesc country date desc div eventName figure forename formula genName gender gloss graphic head idno label lb link list listAnnotation listBibl listObject name note noteGrp object objectName org orgName persName persPronouns ptr quote rb ref region roleName rt ruby s schemaRef settlement standOff state surface surname table term text title unit unitDef xenoData
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype teidata.enumerated
<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l>…</l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</l>
  <l>…</l>
 </lg>
</div>
Note

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

subtype(subtype) provides a sub-categorization of the element, if needed
Status Optional
Datatype teidata.enumerated
Note

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

Schematron

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

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

att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membersatt.transcriptional [rt] div figure head hi label note noteGrp p text
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Status Optional
Datatype teidata.pointer

Schema Grobid: Datatypes

teidata.certainty

@@ -1390,13 +1417,13 @@ - - - + + + - + @@ -1409,13 +1436,13 @@ - - - + + + - + @@ -1497,7 +1524,7 @@ { pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)" } - + @@ -1522,7 +1549,7 @@ - +
teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
teidata.probCert
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
Declaration
 tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0,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>
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.

Content model
<content>
 <dataRef name="duration"/>
</content>
Declaration
 tei_teidata.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="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>
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.

Example
<figure>
 <head>The TEI Logo</head>
 <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
   background.</figDesc>
 <graphic height="600px"
  url="http://www.tei-c.org/logos/TEI-600.jpg" width="600px"/>
</figure>
Example
<figure>
 <head>The TEI Logo</head>
 <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
   background.</figDesc>
 <graphic height="600px"
  url="http://www.tei-c.org/logos/TEI-600.jpg" width="600px"/>
</figure>
Note

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

Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
Declaration
 tei_teidata.point =
    token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>
 <surface lrx="400" lry="280" ulx="0" uly="0">
  <zone points="220,100 300,210 170,250 123,234">
   <graphic url="handwriting.png"/>
  </zone>
 </surface>
</facsimile>
Example
<facsimile>
 <surface lrx="400" lry="280" ulx="0" uly="0">
  <zone points="220,100 300,210 170,250 123,234">
   <graphic url="handwriting.png"/>
  </zone>
 </surface>
</facsimile>
Note

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

teidata.pointer

@@ -1687,7 +1714,7 @@
teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei
Used by
Element:

Schema Grobid: Macros

macro.limitedContent

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

macro.paraContent

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

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
addName addrLine affiliation author biblScope country edition editor email eventName forename genName gender label name objectName orgName persName persPronouns pubPlace publisher rb region roleName rt s settlement street surname term unit
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
+tei_macro.paraContent = ( text | tei_model.paraPart )*

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
addName addrLine affiliation author biblScope country edition editor email eventName forename genName gender gloss label name objectName orgName persName persPronouns pubPlace publisher rb region roleName rt s settlement street surname term unit
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
 tei_macro.phraseSeq =
    (
       text
@@ -1697,7 +1724,7 @@
     | tei_model.global
    )*

macro.phraseSeq.limited

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

macro.specialPara

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

macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
cell change item licence note quote
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
 tei_macro.specialPara =
    (
       text
@@ -1706,9 +1733,9 @@
     | tei_model.inter
     | tei_model.divPart
     | tei_model.global
-   )*
 Home Feedback 
Patrice Lopez. Date: 2024-02-08
 Home Feedback 
Patrice Lopez. Date: 2024-02-09
\ No newline at end of file diff --git a/grobid-home/schemas/dtd/Grobid.dtd b/grobid-home/schemas/dtd/Grobid.dtd index 7f3eb146c2..ea425389c8 100644 --- a/grobid-home/schemas/dtd/Grobid.dtd +++ b/grobid-home/schemas/dtd/Grobid.dtd @@ -1,6 +1,6 @@ + + + @@ -1556,6 +1581,16 @@ scheme %teidata.pointer; #IMPLIED > %tei_att.typed.attributes; %tei_att.placement.attributes; %tei_att.written.attributes; > + + + + @@ -1776,6 +1811,13 @@ age %teidata.enumerated; #IMPLIED > + + + + diff --git a/grobid-home/schemas/odd/Grobid.compiled.odd b/grobid-home/schemas/odd/Grobid.compiled.odd index f1eaf9cd4a..ba06db510b 100644 --- a/grobid-home/schemas/odd/Grobid.compiled.odd +++ b/grobid-home/schemas/odd/Grobid.compiled.odd @@ -15,7 +15,7 @@

created on Sunday 05th October 2014 06:25:09 AM

 - File edited with RomaJS + File edited with RomaJS @@ -532,6 +532,69 @@ The MS. was lost in transmission by mail from 1.3.1. Attribute Classes + + provides attributes to indicate whether or not the element + concerned is considered to mark the end of an orthographic token in the same way + as whitespace. + fournit un attribut pour indiquer si un élément est +consideré ou pas comme marquant la fin d'un mot orthographique, comme +le fait une espace. + 当該要素が空白と同じ方法で正字トークンの終わりを示すとみなされるかどうかを示す属性を提供する。 + + + indicates whether or not the element + bearing this attribute should be considered to mark the end of + an orthographic token in the same way as whitespace. + indique si l'élément qui porte cet attribut + peut être considéré comme une espace blanc indiquant la fin d'un mot + orthographique. + この属性を持つ要素が空白と同じ方法で正字トークンの終わりを示すとみなされるべきかどうかを示す。 + + + + the element bearing this attribute is considered +to mark the end of any adjacent orthographic token irrespective of the presence +of any adjacent whitespace + l'élément qui porte cet attribut + peut être considéré comme indiquant la fin d'un mot + orthographique + この属性を持つ要素は、隣接する任意の空白の存在に関係なく、隣接する正字法トークンの終わりをマークするとみなされる。 + + + the element bearing this attribute is considered +not to mark the end of any adjacent orthographic token irrespective of the presence +of any adjacent whitespace + l'élément qui porte cet attribut + ne peut être pas considéré comme indiquant la fin d'un mot + orthographique + この属性を持つ要素は、隣接する空白の存在に関係なく、隣接する正字法トークンの終わりをマークしないとみなされる。 + + + the encoding does not take any position on this issue. + l'encodage ne prends aucune position sur la question. + 当該符号化はこの問題に関していかなる立場もとらない。 + + + +

In the following lines from the Dream of the Rood, + linebreaks occur in the middle of the words lāðost + and reord-berendum. +

+ + + ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . + leodum la ðost ærþan ichim lifes + ƿeȝ rihtne ȝerymde reord be + rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... + + + + + + + 3.11.3. Milestone +Elements + provides attributes that may be used to supply a canonical reference as a means of identifying the @@ -3397,6 +3460,122 @@ subject, predicate etc. may be more appropriate. Such constraints will typically 9.1. Dictionary Body and Overall Structure + + provides attributes identifying the source edition from which + some encoded feature derives. + fournit des attributs identifiant l'édition source dont provient une quelconque caractéristique encodée. + 符号化された属性が派生する元のソースのエディションを特定する属性を提供する。 + + + edition + édition + 版 + supplies a sigil or other arbitrary identifier for the source edition in which + the associated feature (for example, a page, column, or line + break) occurs at this point in the text. + fournit un identifiant arbitraire pour l'édition source dans laquelle la caractéristique associée + (par exemple, une page, une colonne ou un saut de ligne) apparaît à ce point du texte. + 関連する属性（ページ・段落・行の切れ目）がテキストのこの地点において発生するソースのエディションについての印やその他の任意の識別子を提供する。 + + + + edition reference + 参照 + provides a pointer to the source edition in which + the associated feature (for example, a page, column, or line + break) occurs at this point in the text. + このポインタが示すのは、当該テキスト中に現れる（頁や段、行等の）関連する素性が生じる元の版である。 + + + + + + Of Mans First Disobedience, and the Fruit + Of that Forbidden Tree, whose mortal tast + Brought Death into the World, and all our woe, + + + + + + Olaf Stapledon, + Starmaker, Methuen, 1937 + Olaf Stapledon, + Starmaker, Dover, 1968 + + +

Looking into the future aeons from the supreme moment of + the cosmos, I saw the populations still with all their + strength maintaining theessentials of their ancient culture, + still living their personal lives in zest and endless + novelty of action, … I saw myself still + preserving, though with increasing difficulty, my lucid + con-sciousness;

+ + + + provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. + 포함보다는 포인터 메카니즘을 통하여 구분된 텍스트 구간을 나타내는 요소의 속성을 제공한다. + 提供元素的屬性，這些元素使用參照機制來限定某一文字段，而非包含此文字段。 + テキスト幅の範囲を内容としてではなく参照機能を使って示す要素に付与さ + れる属性を示す。 + fournit des attributs pour les éléments qui délimitent un passage de texte par des mécanismes de pointage plutôt qu'en entourant le passage. + proporciona atributos para elementos que delimitan un fragmento de texto utilizando los señalizadores en lugar de cerrando el texto. + assegna degli attributi agli elementi che delimitano una porzione di testo utilizzando dei puntatori invece di racchiudere il testo stesso + + + indicates the end of a span initiated by the element + bearing this attribute. + 이 속성을 포함하는 요소에 의해 시작된 구간의 끝을 나타낸다. + 指出文字段的結尾，該文字段以帶有此屬性的元素開頭。 + 当該要素が示す範囲の終点を示す。 + indique la fin d'un passage introduit par l'élément portant cet attribut. + indica el final de un fragmento de texto iniciado con el elemento al cual es asignaado el atributo. + indica la fine della porzione di testo che ha inizio con l'elemento a cui è assegnato l'attributo + + + The @spanTo attribute must point to an element following the + current element + + + +The element indicated by @spanTo () must follow the current element + + + + + + + +

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

+ + +

Le passage est défini comme courant depuis le début du contenu de l'élément pointeur (s'il y en a un) jusqu'à la fin du contenu de l'élément + pointé par l'attribut spanTo (s'il y en a un), dans l'ordre du document. Si aucune valeur n'est fournie pour l'attribut, il est entendu + que le passage est de même étendue que l'élément pointeur.

+ + +

El span se define como ejecutándose en la orden del documento des del comienzo del contenido del elemento indicado (si lo hay) al extremo del contenido del elemento señalado por el atributo del spanTo (si lo hay). + Si no se suministra ningún valor para el atributo, la asunción es que el span es coextensivo con el elemento indicado.

+ + +

+ 当該範囲は、当該文書中にある、(もしあれば)参照要素の内容の始点から、 + (もしあれば)属性spanToで示された要素の内容の終点までになる。 + 当該属性に値がない場合、当該範囲は、当該参照要素と同じ範囲と想定す + る。 +

+ + + 11.3.1.4. Additions and Deletions + 1.3.1. Attribute Classes + provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference @@ -3805,44 +3984,27 @@ or corporate bodies. 3.6. Names, Numbers, Dates, Abbreviations, and Addresses - - groups elements used for arbitrary segmentation. - 임의적 분할에 사용되는 요소를 모아 놓는다. - 匯集用於隨機分割的元素。 - 任意の区分で使用される要素をまとめる。 - regroupe des éléments utilisés pour une segmentation - arbitraire. - agrupa elementos usados por una segmentación arbitraria. - raggruppa elementi utilizzati per una segmentazione - arbitraria - - - - - +groups elements used for arbitrary segmentation.임의적 분할에 사용되는 요소를 모아 놓는다.匯集用於隨機分割的元素。任意の区分で使用される要素をまとめる。regroupe des éléments utilisés pour une segmentation + arbitraire.agrupa elementos usados por una segmentación arbitraria.raggruppa elementi utilizzati per una segmentazione + arbitraria

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

- - +

Les principes sur lesquels repose la segmentation, ainsi que tout code particulier ou valeur d'attribut utilisée, doivent être définis explicitement dans l'élément segmentation de l'élément encodingDesc situé dans l'En-tête TEI associé.

- - +

Los principios en los cuales se realiza la segmentación, y cualesquiera sean los códigos o valores de atributo especiales usados, se deben definir explícitamente en el elemento segmentación del encodingDesc dentro del encabezado TEI asociado.

- - +

どの区分、どのコード、どの属性値を使うかを決める原則は、関連する TEIヘダー内の要素encodingDescにある要素 segmentation中で明示的に宣言されるべきである。

- - + 16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories - - + groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. 인쇄상 구분되나 특정 기능이 없는 구 층위 요소를 모아 놓는다. @@ -6786,6 +6948,74 @@ one initial. 3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language + + quotation + 인용 + 引文 + citation + cita + citazione + contains a phrase or passage attributed by the narrator or author to some agency external + to the text. + 해설자 또는 저자에 의해, 텍스트의 외부 주체에 의해 생성된 것이라 밝혀진 구 또는 단락을 + 포함한다. + 包含敘述者或作者引用自文本以外來源的字 (句) 詞或段落。 + 語り手や著者が、当該テキスト外にあるものに向けた、一節を示す。 + contient une expression ou un passage que le + narrateur ou l'auteur attribue à une origine extérieure au texte. + contiene una frase o pasaje atribuido por el narrador o + autor a un agente externo al texto. + contiene una frase o un brano attribuito dall'autore o + dal narratore a soggetti esterni al testo + + + + + + + + + + + + Lexicography has shown little sign of being affected by the + work of followers of J.R. Firth, probably best summarized in his + slogan, You shall know a word by the company it + keeps + (Firth, 1957) + + + + C'est sûrement ça + qu'on appelle la glorieuse liberté des enfants de Dieu. Aime et fais tout ce que tu + voudras.Mais moi, ça me démolit. + + + + 孟懿子問孝。子曰：無違。 + (論語：卷一：為政第二) + + + +

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

+ + +

Si une référence bibliographique est donnée comme source de la citation, + on peut les regrouper dans l'élément cit.

+ + +

Si una citación bibliográfica es proporcionada como fuente de una cita, las dos se pueden + agrupar usando el elemento CIT +

+ + +

引用部分に書誌情報の引用がある場合、この2つの部分は、要素 citでまとめられる。

+ + + 3.3.3. Quotation + 4.3.1. Grouped Texts + description 기술 @@ -6924,6 +7154,66 @@ one initial. 22.4.1. Description of Components + + gloss + glose + identifies a phrase or word used to provide a gloss or definition for some other word or + phrase. + 다른 단어나 구에 대한 해설 또는 정의를 제공할 때 사용되는 구나 단어를 표시한다. + 標明用來為另一個字詞下定義或提供註解的字詞。 + 語句の説明や定義を示す。 + identifie une expression ou un mot utilisé pour fournir + une glose ou une définition à quelque autre mot ou expression. + identifica una locución o palabra usada para proporcionar + una glosa o definición sobre otra palabra o frase. + identifica un sintagma o una parola che fornisce una + glossa o definizione per qualche altra parola o sintagma. + + + + + + + + + + + + + + + We may define discoursal point of view as the relationship, expressed + through discourse structure, between the implied author or some other addresser, and the + fiction. + + + + Les + embrayeurs sont une classe de mots dont le sens varie avec la situation; ces + mots, n'ayant pas de référence propre dans la langue, ne reçoivent un référent que + lorsqu'ils sont inclus dans un message. + + + + 我們可以定義 戀母情結 為 佛洛伊德心理分析理論中的重要觀念，指三至六歲大的男孩在性慾上有一種戀母情結的階段，這情結更進一步發展成對父親的忌妒仇視，甚至亟欲除之而後快。 + + + +

The target and cRef attributes are mutually exclusive.

+ + +

Les attributs target et cRef sont exclusifs l'un de l'autre.

+ + +

Los atributos blanco y cRef son mutuamente exclusivos.

+ + +

属性targetとcRefは、排他的に使用される。

+ + + 3.4.1. Terms and Glosses + 22.4.1. Description of Components + term terme @@ -9543,6 +9833,143 @@ psychological significance. 11.1. Digital Facsimiles + + line beginning + 행 바꿈 + 分行 + début de ligne + inicio de línea + inizio di riga + Zeilenanfang + marks the beginning of a new (typographic) line in some edition or version of a text. + 텍스트의 편집 또는 버전에서 새로운 (인쇄상의) 행 시작을 표지한다. + 標記某版本文本裡 (在印刷上) 的新起行。 + ある版における新しい(印刷上の)行の始まりを示す。 + marque le début d'une nouvelle ligne (typographique) dans + une édition ou dans une version d'un texte. + marca el comienzo de una nueva línea (topográfica) en + alguna edición o versión del texto. + segna l'inizio di una nuova riga (tipografica) in qualche + edizione o versione di un testo. + markiert den Anfang einer neuen typographischen + Zeile in einer bestimmten Auflage oder Version eines Textes. + + + + + + + + + + +

This example shows typographical line breaks within metrical lines, where they occur at different + places in different editions:

+ + Of Mans First Disobedience, and the Fruit + Of that Forbidden Tree, whose mortal tast + Brought Death into the World, and all our woe, + + + +

Cet exemple montre les sauts de ligne dans des vers, qui apparaissent à différents endroits selon les éditions.

+ + Of Mans First Disobedience, and the Fruit + Of that Forbidden Tree, whose mortal tast + Brought Death into the World, and all our woe, + + + +

Dieses Beispiel zeigt typografische Zeilenumbrüche innerhalb von Verszeilen, so wie sie an + verschiedenen Stellen in unterschiedlichen Ausgaben auftreten:

+ + Of Mans First Disobedience, and the Fruit + Of that Forbidden Tree, whose mortal tast + Brought Death into the World, and all our woe, + + + +

This example encodes typographical line breaks as a means of +preserving the visual appearance of a title page. The break +attribute is used to show that the line break does not (as elsewhere) +mark the start of a new word.

+ + With Additions, ne-ver before Printed. + + + +

Cet exemple encode les sauts de ligne pour montre l'apparence visuelle d'une page titre. L'attribut break est utilisé pour montrer que le saut de ligne ne marque pas le début d'un nouveau mot.

+ + + L'auteur susdict supplie les Lecteurs +benevoles, soy reserver à rire au +soi-xante & dixhuytiesme livre. + + + + +

Dieses Beispiel kodiert typografische Zeilenumbrüche, um das visuelle Erscheinungsbild einer + Titelseite zu bewahren. Das break-Attribut zeigt an, dass der Zeilenumbruch nicht + (wie anderswo) den Anfang eines neuen Wortes markiert.

+ + With Additions, ne-ver before Printed. + + + +

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

+

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

+ + +

Par convention, l'élément lb apparaît à l’endroit du texte où commence une nouvelle + ligne. L'attribut n, s’il est utilisé, donne un nombre ou une autre valeur associée + au texte entre ce point et l’élément suivant lb, spécifiquement le numéro de la ligne + dans la page, ou une autre unité de mesure appropriée. Cet élément est prévu pour être employé + pour marquer un saut de ligne sur un manuscrit ou sur une page imprimée, à l’endroit où il se + survient; on n’utilisera pas de balisage structurel comme une succession de vers (pour lequel + l’élément l est disponible) sauf dans le cas où des blocs structurés ne peuvent pas + être marqués autrement.

+

L'attribut type sera employé pour caractériser toute espèce de caractéristiques + du saut de ligne, sauf la coupure des mots (indique par + l'attribut break) ou la source concernée.

+ + +

当該要素にあるグローバル属性nは、要素lbに続く 行と関連する数値を示す。符号化する人は、改行を示す当該数値が、ペー + ジ内にある物理的行数またはテキストの論理構造と関連するかについて、 明確で一貫した方針を採るべきである。 一般には、要素lbは、参照する行の開始地点にあるべきである。

+

要素lbは、散文中における印刷上の行を示すためのものである。 韻文中の行を示す要素lとは注意して使い分けるべきである。

+ + +

Es ist Konvention, dass lb-Elemente an der Stelle im Text stehen sollen, + an der eine neue Zeile beginnt. Das n-Attribut enhält gegebenenfalls + die Nummer der Zeile oder einen ähnlichen Wert, der sich auf den Text bezieht, + der bis zum nächsten lb folgt, typischerweise die Nummer einer Zeile + auf einer Seite oder andere einschlägige Einheiten.

+

Das Element dient dazu, typographische oder paläographische Phänomene an der + Stelle zu beschreiben, an der sie auf dem Schriftträger sichtbar sind; + es sollte nicht für Struktureinheiten wie z. B. Verszeilen in Lyrik verwendet + werden (wofür das Element l zur Verfügung steht), außer wenn derartige + Struktureinheiten anders nicht markiert werden können.

+

Das type-Attribut kann verwendet werden, den Zeilenwechsel näher + zu beschreiben, wenn nicht die speziellen Attribute break + (Worttrennung), ed oder edRef (Textzeuge, in dem der + Zeilenwechsel vorkommt) verwendet werden können.

+ + + 3.11.3. Milestone +Elements + 7.2.5. Speech Contents + analytic level 분석적 층위 @@ -19224,12 +19651,40 @@ contexts.

17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations -s-units-단위句子單元phraseoraciónunità sSatzeinheitcontains a sentence-like division of a text.텍스트의 문장에 해당하는 부분을 포함한다.包含文字中一個句子組成的區段。文に相当するテキスト単位を示す。contient une division textuelle de type phrasecontiene una oración del texto.contiene la divisione del testo del tipo proposizioneenthält einen satzähnlichen Textabschnitt. + + s-unit + s-단위 + 句子單元 + phrase + oración + unità s + Satzeinheit + contains a sentence-like division of a text. + 텍스트의 문장에 해당하는 부분을 포함한다. + 包含文字中一個句子組成的區段。 + 文に相当するテキスト単位を示す。 + contient une division textuelle de type phrase + contiene una oración del texto. + contiene la divisione del testo del tipo proposizione + enthält einen satzähnlichen Textabschnitt. + + + + + + + + + + + + You may not nest one s element within another: use seg instead - + + A short affair @@ -19237,42 +19692,50 @@ contexts.

When are you leaving? Tomorrow. - + + Quandpartez-vous ? Demain. - + + 士何事？” 尚志。 - + +

The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the seg should be used instead.

The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

- + +

L'élément s peut être utilisé pour marquer les phrases ou toute autre segmentation existant dans un texte, pourvu que cette segmentation soit présente du début à la fin du texte, complète et sans imbrication. Dans le cas d'une segmentation partielle ou récursive, l'élément seg doit remplacer l'élément s.

L'attribut type peut être utilisé pour indiquer le type de segmentation prévue, selon une typologie appropriée.

- + +

テキストや句レベルの要素が混在する。また、当該要素自身も含むかもし れない。

要素sが、ある単位の全体を完全に、入れ子なく示す場合には、 正書形の文や、他のテキスト部分を示すために使われるかもしれない。

- + +

Das s-Element wird verwendet um orthographische Sätze oder andere Textsegmente zu kodieren, vorausgesetzt das Segment ist lückenlos, vollständig und nicht verschachtelt. Für unvollständige oder rekursive Segmente soll stattdessen das seg-Element verwendet werden.

Das type-Attribut wird verwendet, um den Segmenttyp entsprechend einer geeigneten Typologie anzugeben.

- + + 17.1. Linguistic Segment Categories 8.4.1. Segmentation - Trashcontains noise information to be ignored, typically from vectoriel images + +Trashcontains noise information to be ignored, typically from vectoriel images diff --git a/grobid-home/schemas/odd/Grobid.odd b/grobid-home/schemas/odd/Grobid.odd index adf4343fd9..0d93153de6 100644 --- a/grobid-home/schemas/odd/Grobid.odd +++ b/grobid-home/schemas/odd/Grobid.odd @@ -15,7 +15,7 @@

created on Sunday 05th October 2014 06:25:09 AM

 - File edited with RomaJS + File edited with RomaJS @@ -27,7 +27,7 @@ - + @@ -245,30 +245,27 @@ - + + Copyrights owner of the document are the authorsCopyrights owner of the document is the publisher \ No newline at end of file diff --git a/grobid-home/schemas/rng/Grobid.rnc b/grobid-home/schemas/rng/Grobid.rnc index d4c8bfb242..d27a11f28f 100644 Binary files a/grobid-home/schemas/rng/Grobid.rnc and b/grobid-home/schemas/rng/Grobid.rnc differ diff --git a/grobid-home/schemas/rng/Grobid.rng b/grobid-home/schemas/rng/Grobid.rng index dfc0acfe19..4de58d55bd 100644 --- a/grobid-home/schemas/rng/Grobid.rng +++ b/grobid-home/schemas/rng/Grobid.rng @@ -5,7 +5,7 @@ xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes" ns="http://www.tei-c.org/ns/1.0">