My TEI Customization starts with modules tei, core, textstructure and header
<additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information] | |
Module | msdescription |
Contained by |
msdescription: msDesc
|
May contain |
core: listBibl
|
Example |
<additional>
<adminInfo> <recordHist> <p> <!-- record history here --> </p> </recordHist> <custodialHist> <p> <!-- custodial history here --> </p> </custodialHist> </adminInfo> <surrogates> <p> <!-- information about surrogates here --> </p> </surrogates> <listBibl> <bibl> <!-- ... --> </bibl> <!-- full bibliography here --> </listBibl> </additional> |
Content model |
<content> |
Schema Declaration |
element additional { adminInfo?, surrogates?, tei_listBibl? } |
<additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations] | |
Module | msdescription |
Member of | |
Contained by |
msdescription: physDesc
|
May contain | |
Example |
<additions>
<p>There are several marginalia in this manuscript. Some consist of single characters and others are figurative. On 8v is to be found a drawing of a mans head wearing a hat. At times sentences occurs: On 5v: <q xml:lang="is">Her er skrif andres isslendin</q>, on 19r: <q xml:lang="is">þeim go</q>, on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad batar þad mælgi ok mal</q>, On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p> </additions> |
Content model |
<content> |
Schema Declaration |
element additions { tei_macro.specialPara } |
<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier] | |||||||||||
Module | msdescription | ||||||||||
Attributes | att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
|
||||||||||
Contained by |
msdescription: msIdentifier
|
||||||||||
May contain | |||||||||||
Note |
An identifying number of some kind must be supplied if known; if it is not known, this should be stated. |
||||||||||
Example |
<altIdentifier>
<settlement>San Marino</settlement> <repository>Huntington Library</repository> <idno>MS.El.26.C.9</idno> </altIdentifier> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element altIdentifier { tei_att.datable.attributes, attribute type { "siglum" }?, ( tei_placeName?, institution?, tei_repository?, collection?, tei_idno, tei_note? ) } |
<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels] | |
Module | core |
Contained by |
core: biblStruct
|
May contain | |
Note |
May contain titles and statements of responsibility (author, editor, or other), in any order. The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item. |
Example |
<biblStruct>
<analytic> <author>Chesnutt, David</author> <title>Historical Editions in the States</title> </analytic> <monogr> <title level="j">Computers and the Humanities</title> <imprint> <date when="1991-12">(December, 1991):</date> </imprint> <biblScope>25.6</biblScope> <biblScope>377–380</biblScope> </monogr> </biblStruct> |
Content model |
<content> |
Schema Declaration |
element analytic { ( tei_author | tei_editor | tei_respStmt | tei_title | tei_model.ptrLike | tei_date | tei_textLang | tei_idno | tei_availability )* } |
<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment] | |||||||||||||||||||||||||||||
Module | linking | ||||||||||||||||||||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||
Contained by | |||||||||||||||||||||||||||||
May contain | Empty element | ||||||||||||||||||||||||||||
Note |
On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence. |
||||||||||||||||||||||||||||
Example |
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/> </s> |
||||||||||||||||||||||||||||
Content model |
<content> |
||||||||||||||||||||||||||||
Schema Declaration |
element anchor { tei_att.global.attribute.xmlid, attribute n { teidata.text }?, attribute type { "crit" | "footnote" | "wdb" }, attribute ref { text }?, attribute place { "start" | "end" }?, empty } |
<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 | att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (key, @ref) |
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> |
Schema Declaration |
element author { tei_att.canonical.attribute.ref, tei_att.datable.attributes, tei_macro.phraseSeq } |
<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 |
core: p
|
||||||||
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> |
||||||||
Schema Declaration |
element availability { attribute status { "free" | "restricted" }, ( tei_model.availabilityPart | tei_model.pLike )+ } |
<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
Module | textstructure |
Contained by |
textstructure: text
|
May contain | |
Note |
Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and <front> elements are identical. |
Example |
<back>
<div type="appendix"> <head>The Golden Dream or, the Ingenuous Confession</head> <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she had like to have been, too fond of Money <!-- .... --> </p> </div> <!-- ... --> <div type="epistle"> <head>A letter from the Printer, which he desires may be inserted</head> <salute>Sir.</salute> <p>I have done with your Copy, so you may return it to the Vatican, if you please; <!-- ... --> </p> </div> <div type="advert"> <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr Newbery's at the Bible and Sun in St Paul's Church-yard.</head> <list> <item n="1">The Christmas Box, Price 1d.</item> <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... --> <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations, 10 Vol, Pr. bound 1l.</item> </list> </div> <div type="advert"> <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St. Paul's Church-Yard.</head> <list> <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d</item> <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... --> </list> </div> </back> |
Content model |
<content> |
Schema Declaration |
element back { ( tei_model.frontPart | tei_model.pLike.front | tei_model.pLike | tei_model.listLike | tei_model.global )*, ( ( tei_model.div1Like, ( tei_model.frontPart | tei_model.div1Like | tei_model.global )* ) | ( tei_model.divLike, ( tei_model.frontPart | tei_model.divLike | tei_model.global )* ) )?, ( tei_model.divBottomPart, ( tei_model.divBottomPart | tei_model.global )* )? } |
<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
Module | core |
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status) |
Member of | |
Contained by | |
May contain | |
Note |
Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
Example |
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl> |
Example |
<bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher> <date>1968</date>. </bibl> |
Example |
<bibl subtype="book_chapter" type="article"
xml:id="carlin_2003"> <author> <name> <surname>Carlin</surname> (<forename>Claire</forename>)</name> </author>, <title level="a">The Staging of Impotence : France’s last congrès</title> dans <bibl type="monogr"> <title level="m">Theatrum mundi : studies in honor of Ronald W. Tobin</title>, éd. <editor> <name> <forename>Claire</forename> <surname>Carlin</surname> </name> </editor> et <editor> <name> <forename>Kathleen</forename> <surname>Wine</surname> </name> </editor>, <pubPlace>Charlottesville, Va.</pubPlace>, <publisher>Rookwood Press</publisher>, <date when="2003">2003</date>. </bibl> </bibl> |
Content model |
<content> |
Schema Declaration |
element bibl { tei_att.global.attributes, tei_att.declarable.attributes, tei_att.typed.attributes, tei_att.sortable.attributes, tei_att.docStatus.attributes, ( text | tei_model.gLike | tei_model.highlighted | tei_model.pPart.data | tei_model.pPart.edit | tei_model.segLike | tei_model.ptrLike | tei_model.biblPart | tei_model.global )* } |
<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 |
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 from="12" to="34" unit="page"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope> |
Content model |
<content> |
Schema Declaration |
element biblScope { tei_macro.phraseSeq } |
<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |||||||||||
Module | core | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<biblStruct>
<monogr> <author>Blain, Virginia</author> <author>Clements, Patricia</author> <author>Grundy, Isobel</author> <title>The Feminist Companion to Literature in English: women writers from the middle ages to the present</title> <edition>first edition</edition> <imprint> <publisher>Yale University Press</publisher> <pubPlace>New Haven and London</pubPlace> <date>1990</date> </imprint> </monogr> </biblStruct> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element biblStruct { tei_att.global.attribute.xmlid, attribute type { "imprint" }?, ( tei_analytic*, ( tei_monogr, series* )+, ( tei_model.noteLike | tei_model.ptrLike | relatedItem | citedRange | tei_model.msItemPart )* ) } |
<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
Module | textstructure |
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> |
Schema Declaration |
element body { tei_model.global*, ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )?, ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?, ( ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+ | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+ | ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+, ( ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+ | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+ )? ) ), ( tei_model.divBottom, tei_model.global* )* } |
<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables] | |
Module | figures |
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) att.tableDecoration (role, @rows, @cols) |
Contained by |
figures: row
|
May contain | |
Example |
<row>
<cell role="label">General conduct</cell> <cell role="data">Not satisfactory, on account of his great unpunctuality and inattention to duties</cell> </row> |
Content model |
<content> |
Schema Declaration |
element cell { tei_att.global.attribute.xmlid, tei_att.tableDecoration.attribute.rows, tei_att.tableDecoration.attribute.cols, tei_macro.specialPara } |
<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions] | |||||||||||
Module | textstructure | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<div type="letter">
<p> perhaps you will favour me with a sight of it when convenient.</p> <closer> <salute>I remain, &c. &c.</salute> <signed>H. Colburn</signed> </closer> </div> |
||||||||||
Example |
<div type="chapter">
<p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p> <closer> <dateline> <name type="place">Trieste-Zürich-Paris,</name> <date>1914–1921</date> </dateline> </closer> </div> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element closer { tei_att.global.attribute.xmlid, attribute rend { list { ( "right-align-right" | "right-align-left" | "left-align-right" | "left-align-left" | "center-align-left" | "center-align-right" | "center" | "inline" | "hanging" )+ } }?, ( text | tei_model.gLike | signed | dateline | tei_salute | tei_model.phrase | tei_model.global )* } |
<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates] | |||||||||||||||||||||
Module | core | ||||||||||||||||||||
Attributes | att.datable.w3c (from, to, @when, @notBefore, @notAfter)
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by |
core: analytic author bibl biblScope date editor foreign head hi imprint item l label note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
textcrit: witness
transcr: supplied
|
||||||||||||||||||||
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> |
||||||||||||||||||||
Schema Declaration |
element date { tei_att.datable.w3c.attribute.when, tei_att.datable.w3c.attribute.notBefore, tei_att.datable.w3c.attribute.notAfter, attribute cert { "low" }?, attribute type { "created" }?, ( text | tei_model.gLike | tei_model.phrase | tei_model.global )* } |
<distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
Module | header |
Member of | |
Contained by |
header: publicationStmt
|
May contain | |
Example |
<distributor>Oxford Text Archive</distributor>
<distributor>Redwood and Burn Ltd</distributor> |
Content model |
<content> |
Schema Declaration |
element distributor { tei_macro.phraseSeq } |
<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |||||||||||||||||||
Module | textstructure | ||||||||||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) att.global.linking (synch, sameAs, copyOf, next, prev, exclude, select, @corresp)
|
||||||||||||||||||
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:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> |
||||||||||||||||||
Schematron |
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> |
||||||||||||||||||
Content model |
<content> |
||||||||||||||||||
Schema Declaration |
element div { tei_att.global.attribute.xmlid, tei_att.global.linking.attribute.corresp, attribute xml:lang { teidata.language }?, attribute type { "contents" | "corrigenda" | "titlepage" | "reference" | "history_of_the_work" | "evidence" | "transcript" | "supplement" | "crit_app" | "footnotes" | "main" | "introduction" | "introduction_codex_lost" | "register" | "front" }, ( ( tei_model.divTop | tei_model.global )*, ( ( ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )+ | ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+, ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )* ) ), ( tei_model.divBottom, tei_model.global* )* )? ) } |
<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 | att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) |
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> |
Schema Declaration |
element editor { tei_att.datable.attributes, tei_macro.phraseSeq } |
<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 |
Member of | |
Contained by |
header: teiHeader
|
May contain |
core: p
header: projectDesc
|
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> |
Schema Declaration |
element encodingDesc { ( tei_model.encodingDescPart | tei_model.pLike )+ } |
<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
Module | transcr |
Member of | |
Contained by | |
May contain | Character data only |
Example |
The address is Southmoor <choice>
<expan>R<ex>oa</ex>d</expan> <abbr>Rd</abbr> </choice> |
Content model |
<content> |
Schema Declaration |
element ex { tei_macro.xtext } |
<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description] | |
Module | header |
Member of | |
Contained by | |
May contain | |
Example |
<extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent> |
Example |
The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned. <extent>
<measure quantity="4.2" unit="MiB">About four megabytes</measure> <measure quantity="245" unit="pages">245 pages of source material</measure> </extent> |
Content model |
<content> |
Schema Declaration |
element extent { tei_macro.phraseSeq } |
<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 |
Contained by |
header: teiHeader
|
May contain |
header: extent 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> |
Schema Declaration |
element fileDesc { ( tei_titleStmt, editionStmt?, tei_extent?, tei_publicationStmt, seriesStmt*, notesStmt? ), tei_sourceDesc+ } |
<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> |
||||||||||
Schema Declaration |
element foreign { attribute xml:lang { "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat" }, tei_macro.phraseSeq } |
<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 | Empty element | ||||||||
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 11.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" reason="illegible"
unit="chars"/> |
||||||||
Example |
<gap quantity="1" reason="sampling"
unit="essay"/> |
||||||||
Example |
<del>
<gap atLeast="4" atMost="8" reason="illegible" unit="chars"/> </del> |
||||||||
Example |
<gap extent="several lines" reason="lost"/>
|
||||||||
Content model |
<content> |
||||||||
Schema Declaration |
element gap { attribute reason { list { "illegible"+ } }?, ( tei_model.descLike | tei_model.certLike )* } |
<gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics] | |||||||||
Module | namesdates | ||||||||
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
|
||||||||
Contained by |
—
|
||||||||
May contain | |||||||||
Note |
As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail. |
||||||||
Example |
<gender value="W">woman</gender>
|
||||||||
Example |
<gender value="NB">non-binary</gender>
|
||||||||
Content model |
<content> |
||||||||
Schema Declaration |
element gender { tei_att.global.attributes, tei_att.editLike.attributes, tei_att.datable.attributes, tei_att.typed.attributes, attribute value { list { teidata.gender+ } }?, tei_macro.phraseSeq } |
<handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations] | |
Module | msdescription |
Member of | |
Contained by |
msdescription: physDesc
|
May contain | |
Example |
<handDesc>
<handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote> </handDesc> |
Example |
<handDesc hands="2">
<p>The manuscript is written in two contemporary hands, otherwise unknown, but clearly those of practised scribes. Hand I writes ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand on f. 24, but the evidence for this is insubstantial.</p> </handDesc> |
Content model |
<content> |
Schema Declaration |
element handDesc { tei_model.pLike+ | ( summary?, tei_handNote+ ) } |
<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations] | |
Module | header |
Contained by |
msdescription: handDesc
|
May contain | |
Example |
<handNote scope="sole">
<p>Written in insular phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed minuscule.</p> </handNote> |
Content model |
<content> |
Schema Declaration |
element handNote { tei_macro.specialPara } |
<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 | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||||||||||||
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> |
||||||||||||||||||||
Schema Declaration |
element head { tei_att.global.attribute.xmlid, attribute rend { list { "inline"+ } }?, attribute place { list { "margin"+ } }?, ( text | tei_lg | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.lLike | tei_model.global )* } |
<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language] | |||||||||||
Module | core | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ... |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element hi { attribute rend { list { ( "super" | "sub" )+ } }?, tei_macro.paraContent } |
<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||
Module | header | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: analytic author bibl biblScope biblStruct date editor foreign head hi item l label listBibl monogr note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote idno publicationStmt
linking: seg
msdescription: additions altIdentifier msIdentifier msItem repository
textcrit: witness
transcr: supplied
|
||||||||||
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 |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element idno { attribute type { "vd16" | "vd17" | "siglum" | "signatur" }, ( text | tei_model.gLike | tei_idno )* } |
<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 |
Contained by |
core: monogr
|
May contain | |
Example |
<imprint>
<pubPlace>Oxford</pubPlace> <publisher>Clarendon Press</publisher> <date>1987</date> </imprint> |
Content model |
<content> |
Schema Declaration |
element imprint { ( classCode | catRef )*, ( ( tei_model.imprintPart | tei_model.dateLike ), tei_respStmt*, tei_model.global* )+ } |
<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |||||||||||
Module | core | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
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> |
||||||||||
Schema Declaration |
element item { tei_att.global.attribute.xmlid, attribute n { teidata.text }?, tei_macro.specialPara } |
<keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification] | |
Module | header |
Contained by |
header: textClass
|
May contain | |
Note |
Each individual keyword (including compound subject headings) should be supplied as a term element directly within the keywords element. An alternative usage, in which each term appears within an item inside a list is permitted for backwards compatibility, but is deprecated. If no control list exists for the keywords used, then no value should be supplied for the scheme attribute. |
Example |
<keywords scheme="http://classificationweb.net">
<term>Babbage, Charles</term> <term>Mathematicians - Great Britain - Biography</term> </keywords> |
Example |
<keywords>
<term>Fermented beverages</term> <term>Central Andes</term> <term>Schinus molle</term> <term>Molle beer</term> <term>Indigenous peoples</term> <term>Ethnography</term> <term>Archaeology</term> </keywords> |
Content model |
<content> |
Schema Declaration |
element keywords { tei_term+ | tei_list } |
<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 | att.global (n, xml:lang, xml:base, xml:space, @xml:id) |
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:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements. </sch:report> |
Content model |
<content> |
Schema Declaration |
element l { tei_att.global.attribute.xmlid, ( text | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.global )* } |
<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 | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
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> |
||||||||||
Schema Declaration |
element label { tei_att.global.attribute.xmlid, attribute rend { list { "post"+ } }?, tei_macro.phraseSeq } |
<lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents] | |||||||||||
Module | core | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | Empty element | ||||||||||
Note |
By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked. The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives. |
||||||||||
Example |
This example shows typographical line breaks within metrical lines, where they occur at different places in different editions: <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> |
||||||||||
Example |
This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word. <titlePart>
<lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element lb { tei_att.global.attribute.xmlid, attribute break { "no" }?, empty } |
<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 | att.global (n, xml:lang, xml:base, xml:space, @xml:id) |
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: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> |
Schematron |
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups. </sch:report> |
Content model |
<content> |
Schema Declaration |
element lg { tei_att.global.attribute.xmlid, ( ( tei_model.divTop | tei_model.global )*, ( tei_model.lLike | tei_model.stageLike | tei_model.labelLike | tei_lg ), ( tei_model.lLike | tei_model.stageLike | tei_model.labelLike | tei_model.global | tei_lg )*, ( tei_model.divBottom, tei_model.global* )* ) } |
<list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |
Module | core |
Attributes | att.global (xml:id, xml:lang, xml:base, xml:space, @n) att.global.rendition (style, rendition, @rend) |
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 rend="bulleted" type="syllogism">
<item>All Cretans are liars.</item> <item>Epimenides is a Cretan.</item> <item>ERGO Epimenides is a liar.</item> </list> |
Example |
<list rend="simple" type="litany">
<item>God save us from drought.</item> <item>God save us from pestilence.</item> <item>God save us from wickedness in high places.</item> <item>Praise be to God.</item> </list> |
Example |
The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section">
<head>Athelstan's Ordinance</head> <list rend="numbered"> <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with the stolen goods, [if he is] over twelve years and [if the value of the goods is] over eightpence. <list rend="numbered"> <item n="1.1">And if anyone does spare one, he is to pay for the thief with his wergild — and the thief is to be no nearer a settlement on that account — or to clear himself by an oath of that amount.</item> <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is not to be spared [whether younger or older than twelve].</item> <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may then be redeemed with 120 shillings; and the kindred are to stand surety for him that he will desist for ever.</item> <item n="1.4">And if he steals after that, they are to pay for him with his wergild, or to bring him back there.</item> <item n="1.5">And if he steals after that, they are to pay for him with his wergild, whether to the king or to him to whom it rightly belongs; and everyone of those who supported him is to pay 120 shillings to the king as a fine.</item> </list> </item> <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom no justice can be obtained, that one should order their kindred to fetch back such a person to justice and to find him a lord in public meeting. <list rend="numbered"> <item n="2.1">And if they then will not, or cannot, produce him on that appointed day, he is then to be a fugitive afterwards, and he who encounters him is to strike him down as a thief.</item> <item n="2.2">And he who harbours him after that, is to pay for him with his wergild or to clear himself by an oath of that amount.</item> </list> </item> <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds his guilty man, so that the king is appealed to, is to repay the value of the goods and 120 shillings to the king; and he who appeals to the king before he demands justice as often as he ought, is to pay the same fine as the other would have done, if he had refused him justice. <list rend="numbered"> <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes known about him, is to forfeit the slave and be liable to his wergild on the first occasionp if he does it more often, he is to be liable to pay all that he owns.</item> <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been an accessory of thieves who have committed theft, is to liable to the same.</item> </list> </item> <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is afterwards convicted at the three-fold ordeal.</item> </list> </div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. |
Example |
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ...
and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple"> <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have subscribed to the pious and catholic validity of this document with the sign of the Holy Cross.</item> <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with the sign of the Holy Cross.</item> <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the sign of the Holy Cross.</item> <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the sign of the Holy Cross.</item> <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of the Holy Cross.</item> <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item> <item>I, Æthelwine, bishop, have subscribed through delegates.</item> <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy Cross.</item> </list> </p> |
Schematron |
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule> |
Content model |
<content> |
Schema Declaration |
element list { tei_att.global.attribute.n, tei_att.global.rendition.attribute.rend, ( ( tei_model.divTop | tei_model.global | desc* )*, ( ( tei_item, tei_model.global* )+ | ( headLabel?, headItem?, ( tei_label, tei_model.global*, tei_item, tei_model.global* )+ ) ), ( tei_model.divBottom, tei_model.global* )* ) } |
<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |||||||||||
Module | core | ||||||||||
Attributes | att.sortable (@sortKey)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<listBibl>
<head>Works consulted</head> <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990) </bibl> <biblStruct> <analytic> <title>The Interesting story of the Children in the Wood</title> </analytic> <monogr> <title>The Penny Histories</title> <author>Victor E Neuberg</author> <imprint> <publisher>OUP</publisher> <date>1968</date> </imprint> </monogr> </biblStruct> </listBibl> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element listBibl { tei_att.sortable.attributes, attribute type { "editions" | "literature" | "sigla" | "regest" | "translation" }?, ( tei_model.headLike*, desc*, ( tei_model.biblLike | tei_model.milestoneLike | tei_model.nameLike )*, ( relation | listRelation )* ) } |
<listWit> (witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
Module | textcrit |
Attributes | att.global (xml:lang, xml:base, xml:space, @xml:id, @n) |
Member of | |
Contained by | |
May contain | |
Note |
May contain a series of witness or listWit elements. The provision of a listWit element simplifies the automatic processing of the apparatus, e.g. the reconstruction of the readings for all witnesses from an exhaustive apparatus. Situations commonly arise where there are many more or less fragmentary witnesses, such that there may be quite distinct groups of witnesses for different parts of a text or collection of texts. Such groups may be given separately, or nested within a single listWit element at the beginning of the file listing all the witnesses, partial and complete, for the text, with the attestation of fragmentary witnesses indicated within the apparatus by use of the <witStart> and <witEnd> elements described in section 12.1.5. Fragmentary Witnesses. Note however that a given witness can only be defined once, and can therefore only appear within a single listWit element. |
Example |
<listWit>
<witness xml:id="HL26">Ellesmere, Huntingdon Library 26.C.9</witness> <witness xml:id="PN392">Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D</witness> <witness xml:id="RP149">Bodleian Library Rawlinson Poetic 149 (see further <ptr target="#MSRP149"/>)</witness> </listWit> |
Content model |
<content> |
Schema Declaration |
element listWit { tei_att.global.attribute.xmlid, tei_att.global.attribute.n, ( tei_model.headLike?, desc*, ( tei_witness | tei_listWit )+ ) } |
<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript] | |
Module | msdescription |
Member of | |
Contained by | |
May contain | |
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 from="1r" target="#F1r #F1v #F2r" to="2r">ff. 1r-2r</locus> <author>Ben Jonson</author> <title>Ode to himself</title> <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric> <incipit>Com leaue the loathed stage</incipit> <explicit>And see his chariot triumph ore his wayne.</explicit> <bibl> <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... --> |
Example |
The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example: <msItem>
<locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus> <title>Birds Praise of Love</title> <bibl> <title>IMEV</title> <biblScope>1506</biblScope> </bibl> </msItem> |
Content model |
<content> |
Schema Declaration |
element locus { ( text | tei_model.gLike | tei_hi | tei_locus )* } |
<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 |
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 from="377" to="380" unit="page">377–380</biblScope> </monogr> </biblStruct> |
Example |
<biblStruct type="book">
<monogr> <author> <persName> <forename>Leo Joachim</forename> <surname>Frachtenberg</surname> </persName> </author> <title level="m" type="main">Lower Umpqua Texts</title> <imprint> <pubPlace>New York</pubPlace> <publisher>Columbia University Press</publisher> <date>1914</date> </imprint> </monogr> <series> <title level="s" type="main">Columbia University Contributions to Anthropology</title> <biblScope unit="volume">4</biblScope> </series> </biblStruct> |
Content model |
<content> |
Schema Declaration |
element monogr { ( ( ( tei_author | tei_editor | meeting | tei_respStmt ), ( tei_author | tei_editor | meeting | tei_respStmt )*, tei_title+, ( tei_model.ptrLike | tei_idno | tei_textLang | tei_editor | tei_respStmt )* ) | ( ( tei_title | tei_model.ptrLike | tei_idno )+, ( tei_textLang | tei_author | tei_editor | meeting | tei_respStmt )* ) | ( authority, tei_idno ) )?, tei_availability*, tei_model.noteLike*, ( edition, ( tei_idno | tei_model.ptrLike | tei_editor | sponsor | funder | tei_respStmt )* )*, tei_imprint, ( tei_imprint | tei_extent | tei_biblScope )* } |
<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. [10.6. Intellectual Content] | |
Module | msdescription |
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> |
Schema Declaration |
element msContents { tei_model.pLike+ | ( summary?, tei_textLang?, titlePage?, ( tei_msItem | msItemStruct )* ) } |
<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview] | |
Module | msdescription |
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) |
Member of | |
Contained by | |
May contain |
msdescription: additional msContents msIdentifier physDesc
|
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> |
Content model |
<content> |
Schema Declaration |
element msDesc { tei_att.global.attribute.xmlid, ( tei_msIdentifier, tei_model.headLike*, ( tei_model.pLike+ | ( tei_msContents?, tei_physDesc?, history?, tei_additional?, ( msPart* | msFrag* ) ) ) ) } |
<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier] | |
Module | msdescription |
Member of | |
Contained by | |
May contain | |
Example |
<msIdentifier>
<settlement>San Marino</settlement> <repository>Huntington Library</repository> <idno>MS.El.26.C.9</idno> </msIdentifier> |
Schematron |
<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report> |
Content model |
<content> |
Schema Declaration |
element msIdentifier { ( tei_placeName?, institution?, tei_repository?, collection*, tei_idno* ), ( msName | objectName | tei_altIdentifier )* } |
<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements] | |
Module | msdescription |
Member of | |
Contained by |
core: biblStruct
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 extent="7" reason="illegible"/>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> |
Schema Declaration |
element msItem { ( tei_locus | locusGrp )*, ( tei_model.pLike+ | ( tei_model.titlepagePart | tei_model.msItemPart | tei_model.global )+ ) } |
<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries] | |||||||||||||||||||||||||||||||||||||||||
Module | core | ||||||||||||||||||||||||||||||||||||||||
Attributes | att.placement (@place) att.global.linking (synch, sameAs, copyOf, next, prev, exclude, select, @corresp)
|
||||||||||||||||||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||||||||||||||||||
Contained by |
analysis: w
core: author bibl biblScope biblStruct date editor foreign head hi imprint item l label lg list monogr note noteGrp orig p pubPlace publisher quote ref resp respStmt rs term textLang title
header: distributor extent handNote
linking: seg
msdescription: additions altIdentifier msItem repository
textcrit: witness
transcr: supplied
|
||||||||||||||||||||||||||||||||||||||||
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" resp="#MDMH" type="gloss"> <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH"> <resp>translation from German to English</resp> <name>Hottinger, Marie Donald Mackie</name> </respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
||||||||||||||||||||||||||||||||||||||||
Example |
The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="true" n="126"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
||||||||||||||||||||||||||||||||||||||||
Content model |
<content> |
||||||||||||||||||||||||||||||||||||||||
Schema Declaration |
element note { tei_att.global.linking.attribute.corresp, tei_att.placement.attributes, attribute xml:id { xsd:ID }, attribute n { teidata.text }, attribute type { "footnote" | "crit" | "copies" | "references" }?, attribute subtype { "span" }?, attribute ref { text }, tei_macro.specialPara } |
<noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes] | |
Module | core |
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd) |
Member of | |
Contained by |
analysis: w
core: author bibl biblScope biblStruct date editor foreign head hi imprint item l label lg list monogr note noteGrp orig p pubPlace publisher quote ref resp rs term textLang title
header: distributor extent handNote
linking: seg
msdescription: additions msItem repository
transcr: supplied
|
May contain | |
Example |
In the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text: <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus <noteGrp> <note xml:lang="en">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday) falling on each of the quarters of the year. In the first quarter they were called Cinerum (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis (after the Exaltation of the Holy Cross, September 14th), and Luciae in the fourth (after the feast of St. Lucia, December 13th). </note> <note xml:lang="pl">Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota) przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae (po dniu św. Łucji 13 grudnia). </note> </noteGrp> totaliter expediui. </p> |
Content model |
<content> |
Schema Declaration |
element noteGrp { tei_att.global.attributes, tei_att.placement.attributes, tei_att.pointing.attributes, tei_att.typed.attributes, tei_att.written.attributes, tei_att.anchoring.attributes, ( desc*, ( tei_note | tei_noteGrp )+ ) } |
<objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description] | |||||||||||
Module | msdescription | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
msdescription: physDesc
|
||||||||||
May contain |
core: p
|
||||||||||
Example |
<objectDesc form="codex">
<supportDesc material="mixed"> <p>Early modern <material>parchment</material> and <material>paper</material>.</p> </supportDesc> <layoutDesc> <layout ruledLines="25 32"/> </layoutDesc> </objectDesc> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element objectDesc { attribute form { "codex_lost" }?, ( tei_model.pLike+ | ( supportDesc?, layoutDesc? ) ) } |
<opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions] | |||||||||||
Module | textstructure | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<opener>
<dateline>Walden, this 29. of August 1592</dateline> </opener> |
||||||||||
Example |
<opener>
<dateline> <name type="place">Great Marlborough Street</name> <date>November 11, 1848</date> </dateline> <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element opener { tei_att.global.attribute.xmlid, attribute rend { list { ( "right-align-right" | "right-align-left" | "left-align-right" | "left-align-left" | "center-align-left" | "center-align-right" | "center" | "inline" | "hanging" )+ } }?, ( text | tei_model.gLike | tei_model.phrase | argument | byline | dateline | epigraph | tei_salute | signed | tei_model.global )* } |
<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus] | |||||||||
Module | core | ||||||||
Attributes |
|
||||||||
Member of | |||||||||
Contained by | |||||||||
May contain | |||||||||
Example |
If all that is desired is to call attention to the original version in the copy text, orig may be used alone: <l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig> </l> |
||||||||
Example |
More usually, an orig will be combined with a regularized form within a <choice> element: <l>But this will be a <choice>
<orig>meere</orig> <reg>mere</reg> </choice> confusion</l> <l>And hardly shall we all be <choice> <orig>vnderstoode</orig> <reg>understood</reg> </choice> </l> |
||||||||
Content model |
<content> |
||||||||
Schema Declaration |
element orig { attribute corresp { list { teidata.pointer+ } }?, tei_macro.paraContent } |
<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
Module | core |
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) |
Member of | |
Contained by |
figures: cell
msdescription: additions handDesc msContents msDesc msItem objectDesc physDesc
|
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:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> |
Schematron |
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText |parent::tei:figure |parent::tei:note )"> Abstract model violation: 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:report> |
Content model |
<content> |
Schema Declaration |
element p { tei_att.global.attribute.xmlid, tei_macro.paraContent } |
<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements] | |
Module | core |
Attributes | att.global (xml:lang, xml:base, xml:space, @xml:id, @n) att.global.facs (@facs) |
Member of | |
Contained by | |
May contain | Empty element |
Note |
A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself. The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives. |
Example |
Page numbers may vary in different editions of a text. <p> ... <pb ed="ed2" n="145"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb ed="ed1" n="283"/> <!-- Page 283 in edition "ed1" starts here--> ... </p> |
Example |
A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body>
<pb facs="page1.png" n="1"/> <!-- page1.png contains an image of the page; the text it contains is encoded here --> <p> <!-- ... --> </p> <pb facs="page2.png" n="2"/> <!-- similarly, for page 2 --> <p> <!-- ... --> </p> </body> |
Content model |
<content> |
Schema Declaration |
element pb { tei_att.global.attribute.xmlid, tei_att.global.attribute.n, tei_att.global.facs.attribute.facs, empty } |
<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names] | |
Module | namesdates |
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> |
Schema Declaration |
element persName { tei_macro.phraseSeq } |
<physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description] | |
Module | msdescription |
Contained by |
msdescription: msDesc
|
May contain |
core: p
msdescription: additions handDesc objectDesc
|
Example |
<physDesc>
<objectDesc form="codex"> <supportDesc material="perg"> <support>Parchment.</support> <extent>i + 55 leaves <dimensions scope="all" type="leaf" unit="inch"> <height>7¼</height> <width>5⅜</width> </dimensions> </extent> </supportDesc> <layoutDesc> <layout columns="2">In double columns.</layout> </layoutDesc> </objectDesc> <handDesc> <p>Written in more than one hand.</p> </handDesc> <decoDesc> <p>With a few coloured capitals.</p> </decoDesc> </physDesc> |
Content model |
<content> |
Schema Declaration |
element physDesc { tei_model.pLike*, tei_objectDesc?, tei_handDesc?, tei_additions? } |
<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names] | |||||||||||
Module | namesdates | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
core: author bibl biblScope date editor foreign head hi item l label listBibl note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote
linking: seg
msdescription: additions altIdentifier msIdentifier repository
textcrit: witness
transcr: supplied
|
||||||||||
May contain | |||||||||||
Example |
<placeName>
<settlement>Rochester</settlement> <region>New York</region> </placeName> |
||||||||||
Example |
<placeName>
<geogName>Arrochar Alps</geogName> <region>Argylshire</region> </placeName> |
||||||||||
Example |
<placeName>
<measure>10 miles</measure> <offset>Northeast of</offset> <settlement>Attica</settlement> </placeName> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element placeName { attribute cert { "low" }?, tei_macro.phraseSeq } |
<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components] | |
Module | header |
Member of | |
Contained by |
header: teiHeader
|
May contain |
header: textClass
|
Note |
Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts. |
Example |
<profileDesc>
<langUsage> <language ident="fr">French</language> </langUsage> <textDesc n="novel"> <channel mode="w">print; part issues</channel> <constitution type="single"/> <derivation type="original"/> <domain type="art"/> <factuality type="fiction"/> <interaction type="none"/> <preparedness type="prepared"/> <purpose degree="high" type="entertain"/> <purpose degree="medium" type="inform"/> </textDesc> <settingDesc> <setting> <name>Paris, France</name> <time>Late 19th century</time> </setting> </settingDesc> </profileDesc> |
Content model |
<content> |
Schema Declaration |
element profileDesc { tei_model.profileDescPart* } |
<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
Module | header |
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> |
Schema Declaration |
element projectDesc { tei_model.pLike+ } |
<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links] | |||||||||||
Module | core | ||||||||||
Attributes | att.pointing (targetLang, evaluate, @target)
|
||||||||||
Member of | |||||||||||
Contained by |
core: analytic author bibl biblScope biblStruct date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
textcrit: witness
transcr: supplied
|
||||||||||
May contain | Empty element | ||||||||||
Example |
<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/> |
||||||||||
Schematron |
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> |
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element ptr { tei_att.pointing.attribute.target, attribute type { "link" | "wdb" | "digitalisat" }, empty } |
<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 |
Contained by |
header: fileDesc
|
May contain |
header: availability distributor idno
|
Note |
Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
Example |
<publicationStmt>
<publisher>C. Muquardt </publisher> <pubPlace>Bruxelles & 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> |
Schema Declaration |
element publicationStmt { ( tei_model.publicationStmtPart.agency, tei_model.publicationStmtPart.detail* )+ | tei_model.pLike+ } |
<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> |
||||||||||
Schema Declaration |
element publisher { attribute cert { "low" }?, tei_macro.phraseSeq } |
<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> |
||||||||||
Schema Declaration |
element pubPlace { attribute cert { "low" }?, tei_macro.phraseSeq } |
<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 | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
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> |
||||||||||
Schema Declaration |
element quote { tei_att.global.attribute.xmlid, attribute xml:lang { "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat" }?, tei_macro.specialPara } |
<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links] | |||||||||||||||||||||
Module | core | ||||||||||||||||||||
Attributes | att.cReferencing (@cRef) att.pointing (targetLang, evaluate, @target)
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by |
core: analytic author bibl biblScope biblStruct date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
textcrit: witness
transcr: supplied
|
||||||||||||||||||||
May contain | |||||||||||||||||||||
Note |
The target and cRef attributes are mutually exclusive. |
||||||||||||||||||||
Example |
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
sentence</ref> |
||||||||||||||||||||
Example |
See also <ref target="#locution">s.v. <term>locution</term>
</ref>. |
||||||||||||||||||||
Schematron |
<sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> |
||||||||||||||||||||
Content model |
<content> |
||||||||||||||||||||
Schema Declaration |
element ref { tei_att.cReferencing.attributes, tei_att.pointing.attribute.target, attribute rend { list { ( "ebd" | "Ebd" )+ } }?, attribute type { "corrigenda" | "copyright" | "homepage" | "wit" | "wdb" | "print" }, tei_macro.paraContent } |
<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier] | |
Module | msdescription |
Contained by |
msdescription: altIdentifier 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> |
Schema Declaration |
element repository { tei_macro.phraseSeq.limited } |
<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> |
||||||||||
Schema Declaration |
element resp { attribute n { "transcription_and_annotation" | "transcription_and_annotation_assistance" | "transcription_and_annotation_preliminary_work" | "content" | "content_assistance" | "content_preliminary_work" | "encoding" | "encoding_word2tei_transformation" | "encoding_assistance" | "post-coding" }, tei_macro.phraseSeq.limited } |
<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 |
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> |
Schema Declaration |
element respStmt { ( ( tei_resp+, tei_model.nameLike.agent+ ) | ( tei_model.nameLike.agent+, tei_resp+ ) ), tei_note* } |
<row> (row) contains one row of a table. [14.1.1. TEI Tables] | |
Module | figures |
Attributes | att.tableDecoration (role, rows, @cols) |
Contained by |
figures: table
|
May contain |
figures: cell
|
Example |
<row role="data">
<cell role="label">Classics</cell> <cell>Idle listless and unimproving</cell> </row> |
Content model |
<content> |
Schema Declaration |
element row { tei_att.tableDecoration.attribute.cols, tei_cell+ } |
<rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings] | |||||||||||||||||||||||||
Module | core | ||||||||||||||||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) att.canonical (key, @ref)
|
||||||||||||||||||||||||
Member of | |||||||||||||||||||||||||
Contained by | |||||||||||||||||||||||||
May contain | |||||||||||||||||||||||||
Example |
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs>
to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q> |
||||||||||||||||||||||||
Content model |
<content> |
||||||||||||||||||||||||
Schema Declaration |
element rs { tei_att.global.attribute.xmlid, tei_att.canonical.attribute.ref, attribute rend { list { ( "ebd" | "Ebd" )+ } }?, attribute type { "person" | "place" | "bibl" | "biblical" }, attribute cRef { text }?, tei_macro.phraseSeq } |
<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers] | |||||||||||
Module | textstructure | ||||||||||
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id)
|
||||||||||
Member of | |||||||||||
Contained by | |||||||||||
May contain | |||||||||||
Example |
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>
|
||||||||||
Content model |
<content> |
||||||||||
Schema Declaration |
element salute { tei_att.global.attribute.xmlid, attribute rend { list { ( "right-align-right" | "right-align-left" | "left-align-right" | "left-align-left" | "center-align-left" | "center-align-right" | "center" | "inline" | "hanging" )+ } }?, tei_macro.paraContent } |
<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |||||||||||||||||||||||||||||
Module | linking | ||||||||||||||||||||||||||||
Attributes | att.datcat (datcat, valueDatcat, @targetDatcat)
|
||||||||||||||||||||||||||||
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> |
||||||||||||||||||||||||||||
Schema Declaration |
element seg { tei_att.datcat.attribute.targetDatcat, attribute xml:id { xsd:ID }?, attribute rend { list { ( "ebd" | "Ebd" )+ } }?, attribute type { "classical" | "lem" | "corr" | "add" | "wdb" | "comment" | "citation" | "emphasis" }, tei_macro.paraContent } |
<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 |
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> |
Schema Declaration |
element sourceDesc { tei_model.pLike+ | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+ } |
<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |
Module | transcr |
Member of | |
Contained by | |
May contain | |
Note |
The <damage>, gap, <del>, <unclear> and supplied elements may be closely allied in use. See section 11.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. |
Example |
I am dr Sr yr
<supplied reason="illegible" source="#amanuensis_copy">very humble Servt</supplied> Sydney Smith |
Example |
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
|
Content model |
<content> |
Schema Declaration |
element supplied { tei_macro.paraContent } |
<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables] | |
Module | figures |
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) |
Member of | |
Contained by | |
May contain | |
Note |
Contains an optional heading and a series of rows. Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate. |
Example |
<table cols="4" rows="4">
<head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head> <row role="label"> <cell role="data"/> <cell role="data">Dossing Cribs or Lodging Houses</cell> <cell role="data">Beds</cell> <cell role="data">Needys or Nightly Lodgers</cell> </row> <row role="data"> <cell role="label">Bury St Edmund's</cell> <cell role="data">5</cell> <cell role="data">8</cell> <cell role="data">128</cell> </row> <row role="data"> <cell role="label">Thetford</cell> <cell role="data">3</cell> <cell role="data">6</cell> <cell role="data">36</cell> </row> <row role="data"> <cell role="label">Attleboro'</cell> <cell role="data">3</cell> <cell role="data">5</cell> <cell role="data">20</cell> </row> <row role="data"> <cell role="label">Wymondham</cell> <cell role="data">1</cell> <cell role="data">11</cell> <cell role="data">22</cell> </row> </table> |
Content model |
<content> |
Schema Declaration |
element table { tei_att.global.attribute.xmlid, ( ( tei_model.headLike | tei_model.global )*, ( ( tei_row, tei_model.global* )+ | ( tei_model.graphicLike, tei_model.global* )+ ), ( tei_model.divBottom, tei_model.global* )* ) } |
<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text] | |
Module | textstructure |
Attributes | att.global (xml:lang, xml:base, xml:space, @xml:id, @n) att.global.linking (corresp, synch, copyOf, next, prev, exclude, select, @sameAs) |
Contained by |
textstructure: TEI
|
May contain | |
Note |
This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. |
Example |
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader> <fileDesc> <titleStmt> <title>The shortest TEI Document Imaginable</title> </titleStmt> <publicationStmt> <p>First published as part of TEI P2, this is the P5 version using a namespace.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <text> <body> <p>This is about the shortest TEI document imaginable.</p> </body> </text> </TEI> |
Example |
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader> <fileDesc> <titleStmt> <title>A TEI Document containing four page images </title> </titleStmt> <publicationStmt> <p>Unpublished demonstration file.</p> </publicationStmt> <sourceDesc> <p>No source: this is an original work.</p> </sourceDesc> </fileDesc> </teiHeader> <facsimile> <graphic url="page1.png"/> <graphic url="page2.png"/> <graphic url="page3.png"/> <graphic url="page4.png"/> </facsimile> </TEI> |
Schematron |
<sch:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs" uri="http://www.w3.org/2001/XMLSchema"/> |
Schematron |
<sch:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/> |
Content model |
<content> |
Schema Declaration |
element TEI { tei_att.global.attribute.xmlid, tei_att.global.attribute.n, tei_att.global.linking.attribute.sameAs, ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) ) } |
<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text] | |
Module | header |
Contained by |
textstructure: TEI
|
May contain |
header: encodingDesc fileDesc profileDesc
|
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> |
Schema Declaration |
element teiHeader { tei_fileDesc, tei_model.teiHeaderPart*, revisionDesc? } |
<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses] | |||||||||||||||||||||
Module | core | ||||||||||||||||||||
Attributes |
|
||||||||||||||||||||
Member of | |||||||||||||||||||||
Contained by | |||||||||||||||||||||
May contain | |||||||||||||||||||||
Note |
When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a term element by means of its target attribute. In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The term element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the term element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release. |
||||||||||||||||||||
Example |
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers. |
||||||||||||||||||||
Example |
We may define <term rend="sc" xml:id="TDPV1">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> |
||||||||||||||||||||
Example |
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> |
||||||||||||||||||||
Example |
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
|
||||||||||||||||||||
Content model |
<content> |
||||||||||||||||||||
Schema Declaration |
element term { attribute xml:lang { "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat" }?, attribute type { "term" | "title" }?, tei_macro.phraseSeq } |
<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text] | |||||||||||
Module | textstructure | ||||||||||
Attributes |
|
||||||||||
Member of | |||||||||||
Contained by |
textstructure: TEI
|
||||||||||
May contain | |||||||||||
Note |
This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose. |
||||||||||
Example |
<text>
<front> <docTitle> <titlePart>Autumn Haze</titlePart> </docTitle> </front> <body> <l>Is it a dragonfly or a maple leaf</l> <l>That settles softly down upon the water?</l> </body> </text> |
||||||||||
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> |
||||||||||
Schema Declaration |
element text { attribute xml:lang { "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat" }?, ( tei_model.global*, tei_model.global*?, ( tei_body | group ), tei_model.global*, ( tei_back, tei_model.global* )? ) } |
<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification] | |
Module | header |
Member of | |
Contained by |
header: profileDesc
|
May contain |
header: keywords
|
Example |
<taxonomy>
<category xml:id="acprose"> <catDesc>Academic prose</catDesc> </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass> <catRef target="#acprose"/> <classCode scheme="http://www.udcc.org">001.9</classCode> <keywords scheme="http://authorities.loc.gov"> <list> <item>End of the world</item> <item>History - philosophy</item> </list> </keywords> </textClass> |
Content model |
<content> |
Schema Declaration |
element textClass { ( classCode | catRef | tei_keywords )* } |
<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 10.6.6. Languages and Writing Systems] | |||||||||||||
Module | core | ||||||||||||
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
|
||||||||||||
Member of | |||||||||||||
Contained by |
core: analytic bibl biblStruct monogr
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> |
||||||||||||
Schema Declaration |
element textLang { tei_att.global.attributes, attribute mainLang { teidata.language }?, attribute otherLangs { list { teidata.language* } }?, tei_macro.specialPara } |
<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 |
core: analytic author bibl biblScope biblStruct date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref resp rs term textLang title
figures: cell
header: distributor extent handNote titleStmt
linking: seg
msdescription: additions msItem repository
textcrit: witness
transcr: supplied
|
||||||||||||
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> |
||||||||||||
Schema Declaration |
element title { attribute type { "main" | "short" | "quote_title" }?, tei_macro.paraContent } |
<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 |
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> |
Schema Declaration |
element titleStmt { tei_title+, tei_model.respLike* } |
<w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation] | |
Module | analysis |
Attributes | att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation) |
Member of | |
Contained by | |
May contain | |
Example |
This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant. <l>
<w lemma="it" pos="pn" xml:id="A19883-003-a-0100">IT</w> <w lemma="have" pos="vvz" xml:id="A19883-003-a-0110">hath</w> <w lemma="be" pos="vvn" xml:id="A19883-003-a-0120">been</w> <w lemma="say" pos="vvn" xml:id="A19883-003-a-0130">said</w> <w lemma="of" pos="acp-p" xml:id="A19883-003-a-0140">of</w> <w lemma="old" pos="j" xml:id="A19883-003-a-0150">old</w> <pc xml:id="A19883-003-a-0160">,</pc> <w lemma="that" pos="cs" xml:id="A19883-003-a-0170">that</w> <w lemma="play" pos="vvz" xml:id="A19883-003-a-0180"> <choice> <orig>Playes</orig> <reg>Plays</reg> </choice> </w> <w lemma="be" pos="vvb" xml:id="A19883-003-a-0190">are</w> <w lemma="feast" pos="n2" xml:id="A19883-003-a-0200">Feasts</w> <pc xml:id="A19883-003-a-0210">,</pc> </l> <l xml:id="A19883-e100220"> <w lemma="poet" pos="n2" xml:id="A19883-003-a-0220">Poets</w> <w lemma="the" pos="d" xml:id="A19883-003-a-0230">the</w> <w lemma="cook" pos="n2" xml:id="A19883-003-a-0240"> <choice> <orig>Cookes</orig> <reg>Cooks</reg> </choice> </w> <pc xml:id="A19883-003-a-0250">,</pc> <w lemma="and" pos="cc" xml:id="A19883-003-a-0260">and</w> <w lemma="the" pos="d" xml:id="A19883-003-a-0270">the</w> <w lemma="spectator" pos="n2" xml:id="A19883-003-a-0280">Spectators</w> <w lemma="guest" pos="n2" xml:id="A19883-003-a-0290">Guests</w> <pc xml:id="A19883-003-a-0300">,</pc> </l> <l xml:id="A19883-e100230"> <w lemma="the" pos="d" xml:id="A19883-003-a-0310">The</w> <w lemma="actor" pos="n2" xml:id="A19883-003-a-0320">Actors</w> <w lemma="waiter" pos="n2" xml:id="A19883-003-a-0330">Waiters</w> <pc xml:id="A19883-003-a-0340">:</pc> <!-- ... --> </l> |
Content model |
<content> |
Schema Declaration |
element w { tei_att.global.attributes, tei_att.segLike.attributes, tei_att.typed.attributes, tei_att.linguistic.attributes, tei_att.notated.attributes, ( text | tei_model.gLike | tei_seg | tei_w | m | c | pc | tei_model.global | tei_model.lPart | tei_model.hiLike | tei_model.pPart.edit )* } |
<witness> (witness) contains either a description of a single witness referred to within the critical apparatus, or a list of witnesses which is to be referred to by a single sigil. [12.1. The Apparatus Entry, Readings, and Witnesses] | |
Module | textcrit |
Attributes | att.global (n, xml:lang, xml:base, xml:space, @xml:id) att.global.linking (synch, sameAs, copyOf, next, prev, exclude, select, @corresp) |
Contained by |
textcrit: listWit
|
May contain | |
Note |
The content of the witness element may give bibliographic information about the witness or witness group, or it may be empty. |
Example |
<listWit>
<witness xml:id="EL">Ellesmere, Huntingdon Library 26.C.9</witness> <witness xml:id="HG">Hengwrt, National Library of Wales, Aberystwyth, Peniarth 392D</witness> <witness xml:id="RA2">Bodleian Library Rawlinson Poetic 149 (see further <ptr target="http://www.examples.com/MSdescs#MSRP149"/>)</witness> </listWit> |
Content model |
<content> |
Schema Declaration |
element witness { tei_att.global.attribute.xmlid, tei_att.global.linking.attribute.corresp, ( text | tei_model.limitedPhrase | tei_model.inter | tei_note | object )* } |
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.quoteLike [quote] |
model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | bibl biblStruct listBibl msDesc |
model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | model.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor respStmt] availability bibl extent msIdentifier textLang |
model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.divPart [model.lLike [l] model.pLike [p] lg] model.inter [model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [label] model.listLike [list listWit table] model.oddDecl model.stageLike] |
Note |
This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates] | |
Module | tei |
Used by | |
Members | date |
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.divBottomPart [closer] model.divWrapper [salute] |
model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages] | |
Module | tei |
Used by | |
Members | closer |
model.divLike groups elements used to represent un-numbered generic structural divisions. | |
Module | tei |
Used by | |
Members | div |
model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | model.lLike [l] model.pLike [p] lg |
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 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.headLike [head] opener] model.divWrapper [salute] |
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.headLike [head] opener |
model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions] | |
Module | tei |
Used by | |
Members | salute |
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 | foreign term title |
model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times. | |
Module | tei |
Used by | |
Members | projectDesc |
model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ] | |
Module | tei |
Used by | |
Members | model.frontPart.drama listBibl |
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 [gap] model.global.meta model.milestoneLike [anchor lb pb] model.noteLike [note noteGrp] |
model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
Module | tei |
Used by | |
Members | gap |
model.headLike groups elements used to provide a title or heading at the start of a text division. | |
Module | tei |
Used by | |
Members | head |
model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
Module | tei |
Used by | |
Members | model.emphLike [foreign term title] model.hiLike [hi] |
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 | hi |
model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
Module | tei |
Used by | |
Members | biblScope distributor pubPlace publisher |
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.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [label] model.listLike [list listWit table] model.oddDecl model.stageLike |
model.labelLike groups elements used to gloss or explain other parts of a document. | |
Module | tei |
Used by | |
Members | label |
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.emphLike [foreign term title] model.hiLike [hi] model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] idno rs] ] model.pPart.editorial [ex] model.pPart.msdesc [locus] model.phrase.xml model.ptrLike [ptr ref] |
model.listLike groups list-like elements. [3.8. Lists] | |
Module | tei |
Used by | |
Members | list listWit table |
model.lLike groups elements representing metrical components such as verse lines. | |
Module | tei |
Used by | |
Members | l |
model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements] | |
Module | tei |
Used by | |
Members | anchor lb pb |
model.msItemPart groups elements which can appear within a manuscript item description. | |
Module | tei |
Used by | |
Members | model.biblLike [bibl biblStruct listBibl msDesc] model.msQuoteLike [title] model.quoteLike [quote] model.respLike [author editor respStmt] idno msItem textLang |
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 | title |
model.nameLike groups elements which name or refer to a person, place, or organization. | |
Module | tei |
Used by | |
Members | model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] idno rs |
Note |
A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
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 | persName |
Note |
This class is used in the content model of elements which reference names of people or organizations. |
model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing] | |
Module | tei |
Used by | |
Members | note noteGrp |
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 | model.graphicLike model.highlighted [model.emphLike [foreign term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] idno rs] ] model.pPart.edit [model.pPart.editorial [ex] model.pPart.transcriptional [orig supplied] ] model.pPart.msdesc [locus] model.phrase.xml model.ptrLike [ptr ref] model.segLike [seg w] model.specDescLike |
Note |
This class of elements can occur within paragraphs, list items, lines of verse, etc. |
model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source. | |
Module | msdescription |
Used by | |
Members | additions handDesc objectDesc |
model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names] | |
Module | tei |
Used by | |
Members | placeName |
model.placeStateLike groups elements which describe changing states of a place. | |
Module | tei |
Used by | |
Members | model.placeNamePart [placeName] |
model.pLike groups paragraph-like elements. | |
Module | tei |
Used by | |
Members | p |
model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages] | |
Module | tei |
Used by | |
Members | head |
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.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] idno rs] |
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.editorial [ex] model.pPart.transcriptional [orig supplied] |
model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes] | |
Module | tei |
Used by | |
Members | ex |
model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description] | |
Module | tei |
Used by | |
Members | locus |
model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes] | |
Module | tei |
Used by | |
Members | orig supplied |
model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times. | |
Module | tei |
Used by | |
Members | textClass |
model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
Module | tei |
Used by | |
Members | ptr ref |
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 | distributor publisher |
Note |
The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element. See also model.publicationStmtPart.detail. |
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 | model.ptrLike [ptr ref] availability date idno pubPlace |
Note |
A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
model.quoteLike groups elements used to directly contain quotations. | |
Module | tei |
Used by | |
Members | quote |
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 | text |
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 | author editor respStmt |
model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |
Module | tei |
Used by | |
Members | seg w |
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.teiHeaderPart groups high level elements which may appear more than once in a TEI header. | |
Module | tei |
Used by | |
Members | encodingDesc profileDesc |
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 | note noteGrp | ||||||||||||||||||
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.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents] | |||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||
Members | att.naming [att.personal [persName placeName] author editor pubPlace repository rs] date distributor publisher resp respStmt term title | ||||||||||||||||||||||
Attributes |
|
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 | ptr ref term | ||||||||
Attributes |
|
att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||
Module | tei | ||||||||||||||||||||
Members | altIdentifier author date editor gender idno persName placeName resp title | ||||||||||||||||||||
Attributes | att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
|
||||||||||||||||||||
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 provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | att.datable [altIdentifier author date editor gender idno persName placeName resp title] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||||||||||||||||
Module | namesdates | ||||||||||||||||||||||||||||||||||
Members | att.datable [altIdentifier author date editor gender idno persName placeName resp title] | ||||||||||||||||||||||||||||||||||
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 dur-iso="P8D" when-iso="2007-06-01"/> indicates the same time period as
<date when-iso="2007-06-01/P8D"/>
In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading. |
att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates] | |||||||||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||||||||
Members | att.datable [altIdentifier author date editor gender idno persName placeName resp title] | ||||||||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@when]"> <sch:report role="nonfatal" test="@notBefore|@notAfter|@from|@to">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule> |
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@from]"> <sch:report role="nonfatal" test="@notBefore">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule> |
||||||||||||||||||||||||||||||||||||
Schematron |
<sch:rule context="tei:*[@to]"> <sch:report role="nonfatal" test="@notAfter">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule> |
||||||||||||||||||||||||||||||||||||
Example |
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
|
||||||||||||||||||||||||||||||||||||
Note |
The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar. The most commonly-encountered format for the date portion of a temporal attribute
is 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 provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values] | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | att.segLike [seg w] | ||||||||||||||||||
Attributes |
|
||||||||||||||||||
Example |
The example below presents the TEI encoding of the name-value pair The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology. <fs>
<f datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" name="POS"> <symbol value="NN" valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/> </f> <!-- ... --> </fs> ‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun. While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry. If the feature structure markup exemplified above is to be repeated many times in
a single document, it is much more efficient to gather the persistent identifiers
in a single place and to only reference them, implicitly or directly, from feature
structure markup. The following example is much more concise than the one above and
relies on the concepts of feature structure declaration and feature value library,
discussed in chapter [ID FS in TEI Guidelines].
<fs>
<f fVal="#commonNoun" name="POS"/> <!-- ... --> </fs> The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of text or a child of encodingDesc; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option. The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same
time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic
categories.
<fvLib n="POS values">
<symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" value="NN" xml:id="commonNoun"/> <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae" value="NP" xml:id="properNoun"/> <!-- ... --> </fvLib> Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value. |
||||||||||||||||||
Example |
In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above. <gramGrp>
<pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3" valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp> Efficiency of this type of interoperable markup demands that the references to the
particular data categories should best be provided in a single place within the dictionary
(or a single place within the project), rather than being repeated inside every entry.
For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true">
<!-- ... --> <namespace name="http://www.tei-c.org/ns/1.0"> <tagUsage gi="pos" targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage> <tagUsage gi="case" targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... --> </namespace> </tagsDecl> Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>
<prefixDef ident="ccr" matchPattern="pos" replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/> <prefixDef ident="ccr" matchPattern="adj" replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...--> <form> <orth>isotope</orth> </form> <gramGrp> <pos datcat="ccr:pos" valueDatcat="ccr:adj">adj</pos> </gramGrp> <!--...--> </entry> This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised. Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in <equiv> element that is a child of <elementSpec> or <attDef>. |
||||||||||||||||||
Example |
The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object. <fDecl name="POS"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"> <fDescr>part of speech (morphosyntactic category)</fDescr> <vRange> <vAlt> <symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545" value="NN"/> <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae" value="NP"/> <!-- ... --> </vAlt> </vRange> </fDecl> Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element. |
||||||||||||||||||
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 (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 provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text] | |||||||||
Module | tei | ||||||||
Members | availability bibl biblStruct listBibl projectDesc sourceDesc textClass | ||||||||
Attributes |
|
||||||||
Note |
The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true. |
att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
Module | tei | ||||||||
Members | bibl biblStruct msDesc | ||||||||
Attributes |
|
||||||||
Example |
<revisionDesc status="published">
<change status="published" when="2010-10-21"/> <change status="cleared" when="2010-10-02"/> <change status="embargoed" when="2010-08-02"/> <change status="frozen" when="2010-05-01" who="#MSM"/> <change status="draft" when="2010-03-01" who="#LB"/> </revisionDesc> |
att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
Module | tei | ||||||||||||||||
Members | date ex gap gender persName placeName supplied | ||||||||||||||||
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 provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy. | |||||||||||
Module | tei | ||||||||||
Members | att.divLike [div lg] att.segLike [seg w] l p | ||||||||||
Attributes |
|
att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||||||||||||||||
Members | TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness | ||||||||||||||||||||||||||||||||||||||||||||
Attributes | att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
|
att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations] | |||||||||
Module | analysis | ||||||||
Members | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||||
Attributes |
|
att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles] | |||||||
Module | transcr | ||||||
Members | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||
Attributes |
|
att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | linking | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes |
|
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 | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||||||||||||||||||||||||||
Attributes |
|
att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents] | |||||||||||||||
Module | tei | ||||||||||||||
Members | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||||||||||
Attributes |
|
||||||||||||||
Example |
Blessed are the
<choice> <sic>cheesemakers</sic> <corr cert="high" resp="#editor">peacemakers</corr> </choice>: for they shall be called the children of God. |
||||||||||||||
Example |
<!-- in the <text> ... --><lg> <!-- ... --> <l>Punkes, Panders, baſe extortionizing sla<choice> <sic>n</sic> <corr resp="#JENS1_transcriber">u</corr> </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber"> <resp when="2014">Transcriber</resp> <name>Janelle Jenstad</name> </respStmt> |
att.global.source 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 | att.global [TEI additional additions altIdentifier analytic anchor author availability back bibl biblScope biblStruct body cell closer date distributor div editor encodingDesc ex extent fileDesc foreign gap gender handDesc handNote head hi idno imprint item keywords l label lb lg list listBibl listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt row rs salute seg sourceDesc supplied table teiHeader term text textClass textLang title titleStmt w witness] | ||||||||||
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.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module. | |||||||||||||||||||||||||||||||
Module | analysis | ||||||||||||||||||||||||||||||
Members | att.linguistic [w] | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Note |
It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, orig, and <reg> needs to be employed. |
att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and <pc> in the analysis module. [17.4.2. Lightweight Linguistic Annotation] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Module | analysis | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Members | w | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Attributes | att.lexicographic.normalized (@norm, @orig)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Note |
These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion. |
att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms] | |||||||||||||||
Module | tei | ||||||||||||||
Members | att.personal [persName placeName] author editor pubPlace repository rs | ||||||||||||||
Attributes | att.canonical (@key, @ref)
|
att.notated provides attributes to indicate any specialised notation used for element content. | |||||||
Module | tei | ||||||
Members | quote seg w | ||||||
Attributes |
|
att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions] | |||||||||||||
Module | tei | ||||||||||||
Members | head label note noteGrp | ||||||||||||
Attributes |
|
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 | locus note noteGrp ptr ref term | ||||||||||||||||||||||||||||||
Attributes |
|
att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
Module | tei | ||||||||||||||||||||||||||||||
Members | att.dimensions [date ex gap supplied] | ||||||||||||||||||||||||||||||
Attributes |
|
||||||||||||||||||||||||||||||
Example |
The MS. was lost in transmission by mail from <del rend="overstrike">
<gap atLeast="1" atMost="2" extent="one or two letters" reason="illegible" unit="chars"/> </del> Philadelphia to the Graphic office, New York. |
||||||||||||||||||||||||||||||
Example |
Americares has been supporting the health sector in Eastern
Europe since 1986, and since 1992 has provided <measure atLeast="120000000" commodity="currency" unit="USD">more than $120m</measure> in aid to Ukrainians. |
att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |||||||||
Module | tei | ||||||||
Members | seg w | ||||||||
Attributes | att.datcat (@datcat, @valueDatcat, @targetDatcat) att.fragmentable (@part)
|
att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure] | |||||||||||
Module | tei | ||||||||||
Members | bibl biblStruct idno item list listBibl listWit msDesc term witness | ||||||||||
Attributes |
|
att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
Module | tei | ||||||||||||||||||
Members | TEI altIdentifier anchor bibl biblStruct date div gender head idno label lb lg list listBibl locus msDesc note noteGrp pb persName placeName ptr quote ref rs seg table term text title w | ||||||||||||||||||
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 23.3.1.3. Modification of Attribute and Attribute Value Lists . |
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 | closer div head hi label note noteGrp opener p salute seg text | ||||||
Attributes |
|
teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.certainty = "high" | "medium" | "low" | "unknown" |
Note |
Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. |
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> |
Declaration |
tei_teidata.count = xsd:nonNegativeInteger |
Note |
Any positive integer value or zero is permitted |
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> |
Declaration |
tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" } |
Example |
<time dur-iso="PT0,75H">three-quarters of an hour</time>
|
Example |
<date dur-iso="P1,5D">a day and a half</date>
|
Example |
<date dur-iso="P14D">a fortnight</date>
|
Example |
<time dur-iso="PT0.02S">20 ms</time>
|
Note |
A duration is expressed as a sequence of number-letter pairs, preceded by the letter
P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M
(minute), or S (second), in that order. The numbers are all unsigned integers, except
for the last, which may have a decimal component (using either For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
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> |
Declaration |
tei_teidata.duration.w3c = xsd:duration |
Example |
<time dur="PT45M">forty-five minutes</time>
|
Example |
<date dur="P1DT12H">a day and a half</date>
|
Example |
<date dur="P7D">a week</date>
|
Example |
<time dur="PT0.02S">20 ms</time>
|
Note |
A duration is expressed as a sequence of number-letter pairs, preceded by the letter
P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M
(minute), or S (second), in that order. The numbers are all unsigned integers, except
for the For complete details, see the W3C specification. |
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 |
teidata.genderElement:
|
Content model |
<content> |
Declaration |
tei_teidata.enumerated = teidata.word |
Note |
Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character. | |
Module | tei |
Used by |
Element:
|
Content model |
<content> |
Declaration |
tei_teidata.gender = teidata.enumerated |
Note |
Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms). |
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> |
Declaration |
tei_teidata.language = xsd:language | ( "" ) |
Note |
The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice. A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
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 defines the range of attribute values expressed as an XML Name. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.name = xsd:Name |
Note |
Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
teidata.numeric defines the range of attribute values used for numeric values. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.numeric = xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal |
Note |
Any numeric value, represented as a decimal number, in floating point format, or as a ratio. To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3. A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2. |
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> |
Declaration |
tei_teidata.outputMeasurement = token { pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)" } |
Example |
<figure>
<head>The TEI Logo</head> <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in between and <mentioned>text encoding initiative</mentioned> underneath, all on a white background.</figDesc> <graphic height="600px" url="http://www.tei-c.org/logos/TEI-600.jpg" width="600px"/> </figure> |
Note |
These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft. |
teidata.pattern defines attribute values which are expressed as a regular expression. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.pattern = token |
Note |
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give
a concise description of a set, without having to list all elements. For example,
the set containing the three strings Handel, Händel, and Haendel can be described by the pattern Wikipedia H(ä|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 defines the data type used to express a point in cartesian space. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" } |
Example |
<facsimile>
<surface lrx="400" lry="280" ulx="0" uly="0"> <zone points="220,100 300,210 170,250 123,234"> <graphic url="handwriting.png"/> </zone> </surface> </facsimile> |
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 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> |
Declaration |
tei_teidata.pointer = xsd:anyURI { pattern = "\S+" } |
Note |
The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, |
teidata.probability defines the range of attribute values expressing a probability. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.probability = xsd:double |
Note |
Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. |
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> |
Declaration |
tei_teidata.probCert = teidata.probability | teidata.certainty |
teidata.replacement defines attribute values which contain a replacement template. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.replacement = text |
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> |
Declaration |
tei_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 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> |
Declaration |
tei_teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime |
Note |
If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
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> |
Declaration |
tei_teidata.text = string |
Note |
Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
teidata.truthValue defines the range of attribute values used to express a truth value. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.truthValue = xsd:boolean |
Note |
The possible values of this datatype are 1 or true, or 0 or false. This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue. |
teidata.versionNumber defines the range of attribute values used for version numbers. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.versionNumber = token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" } |
teidata.word defines the range of attribute values expressed as a single word or token. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" } |
Note |
Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
teidata.xpath defines attribute values which contain an XPath expression. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_teidata.xpath = text |
Note |
Any XPath expression using the syntax defined in 6.2. . When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP. |
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> |
Declaration |
tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" ) |
Note |
In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
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> |
Declaration |
tei_macro.paraContent = ( text | tei_model.paraPart )* |
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> |
Declaration |
tei_macro.phraseSeq = ( text | tei_model.gLike | tei_model.attributable | tei_model.phrase | tei_model.global )* |
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> |
Declaration |
tei_macro.phraseSeq.limited = ( text | tei_model.limitedPhrase | tei_model.global )* |
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> |
Declaration |
tei_macro.specialPara = ( text | tei_model.gLike | tei_model.phrase | tei_model.inter | tei_model.divPart | tei_model.global )* |
macro.xtext (extended text) defines a sequence of character data and gaiji elements. | |
Module | tei |
Used by | |
Content model |
<content> |
Declaration |
tei_macro.xtext = ( text | tei_model.gLike )* |