TEI for Argumentation
This TEI customization defines elements and attributes for the annotation of argumentative structures within texts. It extends the type attribute on the <list> element and its child <item> elements to support the representation of arguments consisting of a set of premises, an inference rule, and a conclusion. It introduces a new about attribute on the att.global.analytic attribute class to specify what the text is about, as distinct from the ana attribute, which represents what is said about it. Additionally, it broadens the scope of the prev attribute to allow reference to multiple logical antecedents.
Elements
<TEI>
| <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text] | |||||||||
| Module | textstructure | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. | ||||||||
| Example | <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <fileDesc> <titleStmt> <title>The shortest TEI Document Imaginable</title> </titleStmt> <publicationStmt> <p>First published as part of TEI P2, this is the P5 version using a namespace.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <text> <body> <p>This is about the shortest TEI document imaginable.</p> </body> </text> </TEI> | ||||||||
| Example | <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <fileDesc> <titleStmt> <title>A TEI Document containing four page images </title> </titleStmt> <publicationStmt> <p>Unpublished demonstration file.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <facsimile> <graphic url="page1.png"/> <graphic url="page2.png"/> <graphic url="page3.png"/> <graphic url="page4.png"/> </facsimile> </TEI> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="teiHeader"/>
<alternate>
<sequence>
<classRef key="model.resource"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="TEI" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<elementRef key="TEI" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element TEI
{
attribute version { text }?,
( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}⚓ | ||||||||
<author>
| <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource. In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast. Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given. |
| Example | <author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author> <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author> <orgName key="BBC">British Broadcasting Corporation</orgName>: Radio 3 Network </author> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element author { 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.] | |||||||||
| Module | header | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | header: publicationStmt | ||||||||
| May contain | |||||||||
| Note | A consistent format should be adopted | ||||||||
| Example | <availability status="restricted"> <p>Available for academic research purposes only.</p> </availability> <availability status="free"> <p>In the public domain</p> </availability> <availability status="restricted"> <p>Available under licence from the publishers.</p> </availability> | ||||||||
| Example | <availability> <licence target="http://opensource.org/licenses/MIT"> <p>The MIT License applies to this document.</p> <p>Copyright (C) 2011 by The University of Victoria</p> <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p> <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p> <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p> </licence> </availability> | ||||||||
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.availabilityPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element availability
{
attribute status { "free" | "unknown" | "restricted" }?,
( model.availabilityPart | model.pLike )+
}⚓ | ||||||||
<bibl>
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl> |
| Example | <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> |
| Example | <bibl type="article" subtype="book_chapter" xml:id="carlin_2003"> <author> <name> <surname>Carlin</surname> (<forename>Claire</forename>)</name> </author>, <title level="a">The Staging of Impotence : France’s last congrès</title> dans <bibl type="monogr"> <title level="m">Theatrum mundi : studies in honor of Ronald W. Tobin</title>, éd. <editor> <name> <forename>Claire</forename> <surname>Carlin</surname> </name> </editor> et <editor> <name> <forename>Kathleen</forename> <surname>Wine</surname> </name> </editor>, <pubPlace>Charlottesville, Va.</pubPlace>, <publisher>Rookwood Press</publisher>, <date when="2003">2003</date>. </bibl> </bibl> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.highlighted"/>
<classRef key="model.pPart.data"/>
<classRef key="model.pPart.edit"/>
<classRef key="model.segLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.biblPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element bibl
{
(
text
| model.gLike
| model.highlighted
| model.pPart.data
| model.pPart.edit
| model.segLike
| model.ptrLike
| model.biblPart
| 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] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint. |
| Example | <biblScope>pp 12–34</biblScope> <biblScope unit="page" from="12" to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element biblScope { macro.phraseSeq }⚓ |
<biblStruct>
| <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: citedRange monogr note ptr |
| 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>
<elementRef key="analytic" minOccurs="0"
maxOccurs="unbounded"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="monogr"/>
<elementRef key="series" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.noteLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="relatedItem"/>
<elementRef key="citedRange"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element biblStruct
{
analytic*,
( ( monogr, series* )+ ),
( model.noteLike | model.ptrLike | relatedItem | citedRange )*
}⚓ |
<body>
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Example | <body> <l>Nu scylun hergan hefaenricaes uard</l> <l>metudæs maecti end his modgidanc</l> <l>uerc uuldurfadur sue he uundra gihuaes</l> <l>eci dryctin or astelidæ</l> <l>he aerist scop aelda barnum</l> <l>heben til hrofe haleg scepen.</l> <l>tha middungeard moncynnæs uard</l> <l>eci dryctin æfter tiadæ</l> <l>firum foldu frea allmectig</l> <trailer>primo cantauit Cædmon istud carmen.</trailer> </body> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<classRef key="model.divTop"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divTop"/>
</alternate>
</sequence>
<sequence minOccurs="0">
<classRef key="model.divGenLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1" maxOccurs="1">
<elementRef key="schemaSpec"/>
<classRef key="model.common"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0">
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.divLike"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.div1Like"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
</alternate>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element body
{
model.global*,
( ( model.divTop, ( model.global | model.divTop )* )? ),
( ( model.divGenLike, ( model.global | model.divGenLike )* )? ),
(
( ( model.divLike, ( model.global | model.divGenLike )* )+ )
| ( ( model.div1Like, ( model.global | model.divGenLike )* )+ )
| (
( ( ( schemaSpec | model.common ), model.global* )+ ),
(
( ( model.divLike, ( model.global | model.divGenLike )* )+ )
| ( ( model.div1Like, ( model.global | model.divGenLike )* )+ )
)?
)
),
( ( model.divBottom, model.global* )* )
}⚓ |
<cit>
| <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <cit> <quote>and the breath of the whale is frequently attended with such an insupportable smell, as to bring on disorder of the brain.</quote> <bibl>Ulloa's South America</bibl> </cit> |
| Example | <entry> <form> <orth>horrifier</orth> </form> <cit type="translation" xml:lang="en"> <quote>to horrify</quote> </cit> <cit type="example"> <quote>elle était horrifiée par la dépense</quote> <cit type="translation" xml:lang="en"> <quote>she was horrified at the expense.</quote> </cit> </cit> </entry> |
| Example | <cit type="example"> <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote> <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav" mimeType="audio/wav"/> <cit type="translation"> <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote> </cit> <cit type="translation"> <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote> </cit> </cit> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.biblLike"/>
<classRef key="model.egLike"/>
<classRef key="model.entryPart"/>
<classRef key="model.global"/>
<classRef key="model.graphicLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.attributable"/>
<elementRef key="pc"/>
<elementRef key="q"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element cit
{
(
model.biblLike
| model.egLike
| model.entryPart
| model.global
| model.graphicLike
| model.ptrLike
| model.attributable
| pc
| q
)+
}⚓ |
<citedRange>
| <citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl biblStruct |
| May contain | |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded |
| Example | <citedRange>pp 12–13</citedRange> <citedRange unit="page" from="12" to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange> |
| Example | <bibl> <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp. 4-5</citedRange> </bibl> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element citedRange { macro.phraseSeq }⚓ |
<correction>
| <correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements] | |||||||||||||||||
| Module | header | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | header: editorialDecl | ||||||||||||||||
| May contain | core: p | ||||||||||||||||
| Note | May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes. | ||||||||||||||||
| Example | <correction> <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user defined dictionary of 500 extra words taken from Chambers Twentieth Century Dictionary.</p> </correction> | ||||||||||||||||
| Content model |
<content>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element correction
{
attribute status { "high" | "medium" | "low" | "unknown" }?,
attribute method { "silent" | "markup" }?,
model.pLike+
}⚓ | ||||||||||||||||
<date>
| <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <date when="1980-02">early February 1980</date> |
| Example | Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date> |
| Example | <date when="1990-09">September 1990</date> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element date { ( text | model.gLike | model.phrase | 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. [23.4.1. Description of Components] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. | ||||||||||||
| Example | Example of a <desc> element inside a documentation element.<dataSpec module="tei" ident="teidata.point"> <desc versionDate="2010-10-17" xml:lang="en">defines the data type used to express a point in cartesian space.</desc> <content> <dataRef name="token" restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/> </content> <!-- ... --> </dataSpec> | ||||||||||||
| 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> | ||||||||||||
| Schematron | A <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
{
att.typed.attribute.subtype,
attribute type { "deprecationInfo" }?,
macro.limitedContent
}⚓ | ||||||||||||
<div>
| <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <body> <div type="part"> <head>Fallacies of Authority</head> <p>The subject of which is Authority in various shapes, and the object, to repress all exercise of the reasoning faculty.</p> <div n="1" type="chapter"> <head>The Nature of Authority</head> <p>With reference to any proposed measures having for their object the greatest happiness of the greatest number [...]</p> <div n="1.1" type="section"> <head>Analysis of Authority</head> <p>What on any given occasion is the legitimate weight or influence to be attached to authority [...] </p> </div> <div n="1.2" type="section"> <head>Appeal to Authority, in What Cases Fallacious.</head> <p>Reference to authority is open to the charge of fallacy when [...] </p> </div> </div> </div> </body> |
| Schematron | <sch:rule context="tei:l//tei:div"> <sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:assert> </sch:rule> |
| Schematron | <sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
</alternate>
<sequence minOccurs="0">
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate>
<classRef key="model.divLike"/>
<classRef key="model.divGenLike"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1"
maxOccurs="1">
<elementRef key="schemaSpec"/>
<classRef key="model.common"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence minOccurs="0"
maxOccurs="unbounded">
<alternate>
<classRef key="model.divLike"/>
<classRef key="model.divGenLike"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element div
{
( model.divTop | model.global )*,
(
(
(
( ( ( model.divLike | model.divGenLike ), model.global* )+ )
| (
( ( ( schemaSpec | model.common ), model.global* )+ ),
( ( ( model.divLike | model.divGenLike ), model.global* )* )
)
),
( ( model.divBottom, model.global* )* )
)?
)
}⚓ |
<editor>
| <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. |
| Example | <editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element editor { macro.phraseSeq }⚓ |
<editorialDecl>
| <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p header: correction |
| Example | <editorialDecl> <normalization> <p>All words converted to Modern American spelling using Websters 9th Collegiate dictionary </p> </normalization> <quotation marks="all"> <p>All opening quotation marks converted to “ all closing quotation marks converted to &cdq;.</p> </quotation> </editorialDecl> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.pLike"/>
<classRef key="model.editorialDeclPart"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element editorialDecl { ( model.pLike | model.editorialDeclPart )+ }⚓ |
<encodingDesc>
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | core: p header: editorialDecl projectDesc samplingDecl |
| Example | <encodingDesc> <p>Basic encoding, capturing lexical information only. All hyphenation, punctuation, and variant spellings normalized. No formatting or layout information preserved.</p> </encodingDesc> |
| Content model |
<content>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.encodingDescPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element encodingDesc { ( model.encodingDescPart | model.pLike )+ }⚓ |
<fileDesc>
| <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | header: publicationStmt sourceDesc titleStmt |
| Note | The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
| Example | <fileDesc> <titleStmt> <title>The shortest possible TEI document</title> </titleStmt> <publicationStmt> <p>Distributed as part of TEI P5</p> </publicationStmt> <sourceDesc> <p>No print source exists: this is an original digital text</p> </sourceDesc> </fileDesc> |
| Content model |
<content>
<sequence>
<sequence>
<elementRef key="titleStmt"/>
<elementRef key="editionStmt"
minOccurs="0"/>
<elementRef key="extent" minOccurs="0"/>
<elementRef key="publicationStmt"/>
<elementRef key="seriesStmt"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="notesStmt"
minOccurs="0"/>
</sequence>
<elementRef key="sourceDesc"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element fileDesc
{
(
titleStmt,
editionStmt?,
extent?,
publicationStmt,
seriesStmt*,
notesStmt?
),
sourceDesc+
}⚓ |
<foreign>
| <foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification. This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
| Example | This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>? |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element foreign { macro.phraseSeq }⚓ |
<gap>
| <gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions] | |||||||||||||||||
| Module | core | ||||||||||||||||
| Attributes |
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | |||||||||||||||||
| May contain | core: desc | ||||||||||||||||
| Note | The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion. | ||||||||||||||||
| Example | <gap quantity="4" unit="chars"
reason="illegible"/> | ||||||||||||||||
| Example | <gap quantity="1" unit="essay"
reason="sampling"/> | ||||||||||||||||
| Example | <del> <gap atLeast="4" atMost="8" unit="chars" reason="illegible"/> </del> | ||||||||||||||||
| Example | <gap extent="several lines" reason="lost"/> | ||||||||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.descLike"/>
<classRef key="model.certLike"/>
</alternate>
</content>
⚓ | ||||||||||||||||
| Schema Declaration |
element gap
{
attribute reason
{
list
{
(
"cancelled"
| "deleted"
| "editorial"
| "illegible"
| "inaudible"
| "irrelevant"
| "sampling"
)+
}
}?,
attribute agent { text }?,
( model.descLike | model.certLike )*
}⚓ | ||||||||||||||||
<head>
| <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section. |
| 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 minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<elementRef key="lg"/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.lLike"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element head
{
(
text
| lg
| model.gLike
| model.phrase
| model.inter
| model.lLike
| model.global
)*
}⚓ |
<idno>
| <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||
| Module | header | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | header: idno character data | ||||||||||
| Note | <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI. | ||||||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat"> <g ref="#sym"/>345 </idno>In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym. | ||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="idno"/>
</alternate>
</content>
⚓ | ||||||||||
| Schema Declaration |
element idno
{
att.typed.attribute.subtype,
attribute type
{
"ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
}?,
( text | model.gLike | idno )*
}⚓ | ||||||||||
<imprint>
| <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Contained by | core: monogr |
| May contain | |
| Example | <imprint> <pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="classCode"/>
<elementRef key="catRef"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate>
<classRef key="model.imprintPart"/>
<classRef key="model.dateLike"/>
</alternate>
<elementRef key="respStmt" minOccurs="0"
maxOccurs="unbounded"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element imprint
{
( classCode | catRef )*,
( ( ( model.imprintPart | model.dateLike ), respStmt*, model.global* )+ )
}⚓ |
<institution>
| <institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [11.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msIdentifier |
| May contain | |
| Example | <msIdentifier> <settlement>Oxford</settlement> <institution>University of Oxford</institution> <repository>Bodleian Library</repository> <idno>MS. Bodley 406</idno> </msIdentifier> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element institution { macro.phraseSeq.limited }⚓ |
<interp>
| <interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [18.3. Spans and Interpretations] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: desc character data |
| Note | Generally, each <interp> element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an <interp> with any textual element through its ana attribute. Alternatively (or, in addition) an <interp> may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the <interp> applies. |
| Example | <interp type="structuralunit" xml:id="ana_am">aftermath</interp> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.descLike"/>
<classRef key="model.certLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element interp { ( text | model.gLike | model.descLike | model.certLike )* }⚓ |
<interpGrp>
| <interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [18.3. Spans and Interpretations] | |
| Module | analysis |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Any number of <interp> elements. |
| Example | <interpGrp resp="#TMA" type="structuralunit"> <desc>basic structural organization</desc> <interp xml:id="I1">introduction</interp> <interp xml:id="I2">conflict</interp> <interp xml:id="I3">climax</interp> <interp xml:id="I4">revenge</interp> <interp xml:id="I5">reconciliation</interp> <interp xml:id="I6">aftermath</interp> </interpGrp> <bibl xml:id="TMA"> <!-- bibliographic citation for source of this interpretive framework --> </bibl> |
| Content model |
<content>
<sequence>
<classRef key="model.descLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="interp" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element interpGrp { model.descLike*, interp+ }⚓ |
<item>
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |||||||||||
| Module | core | ||||||||||
| Attributes |
| ||||||||||
| Contained by | core: list | ||||||||||
| May contain | |||||||||||
| Note | May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n. | ||||||||||
| Example | <list rend="numbered"> <head>Here begin the chapter headings of Book IV</head> <item n="4.1">The death of Queen Clotild.</item> <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item> <item n="4.3">The wives and children of Lothar.</item> <item n="4.4">The Counts of the Bretons.</item> <item n="4.5">Saint Gall the Bishop.</item> <item n="4.6">The priest Cato.</item> <item> ...</item> </list> | ||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element item
{
att.typed.attribute.subtype,
attribute type { "premise" | "rule" | "conclusion" }?,
macro.specialPara
}⚓ | ||||||||||
<l>
| <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l> |
| Schematron | <sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule> |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element l
{
( text | model.gLike | model.phrase | model.inter | model.global )*
}⚓ |
<label>
| <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| 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/>& n’entrer en mauuais & 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 { macro.phraseSeq }⚓ |
<lg>
| <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | contains verse lines or nested line groups only, possibly prefixed by a heading. |
| Example | <lg type="free"> <l>Let me be my own fool</l> <l>of my own making, the sum of it</l> </lg> <lg type="free"> <l>is equivocal.</l> <l>One says of the drunken farmer:</l> </lg> <lg type="free"> <l>leave him lay off it. And this is</l> <l>the explanation.</l> </lg> |
| Schematron | <sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule> |
| Schematron | <sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
</alternate>
<alternate>
<classRef key="model.lLike"/>
<classRef key="model.stageLike"/>
<classRef key="model.labelLike"/>
<classRef key="model.pPart.transcriptional"/>
<elementRef key="lg"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.lLike"/>
<classRef key="model.stageLike"/>
<classRef key="model.labelLike"/>
<classRef key="model.pPart.transcriptional"/>
<classRef key="model.global"/>
<elementRef key="lg"/>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element lg
{
( model.divTop | model.global )*,
(
model.lLike
| model.stageLike
| model.labelLike
| model.pPart.transcriptional
| lg
),
(
model.lLike
| model.stageLike
| model.labelLike
| model.pPart.transcriptional
| model.global
| lg
)*,
( ( model.divBottom, model.global* )* )
}⚓ |
<licence>
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: availability |
| May contain | |
| Note | A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. |
| Example | <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence> |
| Example | <availability> <licence target="http://creativecommons.org/licenses/by/3.0/" notBefore="2013-01-01"> <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence applies to this document.</p> <p>The licence was added on January 1, 2013.</p> </licence> </availability> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element licence { macro.specialPara }⚓ |
<list>
| <list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||||
| Example | <list rend="numbered"> <item>a butcher</item> <item>a baker</item> <item>a candlestick maker, with <list rend="bulleted"> <item>rings on his fingers</item> <item>bells on his toes</item> </list> </item> </list> | ||||||||||||
| Example | <list type="syllogism" rend="bulleted"> <item>All Cretans are liars.</item> <item>Epimenides is a Cretan.</item> <item>ERGO Epimenides is a liar.</item> </list> | ||||||||||||
| Example | <list type="litany" rend="simple"> <item>God save us from drought.</item> <item>God save us from pestilence.</item> <item>God save us from wickedness in high places.</item> <item>Praise be to God.</item> </list> | ||||||||||||
| 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 minOccurs="1" maxOccurs="1">
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
</alternate>
<alternate minOccurs="1" maxOccurs="1">
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="item"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<sequence minOccurs="1" maxOccurs="1">
<elementRef key="headLabel"
minOccurs="0"/>
<elementRef key="headItem"
minOccurs="0"/>
<sequence minOccurs="1"
maxOccurs="unbounded">
<elementRef key="label"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="item"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</alternate>
<sequence minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.divBottom"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element list
{
att.typed.attribute.subtype,
attribute type { text }?,
(
( model.divTop | model.global | desc* )*,
(
( ( item, model.global* )+ )
| (
headLabel?,
headItem?,
( ( label, model.global*, item, model.global* )+ )
)
),
( ( model.divBottom, model.global* )* )
)
}⚓ | ||||||||||||
<listPerson>
| <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | namesdates: listPerson person |
| Note | The type attribute may be used to distinguish lists of people of a particular type if convenient. |
| Example | <listPerson type="respondents"> <personGrp xml:id="PXXX"/> <person xml:id="P1234" sex="2" age="mid"/> <person xml:id="P4332" sex="1" age="mid"/> <listRelation> <relation type="personal" name="spouse" mutual="#P1234 #P4332"/> </listRelation> </listPerson> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="desc" minOccurs="0"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation" minOccurs="1"
maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.personLike"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listPerson"
minOccurs="1" maxOccurs="1"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="relation"
minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation"
minOccurs="1" maxOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listPerson
{
model.headLike*,
desc*,
( relation | listRelation )*,
( ( ( model.personLike | listPerson )+, ( relation | listRelation )* )+ )
}⚓ |
<locus>
| <locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [11.3.5. References to Locations within a Manuscript] | |||||||||||||||||||
| Module | msdescription | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | |||||||||||||||||||
| May contain | msdescription: locus character data | ||||||||||||||||||
| Note | The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example. To associate a <locus> element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone>, <graphic>, or <binaryObject> elements. When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded | ||||||||||||||||||
| Example | <!-- within ms description --><msItem n="1"> <locus target="#F1r #F1v #F2r" from="1r" to="2r">ff. 1r-2r</locus> <author>Ben Jonson</author> <title>Ode to himself</title> <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric> <incipit>Com leaue the loathed stage</incipit> <explicit>And see his chariot triumph ore his wayne.</explicit> <bibl> <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... --> | ||||||||||||||||||
| Example | The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:<msItem> <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus> <title>Birds Praise of Love</title> <bibl> <title>IMEV</title> <biblScope>1506</biblScope> </bibl> </msItem> | ||||||||||||||||||
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="hi"/>
<elementRef key="locus"/>
</alternate>
</content>
⚓ | ||||||||||||||||||
| Schema Declaration |
element locus
{
attribute scheme { text }?,
attribute from { text }?,
attribute to { text }?,
( text | model.gLike | hi | locus )*
}⚓ | ||||||||||||||||||
<mentioned>
| <mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234" xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235" xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last. |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element mentioned { macro.phraseSeq }⚓ |
<monogr>
| <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core |
| Attributes |
|
| Contained by | core: biblStruct |
| May contain | |
| Note | May contain specialized bibliographic elements, in a prescribed order. The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item. |
| Example | <biblStruct> <analytic> <author>Chesnutt, David</author> <title>Historical Editions in the States</title> </analytic> <monogr> <title level="j">Computers and the Humanities</title> <imprint> <date when="1991-12">(December, 1991):</date> </imprint> <biblScope>25.6</biblScope> <biblScope unit="page" from="377" to="380">377–380</biblScope> </monogr> </biblStruct> |
| Example | <biblStruct type="book"> <monogr> <author> <persName> <forename>Leo Joachim</forename> <surname>Frachtenberg</surname> </persName> </author> <title type="main" level="m">Lower Umpqua Texts</title> <imprint> <pubPlace>New York</pubPlace> <publisher>Columbia University Press</publisher> <date>1914</date> </imprint> </monogr> <series> <title type="main" level="s">Columbia University Contributions to Anthropology</title> <biblScope unit="volume">4</biblScope> </series> </biblStruct> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0">
<sequence>
<alternate>
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
<elementRef key="title" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.ptrLike"/>
<elementRef key="idno"/>
<elementRef key="textLang"/>
<elementRef key="editor"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<sequence>
<alternate minOccurs="1"
maxOccurs="unbounded">
<elementRef key="title"/>
<classRef key="model.ptrLike"/>
<elementRef key="idno"/>
</alternate>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="textLang"/>
<elementRef key="author"/>
<elementRef key="editor"/>
<elementRef key="meeting"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<sequence>
<elementRef key="authority"/>
<elementRef key="idno"/>
</sequence>
</alternate>
<elementRef key="availability"
minOccurs="0" maxOccurs="unbounded"/>
<classRef key="model.noteLike"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0"
maxOccurs="unbounded">
<elementRef key="edition"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="idno"/>
<classRef key="model.ptrLike"/>
<elementRef key="editor"/>
<elementRef key="sponsor"/>
<elementRef key="funder"/>
<elementRef key="respStmt"/>
</alternate>
</sequence>
<elementRef key="imprint"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="imprint"/>
<elementRef key="extent"/>
<elementRef key="biblScope"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element monogr
{
(
(
( author | editor | meeting | respStmt ),
( author | editor | meeting | respStmt )*,
title+,
( model.ptrLike | idno | textLang | editor | respStmt )*
)
| (
( title | model.ptrLike | idno )+,
( textLang | author | editor | meeting | respStmt )*
)
| ( authority, idno )
)?,
availability*,
model.noteLike*,
(
(
edition,
( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
)*
),
imprint,
( imprint | extent | biblScope )*
}⚓ |
<msContents>
| <msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [11.6. Intellectual Content] | |
| Module | msdescription |
| Attributes |
|
| Contained by | msdescription: msDesc |
| May contain | |
| Note | Unless it contains a simple prose description, this element should contain at least one of the elements <summary>, <msItem>, or <msItemStruct>. This constraint is not currently enforced by the schema. |
| Example | <msContents class="#sermons"> <p>A collection of Lollard sermons</p> </msContents> |
| Example | <msContents> <msItem n="1"> <locus>fols. 5r-7v</locus> <title>An ABC</title> <bibl> <title>IMEV</title> <biblScope>239</biblScope> </bibl> </msItem> <msItem n="2"> <locus>fols. 7v-8v</locus> <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title> <bibl> <title>IMEV</title> <biblScope>3747</biblScope> </bibl> </msItem> <msItem n="3"> <locus>fol. 8v</locus> <title>Truth</title> <bibl> <title>IMEV</title> <biblScope>809</biblScope> </bibl> </msItem> <msItem n="4"> <locus>fols. 8v-10v</locus> <title>Birds Praise of Love</title> <bibl> <title>IMEV</title> <biblScope>1506</biblScope> </bibl> </msItem> <msItem n="5"> <locus>fols. 10v-11v</locus> <title xml:lang="la">De amico ad amicam</title> <title xml:lang="la">Responcio</title> <bibl> <title>IMEV</title> <biblScope>16 & 19</biblScope> </bibl> </msItem> <msItem n="6"> <locus>fols. 14r-126v</locus> <title>Troilus and Criseyde</title> <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note> </msItem> </msContents> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<sequence>
<elementRef key="summary" minOccurs="0"/>
<elementRef key="textLang" minOccurs="0"/>
<elementRef key="titlePage"
minOccurs="0"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msItem"/>
<elementRef key="msItemStruct"/>
</alternate>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element msContents
{
model.pLike+
| ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* )
}⚓ |
<msDesc>
| <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [11.1. Overview] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | msdescription: msContents msIdentifier |
| Note | Although the <msDesc> has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable. |
| Example | <msDesc> <msIdentifier> <settlement>Oxford</settlement> <repository>Bodleian Library</repository> <idno type="Bod">MS Poet. Rawl. D. 169.</idno> </msIdentifier> <msContents> <msItem> <author>Geoffrey Chaucer</author> <title>The Canterbury Tales</title> </msItem> </msContents> <physDesc> <objectDesc> <p>A parchment codex of 136 folios, measuring approx 28 by 19 inches, and containing 24 quires.</p> <p>The pages are margined and ruled throughout.</p> <p>Four hands have been identified in the manuscript: the first 44 folios being written in two cursive anglicana scripts, while the remainder is for the most part in a mixed secretary hand.</p> </objectDesc> </physDesc> </msDesc> |
| Schematron | <sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule> |
| Content model |
<content>
<sequence>
<elementRef key="msIdentifier"/>
<classRef key="model.headLike"
minOccurs="0" maxOccurs="unbounded"/>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msContents"/>
<elementRef key="physDesc"/>
<elementRef key="history"/>
<elementRef key="additional"/>
<elementRef key="msPart"/>
<elementRef key="msFrag"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msDesc
{
msIdentifier,
model.headLike*,
(
model.pLike+
| ( msContents | physDesc | history | additional | msPart | msFrag )*
)
}⚓ |
<msIdentifier>
| <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [11.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | header: idno msdescription: institution |
| Example | <msIdentifier> <settlement>San Marino</settlement> <repository>Huntington Library</repository> <idno>MS.El.26.C.9</idno> </msIdentifier> |
| Schematron | <sch:rule context="tei:msIdentifier"> <sch:report test="not( parent::tei:msPart ) and ( child::*[1]/self::idno or child::*[1]/self::altIdentifier or normalize-space(.) eq '')">An msIdentifier must contain either a repository or location.</sch:report> </sch:rule> |
| Content model |
<content>
<sequence>
<sequence>
<classRef key="model.placeNamePart"
expand="sequenceOptional"/>
<elementRef key="institution"
minOccurs="0"/>
<elementRef key="repository"
minOccurs="0"/>
<elementRef key="collection"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="idno" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="msName"/>
<elementRef key="objectName"/>
<elementRef key="altIdentifier"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msIdentifier
{
( institution?, repository?, collection*, idno* ),
( msName | objectName | altIdentifier )*
}⚓ |
<msItem>
| <msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [11.6.1. The msItem and msItemStruct Elements] | |
| Module | msdescription |
| Attributes |
|
| Member of | |
| Contained by | msdescription: msContents msItem |
| May contain | |
| Example | <msItem class="#saga"> <locus>ff. 1r-24v</locus> <title>Agrip af Noregs konunga sögum</title> <incipit>regi oc h<ex>ann</ex> setiho <gap reason="illegible" extent="7"/>sc heim se<ex>m</ex> þio</incipit> <explicit>h<ex>on</ex> hev<ex>er</ex> <ex>oc</ex>þa buit hesta .ij. aNan viþ fé enh<ex>on</ex>o<ex>m</ex> aNan til reiþ<ex>ar</ex> </explicit> <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem> |
| Content model |
<content>
<sequence>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="locus"/>
<elementRef key="locusGrp"/>
</alternate>
<alternate>
<classRef key="model.pLike"
minOccurs="1" maxOccurs="unbounded"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.titlepagePart"/>
<classRef key="model.msItemPart"/>
<classRef key="model.global"/>
</alternate>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element msItem
{
( locus | locusGrp )*,
(
model.pLike+
| ( model.titlepagePart | model.msItemPart | model.global )+
)
}⚓ |
<note>
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| 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" type="gloss" resp="#MDMH"> <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH"> <resp>translation from German to English</resp> <name>Hottinger, Marie Donald Mackie</name> </respStmt>For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
| 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 n="126" anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element note { macro.specialPara }⚓ |
<p>
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | header: availability correction editorialDecl encodingDesc licence projectDesc publicationStmt samplingDecl sourceDesc msdescription: msContents msDesc msItem |
| May contain | |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you done?</q> </p> <p> <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p> <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p> <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p> |
| Schematron | <sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule> |
| Schematron | <sch:rule context="tei:l//tei:p"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:assert> </sch:rule> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element p { 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. [14.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <persName> <forename>Edward</forename> <forename>George</forename> <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of <placeName>Knebworth</placeName> </roleName> </persName> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element persName { macro.phraseSeq }⚓ |
<person>
| <person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description] | |||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | namesdates: listPerson | ||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||
| Note | May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class. | ||||||||||||||||||||||||||||||||
| Example | <person sex="F" age="adult"> <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic status B2.</p> </person> | ||||||||||||||||||||||||||||||||
| Example | <person sex="intersex" role="god" age="immortal"> <persName>Hermaphroditos</persName> <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person> | ||||||||||||||||||||||||||||||||
| Example | <person xml:id="Ovi01" sex="M" role="poet"> <persName xml:lang="en">Ovid</persName> <persName xml:lang="la">Publius Ovidius Naso</persName> <birth when="-0044-03-20"> 20 March 43 BC <placeName> <settlement type="city">Sulmona</settlement> <country key="IT">Italy</country> </placeName> </birth> <death notBefore="0017" notAfter="0018">17 or 18 AD <placeName> <settlement type="city">Tomis (Constanta)</settlement> <country key="RO">Romania</country> </placeName> </death> </person> | ||||||||||||||||||||||||||||||||
| Example | The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.<person xml:id="ariel" gender="U"> <persName>Ariel</persName> <note>Character in <title level="m">The Tempest</title>.</note> </person> | ||||||||||||||||||||||||||||||||
| Example | This example demonstrates the use of a <ref> element to provide more information about a person.<person age="G2" role="author" xml:id="W0212" sex="F"> <birth when="1787"/> <death when="1855"/> <persName type="main">Mitford, Mary Russell (1787–1855)</persName> <persName resp="#Nicoll">MITFORD, MARY RUSSELL</persName> <listBibl type="lacyTitles"> <desc>Lacy's Acting Editions</desc> <bibl> <ref target="lacy:L1280">Foscari</ref> </bibl> <bibl> <ref target="lacy:L1337">Rienzi</ref> </bibl> </listBibl> <listRef type="seeAlso"> <ref target="https://www.victorianresearch.org/atcl/show_author.php?aid=1386">ATCL</ref> <ref target="https://doi.org/10.1093/ref:odnb/18859">ODNB</ref> <ref target="https://en.wikipedia.org/wiki/Mary_Russell_Mitford">Wikipedia</ref> <ref target="https://digitalmitford.org">Digital Mitford</ref> </listRef> </person> | ||||||||||||||||||||||||||||||||
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.personPart"/>
<classRef key="model.global"/>
<classRef key="model.ptrLike"/>
</alternate>
</alternate>
</content>
⚓ | ||||||||||||||||||||||||||||||||
| Schema Declaration |
element person
{
attribute role { list { + } }?,
attribute sex { list { + } }?,
attribute gender { list { + } }?,
attribute age { text }?,
( model.pLike+ | ( model.personPart | model.global | model.ptrLike )* )
}⚓ | ||||||||||||||||||||||||||||||||
<persona>
| <persona> provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. [14.3.2. The Person Element] | |||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | |||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||
| 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 sex="M" age="adult"> <persona sex="M"> <persName>Dr Henry Jekyll</persName> </persona> <persona sex="M" age="youth"> <persName>Edward Hyde</persName> </persona> </person> | ||||||||||||||||||||||||||||||||
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="0"
maxOccurs="unbounded">
<classRef key="model.personPart"/>
<classRef key="model.global"/>
</alternate>
</alternate>
</content>
⚓ | ||||||||||||||||||||||||||||||||
| Schema Declaration |
element persona
{
attribute role { list { + } }?,
attribute sex { list { + } }?,
attribute gender { list { + } }?,
attribute age { text }?,
( model.pLike+ | ( model.personPart | model.global )* )
}⚓ | ||||||||||||||||||||||||||||||||
<projectDesc>
| <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Example | <projectDesc> <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc> |
| Content model |
<content>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element projectDesc { model.pLike+ }⚓ |
<ptr>
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Empty element |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | <ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/> |
| Schematron | <sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element ptr { empty }⚓ |
<pubPlace>
| <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | |
| Example | <publicationStmt> <publisher>Oxford University Press</publisher> <pubPlace>Oxford</pubPlace> <date>1989</date> </publicationStmt> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element pubPlace { macro.phraseSeq }⚓ |
<publicationStmt>
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Note | Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
| Example | <publicationStmt> <publisher>C. Muquardt </publisher> <pubPlace>Bruxelles & Leipzig</pubPlace> <date when="1846"/> </publicationStmt> |
| Example | <publicationStmt> <publisher>Chadwyck Healey</publisher> <pubPlace>Cambridge</pubPlace> <availability> <p>Available under licence only</p> </availability> <date when="1992">1992</date> </publicationStmt> |
| Example | <publicationStmt> <publisher>Zea Books</publisher> <pubPlace>Lincoln, NE</pubPlace> <date>2017</date> <availability> <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p> </availability> <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt> |
| Content model |
<content>
<alternate>
<sequence minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.publicationStmtPart.agency"/>
<classRef key="model.publicationStmtPart.detail"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element publicationStmt
{
( ( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+ )
| model.pLike+
}⚓ |
<publisher>
| <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | header: publicationStmt |
| May contain | |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
| Example | <imprint> <pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element publisher { macro.phraseSeq }⚓ |
<q>
| <q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Note | May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks. | ||||||||
| Example | It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q> | ||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||
| Schema Declaration |
element q
{
attribute type
{
"spoken"
| "thought"
| "written"
| "soCalled"
| "foreign"
| "distinct"
| "term"
| "emph"
| "mentioned"
}?,
macro.specialPara
}⚓ | ||||||||
<quote>
| <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element. |
| Example | Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element quote { macro.specialPara }⚓ |
<resp>
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Contained by | core: respStmt |
| May contain | |
| Note | The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. |
| Example | <respStmt> <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp> <name>Edward Child</name> </respStmt> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element resp { macro.phraseSeq.limited }⚓ |
<respStmt>
| <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <respStmt> <resp>transcribed from original ms</resp> <persName>Claus Huitfeldt</persName> </respStmt> |
| Example | <respStmt> <resp>converted to XML encoding</resp> <name>Alan Morrison</name> </respStmt> |
| Content model |
<content>
<sequence>
<alternate>
<sequence>
<elementRef key="resp" minOccurs="1"
maxOccurs="unbounded"/>
<classRef key="model.nameLike.agent"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
<sequence>
<classRef key="model.nameLike.agent"
minOccurs="1" maxOccurs="unbounded"/>
<elementRef key="resp" minOccurs="1"
maxOccurs="unbounded"/>
</sequence>
</alternate>
<elementRef key="note" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element respStmt
{
( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
note*
}⚓ |
<samplingDecl>
| <samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p |
| Note | This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest. |
| Example | <samplingDecl> <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each text identified as relevant by respondents.</p> </samplingDecl> |
| Content model |
<content>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element samplingDecl { model.pLike+ }⚓ |
<seg>
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element. |
| Example | <seg>When are you leaving?</seg> <seg>Tomorrow.</seg> |
| Example | <s> <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield. </s> |
| Example | <seg type="preamble"> <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg> <seg>Sinfiotli was the eldest of his sons ...</seg> <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element seg { macro.paraContent }⚓ |
<sourceDesc>
| <sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <sourceDesc> <bibl> <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> </sourceDesc> |
| Example | <sourceDesc> <p>Born digital: no previous source exists.</p> </sourceDesc> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike" minOccurs="1"
maxOccurs="unbounded"/>
<alternate minOccurs="1"
maxOccurs="unbounded">
<classRef key="model.biblLike"/>
<classRef key="model.sourceDescPart"/>
<classRef key="model.listLike"/>
</alternate>
</alternate>
</content>
⚓ |
| Schema Declaration |
element sourceDesc
{
model.pLike+ | ( model.biblLike | model.sourceDescPart | model.listLike )+
}⚓ |
<standOff>
| <standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [17.10. The standOff Container] | |
| Module | linking |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| 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 target="#w51" ana="#fs01"/> <span target="#w52" ana="#fs02"/> <span target="#w52" ana="#fs03"/> <span target="#w53 #w54" ana="#fs04"/> <span target="#w55" ana="#fs05"/> <span target="#w56" ana="#fs06"/> </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 when="1963" type="interpolatedCensus" quantity="489359" source="https://www.biggestuscities.com/city/atlanta-georgia"/> </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 when="1963" type="interpolatedCensus" quantity="332891" source="https://www.biggestuscities.com/city/birmingham-alabama"/> </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:rule context="tei:standOff"> <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> </sch:rule> |
| Content model |
<content>
<classRef key="model.standOffPart"
minOccurs="1" maxOccurs="unbounded"/>
</content>
⚓ |
| Schema Declaration |
element standOff { model.standOffPart+ }⚓ |
<teiCorpus>
| <teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more <TEI> elements, each containing a single text header and a text. [4. Default Text Structure 16.1. Varieties of Composite Text] | |||||||||
| Module | core | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | core: teiCorpus | ||||||||
| May contain | |||||||||
| Note | Should contain one <teiHeader> for the corpus, and a series of <TEI> elements, one for each text. As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <teiCorpus version="4.8.1" xml:lang="en" xmlns="http://www.tei-c.org/ns/1.0">. | ||||||||
| Example | <teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <!-- header for corpus --> </teiHeader> <TEI> <teiHeader> <!-- header for first text --> </teiHeader> <text> <!-- content of first text --> </text> </TEI> <TEI> <teiHeader> <!-- header for second text --> </teiHeader> <text> <!-- content of second text --> </text> </TEI> <!-- more TEI elements here --> </teiCorpus> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="teiHeader"/>
<classRef key="model.resource"
minOccurs="0" maxOccurs="unbounded"/>
<classRef key="model.describedResource"
minOccurs="1" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element teiCorpus
{
attribute version { text }?,
( teiHeader, model.resource*, model.describedResource+ )
}⚓ | ||||||||
<teiHeader>
| <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | header: encodingDesc fileDesc |
| 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"
minOccurs="0" maxOccurs="unbounded"/>
<elementRef key="revisionDesc"
minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element teiHeader { fileDesc, model.teiHeaderPart*, revisionDesc? }⚓ |
<text>
| <text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose. |
| Example | <text> <front> <docTitle> <titlePart>Autumn Haze</titlePart> </docTitle> </front> <body> <l>Is it a dragonfly or a maple leaf</l> <l>That settles softly down upon the water?</l> </body> </text> |
| 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"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<elementRef key="front"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<alternate>
<elementRef key="body"/>
<elementRef key="group"/>
</alternate>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
<sequence minOccurs="0">
<elementRef key="back"/>
<classRef key="model.global"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element text
{
model.global*,
( ( front, model.global* )? ),
( body | group ),
model.global*,
( ( back, model.global* )? )
}⚓ |
<textLang>
| <textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | msdescription: msContents msItem | ||||||||||||
| May contain | |||||||||||||
| Note | This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description. In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header. | ||||||||||||
| Example | <textLang mainLang="en" otherLangs="la"> Predominantly in English with Latin glosses</textLang> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element textLang
{
attribute mainLang { text }?,
attribute otherLangs { list { * } }?,
macro.specialPara
}⚓ | ||||||||||||
<title>
| <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | |||||||||||||||||||||||
| May contain | |||||||||||||||||||||||
| Note | The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title. | ||||||||||||||||||||||
| Example | <title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title> | ||||||||||||||||||||||
| Example | <title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title> | ||||||||||||||||||||||
| Example | <title type="full"> <title type="main">Synthèse</title> <title type="sub">an international journal for epistemology, methodology and history of science</title> </title> | ||||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||||||||||||||||||
| Schema Declaration |
element title
{
att.typed.attribute.subtype,
attribute type { text }?,
attribute level { "a" | "m" | "j" | "s" | "u" }?,
macro.paraContent
}⚓ | ||||||||||||||||||||||
<titleStmt>
| <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <titleStmt> <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title> <respStmt> <resp>compiled by</resp> <name>P.J. Lucas</name> </respStmt> </titleStmt> |
| Content model |
<content>
<sequence>
<elementRef key="title" minOccurs="1"
maxOccurs="unbounded"/>
<classRef key="model.respLike"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element titleStmt { title+, model.respLike* }⚓ |
Model classes
model.annotationLike
| model.annotationLike groups elements used to represent annotations. [17.10. The standOff Container] | |
| Module | tei |
| Used by | |
| Members | |
model.attributable
| model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts] | |
| Module | tei |
| Used by | |
| Members | |
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.] | |
| Module | tei |
| Used by | |
| Members | |
model.biblLike
| model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | |
model.biblPart
| model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | |
model.common
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
| Note | This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
model.dateLike
| model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates] | |
| Module | tei |
| Used by | |
| Members | |
model.describedResource
| model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.divBottom
| model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | |
model.divPart
| model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
| 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] | |
| Module | tei |
| Used by | |
| Members | |
model.divTopPart
| model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | |
model.editorialDeclPart
| model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | |
model.emphLike
| model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | |
model.encodingDescPart
| model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | |
model.global
| model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.global.edit
| model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.global.meta
| model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
| 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.headLike
| model.headLike groups elements used to provide a title or heading at the start of a text division. | |
| Module | tei |
| Used by | |
| Members | |
model.hiLike
| model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | |
model.highlighted
| model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | |
model.imprintPart
| model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | |
model.inter
| model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.lLike
| model.lLike groups elements representing metrical components such as verse lines. | |
| Module | tei |
| Used by | |
| Members | |
model.labelLike
| model.labelLike groups elements used to gloss or explain other parts of a document. | |
| Module | tei |
| Used by | |
| Members | |
model.limitedPhrase
| model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.listLike
| model.listLike groups list-like elements. [3.8. Lists] | |
| Module | tei |
| Used by | |
| Members | |
model.msItemPart
| model.msItemPart groups elements which can appear within a manuscript item description. | |
| Module | tei |
| Used by | |
| Members | |
model.msQuoteLike
| model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description. | |
| Module | tei |
| Used by | |
| Members | |
model.nameLike
| model.nameLike groups elements which name or refer to a person, place, or organization. | |
| Module | tei |
| Used by | |
| Members | |
| Note | A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
model.nameLike.agent
| model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | |
| Note | This class is used in the content model of elements which reference names of people or organizations. |
model.noteLike
| model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing] | |
| Module | tei |
| Used by | |
| Members | |
model.pPart.data
| model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | |
model.pPart.edit
| model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | |
model.pPart.msdesc
| model.pPart.msdesc groups phrase-level elements used in manuscript description. [11. Manuscript Description] | |
| Module | tei |
| Used by | |
| Members | |
model.paraPart
| model.paraPart groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs] | |
| Module | tei |
| Used by | |
| Members | |
model.persStateLike
| model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name. | |
| Module | tei |
| Used by | |
| Members | |
| Note | These characteristics of an individual are typically a consequence of their own action or that of others. |
model.personLike
| model.personLike groups elements which provide information about people and their relationships. | |
| Module | tei |
| Used by | |
| Members | |
model.personPart
| model.personPart groups elements which form part of the description of a person. [16.2.2. The Participant Description] | |
| Module | tei |
| Used by | |
| Members | |
model.phrase
| model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
| Note | This class of elements can occur within paragraphs, list items, lines of verse, etc. |
model.placeStateLike
| model.placeStateLike groups elements which describe changing states of a place. | |
| Module | tei |
| Used by | |
| Members | |
model.ptrLike
| model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
| Module | tei |
| Used by | |
| Members | |
model.publicationStmtPart.agency
| model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | |
| Note | The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element. See also model.publicationStmtPart.detail. |
model.publicationStmtPart.detail
| model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | |
| Note | A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
model.quoteLike
| model.quoteLike groups elements used to directly contain quotations. | |
| Module | tei |
| Used by | |
| Members | |
model.resource
| model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | |
model.respLike
| model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element. | |
| Module | tei |
| Used by | |
| Members | |
model.segLike
| model.segLike groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories] | |
| Module | tei |
| Used by | |
| Members | |
| 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>. | |
| Module | tei |
| Used by | |
| Members | |
Attribute classes
att.anchoring
| att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations. | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | |||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234"> <note xml:lang="en"> Quatuor Tempora, so called dry fast days. </note> <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne. </note> </noteGrp> | ||||||||||||||||||
att.ascribed
| att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | |||||||||||
| Attributes |
| ||||||||||
att.ascribed.directed
| att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | |||||||||||
| Attributes |
| ||||||||||
att.cReferencing
| att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer. | |||||||||
| Module | tei | ||||||||
| Members | |||||||||
| Attributes |
| ||||||||
att.calendarSystem
| att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | |||||||||||||||
| Attributes |
| ||||||||||||||
att.canonical
| att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | |||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| 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.citing
| att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | |||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
att.cmc
| att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment. | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | |||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
att.datable
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates] | |||||||
| Module | tei | ||||||
| Members | |||||||
| Attributes |
| ||||||
| Note | This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. | ||||||
att.datable.custom
| att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [14.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
att.datable.iso
| att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 14.4. Dates] | |||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||
| 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 when-iso="2007-06-01" dur-iso="P8D"/> indicates the same time period as <date when-iso="2007-06-01/P8D"/>In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading. | ||||||||||||||||||||||||||||||||||
att.datable.w3c
| att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates] | |||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to" role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule> | ||||||||||||||||||||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@from]"> <sch:report test="@notBefore" role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule> | ||||||||||||||||||||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@to]"> <sch:report test="@notAfter" role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule> | ||||||||||||||||||||||||||||||||||||
| Example | <date from="1863-05-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 Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used. | ||||||||||||||||||||||||||||||||||||
att.datcat
| att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [10.5.2. Lexical View 19.3. Other Atomic Feature Values] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | |||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| 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 name="POS" datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"> <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545" value="NN"/> </f> <!-- ... --> </fs>‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]]. <fs> <f name="POS" fVal="#commonNoun"/> <!-- ... --> </fs>The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories. <fvLib n="POS values"> <symbol xml:id="commonNoun" value="NN" datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/> <symbol xml:id="properNoun" value="NP" datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </fvLib>Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value. | ||||||||||||||||||
| 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 xml:id="UD-SYN" datcat="https://universaldependencies.org/u/dep/index.html"> <desc> <term>UD syntactic relations</term> </desc> <category xml:id="acl" valueDatcat="https://universaldependencies.org/u/dep/acl.html"> <catDesc> <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc> </category> <category xml:id="acl_relcl" valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"> <catDesc> <term>acl:relcl</term>: relative clause modifier</catDesc> </category> <category xml:id="advcl" valueDatcat="https://universaldependencies.org/u/dep/advcl.html"> <catDesc> <term>advcl</term>: Adverbial clause modifier</catDesc> </category> <!-- ... --> </taxonomy> </classDecl> </encodingDesc>The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly. | ||||||||||||||||||
| 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 value="NN" datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/> <symbol value="NP" datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </vAlt> </vRange> </fDecl>Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element. | ||||||||||||||||||
| 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 xml:id="domain.medical_and_health_sciences.medicine" valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"> <catDesc xml:lang="en"> <term>Medicine</term> <gloss> <!--...--> </gloss> </catDesc> <catDesc xml:lang="pt"> <term>Medicina</term> <gloss> <!--...--> </gloss> </catDesc> </category> </category> <!--...--> </taxonomy> </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain" valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH). | ||||||||||||||||||
| Note | The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container. A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute. In a TEI XML example of two equivalent serializations expressing the name-value pair 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. [16.3. Associating Contextual Information with a Text] | |||||||||
| Module | tei | ||||||||
| Members | |||||||||
| Attributes |
| ||||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. 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. [16.3. Associating Contextual Information with a Text] | |||||||
| Module | tei | ||||||
| Members | |||||||
| Attributes |
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. | ||||||
att.dimensions
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
att.divLike
| att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | |||||||||||||||||
| Attributes |
| ||||||||||||||||
att.docStatus
| att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
| Module | tei | ||||||||
| Members | |||||||||
| Attributes |
| ||||||||
| Example | <revisionDesc status="published"> <change when="2010-10-21" status="published"/> <change when="2010-10-02" status="cleared"/> <change when="2010-08-02" status="embargoed"/> <change when="2010-05-01" status="frozen" who="#MSM"/> <change when="2010-03-01" status="draft" 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 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | |||||||||||||||||
| Attributes |
| ||||||||||||||||
| Note | The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc. Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned. | ||||||||||||||||
att.fragmentable
| att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy. | |||||||||||
| Module | tei | ||||||||||
| Members | |||||||||||
| Attributes |
| ||||||||||
att.global
| att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||
att.global.analytic
| att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [18.2. Global Attributes for Simple Analyses 18.3. Spans and Interpretations] | |||||||||||||||
| Module | analysis | ||||||||||||||
| Members | |||||||||||||||
| Attributes |
| ||||||||||||||
att.global.change
| att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated. | |||||||
| Module | transcr | ||||||
| Members | |||||||
| Attributes |
| ||||||
att.global.facs
| att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [12.1. Digital Facsimiles] | |||||||
| Module | transcr | ||||||
| Members | |||||||
| Attributes |
| ||||||
att.global.linking
| att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
att.global.rendition
| att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators] | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
att.global.responsibility
| att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | |||||||||||||||
| Attributes |
| ||||||||||||||
| Example | Blessed are the <choice> <sic>cheesemakers</sic> <corr resp="#editor" cert="high">peacemakers</corr> </choice>: for they shall be called the children of God. | ||||||||||||||
| Example | <!-- in the <text> ... --><lg> <!-- ... --> <l>Punkes, Panders, baſe extortionizing sla<choice> <sic>n</sic> <corr resp="#JENS1_transcriber">u</corr> </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber"> <resp when="2014">Transcriber</resp> <name>Janelle Jenstad</name> </respStmt> | ||||||||||||||
att.global.source
| att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing] | |||||||||||
| Module | tei | ||||||||||
| Members | |||||||||||
| Attributes |
| ||||||||||
| 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. | |||||||
| Module | tei | ||||||
| Members | |||||||
| Attributes |
| ||||||
| 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.interpLike
| att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [18.2. Global Attributes for Simple Analyses] | |||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||
att.msClass
| att.msClass provides attributes to indicate text type or classification. [11.6. Intellectual Content 11.6.1. The msItem and msItemStruct Elements] | |||||||
| Module | msdescription | ||||||
| Members | |||||||
| Attributes |
| ||||||
att.msExcerpt
| att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [11.6. Intellectual Content] | |||||||
| Module | msdescription | ||||||
| Members | |||||||
| Attributes |
| ||||||
| Note | In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole. | ||||||
att.naming
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | |||||||||||||||
| Attributes |
| ||||||||||||||
att.notated
| att.notated provides attributes to indicate any specialised notation used for element content. | |||||||
| Module | tei | ||||||
| Members | |||||||
| Attributes |
| ||||||
att.personal
| att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | |||||||||||||||
| Attributes |
| ||||||||||||||
att.placement
| att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 12.3.1.4. Additions and Deletions] | |||||||||||||
| Module | tei | ||||||||||||
| Members | |||||||||||||
| Attributes |
| ||||||||||||
att.pointing
| att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References] | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
att.ranging
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | |||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| Example | The MS. was lost in transmission by mail from <del rend="overstrike"> <gap reason="illegible" extent="one or two letters" atLeast="1" atMost="2" 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" unit="USD" commodity="currency">more than $120m</measure> in aid to Ukrainians. | ||||||||||||||||||||||||||||||
att.segLike
| att.segLike provides attributes for elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories] | |||||||||
| Module | tei | ||||||||
| Members | |||||||||
| Attributes |
| ||||||||
att.sortable
| att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [10.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei | ||||||||||
| Members | |||||||||||
| Attributes |
| ||||||||||
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] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | |||||||||||||||||
| Attributes |
| ||||||||||||||||
att.typed
| att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | |||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Schematron | <sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule> | ||||||||||||||||||
| Note | When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
att.written
| att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes] | |||||||
| Module | tei | ||||||
| Members | |||||||
| Attributes |
| ||||||
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] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.inter"/>
</alternate>
</content>
⚓ |
| Declaration | macro.limitedContent = ( text | model.limitedPhrase | model.inter )*⚓ |
macro.paraContent
| macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.paraPart"/>
</alternate>
</content>
⚓ |
| Declaration | macro.paraContent = ( text | model.paraPart )*⚓ |
macro.phraseSeq
| macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.attributable"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration | macro.phraseSeq = ( text | model.gLike | model.attributable | model.phrase | model.global )*⚓ |
macro.phraseSeq.limited
| macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration | macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*⚓ |
macro.specialPara
| macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.divPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration |
macro.specialPara =
(
text
| model.gLike
| model.phrase
| model.inter
| model.divPart
| model.global
)*⚓ |
Datatypes
teidata.certainty
| teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<valList type="closed">
<valItem ident="high"/>
<valItem ident="medium"/>
<valItem ident="low"/>
<valItem ident="unknown"/>
</valList>
</content>
⚓ |
| Declaration | teidata.certainty = "high" | "medium" | "low" | "unknown"⚓ |
| Note | Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. |
teidata.count
| teidata.count defines the range of attribute values used for a non-negative integer value used as a count. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="nonNegativeInteger"/>
</content>
⚓ |
| Declaration | teidata.count = xsd:nonNegativeInteger⚓ |
| Note | Any positive integer value or zero is permitted |
teidata.duration.iso
| teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
⚓ |
| Declaration |
teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓ |
| Example | <time dur-iso="PT0,75H">three-quarters of an hour</time> |
| Example | <date dur-iso="P1,5D">a day and a half</date> |
| Example | <date dur-iso="P14D">a fortnight</date> |
| Example | <time dur-iso="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
teidata.duration.w3c
| teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="duration"/>
</content>
⚓ |
| Declaration | teidata.duration.w3c = xsd:duration⚓ |
| Example | <time dur="PT45M">forty-five minutes</time> |
| Example | <date dur="P1DT12H">a day and a half</date> |
| Example | <date dur="P7D">a week</date> |
| Example | <time dur="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the For complete details, see the W3C specification. |
teidata.enumerated
| teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef key="teidata.word"/>
</content>
⚓ |
| Declaration | teidata.enumerated = teidata.word⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
teidata.gender
| teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | teidata.gender = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 10.3.1. Information on Written and Spoken Forms). |
teidata.language
| teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="language"/>
<valList>
<valItem ident=""/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | teidata.language = xsd:language | ( "" )⚓ |
| Note | The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice. A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications. Second, an entire language tag can consist of only a private use subtag. These tags start with Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
teidata.name
| teidata.name defines the range of attribute values expressed as an XML Name. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="Name"/>
</content>
⚓ |
| Declaration | teidata.name = xsd:Name⚓ |
| Note | Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
teidata.numeric
| teidata.numeric defines the range of attribute values used for numeric values. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="double"/>
<dataRef name="token"
restriction="(\-?[\d]+/\-?[\d]+)"/>
<dataRef name="decimal"/>
</alternate>
</content>
⚓ |
| Declaration |
teidata.numeric =
xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal⚓ |
| Note | Any numeric value, represented as a decimal number, in floating point format, or as a ratio. To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3. A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2. |
teidata.outputMeasurement
| teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
⚓ |
| Declaration |
teidata.outputMeasurement =
token
{
pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
}⚓ |
| Example | <figure> <head>The TEI Logo</head> <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in between and <mentioned>text encoding initiative</mentioned> underneath, all on a white background.</figDesc> <graphic height="600px" width="600px" url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure> |
| Note | These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft. |
teidata.pattern
| teidata.pattern defines attribute values which are expressed as a regular expression. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"/>
</content>
⚓ |
| Declaration | teidata.pattern = token⚓ |
| Note | A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern WikipediaH(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema. |
teidata.point
| teidata.point defines the data type used to express a point in cartesian space. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
⚓ |
| Declaration |
teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }⚓ |
| Example | <facsimile> <surface ulx="0" uly="0" lrx="400" lry="280"> <zone points="220,100 300,210 170,250 123,234"> <graphic url="handwriting.png"/> </zone> </surface> </facsimile> |
| Note | A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not. |
teidata.pointer
| teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
| Module | tei |
| Used by | Element:
|
| Content model |
<content>
<dataRef restriction="\S+" name="anyURI"/>
</content>
⚓ |
| Declaration |
teidata.pointer = xsd:anyURI { pattern = "\S+" }⚓ |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, |
teidata.probCert
| teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef key="teidata.probability"/>
<dataRef key="teidata.certainty"/>
</alternate>
</content>
⚓ |
| Declaration | teidata.probCert = teidata.probability | teidata.certainty⚓ |
teidata.probability
| teidata.probability defines the range of attribute values expressing a probability. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="double">
<dataFacet name="minInclusive" value="0"/>
<dataFacet name="maxInclusive" value="1"/>
</dataRef>
</content>
⚓ |
| Declaration | teidata.probability = xsd:double⚓ |
| Note | Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. |
teidata.sex
| teidata.sex defines the range of attribute values used to identify the sex of an organism. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | teidata.sex = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. |
teidata.temporal.iso
| teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</alternate>
</content>
⚓ |
| Declaration |
teidata.temporal.iso =
xsd:date
| xsd:gYear
| xsd:gMonth
| xsd:gDay
| xsd:gYearMonth
| xsd:gMonthDay
| xsd:time
| xsd:dateTime
| token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format. |
teidata.temporal.w3c
| teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
</alternate>
</content>
⚓ |
| Declaration | teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
teidata.text
| teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="string"/>
</content>
⚓ |
| Declaration | teidata.text = string⚓ |
| Note | Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
teidata.truthValue
| teidata.truthValue defines the range of attribute values used to express a truth value. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="boolean"/>
</content>
⚓ |
| Declaration | teidata.truthValue = xsd:boolean⚓ |
| Note | The possible values of this datatype are 1 or true, or 0 or false. This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue. |
teidata.version
| teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
⚓ |
| Declaration |
teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }⚓ |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
teidata.versionNumber
| teidata.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
⚓ |
| Declaration |
teidata.versionNumber =
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }⚓ |
teidata.word
| teidata.word defines the range of attribute values expressed as a single word or token. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[^\p{C}\p{Z}]+"/>
</content>
⚓ |
| Declaration |
teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
teidata.xTruthValue
| teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="boolean"/>
<valList>
<valItem ident="unknown"/>
<valItem ident="inapplicable"/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )⚓ |
| Note | In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
teidata.xpath
| teidata.xpath defines attribute values which contain an XPath expression. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Declaration | teidata.xpath = text⚓ |
| Note | Any XPath expression using the syntax defined in 6.2.. When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP. |