This document describes how the TEI standard was customized for the project Lectures that Link. The project focuses on building a data collection of Digital Humanities lecture series hosted by European institutions between 2014 and early 2025. The primary emphasis is on the lecture series themselves, the individual lectures within these series, and the speakers involved. Detailed descriptions of who these data were collected and encoded in TEI are provided in the following sections, with examples included in the running text.
All data used in this project was exclusively sourced from publicly accessible websites, ensuring that only freely available information was included. Data behind authentication barriers, such as those requiring login credentials, was deliberately excluded from the collection process.
In addition to textual information about the lecture series found on individual websites, additional digital materials related to the events were incorporated into the project. These sources were accessed via hyperlinks found on the websites and include presentations, blog posts, related articles, and audiovisual content, such as videos.
While every effort has been made to ensure the dataset is comprehensive within the scope of the project, it does not claim to be exhaustive or definitive. Instead, it serves as a solid foundation for both the current and future analyses.
All lecture series are recorded in the <listEvent> element, which is located within <body>, a sub-element of <text>. To accurately reflect the inherent structure of lecture series, the XML is organized hierarchically. The term lecture series implies a three-tiered structure:
To represent this hierarchy, the following approach is used:
Each lecture series is recorded within an <event> element, with the type attribute set to the value lecture-series. Additionally, the where attribute references the ID of the location where the series is hosted:
The <event> element contains an <eventName> sub-element, which records the original name of the series. The xml:lang attribute specifies the language of the lecture series name. If official translations exist, multiple <eventName> elements may be listed sequentially, as can be seen above.
Each lecture series consists of at least one, but usually multiple <event> elements, each representing an instance of the lecture series, for instance, an academic term in which the series took place. These <event> elements include a type attribute with the value lecture-series-term, as well as the attributes from and to indicating the term’s duration (year and month):
If a consolidated program overview is available for a given term, a <ptr> element is included after the <eventName> element. The type attribute of <ptr> is set to the value programme to indicate its purpose.
After these term-level <event> elements, individual lectures are recorded, as explained in the following sections.
A individual lecture is recorded as an <event> element with the attribute type (with the value lecture) and with the attribute when, which specifies the date of the event in the format year-month-day. The structure of the content within each <event> element remains consistent across all lectures. Therefore, it is described in the following subsections from top to bottom, using the example below:
At the beginning of each entry, the lecture title is recorded using an <eventName> element. The language of the title is specified via the xml:lang attribute.
Directly below the title, the abstract of the lecture follows. This is captured within a <note> element, which is characterized by the type attribute set to the value abstract. Additionally, the xml:lang attribute specifies the language of the abstract.
As the example above already shows, the abstract text itself is recorded within one or more <p> elements. If a list is included within the abstract, a <list> element is used, with individual list items represented by <item> elements.
If the abstract contains formatting elements such as bold, italics, or hyperlinks, these are not explicitly marked up.
If an abstract is available, it is recorded within the <note type="abstract"> tag. If no abstract is provided, the content of the note is set to "not found":
Each recorded lecture is assigned keywords by the encoders to be able to analyze the distribution of disciplines, methods and topics across the lectures and lecture series. That is, the keywords are not collected from the websites of the lecture series but they are added by the editors of this data collection.
The keywords are stored inside of a <note> element, characterized by the attribute type with the value keywords. Within this <note> element, there are two <term> elements:
In case that there is more than one discipline, it is collected in the corresp attribute of the same <term> element. We opted for this (instead of using an individual <term> element for each keyword) to facilitate later processing of the data and for a more compact encoding of the information. For the disciplines, we use a pre-defined list that we created on our own. The topics were generated with a script calling an LLM.
Both discipline and topic assignments are based on the lecture content. This classification relies on the abstract and title of the lecture. Since every lecture has a title but not necessarily an abstract, classification is always possible. However, a longer title or the presence of an abstract allows for a more precise categorization.
The lecture modality is recorded in the <note type="realization"> tag, specifying whether the lecture was held in person, hybrid, or online. The <note> element contains two <term> sub-elements that define the modality separately for speakers and audience members. These <term> elements use the type attribute to distinguish between the modality of the speech and of the audience:
The values for these elements are standardized to ensure consistency in data representation. The possible values are:
If a lecture was canceled, a fourth value, canceled, is used. In this case, as shown in the example below, the <term type="audience"> tag is omitted since no audience attended:
The speakers of a lecture are recorded in a <listPerson> element. Each speaker is described using a <person> element with a corresp attribute that links to the corresponding person entry in the TEI header. The academic title (if provided) is stored within a <roleName type="title"> element inside of the <name> element. The speaker’s affiliation is captured within an <affiliation> element, referencing the corresponding institution, which is encoded in the TEI header. The information about the speakers, their affiliations, and the institutions is encoded in two places for the following reasons: on the one hand, we aim to have a centralized list of people and institutions in the TEI header, to which we can refer from individual events. On the other hand, the affiliations of people can change over time and the same is true for their titles. One person might not have a title at the moment of one event, but might have a title at another event later on, for instance, if someone completed his or her PhD. Therefore, information about the current affiliation of a speaker at the moment of the event and about the current title that a person has when the event takes place is encoded directly inside of the individual event.
The titles of the speaker(s) are recorded according to the information provided in the lecture program, supporting materials (slides, videos, or blog posts), or a short biography. Common academic titles include:
These titles are standardized. For instance, "Univ.-Prof." is simplified to "Prof.", and variations in spelling (e.g., "PhD" and "Ph.D.") are standardized.
Academic degrees such as Bakkalaureus Artium / Bachelor of Arts (B.A.) and Magister Artium / Master of Arts (M.A.) are not recorded, as they are typically not included in the program. Similarly, if no title is available, the value not found is used:
Hosts are recorded at the end of the individual lecture entry to indicate which organizations were responsible for hosting the lecture, i.e., those that invited the speaker(s). The host institution is specified with an <org> element that includes the attribute role with the standardized value host-institution. The corresp attribute references the corresponding organization entry in the TEI header. This value is recorded independently of the lecture modality (i.e., in presence, hybrid, or online).
As mentioned above, information about the hosting institutions concludes the section for an individual lecture. However, the final element within a lecture series term is the information about the organizers of the term. This information is stored within an <org> element with the attribute role and the standardized value organizer.
Unlike host institutions, which are organizations, organizers are recorded as individual persons, as can be seen in the example above. It is possible for an organizer to also be a speaker in another lecture series or even in their own series.
Since organizational responsibility can change from term to term, it is considered appropriate to record this information at this level rather than for the entire series.
The dataset assigns unique IDs to lecture series, lecture series terms, individual lectures, persons, organizations, and locations, which are consistently stored in the xml:id attribute. The following aspects must be considered when creating IDs:
Additional considerations include:
All collected information is recorded exclusively in the languages in which it appears on the respective websites. Each element of a lecture event that contains textual information in a certain language is marked with the attribute xml:lang, specifying the corresponding language value, such as en for English or de for German. No translations of content are produced.
The documentation of series, terms and lectures is mainly focused on English, Italian, German, Spanish, French and Portuguese, due to the language knowledge of the collaborators in this project. Other languages can be included, especially when it comes to recording the names of organizations or places. By default, these informations are documented in the language in which they originally emerged, which may differ from the respective national language.
In some cases, a title may include multiple languages, whether for stylistic reasons or because it contains a key term discussed in the lecture or an introductory quotation. In such instances, only the primary language of the title is recorded, while additional languages are not documented, as shown in the following example:
In such cases, the primary language of the element must be identified and recorded. In the example above, this would be English. The primary language can often be determined by identifying which part of the content conveys the core subject matter rather than serving a decorative or stylistic function. For titles, another useful indicator is the language of the accompanying abstract, if available.
In order to ensure the long-term accessibility and reliability of information, we secure all relevant sources via links, which are then archived using the Wayback Machine from the Internet Archive (https://web.archive.org/). This archiving process applies to all links, except for DOI links, which are permanent by definition and do not require additional archiving. However, links that lead to videos, such as those on YouTube, are not archived because archiving by the Wayback Machine is not possible in this case.
All links within the dataset are encoded using the <ptr> (pointer) element. Within this element, the type attribute is used to specify the exact role of the link, as seen in the following examples:
The values for the type attribute are as follows:
It is important to highlight that we only capture links that directly originate from the lecture series’ website. While further research to gather additional sources is possible, it has not been consistently carried out.
Organizations involved in Digital Humanities lecture series are divided into two main roles: the affiliation of the (invited) speaker and the hosting venue.
In most cases, organizations are listed at the level of entire universities, research institutions, or cultural institutions. Specific departments or institutes within these organizations, where speakers may be affiliated, are not captured in the data. E.g. if an affiliation to the Institute of German Studies at the University of Rostock is mentioned in a program, only the University of Rostock is encoded.
Each organization is represented by a separate entry within the <particDesc> element, found under <listOrg>. The <org> sub-element defines the organization and is assigned a unique ID through the xml:id attribute. This ID is used throughout the dataset to ensure consistent referencing. Additionally, the type attribute within the <org> element is employed to specify the organization's precise role. Available values for the type attribute include:
As can be seen in the example below, the "Università di Bologna" is represented as an organization with the ID uni-bologna. The name of the organization is presented in the original language (Italian, in this case), and an external Wikidata identifier is included within the <idno> element.
As described above, all organizations, including all university entries, are assigned an ID. Unlike those of other organizations, university IDs always begin with uni- or fh- followed by a unique part, typically derived from the name or location of the institution. For example, the University of Rostock is captured as follows:
In order to maintain clarity and allow for future adjustments, the names of universities are standardized. For instance, "Julius-Maximilians-Universität Würzburg" is shortened to "Universität Würzburg", and the corresponding ID becomes uni-wuerzburg:
This simplification also reduces the need for updates when a university undergoes rebranding or changes its name, such as in the case of the recent shift in Münster from "Westfälische Wilhelms-Universität Münster" to "Universität Münster".
When multiple universities exist within the same city, additional distinctions are added to the ID to avoid confusion. These distinctions are appended to the base ID formed by the university's type and location. For example, in London, where several institutions exist, their IDs are distinguished as follows:
In contrast, Berlin presents another situation, as the German naming convention is that distinctions should precede the city name, resulting in IDs such as:
As with all organizations in the dataset, each university is assigned an external identifier, referenced through the <idno> element, which refers to the university’s Wikidata entry.
Research institutions are identified using the type attribute with the value research_institution. This category includes private and public research organizations that are not classified as universities.
The structure follows the same pattern as universities, ensuring consistency across all organization types.
GLAM organizations (Galleries, Libraries, Archives, and Museums) are identified using the type attribute with the value glam. The IDs for GLAM organizations are usually derived from existing abbreviations.
The company category includes both private and public organizations that are not primarily engaged in academic research. This encompasses commercial enterprises as well as organizations funded through grants or sponsorships, such as those providing infrastructure or research support.
Each speaker included in the dataset is represented by an individual entry within the <listPerson> element, specifically under <particDesc>.
To ensure consistent identification, every speaker is assigned a unique ID through the xml:id attribute. This identifier follows a standardized format, combining the speaker's surname and given name, separated by an underscore. In cases where a speaker has multiple given or family names, these are connected using hyphens. For example:
As shown above, each entry also records the speaker's social gender, represented by the <gender> element within the <person> element. The primary values for this element are female and male. The gender assignment is based primarily on the typical gender associations of given names. Additionally, where available, information from Wikidata and other external databases has been used to verify gender identity. If research indicates that a person does not fall within the binary gender spectrum, they are assigned the value non-binary. It should be noted that assigning gender based on name connotations is inherently prone to errors. While every effort has been made to ensure accuracy through external sources, there may still be instances where the assigned gender does not align with the individual's self-identification.
Each speaker entry includes a <name> element, which further contains <forename> and <surname> sub-elements. These store the full given name and surname of the individual without abbreviations or alterations.
Additionally, every speaker entry includes at least one, but typically two, <idno> elements. These elements reference external identifiers. One of these identifiers is the orcid, a researcher-specific identifier maintained by the speaker themselves, while the second is a wikidata ID. If a Wikidata entry does not already exist for a given speaker, a new record is created.
Each location in the dataset is represented by an individual entry within the <listPlace> element, specifically under <settingDesc>. There are three types of entries: for continents, for countries and for cities. This distinction is made using the type attribute, which takes either the value continent, country or city.
All location names are recorded in English or using the vernacular form if no English form is knowsn, following the naming conventions in place at the time of data collection.
To ensure consistent identification, each location is assigned a unique ID using the xml:id attribute. In most cases, this ID matches the name of the city, country or continent. However, exceptions are made when a city shares the same name as the country it belongs to, such as Luxembourg City in Luxembourg. The same rule applies to city-states:
Each city entry includes a <name> element that records the full name of the place without abbreviations or modifications. Additionally, every city entry contains a <country> element, which links the city to its corresponding country via the ref attribute.
Each city entry also includes an <idno> element. Using the type attribute, this element provides a reference to the Getty Thesaurus of Geographic Names (TGN), ensuring precise identification of the location.
For place names consisting of multiple words, hyphens are used to connect the words in the xml:id attribute:
| <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text] | |||||||||
| Module | textstructure | ||||||||
| Attributes |
| ||||||||
| Contained by | textstructure: TEI | ||||||||
| May contain | |||||||||
| Note | As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">. | ||||||||
| Example | <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>The shortest TEI Document Imaginable</title>
</titleStmt>
<publicationStmt>
<p>First published as part of TEI P2, this is the P5
version using a namespace.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<body>
<p>This is about the shortest TEI document imaginable.</p>
</body>
</text>
</TEI> | ||||||||
| Example | <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>A TEI Document containing four page images </title>
</titleStmt>
<publicationStmt>
<p>Unpublished demonstration file.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<facsimile>
<graphic url="page1.png"/>
<graphic url="page2.png"/>
<graphic url="page3.png"/>
<graphic url="page4.png"/>
</facsimile>
</TEI> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="teiHeader"/>
<alternate>
<sequence>
<classRef key="model.resource"
maxOccurs="unbounded" minOccurs="1"/>
<elementRef key="TEI"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<elementRef key="TEI"
maxOccurs="unbounded" minOccurs="1"/>
</alternate>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element TEI
{
tei_att.global.attributes,
tei_att.typed.attributes,
attribute version { text }?,
( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}⚓ | ||||||||
| <affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [16.2.2. The Participant Description] | |||||||||||
| Module | namesdates | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Note | If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element. | ||||||||||
| Example | <affiliation>Junior project officer for the US <name type="org">National Endowment for
the Humanities</name>
</affiliation> | ||||||||||
| Example | This example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed. <affiliation notAfter="1960-01-01"
notBefore="1957-02-28">Paid up member of the
<orgName>Australian Journalists Association</orgName>
</affiliation> | ||||||||||
| Example | This example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed. <affiliation from="1902-01-01"
to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation> | ||||||||||
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||||
| Schema Declaration |
element affiliation
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.naming.attributes,
tei_att.typed.attribute.subtype,
attribute type { text }?,
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 | core: bibl header: publicationStmt | ||||||||
| May contain | |||||||||
| Note | A consistent format should be adopted | ||||||||
| Example | <availability status="restricted">
<p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
<p>In the public domain</p>
</availability>
<availability status="restricted">
<p>Available under licence from the publishers.</p>
</availability> | ||||||||
| Example | <availability>
<licence target="http://opensource.org/licenses/MIT">
<p>The MIT License
applies to this document.</p>
<p>Copyright (C) 2011 by The University of Victoria</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.</p>
</licence>
</availability> | ||||||||
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde"
value="tei:availability"/>
</sch:pattern> | ||||||||
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.availabilityPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ | ||||||||
| Schema Declaration |
element availability
{
tei_att.global.attributes,
tei_att.declarable.attributes,
attribute status { "free" | "unknown" | "restricted" }?,
( tei_model.availabilityPart | tei_model.pLike )+
}⚓ | ||||||||
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Contains phrase-level elements, together with any combination of elements from the model.biblPart class |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl> |
| Example | <bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>.
</bibl> |
| Example | <bibl 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> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:bibl"/>
</sch:pattern> |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.highlighted"/>
<classRef key="model.pPart.data"/>
<classRef key="model.pPart.edit"/>
<classRef key="model.segLike"/>
<classRef key="model.ptrLike"/>
<classRef key="model.biblPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element bibl
{
tei_att.global.attributes,
tei_att.canonical.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.docStatus.attributes,
tei_att.sortable.attributes,
tei_att.typed.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
)*
}⚓ |
| <bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [14.2.3. Place Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <bloc type="union">the European Union</bloc>
<bloc type="continent">Africa</bloc> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element bloc
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.naming.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure |
| Attributes |
|
| Contained by | textstructure: text |
| May contain | |
| Example | <body>
<l>Nu scylun hergan hefaenricaes uard</l>
<l>metudæs maecti end his modgidanc</l>
<l>uerc uuldurfadur sue he uundra gihuaes</l>
<l>eci dryctin or astelidæ</l>
<l>he aerist scop aelda barnum</l>
<l>heben til hrofe haleg scepen.</l>
<l>tha middungeard moncynnæs uard</l>
<l>eci dryctin æfter tiadæ</l>
<l>firum foldu frea allmectig</l>
<trailer>primo cantauit Cædmon istud carmen.</trailer>
</body> |
| Content model |
<content>
<sequence>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
<sequence minOccurs="0">
<classRef key="model.divTop"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divTop"/>
</alternate>
</sequence>
<sequence minOccurs="0">
<classRef key="model.divGenLike"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.divLike"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.div1Like"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence>
<sequence maxOccurs="unbounded"
minOccurs="1">
<alternate maxOccurs="1" minOccurs="1">
<elementRef key="schemaSpec"/>
<classRef key="model.common"/>
</alternate>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<alternate minOccurs="0">
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.divLike"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.div1Like"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.global"/>
<classRef key="model.divGenLike"/>
</alternate>
</sequence>
</alternate>
</sequence>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.divBottom"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element body
{
tei_att.global.attributes,
tei_att.declaring.attributes,
(
tei_model.global*,
( ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )? ),
(
( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?
),
(
(
( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
)
| (
(
tei_model.div1Like,
( tei_model.global | tei_model.divGenLike )*
)+
)
| (
( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
(
(
(
tei_model.divLike,
( tei_model.global | tei_model.divGenLike )*
)+
)
| (
(
tei_model.div1Like,
( tei_model.global | tei_model.divGenLike )*
)+
)
)?
)
),
( ( tei_model.divBottom, tei_model.global* )* )
)
}⚓ |
| <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | header: category |
| May contain | |
| Example | <catDesc>Prose reportage</catDesc> |
| Example | <catDesc>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose degree="high" type="entertain"/>
<purpose degree="medium" type="inform"/>
</textDesc>
</catDesc> |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.catDescPart"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element catDesc
{
tei_att.global.attributes,
tei_att.canonical.attributes,
( text | tei_model.limitedPhrase | tei_model.catDescPart )*
}⚓ |
| <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | |
| Example | <category xml:id="b1">
<catDesc>Prose reportage</catDesc>
</category> |
| Example | <category xml:id="b2">
<catDesc>Prose </catDesc>
<category xml:id="b11">
<catDesc>journalism</catDesc>
</category>
<category xml:id="b12">
<catDesc>fiction</catDesc>
</category>
</category> |
| Example | <category xml:id="LIT">
<catDesc xml:lang="pl">literatura piękna</catDesc>
<catDesc xml:lang="en">fiction</catDesc>
<category xml:id="LPROSE">
<catDesc xml:lang="pl">proza</catDesc>
<catDesc xml:lang="en">prose</catDesc>
</category>
<category xml:id="LPOETRY">
<catDesc xml:lang="pl">poezja</catDesc>
<catDesc xml:lang="en">poetry</catDesc>
</category>
<category xml:id="LDRAMA">
<catDesc xml:lang="pl">dramat</catDesc>
<catDesc xml:lang="en">drama</catDesc>
</category>
</category> |
| Content model |
<content>
<sequence>
<alternate>
<elementRef key="catDesc"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.descLike"/>
<elementRef key="equiv"/>
<elementRef key="gloss"/>
</alternate>
</alternate>
<elementRef key="category"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element category
{
tei_att.global.attributes,
tei_att.datcat.attributes,
(
( tei_catDesc+ | ( tei_model.descLike | equiv | gloss )* ),
tei_category*
)
}⚓ |
| <change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions] | |||||||
| Module | header | ||||||
| Attributes |
| ||||||
| Contained by | header: listChange revisionDesc | ||||||
| May contain | |||||||
| Note | The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it. It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented. | ||||||
| Example | <titleStmt>
<title> ... </title>
<editor xml:id="LDB">Lou Burnard</editor>
<respStmt xml:id="BZ">
<resp>copy editing</resp>
<name>Brett Zamir</name>
</respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
<change status="public" when="2008-02-02"
who="#BZ">Finished chapter 23</change>
<change status="draft" when="2008-01-02"
who="#BZ">Finished chapter 2</change>
<change n="P2.2" when="1991-12-21"
who="#LDB">Added examples to section 3</change>
<change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc> | ||||||
| Example | <profileDesc>
<creation>
<listChange>
<change xml:id="DRAFT1">First draft in pencil</change>
<change notBefore="1880-12-09"
xml:id="DRAFT2">First revision, mostly
using green ink</change>
<change notBefore="1881-02-13"
xml:id="DRAFT3">Final corrections as
supplied to printer.</change>
</listChange>
</creation>
</profileDesc> | ||||||
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ | ||||||
| Schema Declaration |
element change
{
tei_att.global.attributes,
tei_att.ascribed.attributes,
tei_att.datable.attributes,
tei_att.docStatus.attributes,
tei_att.typed.attributes,
attribute target { list { + } }?,
tei_macro.specialPara
}⚓ | ||||||
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: encodingDesc |
| May contain | header: taxonomy |
| Example | <classDecl>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
<!-- ... -->
<textClass>
<keywords scheme="#LCSH">
<term>Political science</term>
<term>United States -- Politics and government --
Revolution, 1775-1783</term>
</keywords>
</textClass> |
| Content model |
<content>
<elementRef key="taxonomy"
maxOccurs="unbounded" minOccurs="1"/>
</content>
⚓ |
| Schema Declaration |
element classDecl { tei_att.global.attributes, tei_taxonomy+ }⚓ |
| <country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [14.2.3. Place Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The recommended source for codes to represent coded country names is ISO 3166. |
| Example | <country key="DK">Denmark</country> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element country
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.naming.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <date when="1980-02">early February 1980</date> |
| Example | Given on the <date when="1977-06-12">Twelfth Day
of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
the Two Hundredth and first and of the University the Eighty-Sixth.</date> |
| Example | <date when="1990-09">September 1990</date> |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element date
{
tei_att.global.attributes,
tei_att.calendarSystem.attributes,
tei_att.canonical.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.dimensions.attributes,
tei_att.editLike.attributes,
tei_att.typed.attributes,
( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}⚓ |
| <desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb. | ||||||||||||
| Example | Example of a <desc> element inside a documentation element. <dataSpec ident="teidata.point"
module="tei">
<desc versionDate="2010-10-17"
xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
<!-- ... -->
</dataSpec> | ||||||||||||
| Example | Example of a <desc> element in a non-documentation element. <place xml:id="KERG2">
<placeName>Kerguelen Islands</placeName>
<!-- ... -->
<terrain>
<desc>antarctic tundra</desc>
</terrain>
<!-- ... -->
</place> | ||||||||||||
| Schematron | A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule> | ||||||||||||
| Content model |
<content>
<macroRef key="macro.limitedContent"/>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element desc
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.typed.attribute.subtype,
attribute type { "deprecationInfo" }?,
tei_macro.limitedContent
}⚓ | ||||||||||||
| <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt |
| May contain | |
| Example | <edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element edition { tei_att.global.attributes, tei_macro.phraseSeq }⚓ |
| <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <editionStmt>
<edition n="S2">Students' edition</edition>
<respStmt>
<resp>Adapted by </resp>
<name>Elizabeth Kirk</name>
</respStmt>
</editionStmt> |
| Example | <editionStmt>
<p>First edition, <date>Michaelmas Term, 1991.</date>
</p>
</editionStmt> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<sequence>
<elementRef key="edition"/>
<classRef key="model.respLike"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element editionStmt
{
tei_att.global.attributes,
( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
}⚓ |
| <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Note | A consistent format should be adopted. Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. |
| Example | <editor role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element editor
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.naming.attributes,
tei_macro.phraseSeq
}⚓ |
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | |
| Example | <encodingDesc>
<p>Basic encoding, capturing lexical information only. All
hyphenation, punctuation, and variant spellings normalized. No
formatting or layout information preserved.</p>
</encodingDesc> |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.encodingDescPart"/>
<classRef key="model.pLike"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element encodingDesc
{
tei_att.global.attributes,
( tei_model.encodingDescPart | tei_model.pLike )+
}⚓ |
| <event> (event) contains data relating to anything of significance that happens in time. [14.3.1. Basic Principles] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listEvent>
<event when="1618-05-23" where="#Prague"
xml:id="SecondDefPrague">
<eventName>1618 Defenestration of Prague</eventName>
<idno>https://www.wikidata.org/wiki/Q13365740</idno>
<listPerson type="defenstrated">
<person>
<persName>Jaroslav Bořita z Martinic</persName>
<idno type="GND">https://d-nb.info/gnd/116810998</idno>
</person>
<person>
<persName>Vilém Slavata z Chlumu a Košumberka</persName>
<idno type="GND">https://d-nb.info/gnd/1018376615</idno>
</person>
<person>
<persName>Filip Fabricius</persName>
<idno type="GND">https://d-nb.info/gnd/133946118</idno>
</person>
</listPerson>
<place xml:id="Prague">
<placeName>Prague</placeName>
</place>
</event>
<event from="1618" to="1648"
xml:id="ThirtyYearsWar">
<eventName>Thirty Years’ War</eventName>
<idno>https://www.wikidata.org/wiki/Q2487</idno>
<event when="1643-03-19" where="#Rocroi"
xml:id="BattleofRocroi">
<eventName>Battle of Rocroi</eventName>
<idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>
<idno type="GND">https://d-nb.info/gnd/4202901-6</idno>
<place xml:id="Rocroi">
<placeName>Rocroi</placeName>
<location>
<geo decls="#WGS">49.926111 4.522222</geo>
</location>
</place>
</event>
</event>
</listEvent> |
| Example | <person>
<event type="mat" when="1972-10-12">
<label>matriculation</label>
</event>
<event type="grad" when="1975-06-23">
<label>graduation</label>
</event>
</person> |
| Content model |
<content>
<sequence>
<elementRef key="idno"
maxOccurs="unbounded" minOccurs="0"/>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<classRef key="model.labelLike"
maxOccurs="unbounded" minOccurs="1"/>
<elementRef key="eventName"
maxOccurs="unbounded" minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.noteLike"/>
<classRef key="model.biblLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="linkGrp"/>
<elementRef key="link"/>
<elementRef key="idno"/>
</alternate>
<classRef key="model.eventLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.personLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listPerson"
maxOccurs="1" minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.placeLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listPlace"
maxOccurs="1" minOccurs="1"/>
</alternate>
<classRef key="model.objectLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element event
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.locatable.attributes,
tei_att.naming.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_idno*,
tei_model.headLike*,
( tei_model.pLike+ | tei_model.labelLike+ | tei_eventName+ ),
(
tei_model.noteLike
| tei_model.biblLike
| tei_model.ptrLike
| linkGrp
| link
| tei_idno
)*,
tei_model.eventLike*,
( tei_model.personLike | tei_listPerson )*,
( tei_model.placeLike | tei_listPlace )*,
tei_model.objectLike*,
( relation | listRelation )*
)
}⚓ |
| <eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [14.2.4. Event Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listEvent>
<event from="1939-09-01" to="1945-09-02">
<eventName xml:lang="de">Zweiter Weltkrieg</eventName>
<eventName xml:lang="en">World War II</eventName>
<idno type="GND">https://d-nb.info/gnd/4079167-1</idno>
<idno type="Wikidata">https://www.wikidata.org/wiki/Q362</idno>
<event from="1939-09-01" to="1939-10-06"
xml:id="UeberfallAufPolen">
<eventName xml:lang="de">Überfall auf Polen</eventName>
<eventName xml:lang="en">Invasion of Poland</eventName>
<idno type="GND">https://d-nb.info/gnd/4175002-0</idno>
<idno type="LOC">https://id.loc.gov/authorities/sh85148341</idno>
<listPlace type="affected">
<place>
<placeName xml:lang="pl">Gdańsk</placeName>
<location>
<geo>54.350556 18.652778</geo>
</location>
</place>
</listPlace>
</event>
<event from="1941-06-22" to="1945-05-09">
<eventName xml:lang="de">Deutsch-Sowjetischer Krieg</eventName>
<eventName xml:lang="ru">Великая Отечественная война</eventName>
<idno type="GND">https://d-nb.info/gnd/4076906-9</idno>
<idno type="Wikidata">https://www.wikidata.org/wiki/Q189266</idno>
</event>
</event>
</listEvent> |
| Example | <p>On <date when="1719-03-19">Monday</date>, <rs type="person">she</rs> was writing about the
<eventName ref="#SecondDefPrague">1618 Defenestration of Prague</eventName> which initiated the
<rs ref="#ThirtyYearsWar" type="event">long war</rs>.</p> |
| Example | <event from="2019-09-16" to="2019-09-20"
xml:id="tei2019graz">
<eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>
<eventName type="short">TEI 2019</eventName>
<note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.
Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the
<ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.
</note>
<listPerson type="LocalOrganizers">
<person>
<persName>
<surname>Raunig</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Martina</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Walter</forename>
</persName>
</person>
<person>
<persName>
<surname>Steiner</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Vogeler</surname>
<forename>Georg</forename>
</persName>
</person>
</listPerson>
<place xml:lang="de">
<placeName>Universität Graz</placeName>
<location>
<address>
<addrLine>ReSoWi Gebäude</addrLine>
<addrLine>Universitätsstraße 15</addrLine>
<postCode>8010</postCode>
<settlement>Graz</settlement>
<country>Österreich</country>
</address>
<geo>15.451651587656 47.078215112534</geo>
</location>
</place>
<listRelation>
<relation active="#tei2019graz"
name="P31_is_instance_of" passive="#AnnualTEIConference"
ref="https://www.wikidata.org/wiki/Property:P31" type="CRM"/>
</listRelation>
</event> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element eventName
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
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 |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | |
| Note | The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
| Example | <fileDesc>
<titleStmt>
<title>The shortest possible TEI document</title>
</titleStmt>
<publicationStmt>
<p>Distributed as part of TEI P5</p>
</publicationStmt>
<sourceDesc>
<p>No print source exists: this is an original digital text</p>
</sourceDesc>
</fileDesc> |
| Content model |
<content>
<sequence>
<sequence>
<elementRef key="titleStmt"/>
<elementRef key="editionStmt"
minOccurs="0"/>
<elementRef key="extent" minOccurs="0"/>
<elementRef key="publicationStmt"/>
<elementRef key="seriesStmt"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="notesStmt"
minOccurs="0"/>
</sequence>
<elementRef key="sourceDesc"
maxOccurs="unbounded" minOccurs="1"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element fileDesc
{
tei_att.global.attributes,
(
(
tei_titleStmt,
tei_editionStmt?,
extent?,
tei_publicationStmt,
seriesStmt*,
notesStmt?
),
tei_sourceDesc+
)
}⚓ |
| <forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <persName>
<roleName>Ex-President</roleName>
<forename>George</forename>
<surname>Bush</surname>
</persName> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element forename
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <gender> (gender) specifies the gender identity of a person, persona, or character. [14.3.2.1. Personal Characteristics] | |||||||||
| Module | namesdates | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | namesdates: person | ||||||||
| 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>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ | ||||||||
| Schema Declaration |
element gender
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.typed.attributes,
attribute value { list { + } }?,
tei_macro.phraseSeq
}⚓ | ||||||||
| <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||||||
| Module | header | ||||||||||
| Attributes |
| ||||||||||
| Member of | |||||||||||
| Contained by | |||||||||||
| May contain | header: idno character data | ||||||||||
| Note | <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI. | ||||||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
<g ref="#sym"/>345
</idno> In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym. | ||||||||||
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="idno"/>
</alternate>
</content>
⚓ | ||||||||||
| Schema Declaration |
element idno
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attribute.subtype,
attribute type
{
"ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
}?,
( text | tei_model.gLike | tei_idno )*
}⚓ | ||||||||||
| <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description] | |
| Module | core |
| Attributes |
|
| Contained by | core: list |
| May contain | |
| Note | May contain simple prose or a sequence of chunks. Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n. |
| Example | <list rend="numbered">
<head>Here begin the chapter headings of Book IV</head>
<item n="4.1">The death of Queen Clotild.</item>
<item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
<item n="4.3">The wives and children of Lothar.</item>
<item n="4.4">The Counts of the Bretons.</item>
<item n="4.5">Saint Gall the Bishop.</item>
<item n="4.6">The priest Cato.</item>
<item> ...</item>
</list> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element item
{
tei_att.global.attributes,
tei_att.sortable.attributes,
tei_macro.specialPara
}⚓ |
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes |
|
| Member of | |
| Contained by | header: availability |
| May contain | |
| Note | A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. |
| Example | <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence> |
| Example | <availability>
<licence notBefore="2013-01-01"
target="http://creativecommons.org/licenses/by/3.0/">
<p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
applies to this document.</p>
<p>The licence was added on January 1, 2013.</p>
</licence>
</availability> |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element licence
{
tei_att.global.attributes,
tei_att.datable.attributes,
tei_att.pointing.attributes,
tei_macro.specialPara
}⚓ |
| <list> (list) contains any sequence of items organized as a list. [3.8. Lists] | |||||||||||||
| Module | core | ||||||||||||
| Attributes |
| ||||||||||||
| Member of | |||||||||||||
| Contained by | |||||||||||||
| May contain | |||||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||||
| Example | <list rend="numbered">
<item>a butcher</item>
<item>a baker</item>
<item>a candlestick maker, with
<list rend="bulleted">
<item>rings on his fingers</item>
<item>bells on his toes</item>
</list>
</item>
</list> | ||||||||||||
| Example | <list rend="bulleted" type="syllogism">
<item>All Cretans are liars.</item>
<item>Epimenides is a Cretan.</item>
<item>ERGO Epimenides is a liar.</item>
</list> | ||||||||||||
| Example | <list rend="simple" type="litany">
<item>God save us from drought.</item>
<item>God save us from pestilence.</item>
<item>God save us from wickedness in high places.</item>
<item>Praise be to God.</item>
</list> | ||||||||||||
| Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section">
<head>Athelstan's Ordinance</head>
<list rend="numbered">
<item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
eightpence.
<list rend="numbered">
<item n="1.1">And if anyone does spare one, he is to pay for the thief with his
wergild — and the thief is to be no nearer a settlement on that account — or to
clear himself by an oath of that amount.</item>
<item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
not to be spared [whether younger or older than twelve].</item>
<item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
then be redeemed with 120 shillings; and the kindred are to stand surety for him
that he will desist for ever.</item>
<item n="1.4">And if he steals after that, they are to pay for him with his wergild,
or to bring him back there.</item>
<item n="1.5">And if he steals after that, they are to pay for him with his wergild,
whether to the king or to him to whom it rightly belongs; and everyone of those who
supported him is to pay 120 shillings to the king as a fine.</item>
</list>
</item>
<item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
no justice can be obtained, that one should order their kindred to fetch back such a
person to justice and to find him a lord in public meeting.
<list rend="numbered">
<item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
he is then to be a fugitive afterwards, and he who encounters him is to strike him
down as a thief.</item>
<item n="2.2">And he who harbours him after that, is to pay for him with his wergild
or to clear himself by an oath of that amount.</item>
</list>
</item>
<item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
his guilty man, so that the king is appealed to, is to repay the value of the goods and
120 shillings to the king; and he who appeals to the king before he demands justice as
often as he ought, is to pay the same fine as the other would have done, if he had
refused him justice.
<list rend="numbered">
<item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
known about him, is to forfeit the slave and be liable to his wergild on the first
occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
<item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
an accessory of thieves who have committed theft, is to liable to the same.</item>
</list>
</item>
<item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
afterwards convicted at the three-fold ordeal.</item>
</list>
</div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. | ||||||||||||
| Example | <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross.
<list rend="simple">
<item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
subscribed to the pious and catholic validity of this document with the sign of the Holy
Cross.</item>
<item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
the sign of the Holy Cross.</item>
<item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
sign of the Holy Cross.</item>
<item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
sign of the Holy Cross.</item>
<item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
the Holy Cross.</item>
<item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
<item>I, Æthelwine, bishop, have subscribed through delegates.</item>
<item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
Cross.</item>
</list>
</p> | ||||||||||||
| Schematron |
<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule> | ||||||||||||
| Content model |
<content>
<sequence>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.divTop"/>
<classRef key="model.global"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
</alternate>
<alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<elementRef key="item"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<sequence>
<elementRef key="headLabel"
minOccurs="0"/>
<elementRef key="headItem"
minOccurs="0"/>
<sequence maxOccurs="unbounded"
minOccurs="1">
<elementRef key="label"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="item"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</sequence>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.divBottom"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</sequence>
</content>
⚓ | ||||||||||||
| Schema Declaration |
element list
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.sortable.attributes,
tei_att.typed.attribute.subtype,
attribute type
{
"gloss" | "index" | "instructions" | "litany" | "syllogism"
}?,
(
( tei_model.divTop | tei_model.global | tei_desc* )*,
(
( ( tei_item, tei_model.global* )+ )
| (
headLabel?,
headItem?,
( ( 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 16.3.2. Declarable Elements] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listBibl>
<head>Works consulted</head>
<bibl>Blain, Clements and Grundy: Feminist Companion to
Literature in English (Yale, 1990)
</bibl>
<biblStruct>
<analytic>
<title>The Interesting story of the Children in the Wood</title>
</analytic>
<monogr>
<title>The Penny Histories</title>
<author>Victor E Neuberg</author>
<imprint>
<publisher>OUP</publisher>
<date>1968</date>
</imprint>
</monogr>
</biblStruct>
</listBibl> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listBibl"/>
</sch:pattern> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.milestoneLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.biblLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.milestoneLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="relation"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listBibl
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
tei_desc*,
( tei_model.milestoneLike | relation | listRelation )*,
(
(
tei_model.biblLike+,
( tei_model.milestoneLike | relation | listRelation )*
)+
)
)
}⚓ |
| <listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 12.7. Identifying Changes and Revisions] | |||||||||
| Module | header | ||||||||
| Attributes |
| ||||||||
| Contained by | header: listChange revisionDesc | ||||||||
| May contain | core: desc header: change listChange | ||||||||
| Note | When this element appears within the <creation> element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text. | ||||||||
| Example | <revisionDesc>
<listChange>
<change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
<change when="1991-11-02" who="#MSM"> completed first draft </change>
</listChange>
</revisionDesc> | ||||||||
| Example | <profileDesc>
<creation>
<listChange ordered="true">
<change xml:id="CHG-1">First stage, written in ink by a writer</change>
<change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>
<change xml:id="CHG-3">Fixation of the revised passages and further revisions by
Goethe using ink</change>
<change xml:id="CHG-4">Addition of another stanza in a different hand,
probably at a later stage</change>
</listChange>
</creation>
</profileDesc> | ||||||||
| Content model |
<content>
<sequence>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="1">
<elementRef key="listChange"/>
<elementRef key="change"/>
</alternate>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element listChange
{
tei_att.global.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
attribute ordered { text }?,
( tei_desc*, ( tei_listChange | tei_change )+ )
}⚓ | ||||||||
| <listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [14.3.1. Basic Principles] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listEvent>
<head>Battles of the American Civil War: Kentucky</head>
<event when="1861-09-19" xml:id="event01">
<label>Barbourville</label>
<desc>The Battle of Barbourville was one of the early engagements of
the American Civil War. It occurred September 19, 1861, in Knox
County, Kentucky during the campaign known as the Kentucky Confederate
Offensive. The battle is considered the first Confederate victory in
the commonwealth, and threw a scare into Federal commanders, who
rushed troops to central Kentucky in an effort to repel the invasion,
which was finally thwarted at the <ref target="#event02">Battle of
Camp Wildcat</ref> in October.</desc>
</event>
<event when="1861-10-21" xml:id="event02">
<label>Camp Wild Cat</label>
<desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp
Wild Cat) was one of the early engagements of the American Civil
War. It occurred October 21, 1861, in northern Laurel County, Kentucky
during the campaign known as the Kentucky Confederate Offensive. The
battle is considered one of the very first Union victories, and marked
the first engagement of troops in the commonwealth of Kentucky.</desc>
</event>
<event from="1864-06-11" to="1864-06-12"
xml:id="event03">
<label>Cynthiana</label>
<desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement
during the American Civil War that was fought on June 11 and 12, 1864,
in Harrison County, Kentucky, near the town of Cynthiana. A part of
Confederate Brigadier General John Hunt Morgan's 1864 Raid into
Kentucky, the battle resulted in a victory by Union forces over the
raiders and saved the town from capture.</desc>
</event>
</listEvent> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listEvent"/>
</sch:pattern> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.eventLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listEvent
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
tei_desc*,
( relation | listRelation )*,
( ( tei_model.eventLike+, ( relation | listRelation )* )+ )
)
}⚓ |
| <listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [14.2.2. Organizational Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | The type attribute may be used to distinguish lists of organizations of a particular type if convenient. |
| Example | <listOrg>
<head>Libyans</head>
<org>
<orgName>Adyrmachidae</orgName>
<desc>These people have, in most points, the same customs as the Egyptians, but
use the costume of the Libyans. Their women wear on each leg a ring made of
bronze [...]</desc>
</org>
<org>
<orgName>Nasamonians</orgName>
<desc>In summer they leave their flocks and herds upon the sea-shore, and go up
the country to a place called Augila, where they gather the dates from the
palms [...]</desc>
</org>
<org>
<orgName>Garamantians</orgName>
<desc>[...] avoid all society or intercourse with their fellow-men, have no
weapon of war, and do not know how to defend themselves. [...]</desc>
<!-- ... -->
</org>
</listOrg> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listOrg"/>
</sch:pattern> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<alternate maxOccurs="unbounded"
minOccurs="1">
<elementRef key="org" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listOrg" maxOccurs="1"
minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listOrg
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
tei_desc*,
( relation | listRelation )*,
( ( ( tei_org | tei_listOrg )+, ( relation | listRelation )* )+ )
)
}⚓ |
| <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | corpus: particDesc header: change licence sourceDesc namesdates: event listPerson org textstructure: body |
| May contain | core: desc namesdates: listPerson org person |
| Note | The type attribute may be used to distinguish lists of people of a particular type if convenient. |
| Example | <listPerson type="respondents">
<personGrp xml:id="PXXX"/>
<person age="mid" sex="2" xml:id="P1234"/>
<person age="mid" sex="1" xml:id="P4332"/>
<listRelation>
<relation mutual="#P1234 #P4332"
name="spouse" type="personal"/>
</listRelation>
</listPerson> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde"
value="tei:listPerson"/>
</sch:pattern> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.personLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listPerson"
maxOccurs="1" minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listPerson
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
tei_desc*,
( relation | listRelation )*,
(
(
( tei_model.personLike | tei_listPerson )+,
( relation | listRelation )*
)+
)
)
}⚓ |
| <listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 14.3.4. Places] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <listPlace type="offshoreIslands">
<place>
<placeName>La roche qui pleure</placeName>
</place>
<place>
<placeName>Ile aux cerfs</placeName>
</place>
</listPlace> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listPlace"/>
</sch:pattern> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="desc"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation" maxOccurs="1"
minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.placeLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listPlace"
maxOccurs="1" minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="relation"
maxOccurs="1" minOccurs="1"/>
<elementRef key="listRelation"
maxOccurs="1" minOccurs="1"/>
</alternate>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element listPlace
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declarable.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
tei_desc*,
( relation | listRelation )*,
(
(
( tei_model.placeLike | tei_listPlace )+,
( relation | listRelation )*
)+
)
)
}⚓ |
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. |
| Example | <name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name ref="#HOC001" type="person">Occleve</name> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element name
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <nameLink> (name link) contains a connecting phrase or link used within a name but not regarded as part of it, such as van der or of. [14.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <persName>
<forename>Frederick</forename>
<nameLink>van der</nameLink>
<surname>Tronck</surname>
</persName> |
| Example | <persName>
<forename>Alfred</forename>
<nameLink>de</nameLink>
<surname>Musset</surname>
</persName> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element nameLink
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" resp="#MDMH"
type="gloss">
<term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.
<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
<resp>translation from German to English</resp>
<name>Hottinger, Marie Donald Mackie</name>
</respStmt> For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header. |
| Example | The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="true" n="126"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. |
| Content model |
<content>
<macroRef key="macro.specialPara"/>
</content>
⚓ |
| Schema Declaration |
element note
{
tei_att.global.attributes,
tei_att.anchoring.attributes,
tei_att.cmc.attributes,
tei_att.placement.attributes,
tei_att.pointing.attributes,
tei_att.typed.attributes,
tei_att.written.attributes,
tei_macro.specialPara
}⚓ |
| <org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [14.3.3. Organizational Data] | |||||||||
| Module | namesdates | ||||||||
| Attributes |
| ||||||||
| Member of | |||||||||
| Contained by | corpus: particDesc namesdates: event listOrg listPerson org | ||||||||
| May contain | |||||||||
| Example | <org xml:id="JAMs">
<orgName>Justified Ancients of Mummu</orgName>
<desc>An underground anarchist collective spearheaded by
<persName>Hagbard Celine</persName>, who fight the Illuminati
from a golden submarine, the <name>Leif Ericson</name>
</desc>
<bibl>
<author>Robert Shea</author>
<author>Robert Anton Wilson</author>
<title>The Illuminatus! Trilogy</title>
</bibl>
</org> | ||||||||
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.labelLike"/>
<classRef key="model.nameLike"/>
<classRef key="model.placeLike"/>
<classRef key="model.orgPart"/>
<classRef key="model.milestoneLike"/>
</alternate>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.noteLike"/>
<classRef key="model.biblLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="linkGrp"/>
<elementRef key="link"/>
</alternate>
<classRef key="model.personLike"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</content>
⚓ | ||||||||
| Schema Declaration |
element org
{
tei_att.global.attributes,
tei_att.editLike.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
attribute role { list { + } }?,
(
tei_model.headLike*,
(
tei_model.pLike*
| (
tei_model.labelLike
| tei_model.nameLike
| tei_model.placeLike
| tei_model.orgPart
| tei_model.milestoneLike
)*
),
(
tei_model.noteLike
| tei_model.biblLike
| tei_model.ptrLike
| linkGrp
| link
)*,
tei_model.personLike*
)
}⚓ | ||||||||
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | corpus: particDesc settingDesc textstructure: body |
| May contain | |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
done?</q>
</p>
<p>
<q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
<q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
<q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p> |
| Schematron |
<sch:rule context="tei:p">
<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText
| parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q
| parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp
| parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
</sch:report>
</sch:rule> |
| Schematron |
<sch:rule context="tei:l//tei:p">
<sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText.
</sch:assert>
</sch:rule> |
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ |
| Schema Declaration |
element p
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.declaring.attributes,
tei_att.fragmentable.attributes,
tei_att.written.attributes,
tei_macro.paraContent
}⚓ |
| <particDesc> (participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata. [16.2. Contextual Information] | |
| Module | corpus |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | core: p namesdates: listOrg listPerson org person |
| Note | May contain a prose description organized as paragraphs, or a structured list of persons and person groups, with an optional formal specification of any relationships amongst them. |
| Example | <particDesc>
<listPerson>
<person age="mid" sex="2" xml:id="P-1234">
<p>Female informant, well-educated, born in
Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently.
Socio-Economic status B2.</p>
</person>
<person sex="1" xml:id="P-4332">
<persName>
<surname>Hancock</surname>
<forename>Antony</forename>
<forename>Aloysius</forename>
<forename>St John</forename>
</persName>
<residence notAfter="1959">
<address>
<street>Railway Cuttings</street>
<settlement>East Cheam</settlement>
</address>
</residence>
<occupation>comedian</occupation>
</person>
<listRelation>
<relation mutual="#P-1234 #P-4332"
name="spouse" type="personal"/>
</listRelation>
</listPerson>
</particDesc> This example shows both a very simple person description, and a very detailed one, using some of the more specialized elements from the module for Names and Dates. |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde"
value="tei:particDesc"/>
</sch:pattern> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.personLike"/>
<elementRef key="listPerson"/>
<elementRef key="listOrg"/>
</alternate>
</alternate>
</content>
⚓ |
| Schema Declaration |
element particDesc
{
tei_att.global.attributes,
tei_att.declarable.attributes,
(
tei_model.pLike+
| ( tei_model.personLike | tei_listPerson | tei_listOrg )+
)
}⚓ |
| <person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description] | |||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||||||||||
| Contained by | corpus: particDesc namesdates: event listPerson org | ||||||||||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||||||||||
| Note | May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class. | ||||||||||||||||||||||||||||||||
| Example | <person age="adult" sex="F">
<p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
status B2.</p>
</person> | ||||||||||||||||||||||||||||||||
| Example | <person age="immortal" role="god"
sex="intersex">
<persName>Hermaphroditos</persName>
<persName xml:lang="grc">Ἑρμαφρόδιτος</persName>
</person> | ||||||||||||||||||||||||||||||||
| Example | <person role="poet" sex="M" xml:id="Ovi01">
<persName xml:lang="en">Ovid</persName>
<persName xml:lang="la">Publius Ovidius Naso</persName>
<birth when="-0044-03-20"> 20 March 43 BC <placeName>
<settlement type="city">Sulmona</settlement>
<country key="IT">Italy</country>
</placeName>
</birth>
<death notAfter="0018" notBefore="0017">17 or 18 AD <placeName>
<settlement type="city">Tomis (Constanta)</settlement>
<country key="RO">Romania</country>
</placeName>
</death>
</person> | ||||||||||||||||||||||||||||||||
| Example | The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character. <person gender="U" xml:id="ariel">
<persName>Ariel</persName>
<note>Character in <title level="m">The Tempest</title>.</note>
</person> | ||||||||||||||||||||||||||||||||
| Example | This example demonstrates the use of a <ref> element to provide more information about a person. <person age="G2" role="author" sex="F"
xml:id="W0212">
<birth when="1787"/>
<death when="1855"/>
<persName type="main">Mitford, Mary Russell (1787–1855)</persName>
<persName resp="#Nicoll">MITFORD, MARY RUSSELL</persName>
<listBibl type="lacyTitles">
<desc>Lacy's Acting Editions</desc>
<bibl>
<ref target="lacy:L1280">Foscari</ref>
</bibl>
<bibl>
<ref target="lacy:L1337">Rienzi</ref>
</bibl>
</listBibl>
<listRef type="seeAlso">
<ref target="https://www.victorianresearch.org/atcl/show_author.php?aid=1386">ATCL</ref>
<ref target="https://doi.org/10.1093/ref:odnb/18859">ODNB</ref>
<ref target="https://en.wikipedia.org/wiki/Mary_Russell_Mitford">Wikipedia</ref>
<ref target="https://digitalmitford.org">Digital Mitford</ref>
</listRef>
</person> | ||||||||||||||||||||||||||||||||
| Content model |
<content>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.personPart"/>
<classRef key="model.global"/>
<classRef key="model.ptrLike"/>
</alternate>
</alternate>
</content>
⚓ | ||||||||||||||||||||||||||||||||
| Schema Declaration |
element person
{
tei_att.global.attributes,
tei_att.editLike.attributes,
tei_att.sortable.attributes,
attribute role { list { + } }?,
attribute sex { list { + } }?,
attribute gender { list { + } }?,
attribute age { text }?,
(
tei_model.pLike+
| ( tei_model.personPart | tei_model.global | tei_model.ptrLike )*
)
}⚓ | ||||||||||||||||||||||||||||||||
| <place> (place) contains data about a geographic location. [14.3.4. Places] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | corpus: settingDesc |
| May contain | |
| Example | <place>
<country>Lithuania</country>
<country xml:lang="lt">Lietuva</country>
<place>
<settlement>Vilnius</settlement>
</place>
<place>
<settlement>Kaunas</settlement>
</place>
</place> |
| Content model |
<content>
<sequence>
<classRef key="model.headLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="0"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.labelLike"/>
<classRef key="model.placeStateLike"/>
<classRef key="model.eventLike"/>
<elementRef key="name"/>
</alternate>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.noteLike"/>
<classRef key="model.biblLike"/>
<classRef key="model.ptrLike"/>
<elementRef key="idno"/>
<elementRef key="linkGrp"/>
<elementRef key="link"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<classRef key="model.placeLike"/>
<elementRef key="listPlace"/>
</alternate>
</sequence>
</content>
⚓ |
| Schema Declaration |
element place
{
tei_att.global.attributes,
tei_att.editLike.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
(
tei_model.headLike*,
(
tei_model.pLike*
| (
tei_model.labelLike
| tei_model.placeStateLike
| tei_model.eventLike
| tei_name
)*
),
(
tei_model.noteLike
| tei_model.biblLike
| tei_model.ptrLike
| tei_idno
| linkGrp
| link
)*,
( tei_model.placeLike | tei_listPlace )*
)
}⚓ |
| <placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <placeName>
<settlement>Rochester</settlement>
<region>New York</region>
</placeName> |
| Example | <placeName>
<geogName>Arrochar Alps</geogName>
<region>Argylshire</region>
</placeName> |
| Example | <placeName>
<measure>10 miles</measure>
<offset>Northeast of</offset>
<settlement>Attica</settlement>
</placeName> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element placeName
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.editLike.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
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 |
| Attributes |
|
| Member of | |
| Contained by | header: teiHeader |
| May contain | corpus: particDesc settingDesc |
| Note | Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts. |
| Example | <profileDesc>
<langUsage>
<language ident="fr">French</language>
</langUsage>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose degree="high" type="entertain"/>
<purpose degree="medium" type="inform"/>
</textDesc>
<settingDesc>
<setting>
<name>Paris, France</name>
<time>Late 19th century</time>
</setting>
</settingDesc>
</profileDesc> |
| Content model |
<content>
<classRef key="model.profileDescPart"
maxOccurs="unbounded" minOccurs="0"/>
</content>
⚓ |
| Schema Declaration |
element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }⚓ |
| <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links] | |
| Module | core |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | Empty element |
| Note | The target and cRef attributes are mutually exclusive. |
| Example | <ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/> |
| Schematron |
<sch:rule context="tei:ptr">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
</sch:rule> |
| Content model |
<content>
<empty/>
</content>
⚓ |
| Schema Declaration |
element ptr
{
tei_att.global.attributes,
tei_att.cReferencing.attributes,
tei_att.cmc.attributes,
tei_att.declaring.attributes,
tei_att.internetMedia.attributes,
tei_att.pointing.attributes,
tei_att.typed.attributes,
empty
}⚓ |
| <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 | core: bibl header: publicationStmt |
| May contain | |
| Example | <publicationStmt>
<publisher>Oxford University Press</publisher>
<pubPlace>Oxford</pubPlace>
<date>1989</date>
</publicationStmt> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element pubPlace
{
tei_att.global.attributes,
tei_att.naming.attributes,
tei_macro.phraseSeq
}⚓ |
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Note | Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
| Example | <publicationStmt>
<publisher>C. Muquardt </publisher>
<pubPlace>Bruxelles & Leipzig</pubPlace>
<date when="1846"/>
</publicationStmt> |
| Example | <publicationStmt>
<publisher>Chadwyck Healey</publisher>
<pubPlace>Cambridge</pubPlace>
<availability>
<p>Available under licence only</p>
</availability>
<date when="1992">1992</date>
</publicationStmt> |
| Example | <publicationStmt>
<publisher>Zea Books</publisher>
<pubPlace>Lincoln, NE</pubPlace>
<date>2017</date>
<availability>
<p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
</availability>
<ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt> |
| Content model |
<content>
<alternate>
<sequence maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.publicationStmtPart.agency"/>
<classRef key="model.publicationStmtPart.detail"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element publicationStmt
{
tei_att.global.attributes,
(
(
(
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 | core: bibl header: publicationStmt |
| May contain | |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
| Example | <imprint>
<pubPlace>Oxford</pubPlace>
<publisher>Clarendon Press</publisher>
<date>1987</date>
</imprint> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element publisher
{
tei_att.global.attributes,
tei_att.canonical.attributes,
tei_macro.phraseSeq
}⚓ |
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes |
|
| Contained by | core: respStmt |
| May contain | |
| Note | The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. |
| Example | <respStmt>
<resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
<name>Edward Child</name>
</respStmt> |
| Content model |
<content>
<macroRef key="macro.phraseSeq.limited"/>
</content>
⚓ |
| Schema Declaration |
element resp
{
tei_att.global.attributes,
tei_att.canonical.attributes,
tei_att.datable.attributes,
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 |
| Attributes |
|
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Example | <respStmt>
<resp>transcribed from original ms</resp>
<persName>Claus Huitfeldt</persName>
</respStmt> |
| Example | <respStmt>
<resp>converted to XML encoding</resp>
<name>Alan Morrison</name>
</respStmt> |
| Content model |
<content>
<sequence>
<alternate>
<sequence>
<elementRef key="resp"
maxOccurs="unbounded" minOccurs="1"/>
<classRef key="model.nameLike.agent"
maxOccurs="unbounded" minOccurs="1"/>
</sequence>
<sequence>
<classRef key="model.nameLike.agent"
maxOccurs="unbounded" minOccurs="1"/>
<elementRef key="resp"
maxOccurs="unbounded" minOccurs="1"/>
</sequence>
</alternate>
<elementRef key="note"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element respStmt
{
tei_att.global.attributes,
tei_att.canonical.attributes,
(
(
( tei_resp+, tei_model.nameLike.agent+ )
| ( tei_model.nameLike.agent+, tei_resp+ )
),
tei_note*
)
}⚓ |
| <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes |
|
| Contained by | header: teiHeader |
| May contain | core: list header: change listChange |
| Note | If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list. |
| Example | <revisionDesc status="embargoed">
<change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
</revisionDesc> |
| Content model |
<content>
<alternate>
<elementRef key="list"
maxOccurs="unbounded" minOccurs="1"/>
<elementRef key="listChange"
maxOccurs="unbounded" minOccurs="1"/>
<elementRef key="change"
maxOccurs="unbounded" minOccurs="1"/>
</alternate>
</content>
⚓ |
| Schema Declaration |
element revisionDesc
{
tei_att.global.attributes,
tei_att.docStatus.attributes,
( tei_list+ | tei_listChange+ | tei_change+ )
}⚓ |
| <roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [14.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Note | A <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder. |
| Example | <persName>
<forename>William</forename>
<surname>Poulteny</surname>
<roleName>Earl of Bath</roleName>
</persName> |
| Example | <p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
including the Supreme Court justices, required by statute to be “learned in the law.”</p> |
| Example | <p>
<persName ref="#NJF">
<roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
representing the administration, asserted in rebuttal that there was nothing to disavow (...)
<persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
alike, have repeatedly said they must honor.
</p> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element roleName
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <settingDesc> (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata. [16.2. Contextual Information 2.4. The Profile Description] | |
| Module | corpus |
| Attributes |
|
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Note | May contain a prose description organized as paragraphs, or a series of <setting> elements. If used to record not settings of language interactions, but other places mentioned in the text, then <place> optionally grouped by <listPlace> inside <standOff> should be preferred. |
| Example | <settingDesc>
<p>Texts recorded in the
Canadian Parliament building in Ottawa, between April and November 1988 </p>
</settingDesc> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde"
value="tei:settingDesc"/>
</sch:pattern> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="1">
<elementRef key="setting"/>
<classRef key="model.placeLike"/>
<elementRef key="listPlace"/>
</alternate>
</alternate>
</content>
⚓ |
| Schema Declaration |
element settingDesc
{
tei_att.global.attributes,
tei_att.declarable.attributes,
( tei_model.pLike+ | ( setting | tei_model.placeLike | tei_listPlace )+ )
}⚓ |
| <sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description] | |
| Module | header |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <sourceDesc>
<bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>. </bibl>
</sourceDesc> |
| Example | <sourceDesc>
<p>Born digital: no previous source exists.</p>
</sourceDesc> |
| Schematron |
<sch:pattern is-a="declarable">
<sch:param name="tde"
value="tei:sourceDesc"/>
</sch:pattern> |
| Content model |
<content>
<alternate>
<classRef key="model.pLike"
maxOccurs="unbounded" minOccurs="1"/>
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.biblLike"/>
<classRef key="model.sourceDescPart"/>
<classRef key="model.listLike"/>
</alternate>
</alternate>
</content>
⚓ |
| Schema Declaration |
element sourceDesc
{
tei_att.global.attributes,
tei_att.declarable.attributes,
(
tei_model.pLike+
| ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
)
}⚓ |
| <surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names] | |
| Module | namesdates |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | |
| Example | <surname type="combine">St John Stevas</surname> |
| Content model |
<content>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element surname
{
tei_att.global.attributes,
tei_att.cmc.attributes,
tei_att.personal.attributes,
tei_att.typed.attributes,
tei_macro.phraseSeq
}⚓ |
| <taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes |
|
| Contained by | |
| May contain | |
| Note | Nested taxonomies are common in many fields, so the <taxonomy> element can be nested. |
| Example | <taxonomy xml:id="tax.b">
<bibl>Brown Corpus</bibl>
<category xml:id="tax.b.a">
<catDesc>Press Reportage</catDesc>
<category xml:id="tax.b.a1">
<catDesc>Daily</catDesc>
</category>
<category xml:id="tax.b.a2">
<catDesc>Sunday</catDesc>
</category>
<category xml:id="tax.b.a3">
<catDesc>National</catDesc>
</category>
<category xml:id="tax.b.a4">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="tax.b.a5">
<catDesc>Political</catDesc>
</category>
<category xml:id="tax.b.a6">
<catDesc>Sports</catDesc>
</category>
</category>
<category xml:id="tax.b.d">
<catDesc>Religion</catDesc>
<category xml:id="tax.b.d1">
<catDesc>Books</catDesc>
</category>
<category xml:id="tax.b.d2">
<catDesc>Periodicals and tracts</catDesc>
</category>
</category>
</taxonomy> |
| Example | <taxonomy>
<category xml:id="literature">
<catDesc>Literature</catDesc>
<category xml:id="poetry">
<catDesc>Poetry</catDesc>
<category xml:id="sonnet">
<catDesc>Sonnet</catDesc>
<category xml:id="shakesSonnet">
<catDesc>Shakespearean Sonnet</catDesc>
</category>
<category xml:id="petraSonnet">
<catDesc>Petrarchan Sonnet</catDesc>
</category>
</category>
<category xml:id="haiku">
<catDesc>Haiku</catDesc>
</category>
</category>
<category xml:id="drama">
<catDesc>Drama</catDesc>
</category>
</category>
<category xml:id="meter">
<catDesc>Metrical Categories</catDesc>
<category xml:id="feet">
<catDesc>Metrical Feet</catDesc>
<category xml:id="iambic">
<catDesc>Iambic</catDesc>
</category>
<category xml:id="trochaic">
<catDesc>trochaic</catDesc>
</category>
</category>
<category xml:id="feetNumber">
<catDesc>Number of feet</catDesc>
<category xml:id="pentameter">
<catDesc>>Pentameter</catDesc>
</category>
<category xml:id="tetrameter">
<catDesc>>Tetrameter</catDesc>
</category>
</category>
</category>
</taxonomy>
<!-- elsewhere in document -->
<lg ana="#shakesSonnet #iambic #pentameter">
<l>Shall I compare thee to a summer's day</l>
<!-- ... -->
</lg> |
| Content model |
<content>
<alternate>
<alternate>
<alternate maxOccurs="unbounded"
minOccurs="1">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
<sequence>
<alternate maxOccurs="unbounded"
minOccurs="1">
<classRef key="model.descLike"
maxOccurs="1" minOccurs="1"/>
<elementRef key="equiv" maxOccurs="1"
minOccurs="1"/>
<elementRef key="gloss" maxOccurs="1"
minOccurs="1"/>
</alternate>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
</sequence>
</alternate>
<sequence>
<classRef key="model.biblLike"/>
<alternate maxOccurs="unbounded"
minOccurs="0">
<elementRef key="category"/>
<elementRef key="taxonomy"/>
</alternate>
</sequence>
</alternate>
</content>
⚓ |
| Schema Declaration |
element taxonomy
{
tei_att.global.attributes,
tei_att.datcat.attributes,
(
(
( tei_category | tei_taxonomy )+
| (
( tei_model.descLike | equiv | gloss )+,
( tei_category | tei_taxonomy )*
)
)
| ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
)
}⚓ |
| <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text] | |
| Module | header |
| Attributes |
|
| Contained by | textstructure: TEI |
| May contain | header: encodingDesc fileDesc profileDesc revisionDesc |
| Note | One of the few elements unconditionally required in any TEI document. |
| Example | <teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader> |
| Content model |
<content>
<sequence>
<elementRef key="fileDesc"/>
<classRef key="model.teiHeaderPart"
maxOccurs="unbounded" minOccurs="0"/>
<elementRef key="revisionDesc"
minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element teiHeader
{
tei_att.global.attributes,
( tei_fileDesc, tei_model.teiHeaderPart*, tei_revisionDesc? )
}⚓ |
| <term> (term) 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>
<macroRef key="macro.phraseSeq"/>
</content>
⚓ |
| Schema Declaration |
element term
{
tei_att.global.attributes,
tei_att.cReferencing.attributes,
tei_att.canonical.attributes,
tei_att.cmc.attributes,
tei_att.declaring.attributes,
tei_att.pointing.attributes,
tei_att.sortable.attributes,
tei_att.typed.attributes,
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 16.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>
<sequence>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
<sequence minOccurs="0">
<elementRef key="front"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
<alternate>
<elementRef key="body"/>
<elementRef key="group"/>
</alternate>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
<sequence minOccurs="0">
<elementRef key="back"/>
<classRef key="model.global"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</sequence>
</content>
⚓ |
| Schema Declaration |
element text
{
tei_att.global.attributes,
tei_att.declaring.attributes,
tei_att.typed.attributes,
tei_att.written.attributes,
(
tei_model.global*,
( ( front, tei_model.global* )? ),
( tei_body | group ),
tei_model.global*,
( ( back, tei_model.global* )? )
)
}⚓ |
| <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | |||||||||||||||||||||||
| May contain | |||||||||||||||||||||||
| Note | The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title. | ||||||||||||||||||||||
| Example | <title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title> | ||||||||||||||||||||||
| Example | <title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title> | ||||||||||||||||||||||
| Example | <title type="full">
<title type="main">Synthèse</title>
<title type="sub">an international journal for
epistemology, methodology and history of
science</title>
</title> | ||||||||||||||||||||||
| Content model |
<content>
<macroRef key="macro.paraContent"/>
</content>
⚓ | ||||||||||||||||||||||
| Schema Declaration |
element title
{
tei_att.global.attributes,
tei_att.canonical.attributes,
tei_att.cmc.attributes,
tei_att.datable.attributes,
tei_att.typed.attribute.subtype,
attribute type { text }?,
attribute level { "a" | "m" | "j" | "s" | "u" }?,
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 |
| Attributes |
|
| Contained by | header: fileDesc |
| May contain | |
| Example | <titleStmt>
<title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
<respStmt>
<resp>compiled by</resp>
<name>P.J. Lucas</name>
</respStmt>
</titleStmt> |
| Content model |
<content>
<sequence>
<elementRef key="title"
maxOccurs="unbounded" minOccurs="1"/>
<classRef key="model.respLike"
maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</content>
⚓ |
| Schema Declaration |
element titleStmt
{
tei_att.global.attributes,
( tei_title+, tei_model.respLike* )
}⚓ |
| model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure] | |
| Module | tei |
| Used by | |
| Members | affiliation |
| 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 |
| model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | licence |
| model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | bibl listBibl |
| model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | model.imprintPart[pubPlace publisher] model.respLike[editor respStmt] availability bibl edition |
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.cmc model.divPart[model.lLike model.pLike[p]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl listBibl] model.egLike model.labelLike[desc] model.listLike[list listEvent listOrg listPerson listPlace] 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 14.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 model.divWrapper |
| model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.lLike model.pLike[p] |
| 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] model.divWrapper |
| 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 |
| 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 | term title |
| model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | classDecl |
| model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.global.edit model.global.meta model.milestoneLike model.noteLike[note] |
| model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | model.emphLike[term title] model.hiLike |
| model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | 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] model.biblLike[bibl listBibl] model.egLike model.labelLike[desc] model.listLike[list listEvent listOrg listPerson listPlace] model.oddDecl model.stageLike |
| model.labelLike groups elements used to gloss or explain other parts of a document. | |
| Module | tei |
| Used by | |
| Members | desc |
| 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[term title] model.hiLike model.pPart.data[model.addressLike[affiliation] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart[forename nameLink roleName surname] model.placeStateLike[model.placeNamePart[bloc country placeName]] eventName idno]] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike[ptr] |
| model.listLike groups list-like elements. [3.8. Lists] | |
| Module | tei |
| Used by | |
| Members | list listEvent listOrg listPerson listPlace |
| model.nameLike groups elements which name or refer to a person, place, or organization. | |
| Module | tei |
| Used by | |
| Members | model.nameLike.agent[name] model.offsetLike model.persNamePart[forename nameLink roleName surname] model.placeStateLike[model.placeNamePart[bloc country placeName]] eventName idno |
| 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 | name |
| 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 |
| model.orgPart groups elements which form part of the description of an organization. | |
| Module | tei |
| Used by | |
| Members | model.eventLike[event listEvent] listOrg listPerson listPlace |
| model.pLike groups paragraph-like elements. | |
| Module | tei |
| Used by | |
| Members | p |
| 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[affiliation] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart[forename nameLink roleName surname] model.placeStateLike[model.placeNamePart[bloc country placeName]] eventName idno] |
| 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 model.pPart.transcriptional |
| model.paraPart groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs] | |
| Module | tei |
| Used by | |
| Members | model.gLike model.global[model.global.edit model.global.meta model.milestoneLike model.noteLike[note]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl listBibl] model.egLike model.labelLike[desc] model.listLike[list listEvent listOrg listPerson listPlace] model.oddDecl model.stageLike] model.lLike model.phrase[model.graphicLike model.highlighted[model.emphLike[term title] model.hiLike] model.lPart model.pPart.data[model.addressLike[affiliation] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart[forename nameLink roleName surname] model.placeStateLike[model.placeNamePart[bloc country placeName]] eventName idno]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr] model.segLike model.specDescLike] |
| model.persNamePart groups elements which form part of a personal name. [14.2.1. Personal Names] | |
| Module | namesdates |
| Used by | |
| Members | forename nameLink roleName surname |
| model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name. | |
| Module | tei |
| Used by | |
| Members | affiliation gender |
| Note | These characteristics of an individual are typically a consequence of their own action or that of others. |
| model.personPart groups elements which form part of the description of a person. [16.2.2. The Participant Description] | |
| Module | tei |
| Used by | |
| Members | model.biblLike[bibl listBibl] model.eventLike[event listEvent] model.persStateLike[affiliation gender] idno name |
| 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[term title] model.hiLike] model.lPart model.pPart.data[model.addressLike[affiliation] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart[forename nameLink roleName surname] model.placeStateLike[model.placeNamePart[bloc country placeName]] eventName idno]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr] model.segLike model.specDescLike |
| Note | This class of elements can occur within paragraphs, list items, lines of verse, etc. |
| model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names] | |
| Module | tei |
| Used by | |
| Members | bloc country placeName |
| model.placeStateLike groups elements which describe changing states of a place. | |
| Module | tei |
| Used by | |
| Members | model.placeNamePart[bloc country placeName] |
| model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | particDesc settingDesc |
| model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References] | |
| Module | tei |
| Used by | |
| Members | ptr |
| 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 | 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] availability date idno pubPlace |
| Note | A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it. See also model.publicationStmtPart.agency. |
| model.resource 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.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 | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
<!-- elsewhere in the document -->
<noteGrp targetEnd="#A55234">
<note xml:lang="en"> Quatuor Tempora, so called dry fast days.
</note>
<note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
</note>
</noteGrp> | ||||||||||||||||||
| att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | change | ||||||||||
| 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 term | ||||||||
| Attributes |
| ||||||||
| att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | date | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | att.naming[att.personal[eventName forename name placeName roleName surname] affiliation bloc country editor event pubPlace] bibl catDesc date publisher resp respStmt term title | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| Example | In this contrived example, a canonical reference to the same organisation is provided in four different ways. <author n="1">
<name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="2">
<name ref="nzvn:427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="3">
<name ref="./named_entities.xml#o427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
<author n="4">
<name key="name-427308"
type="organisation">New Zealand Parliament, Legislative Council</name>
</author> The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available. | ||||||||||||||||||||
| Note | The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange. These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customization, for interchange. | ||||||||||||||||||||
| att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment. | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | affiliation bibl bloc country date desc forename idno list listBibl listEvent listOrg listPerson listPlace name nameLink note p placeName ptr roleName surname term title | ||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates] | |||||||
| Module | tei | ||||||
| Members | affiliation bloc change country date editor event eventName gender idno licence name placeName resp title | ||||||
| Attributes |
| ||||||
| Note | This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. | ||||||
| att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [14.4. Dates] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.datable[affiliation bloc change country date editor event eventName gender idno licence name 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 14.4. Dates] | |||||||||||||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||||||||||||
| Members | att.datable[affiliation bloc change country date editor event eventName gender idno licence name 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 14.4. Dates] | |||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||
| Members | att.datable[affiliation bloc change country date editor event eventName gender idno licence name 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. [10.5.2. Lexical View 19.3. Other Atomic Feature Values] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | category taxonomy | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Example | The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.<fs>
<f 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 [[undefined FS]]. <fs>
<f fVal="#commonNoun" name="POS"/>
<!-- ... -->
</fs> The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories. <fvLib n="POS values">
<symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
value="NN" xml:id="commonNoun"/>
<symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
value="NP" xml:id="properNoun"/>
<!-- ... -->
</fvLib> Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value. | ||||||||||||||||||
| Example | In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above. <gramGrp>
<pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos>
</gramGrp> Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>: <tagsDecl partial="true">
<!-- ... -->
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="pos"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>
<tagUsage gi="case"
targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage>
<!-- ... -->
</namespace>
</tagsDecl> Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below: <listPrefixDef>
<prefixDef ident="ccr" matchPattern="pos"
replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
<prefixDef ident="ccr" matchPattern="adj"
replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>
</listPrefixDef>
<!-- ... -->
<entry>
<!--...-->
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos datcat="ccr:pos"
valueDatcat="ccr:adj">adj</pos>
</gramGrp>
<!--...-->
</entry> This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>. | ||||||||||||||||||
| Example | The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology. <encodingDesc>
<!-- ... -->
<classDecl>
<!-- ... -->
<taxonomy datcat="https://universaldependencies.org/u/dep/index.html"
xml:id="UD-SYN">
<desc>
<term>UD syntactic relations</term>
</desc>
<category valueDatcat="https://universaldependencies.org/u/dep/acl.html"
xml:id="acl">
<catDesc>
<term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>
</category>
<category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"
xml:id="acl_relcl">
<catDesc>
<term>acl:relcl</term>: relative clause modifier</catDesc>
</category>
<category valueDatcat="https://universaldependencies.org/u/dep/advcl.html"
xml:id="advcl">
<catDesc>
<term>advcl</term>: Adverbial clause modifier</catDesc>
</category>
<!-- ... -->
</taxonomy>
</classDecl>
</encodingDesc> The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly. | ||||||||||||||||||
| Example | The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object. <fDecl name="POS"
targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
<fDescr>part of speech (morphosyntactic category)</fDescr>
<vRange>
<vAlt>
<symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
value="NN"/>
<symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
value="NP"/>
<!-- ... -->
</vAlt>
</vRange>
</fDecl> Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element. | ||||||||||||||||||
| Example | The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>
<classDecl>
<taxonomy xml:id="domains">
<!--...-->
<category xml:id="domain.medical_and_health_sciences">
<catDesc xml:lang="en">Medical and Health Sciences</catDesc>
<catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>
<category valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"
xml:id="domain.medical_and_health_sciences.medicine">
<catDesc xml:lang="en">
<term>Medicine</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
<catDesc xml:lang="pt">
<term>Medicina</term>
<gloss>
<!--...-->
</gloss>
</catDesc>
</category>
</category>
<!--...-->
</taxonomy>
</classDecl>
</encodingDesc>
<!--
inside an <entry> element: -->
<usg type="domain"
valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg> In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH). | ||||||||||||||||||
| Note | The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container. A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute. In a TEI XML example of two equivalent serializations expressing the name-value pair The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech). The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects. Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example. Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices. | ||||||||||||||||||
| att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [16.3. Associating Contextual Information with a Text] | |||||||||
| Module | tei | ||||||||
| Members | availability bibl listBibl listEvent listOrg listPerson listPlace particDesc settingDesc sourceDesc | ||||||||
| Attributes |
| ||||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true. | ||||||||
| att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [16.3. Associating Contextual Information with a Text] | |||||||
| Module | tei | ||||||
| Members | body p ptr term text | ||||||
| Attributes |
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. | ||||||
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | date | ||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||
| att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
| Module | tei | ||||||||
| Members | bibl change revisionDesc | ||||||||
| 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 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | affiliation date event eventName gender name org person place placeName | ||||||||||||||||
| 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 | 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 affiliation availability bibl bloc body catDesc category change classDecl country date desc edition editionStmt editor encodingDesc event eventName fileDesc forename gender idno item licence list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org p particDesc person place placeName profileDesc ptr pubPlace publicationStmt publisher resp respStmt revisionDesc roleName settingDesc sourceDesc surname taxonomy teiHeader term text title titleStmt | ||||||||||||||||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||||||||||||||||
| att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Members | att.global[TEI affiliation availability bibl bloc body catDesc category change classDecl country date desc edition editionStmt editor encodingDesc event eventName fileDesc forename gender idno item licence list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org p particDesc person place placeName profileDesc ptr pubPlace publicationStmt publisher resp respStmt revisionDesc roleName settingDesc sourceDesc surname taxonomy teiHeader term text title titleStmt] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 affiliation availability bibl bloc body catDesc category change classDecl country date desc edition editionStmt editor encodingDesc event eventName fileDesc forename gender idno item licence list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org p particDesc person place placeName profileDesc ptr pubPlace publicationStmt publisher resp respStmt revisionDesc roleName settingDesc sourceDesc surname taxonomy teiHeader term text title titleStmt] | ||||||||||||||||||||||||||||||
| 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 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.global[TEI affiliation availability bibl bloc body catDesc category change classDecl country date desc edition editionStmt editor encodingDesc event eventName fileDesc forename gender idno item licence list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org p particDesc person place placeName profileDesc ptr pubPlace publicationStmt publisher resp respStmt revisionDesc roleName settingDesc sourceDesc surname taxonomy teiHeader term text title titleStmt] | ||||||||||||||
| 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 affiliation availability bibl bloc body catDesc category change classDecl country date desc edition editionStmt editor encodingDesc event eventName fileDesc forename gender idno item licence list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org p particDesc person place placeName profileDesc ptr pubPlace publicationStmt publisher resp respStmt revisionDesc roleName settingDesc sourceDesc surname taxonomy teiHeader term text title titleStmt] | ||||||||||
| Attributes |
| ||||||||||
| Example | <p>
<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
term.</quote>
<!-- ... -->
</p> | ||||||||||
| Example | <p>
<!-- ... -->
<quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
less we seem to know.</quote>
<!-- ... -->
</p>
<!-- ... -->
<bibl xml:id="chicago_15_ed">
<title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.
</bibl> | ||||||||||
| Example | <elementRef key="p" source="tei:2.0.1"/> Include in the schema an element named <p> available from the TEI P5 2.0.1 release. | ||||||||||
| Example | <schemaSpec ident="myODD"
source="mycompiledODD.xml">
<!-- further declarations specifying the components required -->
</schemaSpec> Create a schema using components taken from the file mycompiledODD.xml. | ||||||||||
| att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy. | |||||||
| Module | tei | ||||||
| Members | ptr | ||||||
| Attributes |
| ||||||
| Example | In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8. <ref mimeType="application/tei+xml; charset=UTF-8"
target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/> | ||||||
| Note | This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list. | ||||||
| att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 14.3.4.3. States, Traits, and Events] | |||||||
| Module | tei | ||||||
| Members | event | ||||||
| Attributes |
| ||||||
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.personal[eventName forename name placeName roleName surname] affiliation bloc country editor event pubPlace | ||||||||||||||
| Attributes |
| ||||||||||||||
| att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | eventName forename name placeName roleName surname | ||||||||||||||
| 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 12.3.1.4. Additions and Deletions] | |||||||||||||
| Module | tei | ||||||||||||
| Members | note | ||||||||||||
| 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 | licence note ptr term | ||||||||||||||||||||||||||||||
| Attributes |
| ||||||||||||||||||||||||||||||
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | att.dimensions[date] | ||||||||||||||||||||||||||||||
| 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.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [10.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei | ||||||||||
| Members | bibl event idno item list listBibl listChange listEvent listOrg listPerson listPlace org person place term | ||||||||||
| Attributes |
| ||||||||||
| att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | TEI affiliation bibl bloc change country date desc event eventName forename gender idno list listBibl listChange listEvent listOrg listPerson listPlace name nameLink note org place placeName ptr roleName surname term text title | ||||||||||||||||||
| Attributes |
| ||||||||||||||||||
| Schematron |
<sch:rule context="tei:*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
</sch:rule> | ||||||||||||||||||
| Note | When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
| att.written 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 | note p text | ||||||
| Attributes |
| ||||||
| macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.inter"/>
</alternate>
</content>
⚓ |
| Declaration | tei_macro.limitedContent = ( text | tei_model.limitedPhrase | tei_model.inter )*⚓ |
| macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.paraPart"/>
</alternate>
</content>
⚓ |
| Declaration | tei_macro.paraContent = ( text | tei_model.paraPart )*⚓ |
| macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.attributable"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration |
tei_macro.phraseSeq =
(
text
| 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>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.limitedPhrase"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration | tei_macro.phraseSeq.limited = ( text | tei_model.limitedPhrase | tei_model.global )*⚓ |
| macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate maxOccurs="unbounded"
minOccurs="0">
<textNode/>
<classRef key="model.gLike"/>
<classRef key="model.phrase"/>
<classRef key="model.inter"/>
<classRef key="model.divPart"/>
<classRef key="model.global"/>
</alternate>
</content>
⚓ |
| Declaration |
tei_macro.specialPara =
(
text
| tei_model.gLike
| tei_model.phrase
| tei_model.inter
| tei_model.divPart
| tei_model.global
)*⚓ |
| teidata.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<valList type="closed">
<valItem ident="high"/>
<valItem ident="medium"/>
<valItem ident="low"/>
<valItem ident="unknown"/>
</valList>
</content>
⚓ |
| Declaration | 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>
<dataRef name="nonNegativeInteger"/>
</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>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
⚓ |
| Declaration |
tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }⚓ |
| Example | <time dur-iso="PT0,75H">three-quarters of an hour</time> |
| Example | <date dur-iso="P1,5D">a day and a half</date> |
| Example | <date dur-iso="P14D">a fortnight</date> |
| Example | <time dur-iso="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either 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>
<dataRef name="duration"/>
</content>
⚓ |
| Declaration | tei_teidata.duration.w3c = xsd:duration⚓ |
| Example | <time dur="PT45M">forty-five minutes</time> |
| Example | <date dur="P1DT12H">a day and a half</date> |
| Example | <date dur="P7D">a week</date> |
| Example | <time dur="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the 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.gender teidata.sexElement:
|
| Content model |
<content>
<dataRef key="teidata.word"/>
</content>
⚓ |
| Declaration | tei_teidata.enumerated = teidata.word⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
| teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | tei_teidata.gender = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 10.3.1. Information on Written and Spoken Forms). |
| teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="language"/>
<valList>
<valItem ident=""/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | 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>
<dataRef name="Name"/>
</content>
⚓ |
| Declaration | tei_teidata.name = xsd:Name⚓ |
| Note | Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
| teidata.numeric defines the range of attribute values used for numeric values. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="double"/>
<dataRef name="token"
restriction="(\-?[\d]+/\-?[\d]+)"/>
<dataRef name="decimal"/>
</alternate>
</content>
⚓ |
| Declaration |
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>
<dataRef name="token"
restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
⚓ |
| Declaration |
tei_teidata.outputMeasurement =
token
{
pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
}⚓ |
| Example | <figure>
<head>The TEI Logo</head>
<figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
background.</figDesc>
<graphic height="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>
<dataRef name="token"/>
</content>
⚓ |
| Declaration | tei_teidata.pattern = token⚓ |
| Note | A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern WikipediaH(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema. |
| teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
| Module | tei |
| Used by | Element:
|
| Content model |
<content>
<dataRef name="anyURI" restriction="\S+"/>
</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.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef key="teidata.probability"/>
<dataRef key="teidata.certainty"/>
</alternate>
</content>
⚓ |
| Declaration | tei_teidata.probCert = teidata.probability | teidata.certainty⚓ |
| teidata.probability defines the range of attribute values expressing a probability. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="double">
<dataFacet name="minInclusive" value="0"/>
<dataFacet name="maxInclusive" value="1"/>
</dataRef>
</content>
⚓ |
| Declaration | 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.sex defines the range of attribute values used to identify the sex of an organism. | |
| Module | tei |
| Used by | Element:
|
| Content model |
<content>
<dataRef key="teidata.enumerated"/>
</content>
⚓ |
| Declaration | tei_teidata.sex = teidata.enumerated⚓ |
| Note | Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard. |
| teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
<dataRef name="token"
restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</alternate>
</content>
⚓ |
| Declaration |
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>
<alternate>
<dataRef name="date"/>
<dataRef name="gYear"/>
<dataRef name="gMonth"/>
<dataRef name="gDay"/>
<dataRef name="gYearMonth"/>
<dataRef name="gMonthDay"/>
<dataRef name="time"/>
<dataRef name="dateTime"/>
</alternate>
</content>
⚓ |
| Declaration | tei_teidata.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime⚓ |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
| teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="string"/>
</content>
⚓ |
| Declaration | 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 | Element:
|
| Content model |
<content>
<dataRef name="boolean"/>
</content>
⚓ |
| Declaration | tei_teidata.truthValue = xsd:boolean⚓ |
| Note | The possible values of this datatype are 1 or true, or 0 or false. This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue. |
| teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei |
| Used by | Element:
|
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
⚓ |
| Declaration |
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }⚓ |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
| teidata.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<dataRef name="token"
restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
⚓ |
| Declaration |
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>
<dataRef name="token"
restriction="[^\p{C}\p{Z}]+"/>
</content>
⚓ |
| Declaration |
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }⚓ |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
| teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<alternate>
<dataRef name="boolean"/>
<valList>
<valItem ident="unknown"/>
<valItem ident="inapplicable"/>
</valList>
</alternate>
</content>
⚓ |
| Declaration | tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )⚓ |
| Note | In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue. |
| teidata.xpath defines attribute values which contain an XPath expression. | |
| Module | tei |
| Used by | |
| Content model |
<content>
<textNode/>
</content>
⚓ |
| Declaration | tei_teidata.xpath = text⚓ |
| Note | Any XPath expression using the syntax defined in 6.2.. When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP. |