Drama Corpora | dracor.org
TEI Customization and Documentation
2025
1.0.0-rc.1

Table of contents

TEI Customization for Drama Corpora (dracor.org)

1. Introduction

We are building drama corpora with files encoded following the guidelines of the Text Encoding Initiative (TEI P5), especially the module Performance Texts. The encoded plays are suitable for the field of digital drama analysis, which manifests itself in a growing list of research done based on DraCor corpora and is especially facilitated by also hosting the corpora on GitHub with an open license that allows for extensive re-use.

The encoded texts are the basis for DraCor (Drama Corpora Platform). It is a multi-component system which realizes the concept of “Programmable Corpora” (Fischer et al. 2019), understood as corpora that expose an open, transparently documented and (at least partly) research-driven API to make texts machine-actionable. (cf. Börner and Trilcke 2023). The documentation of the DraCor API can be accessed at https://dracor.org/doc/api. For additional information on the API and a documentation of the attributes returned in the JSON responses see section API.

This customization restricts the use of TEI Guidelines to allow a smooth integration into the DraCor system. It is originally based on the TEI ODD for Drama. Using the TEI Stylesheets a RelaxNG schema (https://dracor.org/schema.rng) with embedded Schematron rules can be generated, that can be used to validate the encoding of the DraCor files.

Although the corpora in DraCor have different sources, they are largely homogeneous both structurally and in terms of metadata. This homogeneity makes it possible, for example, to perform comparative research on the corpora or to perform processing operations (such as extracting information or counting) in a comparable way on the corpora. However, homogeneity is something that has to be created first, because even if corpora are available in the target format TEI, they often differ in the way TEI is applied.

The literary texts in the DraCor corpora have a basic structural markup and are ready for further analysis by various methods of Computational Literary Studies (CLS). They have been additionally enriched with a research-driven markup for the application of a specific method, the network analysis of literary texts (Trilcke 2013). Therefore the encoding is tailored to allow for the extraction of co-presence networks relying on structural segmentation of a given play into acts and scenes and having uniquely identifiable speaking and acting characters (cf. Encoding for Network Analysis).

2. Encoding Guidelines

This section describes how to encode a play and make it DraCor-ready. It is still work in progress.

2.1. File Formats and Copyright Issues

Depending on the source’s original format, you may follow one of these pipelines:

  • If your text is already encoded in XML, it may be possible to write a XSLT or a Python script to adapt it to the DraCor format.
  • If that is not possible, or your text is available in some other digital format (e.g. .txt, .csv, .docx), you’ll have to apply the markup yourself. If you’re working with OCR outputs, please remember we try to remain as close to the source as possible (i.e. reproducing the text as it is on the physical copy, including misprints).

It is possible to convert a .txt file encoded in UTF-8 to a basic DraCor format through the experimental EzDrama conversion tool (Python script).

Please note that DraCor considers for publication only works which are either in the public domain (CC BY 0) or released under an open Creative Commons Attribution Licence (e.g. CC BY 3.0). According to German law, works become public domain after 70 years from their author’s death. Even though it is possible to build copyright-protected corpora, they could be run only on a local DraCor instance built through Docker. Fort hints on how to do this see the CLS INFRA Report On Versioning Living and Programmable Corpora (Boerner/Trilcke 2024).

2.2. Basic Structure

The basic structure of a DraCor file requires a <teiHeader>, containing metadata on the play, and a <text> with the actual text. Between header and text there is a <standOff> element with some additional pieces of information. The structure of your final XML file should therefore look like this:
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- contains Metadata -->  </teiHeader>  <standOff> <!-- contains additional infos -->  </standOff>  <text> <!-- The 'actual' Text: mandatory, if there is no <facsimile> and/or <sourceDoc> -->  </text> </TEI>

You can apply markup to your plays simply by putting tags, consisting of the name of the tag in angle brackets around parts of the text. To do so, open your XML file with an XML editor. There are several options for efficient and non-cumbersome manual work with these files, but we recommend the Oxygen XML Editor, which has rich functionality and an author mode which minimizes the risk of breaking the markup structure. Oxygen is also a TEI-aware editor. You can get a 30-day trial licence here. A good free-source alternative is Notepad++ (which now supports a user-defined EzDrama language!).

If you’re using Oxygen Editor, you can download and try the experimental DraCor Oxygen Framework. It will help you by checking many kinds of inconsistencies in the markup and validating your file against the DraCor schema.

2.3. Metadata in the <teiHeader>

The header is composed of several sections: <fileDesc>, <profileDesc> and <revisionDesc>.

<teiHeader>  <fileDesc>   <titleStmt> <!-- ... -->   </titleStmt>   <publicationStmt> <!-- ... -->   </publicationStmt>   <sourceDesc> <!-- ... -->   </sourceDesc>  </fileDesc>  <profileDesc> <!-- ... -->  </profileDesc>  <revisionDesc> <!-- ... -->  </revisionDesc> </teiHeader>

2.3.1. Bibliographic Metadata of a Play

The basic metadata on the digital file are included in the <fileDesc>. It contains a title statement (<titleStmt>), a publication statement (<publicationStmt>) and a description of the digital and original sources (<sourceDesc>).

<fileDesc>  <titleStmt> <!-- ... -->  </titleStmt>  <publicationStmt> <!-- ... -->  </publicationStmt>  <sourceDesc> <!-- ... -->  </sourceDesc> </fileDesc>

In the following sections, we will discuss those parts in which important information is encoded. However, we do not strictly follow the hierarchy of the elements in the teiHeader. It is therefore important to observe the structure given in the example above.

2.3.1.1. Title

The title is encoded using the element <title> in <titleStmt>. It can be further classified using the attribute type as main and subtitle:
<title type="main">Des Meeres und der Liebe Wellen</title> <title type="sub">Trauerspiel in fünf Aufzügen</title>

2.3.1.2. Author(s)

An author of a play is encoded using the element <author> in <titleStmt>. If there are multiple authors of a play add and element <author> for each of them.

<author>  <persName>   <forename>Gotthold</forename>   <forename>Ephraim</forename>   <surname>Lessing</surname>  </persName>  <idno type="wikidata">Q34628</idno>  <idno type="pnd">118572121</idno> </author>
2.3.1.2.1. Author Name(s)

The author's name is enclosed in the element <persName> and can be additionally structured using the designated elements <forename> and <surname>.

The element <nameLink> can be used to mark-up connecting phrases in a name, like such as ‘van der’ or ‘of’.
<persName>  <forename>Achim</forename>  <nameLink>von</nameLink>  <surname>Arnim</surname> </persName>

Other special elements for marking up name constituents are available in the TEI Guidelines but bear in mind that not everything that is available is actually supported by the DraCor API.

In some cases it makes sense to include only the literal string value of the name as <persName>.

It is possible to include multiple names for an author, e.g. a pen name or a (English) transliteration of an author's name in a corpus with non-latin script.

There are some special types of ‘names’ that are supported and marked by using the attribute type.

For additional examples on encoding names see the documentation of the element <persName>. There are also some GitHub issues in which the encoding of names was discussed, e.g. Refactor author information. If you encounter issues with how names are displayed on DraCor or have questions regarding edge cases please open an issue on GitHub.

2.3.1.2.2. IDs in External Reference Resources

Authors should be linked to external reference resources, e.g. Wikidata. This for example allows to fetch additional data about a person not explicitly included in the TEI file and display it on the front-end: If a Wikidata Identifier (QID) is provided information about the date and place of birth and death of an author and a picture will be displayed.

To record an external ID use the element <idno> and provide the type of identifier in the attribute type:

<idno type="wikidata">Q692</idno>

The URI of the author in the example above can be constructed by prepending the base-URI of Wikidata http://www.wikidata.org/entity/ to the QID resulting in http://www.wikidata.org/entity/Q692.

There are other types of eternal identifiers available. Please refer to the documentation of the element <idno> for supported type values and additional examples.

2.3.1.2.3. Additional Contributors

There can be other roles in which a person contributes to the creation of a play. In DraCor we currently do not support providing explicit information on the role of an individual creator, but add them as authors in <author>. See the example of the German Shakespeare Corpus below:

<titleStmt>  <title>Hamlet. Prinz von Dänemark</title>  <author>   <persName>    <forename>William</forename>    <surname>Shakespeare</surname>   </persName> <!-- ... -->  </author>  <author>   <persName>    <forename>August</forename>    <forename>Wilhelm</forename>    <surname>Schlegel</surname>   </persName> <!-- ... -->  </author>  <respStmt>   <resp>This digital edition was prepared by</resp>   <name ref="https://orcid.org/0000-0003-2419-6629">Frank Fischer</name>  </respStmt> </titleStmt>

This might change in the future. See the GitHub issue on Contributor roles.

2.3.2. Sources

The sources of a play are included in the <sourceDesc> in the <fileDesc>. In most cases files in DraCor are not create from scratch, i.e. there is no scanning and OCR or any manual transcription of a printed source involved. Instead we use already available digital files that are digitizations of a certain printed edition. This fact is expressed with two nested elements <bibl> that are classified by their attributes type: the original print publication (originalSource) is described inside the bibliographic record of the digital surogate (digitalSource).

<sourceDesc>  <bibl type="digitalSource"> <!-- .... -->   <bibl type="originalSource"> <!-- ... -->   </bibl>  </bibl> </sourceDesc>

2.3.2.1. Digital Source

The information on ‘digital source’ should include the name of the source, e.g. the ‘Project Gutenberg’ and an identifier of the document within the source collection as <idno>. The identifier can be a URL from which the document can be retrieved. In the best case there is some persistent identifier that unambiguously identifies the digital document used as the source for the DraCor file.

The information on the licence under which the digital source file is distributed should be included in <availability>.

<bibl type="digitalSource">  <name>TextGrid Repository</name>  <idno type="URL">http://www.textgridrep.org/textgrid:11f78.0</idno>  <availability>   <licence>    <ab>CC-BY-3.0</ab>    <ref target="http://creativecommons.org/licenses/by/3.0/de/legalcode">Lizenzvertrag</ref>   </licence>  </availability> </bibl>

For an exemplary analysis of sources of a corpus see chapter An Algorithmic Archaeology of a Living Corpus: GerDraCor as a Dynamic Epistemic Object in the report "On Versioning Living and Programmable Corpora" (Boerner/Trilcke 2024)

2.3.2.2. Original Source

The original print publication that was the basis of the digital source is included as a bibliographic reference in an element <bibl>.

It is possible to use designated elements to explicitly mark-up the parts of the bibliographic reference, as in the following example:
<bibl type="originalSource">  <author>Jakob Ayrer</author>: <title level="a">Tragedia    Thesei, des zehenten Königs zu Athen, von den vierzehen    Tributkindern, mit 41 Personen, hat 8 Actus</title>. In: <title level="s">Ayrers Dramen</title>. Herausgegeben von <editor>Adelbert von Keller</editor>. <biblScope unit="volume">Zweiter</biblScope> Band. <pubPlace>Stuttgart</pubPlace>: <publisher>Litterarischer    Verein</publisher>  <date>1865</date>, S. <biblScope unit="pagefrom="1207"   to="1303">1207–1303</biblScope>. </bibl>

As an alternative the bibliographic reference can only consist of an element <title> (see also GitHub issue on the single element <title> in the unstructured <bibl> element).

<bibl type="originalSource">  <title>Goethes Werke. Hamburger Ausgabe in 14 Bänden.    Textkritisch durchgesehen und mit Anmerkungen versehen von    Erich Trunz, Hamburg: Christian Wegener, 1948 ff.    [Seitenkonkordanz zu einer Mischauflage aus den Jahren 1959    und 1960.]</title> </bibl>

2.3.3. Analytic or Research-driven Data in the <teiHeader>

There is analytic or research-driven data in the <profileDesc> of the <teiHeader>: Information on the characters in the <particDesc> and the (sub-)genre of a play in <textClass>.

<profileDesc>  <particDesc> <!-- ... -->  </particDesc>  <textClass> <!-- ... -->  </textClass> </profileDesc>

2.3.3.1. Characters

Information on the characters of a play is included in a <listPerson> in the <particDesc>. Fill this section after annotating the text proper of the play (see also section on Encoding for Network Analysis).

The <listPerson> includes the characters speaking in the text proper as elements <person> or <personGrp>. Each element is assigned an unique identifier as the value of the attribute xml:id. Additional information on a character can be recorded in attributes, e.g. the attributes sex and gender allow to encode the sex and/or gender of a character.

Individuals are to be marked with <person>, groups (e.g. “Chorus”, “Soldiers”) with <personGrp>.

The following example shows the encoding of a single female character called "Eleonora":

<person xml:id="eleonorasex="FEMALE">  <persName>Eleonora</persName> </person>
A group of three supposedly male devils ("Drei Teufel") is encoded as follows:
<personGrp xml:id="drei_teufelsex="MALE">  <name>Drei Teufel</name> </personGrp>
2.3.3.1.1. Character Name

Use <persName> to provide the character name. In the case of a group of characters use the element <name> instead.

The values will appear in the network rendering in the frontend as the labels of the nodes. For the sake of visualisation, try to stick to name or name+surname, avoiding too much extra information which will clutter the network. For example: “Henry”, “King Henry” or “Henry VII Tudor” are fine, “Henry, brother to the King of England” is not.

2.3.3.1.2. Character Identifier

Each item must have a unique identifier in the attribute xml:id. As a general rule use letters of the latin alphabet and numbers for these IDs; don't use any special characters apart from dash "-" and underscore "_". If your play is written in a non-latin script use a transliteration of the character name as the identifier.

On a more technical level: The values of the attribute xml:id need to be so-called ‘Nmtokens’ which cannot contain space characters among others (see full spec at https://www.w3.org/TR/REC-xml/#NT-Name). Although they can consist of characters from various scripts, in the case of DraCor we follow the convention to use only ASCII characters. The reason being that IDs may be used to construct URLs and anything beyond the ASCII range would have to be URI encoded which would make the URLs less readable (cf. this GitHub issue.)

For characters defined by numerals (“First Soldier, Second Soldier”), please include the values of the attribute xml:id as follows:xml:id="soldier_1".

2.3.3.1.3. Sex and Gender of Characters

The DraCor schema supports the attribution of both biological sex and gender roles to the characters of a play using the sex and gender attributes respectively.

For the sex attribute the DraCor API expects the values FEMALE, MALE or UNKNOWN. The encoding of the sex of a character should be guided by the following rules:

  • Please use the sex attribute only for characters which unequivocally appear as of a certain sex in the text. If they don’t have a proper name, but are defined by their profession, consider the play’s context (e.g. “soldier” will be surely MALE in a Renaissance play).

  • The same applies to groups (“soldiers”, “weavers”). If the sex is uncertain or no hints are provided, mark them as UNKNOWN (“nobles”, ”citizens”, “servants”).

  • Abstract entities (“Time”, “Fame”, “Death” etc.) should be marked as UNKNOWN. If they are clearly gendered in the text you may consider using an appropriate gender attribute.

For the gender attribute the DraCor API currently does not expect any particular value. It is up to corpus maintainers to use a consistent scheme, possibly documented in an <encodingDesc>.

For more background on sex and gender in the TEI see Beshero-Bondar et al. (2024). For its history in DraCor see the GitHub issue #46.

2.3.3.1.4. Relations between Characters
DraCor supports the encoding of relationships between characters using the <listPerson> element inside the <particDesc>.
<particDesc>  <listPerson>   <person xml:id="character1">    <persName>First Character</persName>   </person> <!-- ... -->   <personGrp xml:id="group99">    <name>A Group of Characters</name>   </personGrp> <!-- after the last character item include: -->   <listRelation> <!-- Character relations go here -->   </listRelation>  </listPerson> </particDesc>
Relations among characters are encoded using <relation> elements in a <listRelation>. Here is an example from Emilia Galotti:
<listRelation type="personal">  <relation name="parent_of"   active="#odoardo #claudiapassive="#emilia"/>  <relation name="associated_with"   active="#marinellipassive="#der_prinz"/>  <relation name="associated_with"   active="#camillo_rotapassive="#der_prinz"/> </listRelation>

It is strongly recommended to include only such relations that are ground on textual evidence, e.g. notes on the relation of characters in the dramatis personae included in the text proper as <castList>. In the <castList> of the play used as an example above the characters "Odoardo" and "Claudia" are marked as a group with a curly bracket and it is noted that they are the parents of the character "Emilia" ("Eltern der Emilia") (in the example see element <roleDesc>):

<castList>  <castItem>   <role>Emilia Galotti.</role>  </castItem>  <castGroup rend="braced">   <castItem>    <role>Odoardo,</role>   </castItem>   <castItem>    <role>Claudia Galotti,</role>   </castItem>   <roleDesc>Eltern der Emilia.</roleDesc>  </castGroup> <!-- ... --> </castList>
This textual finding results in the following encoding of the character relation ‘parent_of’:
<relation name="parent_of"  active="#odoardo #claudiapassive="#emilia"/>

In this case being a parent of someone is a directed relationship. Therefore the <relation> with the value parent_of of the attribute name has two additional attributes that denote the source (active) and the target (passive) of the relation. The values of these attributes are pointers (hence starting with '#') which must refer to a <person> element inside the <particDesc> that has an xml:id with a corresponding value.

Which relations to encode and how to name them in the name attribute is up to the corpus maintainers. We recommend to follow a consistent classification that is documented in the corpus README. As an example, the German Drama Corpus adopted the method of identifying character relationships developed by Wiedmer et al. (2020).

2.3.3.1.5. Characters as Realizations of Concepts

If a character in a play is an actualization of a character archetype, e.g. a mythologic figure or a historic person it is possible to provide a link to the entity on Wikidata by including the full URI in the attribute ana.

<person xml:id="medeasex="FEMALE"  ana="http://www.wikidata.org/entity/Q174278">  <persName>Medea</persName> </person>
<person xml:id="napoleonsex="MALE"  ana="http://www.wikidata.org/entity/Q517">  <persName>Napoleon</persName> </person>

2.3.3.2. Genre

Within <textClass> in the <profileDesc> the genre of the drama can be specified.

<textClass>  <keywords>   <term type="genreTitle">Tragedy</term>  </keywords>  <classCode scheme="http://www.wikidata.org/entity/">Q80930</classCode> </textClass>

The content of the element <term> in the section <keywords> is considered the human-readable label for the classification contained in <classCode>. The value should be the QID of the respective concept on Wikidata. The following values are supported by the API (See also Source Code):

Genre information should only be supplied if there are some indicators that a certain genre is applicable, e.g. a genre term in the subtitle or some other text on the title page in the source. See also the discussion in this issue on GitHub.

2.3.4. <revisionDesc>

Lists revisions and revisers of the file. Update it after each editing.

2.4. Encoding additional metadata in the <standOff> element

The <standOff> element usually includes dates (first written, first printed edition, premiere).

2.4.1. Wikidata QID of a Play

To link a play to its corresponding entry in Wikidata DraCor uses the <listRelation> element inside <standOff>. For this purpose it must have exactly one <relation> child element with the following attributes:

  • name: the value must be wikidata
  • active: The DraCor URI identifying the play. It starts with "https://dracor.org/entity/" followed by the xml:id of the play.
  • passive: The Wikidata entity URI, which start with "http://www.wikidata.org/entity/" followed by the QID.
<standOff>  <listRelation>   <relation name="wikidata"    active="https://dracor.org/entity/ger000171"    passive="http://www.wikidata.org/entity/Q42187688"/>  </listRelation> <!-- ... --> </standOff>

2.5. Encoding the text (<text>)

The text of the play is usually composed of some paratextual elements (title page, dedication, preface, dramatis personae etc.) and of the body of the text. Enclose the first with the <front> tag and the second with the <body> tag.

Most examples (with some adjustments) are taken from Mary Pix' drama The Spanish Wives (ep000676).

2.5.1. Paratexts (<front>)

Paratexts may be encoded with successive layers of complexity. The general rule is to enclose every section in a <div> with an attribute type. Prose text should be enclosed in paragraphs with <p>, lines of verse with <l>. In-text titles of sections may be marked with <head>.

Some examples:
<front>  <div type="title_page">   <p> THE Spanish Wives. A FARCE, As it was Acted by His      MAJESTY's Servants, AT THE THEATRE in Dorset-Garden.   </p>   <p> LONDON: Printed for R. Wellington, at the Sign of the Lute      in St. Paul's Church yard, 1696.   </p>  </div>  <div type="prologue">   <head>PROLOGUE, Spoken by Mr. Penkethman, in a Press-master's Habit.</head>   <l>WHat Chear, my Lads? Igad, I'm come to say,</l>   <l>I'll press to Sea all those who Damn this Play:</l>    [...]  </div> </front>

Dramatis personae can be encoded using the element <castList>.

2.6. <text>

Mark the main elements in the play’s body <body> as follows:

2.6.1. Segments (acts, scenes, etc.)

Use the element <div> to encode segments of a dramatic text. The type of the segment ("act", "scene") should be given in the attribute type:
<div type="act">  <head>ACT I</head>  <div type="scene">   <head>SCENE I.</head> <!-- ... -->  </div> </div>

2.6.2. Stage Directions (non-diegetic elements)

Use the element <stage> to mark stage directions:
<stage>Enter the Governour of Barcellona, and the Marquess of Moncada.</stage> <stage>(taking the Stick, and putting on his Spectacles to view it)</stage>
Stage directions could be nested into speech acts!
<sp who="#ep000676-camillus">  <speaker>Cam. </speaker>  <p> Tell him, I am,-- and long to kiss his Hands.-- I like that    Gentleman, he appears brave <stage>Exit Servus.</stage> And    bold-- shou'd our Designs grow desperate: I dare believe he    would not scruple his Assistance.  </p> </sp>

2.6.3. Speakers and Speech Acts

  • Mark the speech act with enclosing it with the element <sp>.

  • Indicate which character listed in the <particDesc> is speaking by including a reference to the character's xml:id prefixed with a hash (#) in the who attribute of the <sp> element: who="#id-of-the-speaker". Always use the same who-tag, even if the in-text name of the speaker is abbreviated or there are some aliases.

  • Enclose the in-text name of the speaker with the element <speaker>.

  • Again, verse lines should be marked with <l>. Prose text should be marked with the paragraph element <p>.

<sp who="#eleonora">  <speaker>Elen.</speaker>  <p> Now my Desires are so near fulfilling, I begin to fear 'em--    yet I know Camillus is Honourable.  </p> </sp>
<sp who="#camillus">  <speaker>Cam.</speaker>  <l>Greatness was the Attendant of my Birth; </l>  <l>But Love gives me Heaven upon Earth. </l>  <l>These Comforts my Elenora does impart: </l>  <l>Joy to my Eyes, sweet Raptures to my Heart. </l> </sp>

2.6.3.1. Special Cases

2.6.3.1.1. No explicit speaker in text
If the speaker name is not explicitly given in-text, while e.g. being wrapped into a stage direction, just create a normal <sp> block and omit the <speaker> tag (don’t forget the who attribute though).
<sp who="#governor">  <stage>Enter the Governor singing.</stage>  <l>If an old man has a beauteous Treasure,</l>  <l>Let her sing, and dance, and laugh without measure,</l>  <l>And then she'l think of no other Pleasure.</l> </sp>

2.7. Elements used in DraCor files

Only a small subset of the elements available in the TEI Drama Customization are actually used in DraCor corpora. The elements included in the following list are relevant. In the documentation below (section Schema) you can find additional information on the elements and examples of their use in DraCor files. If you are using additional elements that are valid in the TEI Drama Customization bear in mind that there can be unexpected results when using the API (e.g. counting of word tokens, extraction of metadata values, ...) or issues when displaying your files in the front-end (e.g. text not being displayed, ...). If you think that a certain element should be included in the core elements below and thus be better supported by the DraCor system please open an issue in the dracor-schema repository on GitHub and describe your use case.

3. Encoding for Network Analysis

The literary texts in the DraCor corpora are enriched with a research-driven markup for the application of a specific method, the network analysis of literary texts (Trilcke 2013). Therefore, the encoding is tailored to allow for the extraction of ‘co-presence networks’ relying on structural segmentation of a given play into acts and scenes and having uniquely identifiable speaking and acting characters. The cast lists (encoded as <castList>) or dramatis personae that are contained in most dramatic texts are an insufficient source in this regard, because they tend to be incomplete. Speaker labels (encoded as <speaker>) contained in the proper text are also often misleading, because they are often not stable enough to serve as an identifier. Therefore, the plays encoded for the DraCor platform have an additional section in their metadata in the <teiHeader> that lists all characters as <person> or <personGrp> elements in a <listPerson> and assigns them a unique identifier (attribute xml:id), that is then used in the attribute who to link the individual speech acts <sp> with their respective speakers.

While each distinct speaker represents a ‘node’ in a network, a relation (‘edge’) is established if the speeches <sp> of two or more speakers appear in the same segment <div> (normally a “scene” classified by the attribute type).

The co-presence network can then be extracted by a designated algorithm which is implemented in XQuery: The function of the DraCor API metrics:get-network-metrics extracts the segments (element <div>) of a given TEI file using the function dutil:get-segments and for each of these segments gets the distinct speakers with the function dutil:distinct-speakers. The network metrics are calculated based on these extracted features with the “DraCor Metrics Service” using the Python package networkx.

The schema derived from this ODD includes some schematron rules that allow for checking if networks can be extracted from the TEI files:

4. DraCor API

The DraCor API is at the core of the whole DraCor system. It is designed with a domain model of digital drama analysis in mind and thus organizes the API functionality around the two core entities “corpus” and theater “play”, thus following the assumption already mentioned above that corpora are the central epistemic objects of Computational Literary Studies (cf. Gavin 2023: 4).

The machine-readable documentation of the DraCor-API in the OpenAPI format can be accessed at https://dracor.org/doc/api. It defines the available API endpoints and the schemas of the respective response objects. The following section accompanies this specification and provides additional documentation of the attributes in the return JSON objects. The following "features" also form the basis of the DraCor API Ontology which – at a later stage – will be automatically generated from this ODD.

4.1. API features

The following sections list the ‘features’. The tables in the annex provide an overview how these features are dispersed over the response objects of the various endpoints.

4.1.1. Corpus features

4.1.1.1. Corpus Name

Feature C1 corpus_name: Identifier "name" or "corpusname" of a corpus, e.g. "ger" for the "German Drama Corpus".

Normally this identifier is used as path parameter in requests to the DraCor API.

4.1.1.2. Corpus URI

Feature C2 corpus_uri: Identifier "uri" of a corpus. It is equal to the the full URL of the /corpora/{corpusname} endpoint.

4.1.1.3. Corpus Title

Feature C3 corpus_title: Full title of a corpus, e.g. "Ukrainian Drama Corpus".

4.1.1.4. Corpus Acronym

Feature C4 corpus_acronym: Acronym of a corpus. Normally, it is the identifier "name"/"corpusname" (see "corpus_name", but starting with a capital letter) followed by the string "DraCor", e.g. "TatDraCor".

In the TEI source data the corpus acronym can be explicitly set by including an element <title>; with the value acronym of the attribute type in in the metadata file of a corpus ("corpus.xml").

If this element is missing, the value of the element <idno> with with the attribute type value of URI from the "corpus.xml" is extracted and prepended with "DraCor".

4.1.1.5. Corpus Description

Feature C5 corpus_description: Description of a corpus. In the TEI source data this information is contained in the element <projectDesc> in the "corpus.xml" file.

The value returned can be formatted using Markdown. The transformation of TEI into Markdown is handled by the function 'local:to-markdown' in 'util.xqm' which transforms TEI elements <hi> and <ref> for hyperlinks.

4.1.1.6. Corpus Repository

Feature C6 corpus_repository: URL of the (GitHub) repository that contains the TEI source data. The information is extracted from the element <idno> with the value repo of the attribute type in a "corpus.xml" file.

4.1.1.7. Corpus Licence

Feature C7 corpus_licence: Licence information of a corpus. The value is a string identifying the licence, e.g. CC0. The information is extracted from the corpus metadata in "corpus.xml". It is the text content of the element <licence>.

4.1.1.8. Corpus Licence URL

Feature C8 corpus_licence_url: Identifier/URL of a licence. The value is extracted from the attribute target of the element <licence> in the "corpus.xml" file.

4.1.1.9. Number of Plays in a Corpus

Feature C9 corpus_num_of_plays: Number of plays in a corpus. The value is the number of <TEI> elements (should be equal to files) in a given corpus collection in the underlying eXist-DB database.

4.1.1.10. Number of Characters in a Corpus

Feature C10 corpus_num_of_characters: Number of characters in a corpus. The value is the number of all <person> and <personGrp> elements in all <listPerson> elements in a given collection representing a corpus in the underlying eXist-DB database.

4.1.1.11. Number of Male Characters in a Corpus

Feature C11 corpus_num_of_characters_male: Number of male characters in a corpus. The value is the number of all elements <person> and <personGrp> that are classified with the value MALE in the attribute sex in all <listPerson> elements in a given collection representing a corpus in the underlying eXist-DB database.

4.1.1.12. Number of Female Characters in a Corpus

Feature C12 corpus_num_of_characters_female: Number of female characters in a corpus. The value is the number of all <person> and <personGrp> that are classified with the value FEMALE in the attribute sex in all <listPerson> l elements in a given collection representing a corpus in the underlying eXist database.

4.1.1.13. Number of Text Elements in a Corpus

Feature C13 corpus_num_of_tei_text_elements: Number of <text> elements in a corpus. The value is the number of <text> elements in all TEI files in a collection representing a corpus in the underlying eXist-DB database.

In earlier versions of DraCor files a TEI file can contain multiple <tei:text> elements, e.g. when there are multiple one act plays published together.

Since this iteration of the schema the content model of <TEI> is adapted to allow only a single element <text>, therefore the value of this feature should match feature corpus_num_of_plays.

4.1.1.14. Number of Speech Acts in a Corpus

Feature C14 corpus_num_of_sp: Number of speech acts in a corpus.

The value is the number of <sp> elements in a collection representing a corpus in the underlying eXist-DB database.

4.1.1.15. Number of Stage Directions in a Corpus

Feature C15 corpus_num_of_stage: Number of stage directions in a corpus.

The value is the number of <stage> elements in a collection representing a corpus in the underlying eXist-DB database.

4.1.1.16. Number of Word Tokens in Text Elements in a Corpus

Feature C16 corpus_num_of_word_tokens_in_text_elements: Number of word tokens in <text> elements in the corpus.

The number of tokens for each TEI file is pre-calculated upon ingest into the eXist-DB database by tokenizing the contents of the elements <text> with the the built-in xPath function tokenize(). The regular expression '\W+' is used as separator. The values of all documents in a corpus collection are summed up.

4.1.1.17. Number of Word Tokens in Speech Acts in a Corpus

Feature C17 corpus_num_of_word_tokens_in_sp: Number of word tokens in <sp> elements in the corpus.

The number of tokens for each TEI file is pre-calculated upon ingest into the eXist-DB database by tokenizing the contents of the elements <sp> with the built-in xPath function tokenize(). The regular expression '\W+' is used as separator. The values of all documents in a corpus collection are summed up.

4.1.1.18. Number of Word Tokens in Stage Directions in a Corpus

Feature C18 corpus_num_of_word_tokens_in_stage: Number of word tokens in <tei:stage> elements in the corpus. The number of tokens for each TEI file is pre-calculated upon ingest into the eXist database by tokenizing the contents of the elements tei:sp with the built-in xPath function 'tokenize()'. The regular expression '\W+' is used as separator. The values of all documents in a corpus collection are summed up.

4.1.1.19. Date Updated of Corpus Metrics

Feature C19 corpus_metrics_date_updated: Most recent date and time the metrics of a document in a collection in the eXist database representing a corpus were updated. The function retrieves the update date/time values (attribute @updated) of all metrics files in a collection and takes the maximum value using the built-in function 'max'.

4.1.2. Play features

4.1.2.1. Name of the Corpus a Play is part of

Feature P1 play_corpus_name: Name/Identifier "corpusname" (Feature C1) of the corpus the play is contained in.

4.1.2.2. Play ID

Feature P2 play_id:

‘DraCor ID’ of the play, e.g. ger000171.

In the TEI source file the DraCor ID is contained in the attribute xml:id on the root element <TEI>.

The identifier SHOULD match the Regular Expression ^[a-z]+[0-9]{6}$.

The value is retrieved by the xQuery function dutil:get-dracor-id in the module util.xqm [Code].

4.1.2.3. Play URI

Feature P65 play_uri: URI of the play. It is equal to the the full URL of the /corpora/{corpusname}/plays/{playname} endpoint.

4.1.2.4. Play Name

Feature P3 play_name: Identifier "playname". Normally a combination of the name of the author and the title of the play, e.g. lessing-emilia-galotti.

It MUST be unique across a single corpus. This identifier is normally used as path parameters in requests to the DraCor API.

It is recommended that the file name of a document SHOULD be equal to the play name identifier.

4.1.2.5. Play Wikidata Identifier

Feature P4 play_wikidata_id: Wikidata ID of the play. The value is the "Q-Number" of the item on Wikidata, e.g. Q466333.

In the TEI source document the information is contained in the <standOff> element as a <relation> element with the value wikidata of the attribute name as the full URI, e.g. http://www.wikidata.org/entity/Q466333.

4.1.2.6. Play Title

Feature P5 play_title: (Main) title of the play. Normally, the title is in the language of the corpus. The respective function extracts the text of the first element <title> in the <titleStmt> in the <teiHeader>.

4.1.2.7. Play Subtitle

Feature P6 play_subtitle: Subtitle of the play.

Normally, the subtitle is in the language of the corpus. The respective function extracts the text of the first element <title> in <titleStmt> in the <teiHeader> that carries an attribute type with the value sub.

4.1.2.8. Play English Title

Feature P7 play_title_en: English translation of the original main title of the play.

The respective function extracts the text of the element <title> with eng as the attribute's xml:lang value.

4.1.2.9. Play English Subtitle

Feature P8 play_subtitle_en: English translation of the original subtitle of the play.

The respective function extracts the text of the element <title> with the value of the attribute type being sub and eng as the attribute's xml:lang value.

4.1.2.10. Play Author Name

Feature P9 play_author_name: Name of the author of the play in the format '{surname}, {forename}', e.g. 'Shakespeare, William', 'Гоголь, Николай Васильевич'.

The value can be used for sorting. The respective function takes the contents of the elements <persName> or <name> from the element <author> in the <titleStmt> and applies some processing logic: If the constituents are marked up with the special elements <surname> and <forename>, they are arranged in the order "surname, forename". The optional attribute sort on the element <surname> is evaluated as well to distinguish the order of <surname> elements. If no additional markup is present, the contents of the <name> or <persName> element is used.

4.1.2.11. Play English Transliteration/Translation of Author Name

Feature P10 play_author_name_en: English name of the author of a play in the format '{surname}, {forename}', e.g. 'Gogol, Nikolai' (in this case the value of 'author_name' is Гоголь, Николай Васильевич' including the patronym).

4.1.2.12. Play Author Full Name

Feature P11 play_author_fullname: Full name of the author of the play including patronyms and other name constituents as encoded in the TEI source file in the element <persName> or <name> in <author> author. E.g. 'Николай Васильевич Гоголь', 'William Shakespeare'.

4.1.2.13. Play English Transliteration/Translation of the Author Full Name

Feature P12 play_author_fullname_en: Full english name of the author of the play, e.g. 'Nikolai Gogol'.

4.1.2.14. Play Author Shortname

Feature P13 play_author_shortname: Short name of the author of a play.

Normally, the value is the author's surname only, e.g. 'Shakespeare' ,'Гоголь'.

4.1.2.15. Play English Transliteration/Translation of the Author Shortname

Feature P14 play_author_shortname_en: English short name of the author of a play.

Normally, it is the value of the author's surname only, e.g. 'Gogol'.

4.1.2.16. Play Shortname of First Author

Feature P16 play_first_author_shortname: Short name of the first author of a play.

4.1.2.17. Play Author Also Known As

Feature P18 play_author_also_known_as: Alternative name of the author of a play, e.g. 'Titus Maccius Plautus' in case of the author 'Plautus'.

In the source TEI file alternative names are encoded as additional elements <persName>.

4.1.2.18. Play Author ID in External Reference Resource

Feature P19 play_author_ref_external_id: ID of the author in an external reference resource.

This for example can be the 'Q-Number' of Wikidata.

4.1.2.19. Play Author Type of ID in External Reference Resource

Feature P20 play_author_ref_type: Type of the ID of the author in an external reference resource, e.g. wikidata.

4.1.2.20. Play Number of Co-Authors

Feature P21 play_num_of_co_authors: Number of co-authors of a play. The value is the number of all authors of a play minus one.

4.1.2.21. Play Genre Normalized

Feature P22 play_genre_normalized: Normalized genre of a play.

The function performs a lookup using a Wikidata identifier provided in the element <classCode> in <textClass>. The normalized values can be Comedy, Tragedy,Tragicomedy,Satyr play.

4.1.2.22. Play is Libretto

Feature P23 play_is_libretto: Indicates if a play is a libretto.

The function performs a lookup using a Wikidata identifier provided in the element <classCode> in <textClass>. If the returned value is Libretto the value of this property is true, otherwise false.

4.1.2.23. Play Year Written

Feature P24 play_year_written: Year of the creation of the play / year when the play was written.

4.1.2.24. Play Year Printed

Feature P25 play_year_printed: Year the play was published / year of first printing.

4.1.2.25. Play Year Premiered

Feature P26 play_year_premiered: Year the Play was premiered

4.1.2.26. Play Date Premiered

Feature P66 play_date_premiered: Date the play was premiered. This is only available when the exact date of the premiere in ISO format (YYYY-MM-DD) is specified in element <standOff>.

This feature was added later and is not included in the 'Report on Programmable Corpora'.

4.1.2.27. Play Year Normalized

Feature P27 play_year_normalized: Of all available years (written, printed, premiered) a so-called 'normalized year' is selected; It is either the earlier on of printing or premiered or, if a work was published or performed much later (more than 10 years) after its creation, the year of its creation is taken as »Normalized Year« (if it is a range of years, the last of them is taken).

4.1.2.28. Play Digital Source Name

Feature P28 play_digital_source_name: Name of the digital source of a play. Normally it is the name of the repository or project that provides a digital version of the play, e.g. Google Books, Wikisource, TextGrid Repository.

4.1.2.29. Play Digital Source URL

Feature P29 play_digital_source_url: URL of the digital source of a play.

4.1.2.30. Play Original Source Full Citation

Feature P30 play_original_source_full_citation: Full citation of the play's original (print publication) source.

In the TEI file the citation is contained in the element <bibl> with the value originalSource of the attribute type inside the <sourceDesc>.

4.1.2.31. Play Original Source Publisher

Feature P31 play_original_source_publisher: Publisher of the print publication that was used as the original source.

From the TEI data the content of the element <publisher> in the <bibl> representing the original source is extracted.

4.1.2.32. Play Original Source Publication Place

Feature P32 play_original_source_publication_place: Place of publication of the print publication that was used as the original source.

In the TEI data the content of the element <pubPlace> in the <bibl> representing the original source is extracted. If there are multiple places annotated, they are joined to a single string separated by ','.

4.1.2.33. Play Original Source Publication Year

Feature P33 play_original_source_publication_year: Year of publication of the print publication that was used as the original source.

4.1.2.34. Play Original Source Number of Pages

Feature P34 play_original_source_num_of_pages: Extent of the original source in number of pages derived from the bibliographic reference.

In the TEI file the element <biblScope> holds a page range encoded in the attribute from and to. The value is calculated by taking the value of to and subtracting the value of from and adding 1.

4.1.2.36. Play Number of Segments

Feature P37 play_num_of_segments: Number of segments (e.g. scenes) of a play.

Usually <div> elements inside <body> are considered a segment if they contain a speech marked up by an element <sp>.

However, also "empty scenes" with no speaking characters are considered a segment, e.g. elements <div> that consist of stage directions (<stage>) only.

4.1.2.37. Play Number of Acts

Feature P38 play_num_of_acts: Number of acts of a play.

In the TEI file acts are elements <div> with an attribute type value of act. The function extracting the information returns the number of such <div> elements.

4.1.2.38. Play Number of Paragraphs

Feature P39 play_num_of_paragraphs:

4.1.2.39. Play Number of Verse Lines

Feature P40 play_num_of_verse_lines:

4.1.2.40. Play Number of Word Tokens in Text Elements

Feature P41 play_num_of_word_tokens_in_text_elements:

4.1.2.41. Play Number of Word Tokens in Speech Acts

Feature P42 play_num_of_word_tokens_in_sp:

4.1.2.42. Play Number of Word Tokens in Stage Directions

Feature P43 play_num_of_word_tokens_in_stage:

4.1.2.43. Play Number of Speaking Characters

Feature P45 play_num_of_speakers: Number of Speakers of a Play

4.1.2.44. Play Number of Speaking Female Characters

Feature P46 play_num_of_speakers_sex_female:

4.1.2.45. Play Number of Speaking Male Characters

Feature P47 play_num_of_speakers_sex_male:

4.1.2.46. Play Number of Speaking Characters with Unknown Gender

Feature P48 play_num_of_speakers_sex_unknown:

4.1.2.47. Play Number of Person Groups

Feature P49 play_num_of_person_groups:

4.1.2.48. Play All In Segment

Feature P50 play_all_in_segment:

4.1.2.49. Play All In Index

Feature P51 play_all_in_index:

4.1.2.50. Play Network Data CSV URL

Feature P53 play_network_data_csv_url:

4.1.2.51. Play Network Size

Feature P55 play_network_size:

4.1.2.52. Play Number of Edges in the Network

Feature P56 play_network_num_edges:

4.1.2.53. Play Average Degree of the Network

Feature P57 play_network_average_degree: Average Degree of the Network representing a Play

4.1.2.54. Play Density of the Network

Feature P58 play_network_density: Density of a Network representing a Play

4.1.2.55. Play Diameter of the Network

Feature P59 play_network_diameter:

4.1.2.56. Play Average Path Length of the Network

Feature P60 play_network_average_path_length: Average Path Length of a Network representing a Play

4.1.2.57. Play Average Clustering Coefficient of the Network

Feature P61 play_network_average_clustering:

4.1.2.58. Play Number of Connected Components of the Network

Feature P62 play_network_num_connected_components:

4.1.2.59. Play Maximum Degree of the Network

Feature P63 play_network_max_degree:

4.1.2.60. Play IDs of the Character with Maximum Degree in the Network

Feature : ID of the character with the highest degree value in a network representing a play. In the report 'On programmable corpora' the corresponding feature is 'P64'.

4.1.3. Segment features

4.1.3.1. Segment Type

Feature S1 segment_type:

4.1.3.2. Segment Number

Feature S2 segment_number:

4.1.3.3. Segment Title

Feature S3 segment_title:

4.1.3.4. Segment Speaking Characters

Feature S4 segment_speaking_characters:

4.1.4. Character features

4.1.4.1. Character ID

Feature Ch1 character_id:

4.1.4.2. Character Name

Feature Ch2 character_name:

4.1.4.3. Character Is Group

Feature Ch3 character_is_group:

4.1.4.4. Character Sex

Feature Ch4 character_sex:

4.1.4.5. Character Wikidata ID

Feature Ch5 character_wikidata_id:

4.1.4.6. Character Node Betweenness

Feature Ch6 character_node_betweenness:

4.1.4.7. Character Node Degree

Feature Ch7 character_node_degree:

4.1.4.8. Character Node Closeness

Feature Ch8 character_node_closeness:

4.1.4.9. Character Node Eigenvector

Feature Ch9 character_node_eigenvector:

4.1.4.10. Character Node Weighted Degree

Feature Ch10 character_node_weighted_degree:

4.1.4.11. Character Number of Segments

Feature Ch11 character_num_of_segments: Number of Segments a Character appears in

4.1.4.12. Character Number of Speech Acts

Feature Ch12 character_num_of_sp:

4.1.4.13. Character Number of Word Tokens

Feature Ch13 character_num_of_word_tokens:

4.1.4.14. Character Role

Feature : Character Roles. Feature 'Ch14' in the report 'On Programmable Corpora'.

4.1.4.15. Character Spoken Text

Feature Ch15 character_spoken_text:

4.1.5. Character relation features

4.1.5.1. Character Relation Is Directed

Feature character_relation_is_directed: Indicates if a relation is directed (true).

4.1.5.2. Character Relation Type

Feature character_relation_type: Type of relation between characters, e.g. 'parent_of', 'lover_of', 'related_with', 'associated_with', 'siblings', 'spouses', 'friends'.

4.1.5.3. Character Relation From

Feature character_relation_from: Contains the ID/name of a character that is the 'source' of the relation.

4.1.5.4. Character Relation To

Feature character_relation_to: Contains the ID/name of a character that is the 'target' of the relation.

5. Schema

5.1. Elements

5.1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure — Schema
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Note
Should contain the ID of the DraCor play, e.g. ger000171
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusOptional
Datatypeteidata.language
Note
Can encode the language of a corpus. Not the best idea in the world, but this is the way it is done.
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

Member of
Contained by
core: teiCorpus
May contain
header: teiHeader
linking: standOff
textstructure: text
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 xml:id="ger000171xml:lang="ger" xmlns="http://www.tei-c.org/ns/1.0"> <!-- ... --> </TEI>
The TEI namespace http://www.tei-c.org/ns/1.0 should also be added to the root TEI element in the attribute xmlns.
SchematronDraCor identifiers should consist of lower case letters followed by a six-digit number. The value is returned as feature play_id in the API response object.
<sch:rule context="tei:TEI" role="warning"> <sch:assert test="matches(./@xml:id,'^[a-z]+[0-9]{6}$')"> For DraCor IDs we recommend the pattern ^[a-z]+[0-9]{6}$ </sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="standOff" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="text" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.typed.attributes,
   attribute xml:id { text },
   attribute xml:lang { text }?,
   attribute version { text }?,
   ( tei_teiHeader, tei_standOff?, tei_text )
}

5.1.2. <ab>

<ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [17.3. Blocks, Segments, and Anchors]
Modulelinking — Schema
Attributes
Member of
Contained by
May contain
Note

In DraCor the element <ab> is normally used to encode the name of the licence used.

Example
<availability>  <licence>   <ab>CC0 1.0</ab>   <ref target="https://creativecommons.org/publicdomain/zero/1.0/">Licence</ref>  </licence> </availability>
SchematronIn DraCor we discourage the use of the element <ab> anywhere else than to mark the human-readable label of the licence in <availability>.
<sch:rule context="tei:ab" role="warning"  see="https://dracor.org/doc/odd#TEI.ab"> <sch:assert test="./parent::tei:licence"> In DraCor the element 'ab' should only be used to mark the label of the licence in the teiHeader. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:ab"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText. </sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.abContent"/>
</content>
    
Schema Declaration
element ab
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.fragmentable.attributes,
   tei_att.typed.attributes,
   tei_macro.abContent
}

5.1.3. <abbr>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore — Schema
Attributes
type(type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
suspension
(suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
(contraction) the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
(superscription) the abbreviation includes writing above the line.
acronym
(acronym) the abbreviation comprises the initial letters of the words of a phrase.
title
(title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
(organization) the abbreviation is for the name of an organization.
geographic
(geographic) the abbreviation is for a geographic name.
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

5.1.4. <abstract>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
linking: ab
Note

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

Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <elementRef key="listBibl"/>
 </alternate>
</content>
    
Schema Declaration
element abstract
{
   tei_att.global.attributes,
   ( tei_model.pLike | tei_model.listLike | tei_listBibl )+
}

5.1.5. <actor>

<actor> contains the name of an actor appearing within a cast list. [7.1.4. Cast Lists]
Moduledrama — Schema
Attributes
sexspecifies the sex of the actor.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

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

genderspecifies the gender of the actor.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

Member of
Contained by
drama: castItem
May contain
Note

This element should be used only to mark the name of the actor as given in the source. Chapter 14. Names, Dates, People, and Places discusses ways of marking the components of names, and also of associating names with biographical information about a person.

Example
<castItem>  <role>Mathias</role>  <roleDesc>the Burgomaster</roleDesc>  <actor ref="https://en.wikipedia.org/wiki/Henry_Irving">Mr. Henry Irving</actor> </castItem>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element actor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   tei_macro.phraseSeq
}

5.1.6. <add>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.7. <addName>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [14.2.1. Personal Names]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.8. <addrLine>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Schema
Attributes
Member of
Contained by
core: address
May contain
Note

Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.9. <address>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.global*, ( ( tei_model.addrPart, tei_model.global* )+ ) )
}

5.1.10. <alt>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<alt> (alternation) identifies an alternation or a set of choices among elements or passages. [17.8. Alternation]
Modulelinking — Schema
Attributes
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
modestates whether the alternations gathered in this collection are exclusive or inclusive.
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
excl
(exclusive) indicates that the alternation is exclusive, i.e. that at most one of the alternatives occurs.
incl
(inclusive) indicates that the alternation is not exclusive, i.e. that one or more of the alternatives occur.
weightsIf mode is excl, each weight states the probability that the corresponding alternative occurs. If mode is incl each weight states the probability that the corresponding alternative occurs given that at least one of the other alternatives occurs.
StatusOptional
Datatype2–∞ occurrences of teidata.probability separated by whitespace
Note

If mode is excl, the sum of weights must be 1. If mode is incl, the sum of weights must be in the range from 0 to the number of alternants.

Member of
Contained by
May containEmpty element
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element alt
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.attribute.targetLang,
   tei_att.pointing.attribute.evaluate,
   tei_att.typed.attributes,
   attribute target { list { * } }?,
   attribute mode { "excl" | "incl" }?,
   attribute weights { list { * } }?,
   empty
}

5.1.11. <altGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<altGrp> (alternation group) groups a collection of <alt> elements and possibly pointers. [17.8. Alternation]
Modulelinking — Schema
Attributes
modestates whether the alternations gathered in this collection are exclusive or inclusive.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
excl
(exclusive) indicates that the alternation is exclusive, i.e. that at most one of the alternatives occurs.[Default]
incl
(inclusive) indicates that the alternation is not exclusive, i.e. that one or more of the alternatives occur.
Member of
Contained by
May contain
core: desc ptr
linking: alt
Note

Any number of alternations, pointers or extended pointers.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="alt"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element altGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.group.attributes,
   attribute mode { "excl" | "incl" }?,
   ( tei_model.descLike*, ( tei_alt | tei_ptr )* )
}

5.1.12. <analytic>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Schema
Attributes
Contained by
May contain
Note

May contain titles and statements of responsibility (author, editor, or other), in any order.

The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   tei_att.global.attributes,
   (
      tei_author
    | tei_editor
    | tei_respStmt
    | tei_title
    | tei_model.ptrLike
    | tei_date
    | tei_textLang
    | tei_idno
    | tei_availability
   )*
}

5.1.13. <anchor>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 17.5. Correspondence and Alignment]
Modulelinking — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

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

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element anchor
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.14. <annotation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<annotation> represents an annotation following the Web Annotation Data Model. [17.10. The standOff Container]
Modulelinking — Schema
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
motivation
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
assessing
intent is to assess the target resource in some way, rather than simply make a comment about it
bookmarking
intent is to create a bookmark to the target or part thereof
classifying
intent is to classify the target in some way
commenting
intent is to comment about the target
describing
intent is to describe the target, rather than (for example) comment on it
editing
intent is to request an edit or a change to the target resource
highlighting
intent is to highlight the target resource or a segment thereof
identifying
intent is to assign an identity to the target
linking
intent is to link to a resource related to the target
moderating
intent is to assign some value or quality to the target
questioning
intent is to ask a question about the target
replying
intent is to reply to a previous statement, either an annotation or another resource
tagging
intent is to associate a tag with the target
Note

For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.

As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.

Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="respStmt" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="licence" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.annotationPart.body"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element annotation
{
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.pointing.attribute.targetLang,
   tei_att.pointing.attribute.evaluate,
   attribute xml:id { text },
   attribute target { list { + } },
   attribute motivation
   {
      list
      {
         (
            "assessing"
          | "bookmarking"
          | "classifying"
          | "commenting"
          | "describing"
          | "editing"
          | "highlighting"
          | "identifying"
          | "linking"
          | "moderating"
          | "questioning"
          | "replying"
          | "tagging"
         )+
      }
   }?,
   (
      tei_respStmt*,
      tei_revisionDesc*,
      tei_licence*,
      tei_model.annotationPart.body*
   )
}

5.1.15. <appInfo>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: application
Content model
<content>
 <classRef key="model.applicationLike"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element appInfo { tei_att.global.attributes, tei_model.applicationLike+ }

5.1.16. <application>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader — Schema
Attributes
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
linking: ab
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.labelLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.ptrLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element application
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute ident { text },
   attribute version { text },
   ( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
}

5.1.17. <argument>

<argument> (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Example
<argument>  <head>Inhalt des trauer-spiels.</head>  <p> Michael Balbus, käyser Leonis Armenii oberster    feldhauptmann, nach dem er zu unterschiedenen mahlen wegen    seiner untreu und verleumbdungen angeklaget, verschweret    sich wider den käyser, welcher ihn durch Exabolium, seinen    geheimesten rath, offt von seiner leichtfertigkeit    abzustehen ermahnet. Weil aber Michael auf seinem vorsatz    verharret, wird er unversehens gefangen und von dem rath, in    welchem der käyser selbst kläger und richter, zu dem feuer    verdammet.   <!-- ... -->  </p>  <p> Dieses trauerspiel beginnet den mittag vor dem heiligen    christtage, wehret durch die nacht und endet sich vor    auffgang der sonnen.  </p>  <p> Der schauplatz ist Constantinopel und vornehmlich die    käyserliche burg.  </p> </argument>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.headLike"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element argument
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      ( tei_model.global | tei_model.headLike )*,
      ( ( tei_model.common, tei_model.global* )+ )
   )
}

5.1.18. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note
For additional information on the encoding of author names and the rationale also see the following GitHub issues:
Example
<author>  <persName>   <forename>Andreas</forename>   <surname>Gryphius</surname>  </persName>  <idno type="wikidata">Q77214</idno>  <idno type="pnd">118543032</idno> </author>
Encoding of the author "Andreas Gryphius" of the play Leo Armenius oder Fürsten-Mord.
Example
<author>  <persName>   <forename>Владимир</forename>   <forename type="patronym">Иванович</forename>   <surname>Бельский</surname>  </persName>  <persName xml:lang="eng">   <forename>Vladimir</forename>   <surname>Belsky</surname>  </persName>  <idno type="wikidata">Q1259652</idno> </author>
Encoding of the author "Владимир Иванович Бельский" of the play Сказание о невидимом граде Китеже и деве Февронии.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

5.1.19. <authority>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Schema
Attributes
Member of
Contained by
core: monogr
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq.limited
}

5.1.20. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Schema
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
May contain
core: p
header: licence
linking: ab
Note

A consistent format should be adopted

Example
<availability status="free">  <p> In the public domain.  </p> </availability>
Copyright status of the digital source of Karl Kraus: Die letzten Tage der Menschheit.
Example
<availability>  <licence>   <ab>CC-BY-3.0</ab>   <ref target="http://creativecommons.org/licenses/by/3.0/de/legalcode">Lizenzvertrag</ref>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   tei_att.global.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( tei_model.availabilityPart | tei_model.pLike )+
}

5.1.21. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure — Schema
Attributes
Contained by
textstructure: floatingText text
May contain
Note

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

Example
<back>  <div type="notes">   <head>[Anmerkung]</head>   <p> Dem zu Beginn des <emph>Actus quintus</emph> in freier      Weise verwendeten Zitate aus den Selbstbetrachtungen des      Marc Aurel liegt ein griechischer und lateinischer Text      des achtzehnten Jahrhunderts zugrunde. Bei der Übersetzung      ins Deutsche diente in einzelnen Wendungen die Übersetzung      von Otto Kiefer (Eugen Diederichs, Jena 1906) zum      Vorbilde.   </p>  </div> </back>
A note in the <back> of the play Anton Wildgans: Dies irae. Should maybe wrapped with a <note> element.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   tei_att.global.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike.front
       | tei_model.pLike
       | tei_model.listLike
       | tei_model.global
      )*,
      (
         (
            tei_model.div1Like,
            ( tei_model.frontPart | tei_model.div1Like | tei_model.global )*
         )
       | (
            tei_model.divLike,
            ( tei_model.frontPart | tei_model.divLike | tei_model.global )*
         )
      )?,
      (
         (
            tei_model.divBottomPart,
            ( tei_model.divBottomPart | tei_model.global )*
         )?
      )
   )
}

5.1.22. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore — Schema
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
digitalSource
(Digital Source) Digitized version of the print publication
originalSource
(Original Source) Bibliographic citation of the original print publication the digital text is derived from
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

Example
<bibl type="digitalSource">  <name>TextGrid Repository</name>  <idno type="URL">http://www.textgridrep.org/textgrid:jn65.0</idno>  <availability>   <licence>    <ab>CC-BY-3.0</ab>    <ref target="http://creativecommons.org/licenses/by/3.0/de/legalcode">Lizenzvertrag</ref>   </licence>  </availability>  <bibl type="originalSource">   <title>Ludwig Anzengruber: Der Meineidbauer. Herausgegeben      und eingeleitet von Wilhelm Zentner, Stuttgart: Reclam, 1959      [Universal-Bibliothek, Band 133].</title>  </bibl> </bibl>
The element <bibl> is used to encode the sources of the play Ludwig Anzengruber: Der Meineidbauer. The <bibl> of ‘original source’ – marked with a type value of originalSource – is nested into the element <bibl> of the ‘digital source’ – marked with the attribute value digitalSource of type.
Example
<bibl type="digitalSource">  <name>Google Books</name>  <idno type="URL">https://books.google.com/books?id=NbpIAQAAMAAJ&amp;printsec=frontcover</idno>  <availability status="free">   <p> In the public domain.   </p>  </availability>  <bibl type="originalSource">   <author>Joseph von Auffenberg</author>: <title>Der Löwe von      Kurdistan. Ein romantisches Schauspiel in fünf Acten. Nach      W. Scott's Talisman bearbeitet</title>.  <pubPlace>Würzburg</pubPlace>:  <publisher>Etlinger</publisher>   <date>1827</date>, S.  <biblScope unit="pagefrom="1to="155">1–155</biblScope>.  </bibl> </bibl>
The ‘original source’ contained in the inner <bibl> in the <teiHeader> of the play Joseph von Auffenberg: Der Löwe von Kurdistan uses additional elements <author>, <title>, <pubPlace>, <publisher>, <date>, <biblScope> to o explicitly mark the components of the bibliographic reference.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   attribute type { text }?,
   (
      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
   )*
}

5.1.23. <biblFull>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="titleStmt"/>
    <elementRef key="editionStmt"
     minOccurs="0"/>
    <elementRef key="extent" minOccurs="0"/>
    <elementRef key="publicationStmt"/>
    <elementRef key="seriesStmt"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="notesStmt"
     minOccurs="0"/>
   </sequence>
   <elementRef key="sourceDesc"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="fileDesc"/>
   <elementRef key="profileDesc"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element biblFull
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   (
      (
         (
            tei_titleStmt,
            tei_editionStmt?,
            tei_extent?,
            tei_publicationStmt,
            tei_seriesStmt*,
            tei_notesStmt?
         ),
         tei_sourceDesc*
      )
    | ( tei_fileDesc, tei_profileDesc )
   )
}

5.1.24. <biblScope>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Schema
Attributes
type
StatusRecommended
Datatypeteidata.enumerated
Suggested values include:
volume
(Volume) Volume containing a play
page
(Page) Page range of a play in the print publication
Note

The values above are evaluated by the DraCor-API. The TEI Guidelines suggest additional values, see also the documentation of the attribute in the attribute class att.citing.

Member of
Contained by
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   attribute type { "volume" | "page" }?,
   tei_macro.phraseSeq
}

5.1.25. <biblStruct>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   (
      tei_analytic*,
      ( ( tei_monogr, tei_series* )+ ),
      (
         tei_model.noteLike
       | tei_model.ptrLike
       | tei_relatedItem
       | tei_citedRange
      )*
   )
}

5.1.26. <binaryObject>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<binaryObject> provides encoded binary data representing an inline graphic, audio, video or other object. [3.10. Graphics and Other Non-textual Components]
Modulecore — Schema
Attributes
encodingThe encoding used to encode the binary data. If not specified, this is assumed to be Base64.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May containCharacter data only
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element binaryObject
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.media.attributes,
   tei_att.timed.attributes,
   tei_att.typed.attributes,
   attribute encoding { list { + } }?,
   text
}

5.1.27. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure — Schema
Attributes
Contained by
textstructure: floatingText text
May contain
Example
<body>  <div type="act">   <head>Erster Akt.</head>   <stage>Scene: Elegantes Zimmer in Gustav's Hause.</stage>   <div type="scene">    <head>Erster Auftritt.</head>    <stage>Durch die Mittelthür kommen: Ehrenthal und Dörthe.</stage> <!-- ... -->   </div>  </div> <!-- ... --> </body>
Common structure of the <body> element of a play. Example is taken from Karl von Holtei: Ein Trauerspiel in Berlin.
SchematronA network can only be extracted from a play if there is some basic structure. The API expects that there is at least a single <div> present.
<sch:rule context="tei:body" role="warning"> <sch:assert test="tei:div"> A play SHOULD at least have one structural division 'div' for the API to be able to extract a network. </sch:assert> </sch:rule>
SchematronThe network is extracted based on speech acts which SHOULD be encoded using the element <sp>.
<sch:rule context="tei:body" role="warning"> <sch:assert test=".//tei:sp"> A play SHOULD be structured in speech-acts using the element 'sp' for the API to be able to extract a network. </sch:assert> </sch:rule>
SchematronIn the edge case of a play without speaking characters and no speech acts <sp> it is expected that there is at least a single stage direction <stage>.
<sch:rule context="tei:body[not(.//tei:sp)]"  role="warning"> <sch:assert test=".//tei:stage"  role="warning"> A drama that does not contain a speech-act 'sp', SHOULD at least contain a stage direction 'stage'. </sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   tei_att.global.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* )* )
   )
}

5.1.28. <byline>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<byline> (byline) contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Note

The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docAuthor> element.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="docAuthor"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element byline
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_docAuthor
    | tei_model.global
   )*
}

5.1.29. <c>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<c> (character) represents a character. [18.1. Linguistic Segment Categories]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May containCharacter data only
Note

Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc.

Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element c
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   tei_macro.xtext
}

5.1.30. <cRefPattern>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader — Schema
Attributes
Contained by
header: refsDecl
May contain
core: p
linking: ab
Note

The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element cRefPattern
{
   tei_att.global.attributes,
   tei_att.patternReplacement.attributes,
   tei_model.pLike*
}

5.1.31. <calendar>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Moduleheader — Schema
Attributes
Contained by
header: calendarDesc
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendar
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_model.pLike+
}

5.1.32. <calendarDesc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
Moduleheader — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
header: calendar
Note

In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

Content model
<content>
 <elementRef key="calendar" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendarDesc { tei_att.global.attributes, tei_calendar+ }

5.1.33. <camera>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<camera> (camera) describes a particular camera angle or viewpoint in a screen play. [7.3.1. Technical Information 7.3. Other Types of Performance Text]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element camera
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.34. <caption>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<caption> (caption) contains the text of a caption or other text displayed as part of a film script or screenplay. [7.3.1. Technical Information 7.3. Other Types of Performance Text]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Note

A specialized form of stage direction.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element caption { tei_att.global.attributes, tei_macro.paraContent }

5.1.35. <castGroup>

<castGroup> (cast list grouping) groups one or more individual <castItem> elements within a cast list. [7.1.4. Cast Lists]
Moduledrama — Schema
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Suggested values include:
braced
(marked with a bracket) Indicates that a group of characters is visually marked as belonging to a group by means of a bracket. This rendering is supported by the DraCor front-end.
Contained by
May contain
Note

The rend attribute may be used, as here, to indicate whether the grouping is indicated by a brace, whitespace, font change, etc.

Note that in this example the role description ‘friends of Mathias’ is understood to apply to both roles equally.

Example
<castGroup>  <castItem>Silva,</castItem>  <castItem>Gomez,</castItem>  <roleDesc>unter Alba dienend</roleDesc> </castGroup>
The characters are grouped and given a role in the in the "dramatis personae" in the play Goethe: Egmont.
Example
<castGroup rend="braced">  <castItem>Balthasar</castItem>  <castItem>Caspar</castItem>  <roleDesc>Jäger</roleDesc> </castGroup>
A group of characters in Genoveva. In the source, they are marked with a curly bracket.
Example
<castGroup>  <castItem>   <role>Elpore,</role>  </castItem>  <castItem>   <role>Epimeleia,</role>  </castItem>  <roleDesc>Epimetheus' Töchter</roleDesc> </castGroup>
A group of characters with explicitly marked-up roles in Goethe: Pandora.
Example
<castGroup>  <castItem>   <role>Magdalene,</role>   <roleDesc>Behrings Braut, 20 Jahre alt,</roleDesc>  </castItem>  <castItem>   <role>Fritz,</role>   <roleDesc>12 Jahre alt,</roleDesc>  </castItem>  <roleDesc>beider Kinder.</roleDesc> </castGroup>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.headLike"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="castItem"/>
    <elementRef key="castGroup"/>
    <elementRef key="roleDesc"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="trailer"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element castGroup
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.source.attribute.source,
   attribute rend { list { "braced"+ } }?,
   (
      ( tei_model.global | tei_model.headLike )*,
      (
         ( ( tei_castItem | tei_castGroup | tei_roleDesc ), tei_model.global* )+
      ),
      ( ( tei_trailer, tei_model.global* )? )
   )
}

5.1.36. <castItem>

<castItem> (cast list item) contains a single entry within a cast list, describing either a single role or a list of non-speaking roles. [7.1.4. Cast Lists]
Moduledrama — Schema
Attributes
typecharacterizes the cast item.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
role
the item describes a single role.[Default]
list
the item describes a list of non-speaking roles.
Contained by
May contain
Example
<castItem>Marinelli, Kammerherr des Prinzen.</castItem>
A character in the play Lessing: Emilia Galotti.
Example
<castItem>  <role>Leo Armenius,</role>  <roleDesc>käyser von Constantinopel.</roleDesc> </castItem>
A <castItem> in the play Gryphius: Leo Armenius. The name of the role and its description have been explicitly marked-up.
Example
<castItem>  <role>Dämonen</role> </castItem>
Example taken from Goethe: Pandora.
Example
<castItem> Andreas Doria, Doge von Genua <roleDesc>Ehrwürdiger Greis von    achtzig Jahren, Spuren von Feuer. Ein Hauptzug: Gewicht und    strenge befehlende Kürze</roleDesc> </castItem>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.castItemPart"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element castItem
{
   tei_att.global.attributes,
   attribute type { "role" | "list" }?,
   (
      text
    | tei_model.gLike
    | tei_model.castItemPart
    | tei_model.phrase
    | tei_model.global
   )*
}

5.1.37. <castList>

<castList> (cast list) contains a single cast list or dramatis personae. [7.1.4. Cast Lists 7.1. Front and Back Matter ]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Example
<castList>  <head> Personen.</head>  <castGroup>   <castItem>    <role>Prometheus,</role>   </castItem>   <castItem>    <role>Epimetheus,</role>   </castItem>   <roleDesc>Japetiden</roleDesc>  </castGroup>  <castItem>   <role>Phileros,</role>   <roleDesc>Prometheus' Sohn</roleDesc>  </castItem> <!-- ... -->  <castItem>   <role>Dämonen</role>  </castItem>  <castItem>   <role>Helios</role>  </castItem>  <castItem>   <role>Schmiede</role>  </castItem>  <castItem>   <role>Hirten</role>  </castItem> <!-- ... --> </castList>
Example taken from Goethe: Pandora.
ExampleProbably not the best example...
<castList>  <head>ЛИЦА:</head>  <castItem> Раиса Павловна Гурмыжская, вдова, лет 50-ти с небольшим,    очень богатая помещица, одевается скромно, почти в трауре,    постоянно с рабочим ящиком на руке.  </castItem>  <castItem> Аксинья Даниловна (Аксюша), ее дальняя родственница, бедная    девушка лет 20-ти, одета чисто, но бедно, немного лучше    горничной.  </castItem>  <castGroup>   <castItem> Евгений Аполлоныч Милонов, лет 45-ти, гладко причесан,      одет изысканно, в розовом галстуке.   </castItem>   <castItem> Уар Кирилыч Бодаев, лет 60-ти, отставной кавалерист,      седой, гладко стриженный, с большими усами и бакенбардами,      в черном сюртуке, наглухо застегнутом, с крестами и      медалями по-солдатски, с костылем в руке, немного глух.   </castItem>   <roleDesc>Богатые соседи Гурмыжской.</roleDesc>  </castGroup>  <castItem> Иван Петров Восмибратов, купец, торгующий лесом.  </castItem> <!-- ... --> </castList>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="castItem"/>
    <elementRef key="castGroup"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element castList
{
   tei_att.global.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      ( ( tei_model.common, tei_model.global* )* ),
      ( ( ( tei_castItem | tei_castGroup ), tei_model.global* )+ ),
      ( ( tei_model.common, tei_model.global* )* )
   )
}

5.1.38. <catDesc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<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]
Moduleheader — Schema
Attributes
Contained by
header: category
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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 )*
}

5.1.39. <catRef>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Moduleheader — Schema
Attributes
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May containEmpty element
Note

The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   attribute scheme { text }?,
   empty
}

5.1.40. <category>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader — Schema
Attributes
Contained by
May contain
core: desc gloss
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   (
      ( tei_catDesc+ | ( tei_model.descLike | equiv | tei_gloss )* ),
      tei_category*
   )
}

5.1.41. <cb>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column beginnings relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb> element is placed at the head of the column to which it refers.

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element cb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.42. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]
Moduleheader — Schema
Attributes
whenWhen was the change made. Should be an iso-conformant date-time
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.iso
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
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
<revisionDesc>  <listChange>   <change when="2017-01-06">(dlina) file conversion from source</change>   <change when="2017-08-04">(ff) structural cleanup</change>   <change when="2018-12-23">(ff) formalities</change>  </listChange> </revisionDesc>
Example
<revisionDesc>  <listChange>   <change when="2017-05-23">(ds) convert from source</change>   <change when="2017-05-23">(ff) add metadata, insert configuration changes</change>   <change when="2017-06-01">(zh) add dates, ids</change>   <change when="2017-06-03">(gg) gender info</change>   <change when="2017-12-03">(ff) formalities; delete duplicate of poem; work on IDs</change>   <change when="2018-04-07">(zh) group tag</change>  </listChange> </revisionDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   tei_att.global.attributes,
   tei_att.ascribed.attributes,
   tei_att.datable.attribute.period,
   tei_att.datable.w3c.attribute.notBefore,
   tei_att.datable.w3c.attribute.notAfter,
   tei_att.datable.w3c.attribute.from,
   tei_att.datable.w3c.attribute.to,
   tei_att.typed.attributes,
   attribute when { text }?,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

5.1.43. <choice>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

Content model
<content>
 <alternate minOccurs="2"
  maxOccurs="unbounded">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice )*
}

5.1.44. <cit>

<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

In DraCor mostly used to mark citation in epigraphs, see examples.

Example
<epigraph>  <cit>   <quote>    <l>Wie ist mir eine Stimme doch erklungen</l>    <l>Im tiefsten Innern,</l>    <l>Und hat mit einem Male mir verschlungen</l>    <l>All mein Erinnern.</l>   </quote>   <bibl> Adalbert von Chamisso   </bibl>  </cit> </epigraph>
A citation in the epigraph to the play Büchner: Leonce und Lena.
Example
<epigraph>  <cit>   <quote>    <lg>     <l>Leporello. O statua gentilissima</l>     <l>Del gran' Commendatore!..</l>     <l>...Ah, Padrone!</l>    </lg>   </quote>  </cit>  <bibl> Don Giovanni.  </bibl> </epigraph> <ab> Citation in the play <ref target="https://dracor.org/id/rus000021">Пушкин: Каменный    гость</ref> </ab>
Example
<div type="epigraph">  <head>[Motto]</head>  <cit>   <quote>    <p>Introite, nam et heic Dii sunt!</p>   </quote>   <bibl>APUD GELLIUM</bibl>  </cit>  <pb n="206"/> </div>
Only one other example discovered using //cit[not(parent::epigraph)], but this is due to encoding – it's actually kind of an epigraph in the play Lessing: Nathan der Weise
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   (
      tei_model.biblLike
    | tei_model.egLike
    | tei_model.entryPart
    | tei_model.global
    | tei_model.graphicLike
    | tei_model.ptrLike
    | tei_model.attributable
    | tei_pc
    | tei_q
   )+
}

5.1.45. <citeData>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader — Schema
Attributes
property(property) A URI indicating a property definition.
StatusRequired
Datatypeteidata.pointer
Contained by
May containEmpty element
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element citeData
{
   tei_att.global.attributes,
   tei_att.citeStructurePart.attributes,
   attribute property { text },
   empty
}

5.1.46. <citeStructure>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader — Schema
Attributes
delim(delimiter) supplies a delimiting string preceding the structural component.
StatusOptional
Datatypestring
Note

delim must contain at least one character.

match(match) supplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a <citeStructure> without a <citeStructure> parent must be an absolute XPath. If it is relative, its context is set by the match of the parent <citeStructure>.
StatusRequired
Datatypeteidata.xpath
Schematron
<sch:rule context="tei:citeStructure[not(parent::tei:citeStructure)]"> <sch:assert test="starts-with(@match,'/')">An XPath in @match on the outer <sch:name/> must start with '/'.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:citeStructure[parent::tei:citeStructure]"> <sch:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <sch:name/>.</sch:assert> </sch:rule>
unit(unit) describes the structural unit indicated by the <citeStructure>.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="citeData" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="citeStructure"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element citeStructure
{
   tei_att.global.attributes,
   tei_att.citeStructurePart.attributes,
   attribute delim { text }?,
   attribute match { text },
   attribute unit { text }?,
   ( tei_citeData*, tei_citeStructure*, tei_model.descLike* )
}

5.1.47. <citedRange>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <citedRange from="3">p. 3ff</citedRange>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_att.pointing.attributes,
   tei_macro.phraseSeq
}

5.1.48. <cl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<cl> (clause) represents a grammatical clause. [18.1. Linguistic Segment Categories]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to indicate the type of clause, taking values such as finite, nonfinite, declarative, interrogative, relative etc. as appropriate.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element cl
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.49. <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader — Schema
Attributes
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
StatusRequired
Datatypeteidata.pointer
Suggested values include:
http://www.wikidata.org/entity/
(Wikidata) Base-URI of an entity on Wikidata.
Note

Specify the scheme/taxonomy the classification code is coming from.

Contained by
core: imprint
header: textClass
May containCharacter data only
Note

Classification of the genre of the play is done by re-using Wikidata entities.

Example
<textClass>  <keywords>   <term type="genreTitle">Tragedy</term>  </keywords>  <classCode scheme="http://www.wikidata.org/entity/">Q80930</classCode> </textClass>
Genre classification of the play Goethe: Egmont.
Example
<classCode scheme="http://www.wikidata.org/entity/">Q40831</classCode>
The play Schnitzler: Komtesse Mizzi is classified as a "comedy".
Example
<classCode scheme="http://www.wikidata.org/entity/">Q131084</classCode>
The "libretto" to the opera Wagner: Lohengrin.
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element classCode
{
   tei_att.global.attributes,
   attribute scheme { "http://www.wikidata.org/entity/" },
   text
}

5.1.50. <classDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<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]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { tei_att.global.attributes, tei_taxonomy+ }

5.1.51. <closer>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_signed
    | tei_dateline
    | tei_salute
    | tei_model.phrase
    | tei_model.global
   )*
}

5.1.52. <conversion>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Moduleheader — Schema
Attributes
fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
StatusRequired
Datatypeteidata.pointer
toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
StatusRequired
Datatypeteidata.pointer
Contained by
header: unitDef
May containEmpty element
Note

The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element conversion
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.formula.attributes,
   tei_att.locatable.attributes,
   attribute fromUnit { text },
   attribute toUnit { text },
   empty
}

5.1.53. <corr>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.54. <correction>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
linking: ab
Note

May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correction
{
   tei_att.global.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   tei_model.pLike+
}

5.1.55. <correspAction>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader — Schema
Attributes
typedescribes the nature of the action.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
Contained by
header: correspDesc
May contain
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.correspActionPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   attribute type
   {
      "sent" | "received" | "transmitted" | "redirected" | "forwarded"
   }?,
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

5.1.56. <correspContext>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader — Schema
Attributes
Member of
Contained by
header: correspDesc
May contain
linking: ab
Content model
<content>
 <classRef key="model.correspContextPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correspContext
{
   tei_att.global.attributes,
   tei_model.correspContextPart+
}

5.1.57. <correspDesc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Moduleheader — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.correspDescPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspDesc
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.typed.attributes,
   ( tei_model.correspDescPart+ | tei_model.pLike+ )
}

5.1.58. <creation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
Moduleheader — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
Note

The <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.

It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <elementRef key="listChange"/>
 </alternate>
</content>
    
Schema Declaration
element creation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   ( text | tei_model.limitedPhrase | tei_listChange )*
}

5.1.59. <date>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<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]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   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.typed.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

5.1.60. <dateline>

<dateline> (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Example
<dateline>Offenbach am Mayn, gedruckt bey Ulrich Weiß, 1765.</dateline>
Example taken from André: Der Comödienfeind.
Example
<dateline>Am verhängnißvollen 24sten Februar.</dateline>
Example
<dateline>Geschrieben in der Ostermesse. 1781.</dateline>
Example taken from Schiller: Die Räuber
Example
<dateline>Между декабрем 1750 и ноябрем 1751</dateline>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
  <elementRef key="docDate"/>
 </alternate>
</content>
    
Schema Declaration
element dateline
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.global
    | tei_docDate
   )*
}

5.1.61. <del>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility).

There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.62. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]
Modulecore — Schema
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
deprecationInfo
(deprecation information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec module="tei"  ident="teidata.point"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
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
<listEvent>  <event type="printwhen="1745">   <desc/>  </event>  <event type="premierewhen="1745">   <desc/>  </event> </listEvent>
Empty <desc> elements in the <standOff> container of the play Gellert: Die Betschwester. The dates of publication and the premiere are extracted from the when of the corresponding <event>. If there is no more information available the <desc> can be used as an empty element, but has to be included due to the default TEI content model of the parent element.
Example
<listEvent>  <event type="printwhen="1919">   <desc> "Erscheinen konnte das Werk erst nach Aufhebung der      Zensur. Noch am 13. Dezember 1918 erschien der Epilog als      Sonderheft der Fackel, weitere Teile (mit jeweils zwei      Akten) folgten im April, August und (wahrscheinlich)      September 1919." (Wikipedia)   </desc>  </event>  <event type="premierewhen="1964">   <desc> "1964: Wiener Festwochen im Theater an der Wien (Regie:      Leopold Lindtberg). Erste szenische Aufführung mit 42      Szenen des Dramas, nach einer Bühnenfassung von Heinrich      Fischer." (Wikipedia)   </desc>  </event>  <event type="writtennotBefore="1915"   notAfter="1922">   <desc>"in den Jahren 1915–1922 entstanden" (Wikipedia)</desc>  </event> </listEvent>
Descriptions of events in the <standOff> container of the play Kraus: Die Letzten Tage der Menschheit.
SchematronA <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute type { "deprecationInfo" }?,
   tei_macro.limitedContent
}

5.1.63. <distinct>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
Modulecore — Schema
Attributes
typespecifies the sublanguage or register to which the word or phrase is being assigned.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
timespecifies how the phrase is distinct diachronically.
StatusOptional
Datatypeteidata.text
spacespecifies how the phrase is distinct diatopically.
StatusOptional
Datatypeteidata.text
socialspecifies how the phrase is distinct diastratically.
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distinct
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute time { text }?,
   attribute space { text }?,
   attribute social { text }?,
   tei_macro.phraseSeq
}

5.1.64. <distributor>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distributor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq
}

5.1.65. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure — Schema
Attributes
n(number) Number of act or scene
Derived fromatt.global
StatusOptional
Datatypeteidata.text
typeClassifies the segment
StatusRecommended
Datatypeteidata.text
Suggested values include:
act
(Act) Top-level structural division of a play, also "Aufzug", "Auftritt" in German
scene
(Scene) Lower level structural division of a play
Note

Although global usage of values of this attribute is not restricted, the API evaluates the values act and scene on the <div> elements in the text proper. If applicable these attribute values should be used to classify the segments.

Other values of type that are used (in GerDraCor and RusDraCor) to classify non-act or -scene divisions are:

  • appendix: Appendix
  • configuration:

    Change of character constellation, which is not marked as scene change

  • dedication: Dedication
  • dictionary

    Was in use at some point in time but not anymore

  • entracte
  • epigraph
  • epilogue
  • interlude: auch Zwischenspiel
  • location: Location change
  • notes
  • ouverture
  • part
  • postface
  • preface
  • prologue
  • review
  • set: Setting. Could use the designated element <set> instead.
  • subscene: Subscene
  • tableau: Tableau, auch: Kartina
  • variant

There are some values that are used in some plays of Johann Nestroy exclusively:

  • unten
  • oben
  • cholerisch
  • phlegmatisch
  • melancholisch
  • sanguinisch

In general it is recommended that encoders document the additional values used for type on <div> in an <encodingDesc> in the corpus.xml.

Member of
Contained by
textstructure: back body div front
May contain
Example
<div type="scene">  <head>Fünfte Szene</head>  <sp who="#poniatowsky">   <speaker>PONIATOWSKY.</speaker>   <lg>    <l>Der alte Woiwode predigt gut,</l>    <l>Doch seine Weisheit kommt von seinen Haaren,</l>    <l>Ich lobe den, der aus der Kirche läuft.</l>   </lg>  </sp> </div>
A short "scene" in the play Hebbel: Demetrius.
Example
<div type="scene">  <head>Явление 13</head>  <sp who="#zdravomyslov">   <speaker>Г. Здравомыслов.</speaker>   <p> Что это значит? Прогневать я не мог, я ни в чем не      проступился; но докучать не надо, ее нрав более умягчается      повиновением. На прекрасную ее племянницу надежду свою      полагаю; пойду, однако ж, постараюсь узнать причину      холодного сего приема.   </p>  </sp>  <trailer>Конец четвертого действия.</trailer> </div>
The last "scene" of the fourth act of the play Дашкова: Тоисиоков.
Schematron
<sch:rule context="tei:l//tei:div"> <sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.divLike.attributes,
   tei_att.placement.attributes,
   attribute n { text }?,
   attribute type { "act" | "scene" }?,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.divLike | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
                  (
                     (
                        ( tei_model.divLike | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

5.1.66. <divGen>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
Modulecore — Schema
Attributes
typespecifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
index
an index is to be generated and inserted at this point.
toc
a table of contents
figlist
a list of figures
tablist
a list of tables
Note

Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

Member of
Contained by
textstructure: back body div front
May contain
core: head
Note

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

Content model
<content>
 <classRef key="model.headLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element divGen
{
   tei_att.global.attributes,
   attribute type { text }?,
   tei_model.headLike*
}

5.1.67. <docAuthor>

<docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Note

Used inconsistently throughout the corpora. Needs to be revised!

Example
<front>  <docAuthor>Gotthold Ephraim Lessing</docAuthor>  <docTitle>   <titlePart type="main">Emilia Galotti</titlePart>   <titlePart type="sub">Ein Trauerspiel in fünf Aufzügen</titlePart>   <pb n="128"/>  </docTitle> <!-- ... --> </front>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docAuthor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.68. <docDate>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Note

Cf. the general <date> element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docDate
{
   tei_att.global.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq
}

5.1.69. <docEdition>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Note

Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element docEdition { tei_att.global.attributes, tei_macro.paraContent }

5.1.70. <docImprint>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Note

Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="pubPlace"/>
  <elementRef key="docDate"/>
  <elementRef key="publisher"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element docImprint
{
   tei_att.global.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_pubPlace
    | tei_docDate
    | tei_publisher
    | tei_model.global
   )*
}

5.1.71. <docTitle>

<docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Example
<front>  <docTitle>   <titlePart type="main">Die beiden Billets.</titlePart>   <titlePart type="sub">Ein Lustspiel in einem Akt nach Florian von Anton-Wall.</titlePart>  </docTitle> <!-- ... --> </front>
Example taken from Heyne: Die beiden Billets
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="titlePart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element docTitle
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   ( tei_model.global*, ( ( tei_titlePart, tei_model.global* )+ ) )
}

5.1.72. <edition>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader — Schema
Attributes
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.73. <editionStmt>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader — Schema
Attributes
Contained by
May contain
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
}

5.1.74. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

A consistent format should be adopted.

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

Example
<bibl type="originalSource">  <author>William Shakespeare</author>: <title level="a">Romeo und Julia</title>. In: <title level="s">Sämtliche Werke in vier Bänden</title>. Herausgegeben von <editor>Anselm Schlösser</editor>. Band <biblScope unit="volume">4</biblScope>. <pubPlace>Berlin</pubPlace>: <publisher>Aufbau</publisher>  <date>1975</date>, S. <biblScope unit="pagefrom="83to="178">83–178</biblScope>. </bibl>
Example from GerShDraCor
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
}

5.1.75. <editorialDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.editorialDeclPart"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl
{
   tei_att.global.attributes,
   ( tei_model.pLike | tei_model.editorialDeclPart )+
}

5.1.76. <ellipsis>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
core: desc
Note

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

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="metamark"/>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element ellipsis
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_att.timed.attributes,
   ( metamark, tei_model.descLike?, supplied? )
}

5.1.77. <email>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

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

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.78. <emph>

<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Example
<sp who="#titus">  <speaker>TITUS.</speaker>  <p> Oh, der Anzug hat nur zu viel Gärtnerartiges, er is übersä't    mit Fleck, er is <emph>aufgegangen</emph> bei die Ellbögen    und an verschiedenen Orten; weil ich nie ein Paraplü trag',    wird er auch häufig <emph>begossen</emph>, und wie er noch    in der Blüte war, hab' ich ihn oft wie eine Pflanze  <emph>versetzt</emph>.  </p> </sp>
Example taken from Nestroy: Der Talisman.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element emph
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.79. <encodingDesc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Schema
Attributes
Member of
Contained by
header: teiHeader
May contain
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element encodingDesc
{
   tei_att.global.attributes,
   ( tei_model.encodingDescPart | tei_model.pLike )+
}

5.1.80. <epigraph>

<epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Example
<epigraph>  <p> Nichts gibt so sehr das Gefühl der Unendlichkeit als wie die    Dummheit.  </p> </epigraph>
Example
<epigraph xml:lang="lat">  <cit>   <quote>    <l>Flectere si nequeo superos, acheronta movebo.</l>   </quote>  </cit> </epigraph>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.common"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element epigraph
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.common | tei_model.global )*
}

5.1.81. <epilogue>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<epilogue> (epilogue) contains the epilogue to a drama, typically spoken by an actor out of character, possibly in association with a particular performance or venue. [7.1.2. Prologues and Epilogues 7.1. Front and Back Matter ]
Moduledrama — Schema
Attributes
Member of
Contained by
textstructure: back front
May contain
Note

Contains optional headings, a sequence of one or more component-level elements, and an optional sequence of closing material.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element epilogue
{
   tei_att.global.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      ( ( tei_model.common, tei_model.global* )+ ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

5.1.82. <event>

<event> (event) contains data relating to anything of significance that happens in time. [14.3.1. Basic Principles]
Modulenamesdates — Schema
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
Note

The value of this attribute can be evaluated by the DraCor API. Use it to indicate date the event took place. The value can be a year only.

notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
Note

The value of this attribute can be evaluated by the DraCor API. Use it to indicate the earliest possible date the event took place. The value can be a year only.

notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
Note

The value of this attribute can be evaluated by the DraCor API. Use it to indicate the latest possible date the event took place. The value can be a year only.

typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRecommended
Datatypeteidata.enumerated
Suggested values include:
print
(Date printed) Date of the print publication as stated in the impressum
premiere
(Date premiered) Date of debut performance
written
(Date written) Date of writing
Note

The above mentioned values are supported by the DraCor API to encode the dates a play was written, first printed and performed for the first time. Other values are allowed but not evaluated by the API.

Member of
Contained by
May contain
Example
<event type="writtenwhen="1811">  <desc>geschrieben wahrscheinlich im Winter 1811</desc> </event>
Example see Github Issue.
Example
<event type="writtennotBefore="1836"  notAfter="1837">  <label>1836–1837</label> </event>
Written date of the play Büchner: Woyzeck.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <elementRef key="eventName"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.eventLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPerson"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPlace"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <classRef key="model.objectLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element event
{
   tei_att.global.attributes,
   tei_att.datable.attribute.period,
   tei_att.datable.w3c.attribute.from,
   tei_att.datable.w3c.attribute.to,
   tei_att.locatable.attributes,
   tei_att.naming.attributes,
   tei_att.sortable.attributes,
   attribute when { text }?,
   attribute notBefore { text }?,
   attribute notAfter { text }?,
   attribute type { "print" | "premiere" | "written" }?,
   (
      tei_idno*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ | eventName+ ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_linkGrp
       | tei_link
       | tei_idno
       | tei_ptr
      )*,
      tei_model.eventLike*,
      ( tei_model.personLike | tei_listPerson )*,
      ( tei_model.placeLike | listPlace )*,
      tei_model.objectLike*,
      ( tei_relation | tei_listRelation )*
   )
}

5.1.83. <expan>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.84. <extent>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.85. <figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images]
Modulefigures — Schema
Attributes
Member of
Contained by
May contain
Example
<figure>  <graphic url="http://images.zeno.org/Literatur/I/big/haup0031.jpg"/>  <ab>Glumms große Kretschamstube.</ab> </figure>
Example
<figure>  <graphic url="https://textgridlab.org/1.0/tgcrud/rest/textgrid:x3gp.0/data"/> </figure>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
    
Schema Declaration
element figure
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike
    | tei_model.common
    | figDesc
    | tei_model.graphicLike
    | tei_model.global
    | tei_model.divBottom
   )*
}

5.1.86. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Schema
Attributes
Contained by
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 type="main">Egmont</title> <!-- ... -->  </titleStmt>  <publicationStmt>   <publisher xml:id="dracor">DraCor</publisher> <!-- ... -->  </publicationStmt>  <sourceDesc>   <bibl type="digitalSource">    <name>TextGrid Repository</name> <!-- ... -->    <bibl type="originalSource">     <title> Goethes Werke.      <!-- ... -->     </title>    </bibl>   </bibl>  </sourceDesc> </fileDesc>
Example taken adapted from Goethe: Egmont.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   tei_att.global.attributes,
   (
      (
         tei_titleStmt,
         tei_editionStmt?,
         tei_extent?,
         tei_publicationStmt,
         tei_seriesStmt*,
         tei_notesStmt?
      ),
      tei_sourceDesc+
   )
}

5.1.87. <floatingText>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Note

A floating text has the same content as any other <text> and may thus be interrupted by another floating text, or contain a <group> of tesselated texts.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="1" maxOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element floatingText
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   (
      tei_model.global*,
      ( ( tei_front, tei_model.global* )? ),
      ( tei_body | tei_group ),
      tei_model.global*,
      ( ( tei_back, tei_model.global* )? )
   )
}

5.1.88. <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
<sp who="#baronesse_von_ehegestern">  <speaker>B. v. Ehegestern</speaker>  <stage>(für sich.)</stage>  <p>   <foreign xml:lang="fre">Mais, mon Dieu, qu'elle      confidence!</foreign>   <stage>(laut:)</stage> Nun es kann    nicht lange <foreign xml:lang="fre">Mystère</foreign>    bleiben. <foreign xml:lang="fre">Voilà une lettre.</foreign>    Der Doktor hat ihn abgegeben.  </p> </sp>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.89. <forename>

<forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names]
Modulenamesdates — Schema
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
patronym
(Patronym) Father-derived middle name. Used for example in in RusDraCor.
Member of
Contained by
May contain
Example
<persName>  <forename>Hermann</forename>  <surname>Bahr</surname> </persName>
Example
<persName>  <forename>Christian</forename>  <forename>Fürchtegott</forename>  <surname>Gellert</surname> </persName>
Example
<persName>  <forename>Евдокия</forename>  <forename type="patronym">Петровна</forename>  <surname>Ростопчина</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,
   attribute type { "patronym" }?,
   tei_macro.phraseSeq
}

5.1.90. <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure — Schema
Attributes
Contained by
textstructure: floatingText text
May contain
Note

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

Example
<front>  <titlePage>   <docAuthor>Gotthold Ephraim Lessing</docAuthor>   <docTitle>    <titlePart type="main">Emilia Galotti</titlePart>    <titlePart type="sub">Ein Trauerspiel in fünf Aufzügen</titlePart>   </docTitle>  </titlePage>  <pb n="128"/>  <castList>   <head>Personen.</head>   <castItem>    <role>Emilia Galotti.</role>   </castItem>   <castGroup rend="braced">    <castItem>     <role>Odoardo,</role>    </castItem>    <castItem>     <role>Claudia Galotti,</role>    </castItem>    <roleDesc>Eltern der Emilia.</roleDesc>   </castGroup>   <castItem>    <role>Hettore Gonzaga,</role>    <roleDesc>Prinz von Guastalla.</roleDesc>   </castItem>   <castItem>    <role>Marinelli,</role>    <roleDesc>Kammerherr des Prinzen.</roleDesc>   </castItem>   <castItem>    <role>Camillo Rota,</role>    <roleDesc>einer von des Prinzen Räten.</roleDesc>   </castItem>   <castItem>    <role>Conti,</role>    <roleDesc>Maler.</roleDesc>   </castItem>   <castItem>    <role>Graf Appiani.</role>   </castItem>   <castItem>    <role>Gräfin Orsina.</role>   </castItem>   <castItem>    <role>Angelo,</role> und <role>einige Bediente.</role>   </castItem>   <pb n="128"/>  </castList> </front>
Example
<front>  <div type="front">   <head>Johann Nestroy</head>   <head>Der Talisman</head>   <head>Posse mit Gesang in drei Aufzügen</head>   <pb n="244"/>  </div>  <castList>   <head>Personen.</head>   <castItem>Titus Feuerfuchs, ein vazierender Barbiergeselle.</castItem>   <castItem>Frau von Cypressenburg, Witwe.</castItem>   <castItem>Emma, ihre Tochter.</castItem> <!-- ... -->  </castList>  <set>   <p> Die Handlung spielt auf dem Gute der Frau von      Cypressenburg, nahe bei einer großen Stadt.   </p>  </set> </front>
The frontmatter of the play Nestroy: Der Talisman.
<div type="front">  <head>Johann Nestroy</head>  <head>Der Talisman</head>  <head>Posse mit Gesang in drei Aufzügen</head>  <pb n="244"/> </div>
will be deprecated though and replaced with <titlePage>.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence minOccurs="1" maxOccurs="1">
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0" maxOccurs="1">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   tei_att.global.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike
       | tei_model.pLike.front
       | tei_model.global
      )*,
      (
         (
            (
               (
                  tei_model.div1Like,
                  (
                     tei_model.div1Like
                   | tei_model.frontPart
                   | tei_model.global
                  )*
               )
             | (
                  tei_model.divLike,
                  (
                     tei_model.divLike
                   | tei_model.frontPart
                   | tei_model.global
                  )*
               )
            ),
            (
               (
                  tei_model.divBottom,
                  ( tei_model.divBottom | tei_model.global )*
               )?
            )
         )?
      )
   )
}

5.1.91. <funder>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq.limited
}

5.1.92. <gap>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Modulecore — Schema
Attributes
reason(reason) gives the reason for omission.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
cancelled
(cancelled)
deleted
(deleted)
editorial
(editorial) for features omitted from transcription due to editorial policy
illegible
(illegible)
inaudible
(inaudible)
irrelevant
(irrelevant)
sampling
(sampling)
agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
(rubbing) damage results from rubbing of the leaf edges
mildew
(mildew) damage results from mildew on the leaf surface
smoke
(smoke) damage results from smoke
Member of
Contained by
May contain
core: desc
Note

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element gap
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   tei_att.timed.attributes,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
         )+
      }
   }?,
   attribute agent { text }?,
   ( tei_model.descLike | tei_model.certLike )*
}

5.1.93. <gb>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<gb> (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex. [3.11.3. Milestone Elements]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <gb> elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.

The type attribute may be used to further characterize the gathering in any respect.

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element gb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.94. <genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [14.2.1. Personal Names]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Example
<author>  <persName type="nobility">   <forename>Екатерина</forename>   <genName>II</genName>  </persName>  <persName>   <forename>София</forename>   <forename>Августа</forename>   <forename>Фредерика</forename>   <surname>Ангальт-Цербстская</surname>  </persName>  <persName xml:lang="eng">   <forename>Catherine</forename>   <genName>II</genName>  </persName>  <idno type="wikidata">Q36450</idno> </author>
Encoding of the name of the author "Catherine II" of the play Расстроенная семья острожками и подозрениями.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element genName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.95. <geoDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <geo> element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration]
Moduleheader — Schema
Attributes
datumsupplies a commonly used code name for the datum employed.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
WGS84
(World Geodetic System) a pair of numbers to be interpreted as latitude followed by longitude according to the World Geodetic System.[Default]
MGRS
(Military Grid Reference System) values supplied follow the Military Grid Reference System, which designates grid zones in a string of letters and numbers that distinctly indicate each square meter on the planet.
OSGB36
(ordnance survey great britain) the value supplied is to be interpreted as a British National Grid Reference.
ED50
(European Datum coordinate system) the value supplied is to be interpreted as latitude followed by longitude according to the European Datum coordinate system.
Member of
Contained by
header: encodingDesc
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geoDecl
{
   tei_att.global.attributes,
   attribute datum { "WGS84" | "MGRS" | "OSGB36" | "ED50" }?,
   tei_macro.phraseSeq
}

5.1.96. <gloss>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gloss
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.97. <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
core: desc
Note

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

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

Example
<figure>  <graphic url="http://images.zeno.org/Literatur/I/big/haup0031.jpg"/>  <ab>Glumms große Kretschamstube.</ab> </figure>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element graphic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.media.attributes,
   tei_att.resourced.attributes,
   tei_att.typed.attributes,
   tei_model.descLike*
}

5.1.98. <group>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text]
Moduletextstructure — Schema
Attributes
Contained by
textstructure: floatingText group
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="1" maxOccurs="1">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="text"/>
    <elementRef key="group"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="text"/>
    <elementRef key="group"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
  <classRef key="model.divBottom"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element group
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         ( tei_text | tei_group ),
         ( tei_text | tei_group | tei_model.global )*
      ),
      tei_model.divBottom*
   )
}

5.1.99. <handNote>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader — Schema
Attributes
Contained by
May contain
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element handNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

5.1.100. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

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

Example
<div type="act">  <head>Erster Aufzug</head>  <stage> Die Bühne stellt einen Dorfplatz vor. In der Mitte gegen den    Hintergrund ein Brunnen, links eine Gartenmauer mit einer    kleinen, offenstehenden Tür, welche in den Herrschaftsgarten    führt.  </stage>  <div type="scene">   <head>Erster Auftritt</head>   <stage> Bauernmädchen, darunter Hannerl, treten während dem      Ritornell des folgenden Chores aus dem Hintergrunde links      auf.   </stage>   <stage>Chor.</stage>  </div> </div>
Headings of an act and a scene in Nestroy: Der Talisman.
Example
<argument>  <head>Inhalt des trauer-spiels.</head>  <p> Michael Balbus, käyser Leonis Armenii oberster    feldhauptmann, nach dem er zu unterschiedenen mahlen wegen    seiner untreu und verleumbdungen angeklaget, verschweret    sich wider den käyser, welcher ihn durch Exabolium, seinen    geheimesten rath, offt von seiner leichtfertigkeit    abzustehen ermahnet.   <!-- ... -->  </p> </argument>
Example
<castList>  <head>In stummen Rollen</head>  <castGroup>   <castItem>Kardinal Dupin, Erzbischof von Paris</castItem>   <castItem>Minister</castItem> <!-- ... -->  </castGroup> </castList>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

5.1.101. <headItem>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
Modulecore — Schema
Attributes
Contained by
core: list
May contain
Note

The <headItem> element may appear only if each item in the list is preceded by a <label>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headItem { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.102. <headLabel>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
Modulecore — Schema
Attributes
Contained by
core: list
May contain
Note

The <headLabel> element may appear only if each item in the list is preceded by a <label>.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headLabel { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.103. <hi>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.104. <hyphenation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
some
end-of-line hyphenation has been retained in some cases.[Default]
hard
all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
none
all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element hyphenation
{
   tei_att.global.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   tei_model.pLike+
}

5.1.105. <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader — Schema
Attributes
xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Derived fromatt.global
StatusOptional
Datatypeteidata.pointer
Note

In DraCor this is only used on the element <idno> that contains the corpus name in the corpus.xml.

typeClassifies the identifier
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
URL
URL
wikidata
wikidata
pnd
GND
URI
URI
repo
(Repository URL) URL of the (GitHub) Repository of a Corpus
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
<author>  <persName>   <forename>Ferdinand</forename>   <surname>Raimund</surname>  </persName>  <idno type="wikidata">Q45025</idno>  <idno type="pnd">118597914</idno> </author>
Identifiers of the author of the play Raimund: Die gefesselte Phantasie
Example
<publicationStmt>  <publisher xml:id="dracor">DraCor</publisher>  <idno type="URL">https://dracor.org</idno>  <availability>   <licence>    <ab>CC0 1.0</ab>    <ref target="https://creativecommons.org/publicdomain/zero/1.0/">Licence</ref>   </licence>  </availability> </publicationStmt>
Provide an identifier for DraCor (use the URL)
Example
<bibl type="digitalSource">  <name>TextGrid Repository</name>  <idno type="URL">http://www.textgridrep.org/textgrid:t97f.0</idno> <!-- ... --> </bibl>
URL as an identifier of the digital source of the play Raimund: Die gefesselte Phantasie
Example
<sourceDesc>  <bibl type="digitalSource">   <name>Библиотека Максима Мошкова (lib.ru)</name>   <idno type="URL">http://az.lib.ru/p/plawilxshikow_p_a/text_0040.shtml</idno>   <availability status="free">    <p> In the public domain.    </p>   </availability>   <bibl type="originalSource">    <title>Русская драматургия XVIII века. – М.: Современник,        1986. – С. 445–460.</title>   </bibl>  </bibl> </sourceDesc>
SchematronIn the corpus.xml (root element <teiCorpus>) the identifier <idno> containing the corpus name (see Feature corpus_name) SHOULD have an xml:base attribute with the value https://dracor.org/.
<sch:rule context="tei:idno[@type eq 'URI' and parent::tei:publicationStmt and ancestor::tei:teiCorpus]"  role="warning"> <sch:assert test="@xml:base/string() eq 'https://dracor.org/'"> The idno element in publicationStmt in the teiCorpus SHOULD have an xml:base attribute with the value 'https://dracor.org/'. </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.sortable.attributes,
   attribute xml:base { text }?,
   attribute type { "URL" | "wikidata" | "pnd" | "URI" | "repo" }?,
   ( text | tei_model.gLike | tei_idno )*
}

5.1.106. <imprimatur>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<imprimatur> (imprimatur) contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
Member of
Contained by
textstructure: titlePage
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element imprimatur { tei_att.global.attributes, tei_macro.paraContent }

5.1.107. <imprint>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Schema
Attributes
Contained by
core: monogr
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt" minOccurs="0"
    maxOccurs="unbounded"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element imprint
{
   tei_att.global.attributes,
   (
      ( tei_classCode | tei_catRef )*,
      (
         (
            ( tei_model.imprintPart | tei_model.dateLike ),
            tei_respStmt*,
            tei_model.global*
         )+
      )
   )
}

5.1.108. <index>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
Modulecore — Schema
Attributes
indexNamea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), supplying a name to specify which index (of several) the index entry belongs to.
StatusOptional
Datatypeteidata.name
Note

This attribute makes it possible to create multiple indexes for a text.

Member of
Contained by
May contain
core: index term
Content model
<content>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="term"/>
  <elementRef key="index" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element index
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.spanning.attributes,
   attribute indexName { text }?,
   ( ( tei_term, tei_index? )* )
}

5.1.109. <interp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [18.3. Spans and Interpretations]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
core: desc
character data
Note

Generally, each <interp> element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an <interp> with any textual element through its ana attribute.

Alternatively (or, in addition) an <interp> may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the <interp> applies.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element interp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.interpLike.attributes,
   ( text | tei_model.gLike | tei_model.descLike | tei_model.certLike )*
}

5.1.110. <interpGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [18.3. Spans and Interpretations]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
analysis: interp
core: desc
Note

Any number of <interp> elements.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="interp" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element interpGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.interpLike.attributes,
   ( tei_model.descLike*, tei_interp+ )
}

5.1.111. <interpretation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element interpretation { tei_att.global.attributes, tei_model.pLike+ }

5.1.112. <item>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore — Schema
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.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_macro.specialPara
}

5.1.113. <join>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<join> (join) identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it. [17.7. Aggregation]
Modulelinking — Schema
Attributes
resultspecifies the name of an element which this aggregation may be understood to represent.
StatusOptional
Datatypeteidata.name
scopeindicates whether the targets to be joined include the entire element indicated (the entire subtree including its root), or just the children of the target (the branches of the subtree).
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
root
the rooted subtrees indicated by the target attribute are joined, each subtree become a child of the virtual element created by the join[Default]
branches
the children of the subtrees indicated by the target attribute become the children of the virtual element (i.e. the roots of the subtrees are discarded)
Member of
Contained by
May contain
core: desc
Schematron
<sch:rule context="tei:join"> <sch:assert test="contains( normalize-space( @target ),' ')"> You must supply at least two values for @target on <sch:name/> </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element join
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   attribute result { text }?,
   attribute scope { "root" | "branches" }?,
   ( tei_model.descLike | tei_model.certLike )*
}

5.1.114. <joinGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<joinGrp> (join group) groups a collection of <join> elements and possibly pointers. [17.7. Aggregation]
Modulelinking — Schema
Attributes
resultsupplies the default value for the result on each <join> included within the group.
StatusOptional
Datatypeteidata.name
Member of
Contained by
May contain
core: desc gloss ptr
linking: join
Note

Any number of <join> or <ptr> elements.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="equiv"/>
   <elementRef key="gloss"/>
   <classRef key="model.descLike"/>
  </alternate>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="join"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element joinGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.group.attributes,
   attribute result { text }?,
   ( ( equiv | tei_gloss | tei_model.descLike )*, ( tei_join | tei_ptr )+ )
}

5.1.115. <keywords>

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

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

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

Example
<keywords>  <term type="genreTitle">Tragedy</term> </keywords>
Keywords used to classify genre of the play Laube: Struensee.
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="term" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="list"/>
 </alternate>
</content>
    
Schema Declaration
element keywords
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   ( tei_term+ | tei_list )
}

5.1.116. <l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore — Schema
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Suggested values include:
indent
(Indented) Indicates whether or not a verse line is indented
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Derived fromatt.fragmentable
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
F
(Final) Final part of an interrupted or fragmented verse line
I
(Initial) Initial part of an interrupted or fragmented verse line
M
(Medial) Middle part of an interrupted or fragmented verse line
Note

Consecutive verse lines that carry this attribute should be considered as a single unit. On the use of part in dramatic texts see also TEI Guidelines. See also this issue on GitHub.

Member of
Contained by
May contain
Example
<sp who="#chor_2-23">  <speaker>CHOR.</speaker>  <lg>   <l>'s ist nirgends so wie in dem Haus amüsant,</l>   <l>Denn hier sind die Karten und Würfel verbannt,</l>   <l>Bei Frau Von Cypressenburg in Soiree,</l>   <l>Da huldigt den Musen man nur und dem Tee.</l>  </lg>  <stage> Während dem Chor haben Bediente einen großen gedeckten    Teetisch gebracht und die Stühle gesetzt.  </stage> </sp>
Example
<sp who="#TretijMistik">  <speaker>Третий мистик</speaker>  <l part="F">Наступит событие.</l> </sp> <sp who="#Pero">  <speaker>Пьеро</speaker>  <l>О, вечный ужас, вечный мрак!</l> </sp> <sp who="#PervyjMistik">  <speaker>Первый мистик</speaker>  <l part="I">Ты ждешь?</l> </sp> <sp who="#VtorojMistik">  <speaker>Второй мистик</speaker>  <l part="M">Я жду.</l> </sp> <sp who="#TretijMistik">  <speaker>Третий мистик</speaker>  <l part="F">Уж близко прибытие:</l>  <l>За окном нам ветер подал знак.</l> </sp>
Блок: Балаганчик to illustrate usage of part; would need the source as well.
Example
<sp who="#rusalki">  <speaker>Русалки</speaker>  <lg>   <l rend="indent">Веселой толпою</l>   <l rend="indent">С глубокого дна</l>   <l rend="indent">Мы ночью всплываем,</l>   <l rend="indent">Нас греет луна.</l>   <l>Любо нам порой ночною</l>   <l>Дно речное покидать,</l>   <l>Любо вольной головою</l>   <l>Высь речную разрезать,</l>   <l>Подавать друг дружке голос,</l>   <l>Воздух звонкий раздражать,</l>   <l>И зеленый, влажный волос</l>   <l>В нем сушить и отряхать.</l>  </lg> </sp>
Indented lines in the play Пушкин: Русалка.
Schematron
<sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element l
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.source.attribute.source,
   tei_att.cmc.attributes,
   attribute rend { list { "indent"+ } }?,
   attribute part { "F" | "I" | "M" }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

5.1.117. <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore — Schema
Attributes
Member of
Contained by
May containCharacter data only
Note

In DraCor <label> is used exclusively to attach a non-iso date/date string to an event.

Example
<event type="writtennotBefore="1647"  notAfter="1650">  <label>1647–1650</label> </event>
Encoding of the written date of Gryphius: Horribilicribrifax Teutsch.
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element label
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   text
}

5.1.118. <langUsage>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
linking: ab
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | tei_language+ )
}

5.1.119. <language>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader — Schema
Attributes
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

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

Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   tei_att.global.attributes,
   tei_att.scope.attributes,
   attribute ident { text },
   attribute usage { text }?,
   tei_macro.phraseSeq.limited
}

5.1.120. <lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

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

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

ExampleThis example shows the encoding of the beginning of each new topographic line within a metrical line, indicating where it occurs in both the 1667 and 1674 editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
ExampleThis example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.121. <lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

Example
<sp who="#flora #salome">  <speaker>FLORA, SALOME.</speaker>  <lg>   <l>'s laßt sich drüber nix sag'n</l>   <l>Mit ein'm orndlichen Mag'n.</l>   <pb n="312"/>  </lg> </sp>
Grouping of lines in Nestroy: Der Talisman.
Schematron
<sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_lg
      ),
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_model.global
       | tei_lg
      )*,
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

5.1.122. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Schema
Attributes
Member of
Contained by
header: availability
linking: annotation
May contain
Example
<publicationStmt>  <publisher xml:id="dracor">DraCor</publisher>  <idno type="URL">https://dracor.org</idno>  <availability>   <licence>    <ab>CC0 1.0</ab>    <ref target="https://creativecommons.org/publicdomain/zero/1.0/">Licence</ref>   </licence>  </availability> </publicationStmt> <!-- ... --> <sourceDesc>  <bibl type="digitalSource">   <name>TextGrid Repository</name>   <idno type="URL">http://www.textgridrep.org/textgrid:npsg.0</idno>   <availability>    <licence>     <ab>CC-BY-3.0</ab>     <ref target="http://creativecommons.org/licenses/by/3.0/de/legalcode">Lizenzvertrag</ref>    </licence>   </availability>   <bibl type="originalSource">    <title>Franz Grillparzer: Sämtliche Werke. Ausgewählte        Briefe, Gespräche, Berichte. Herausgegeben von Peter Frank        und Karl Pörnbacher, München: Hanser, [1960–1965].</title>   </bibl>  </bibl> </sourceDesc>
The text of the play Grillparzer: Des Meeres und der Liebe Wellen is in the public domain and thus licensed under a CC0 licence, as is the encoding by DraCor. The digital source is also contained in TextGrid and was licensed under a CC BY 3.0 licence.
Example
<licence>  <ab>CC-BY-3.0</ab>  <ref target="http://creativecommons.org/licenses/by/3.0/de/legalcode">Lizenzvertrag</ref> </licence>
The digital source of the play Goethe: Torquato Tasso distributed by TextGrid is licensed under a CC-BY 3.0 licence.
Example
<licence>  <ab>CC BY-NC 3.0</ab>  <ref target="http://creativecommons.org/licenses/by-nc/3.0/de/">Lizenzvertrag</ref> </licence>
The digital source of the play Kotzebue: Der Schutzgeist distributed by the DTA is licensed under a CC-BY-NC 3.0 licence.
Example
<licence>  <ab>CC BY-SA 3.0</ab>  <ref target="https://creativecommons.org/licenses/by-sa/3.0/deed.ru">Licence</ref> </licence>
The digital source of the play Pushkin: Boris Godunov is licensed by Wikisource under a CC BY-SA 3.0 license.
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
}

5.1.124. <linkGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<linkGrp> (link group) defines a collection of associations or hypertextual links. [17.1. Links]
Modulelinking — Schema
Attributes
Member of
Contained by
May contain
core: desc ptr
linking: link
Note

May contain one or more <link> or <ptr> elements.

A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element linkGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.group.attributes,
   ( tei_model.descLike*, ( tei_link | tei_ptr )+ )
}

5.1.125. <list>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

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

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

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

Member of
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.

Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   attribute type
   {
      "gloss" | "index" | "instructions" | "litany" | "syllogism"
   }?,
   (
      ( tei_model.divTop | tei_model.global | tei_desc* )*,
      (
         ( ( tei_item, tei_model.global* )+ )
       | (
            tei_headLabel?,
            tei_headItem?,
            ( ( tei_label, tei_model.global*, tei_item, tei_model.global* )+ )
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

5.1.126. <listAnnotation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<listAnnotation> contains a list of annotations, typically encoded as <annotation>, <annotationBlock>, or <note>, possibly organized with nested <listAnnotation> elements. [17.10. The standOff Container]
Modulelinking — Schema
Attributes
Member of
Contained by
May contain
Note

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

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.labelLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.annotationLike"/>
   <elementRef key="listAnnotation"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listAnnotation
{
   tei_att.global.attributes,
   tei_att.notated.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      tei_model.labelLike*,
      ( tei_model.annotationLike | tei_listAnnotation )+
   )
}

5.1.127. <listBibl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<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]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.milestoneLike | tei_relation | tei_listRelation )*,
      (
         (
            tei_model.biblLike+,
            ( tei_model.milestoneLike | tei_relation | tei_listRelation )*
         )+
      )
   )
}

5.1.128. <listChange>

<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]
Moduleheader — Schema
Attributes
orderedindicates whether the ordering of its child <change> elements is to be considered significant or not.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Member of
Contained by
May contain
header: change
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="2017-01-06">(dlina) file conversion from source</change>   <change when="2017-08-04">(ff) structural cleanup</change>   <change when="2018-09-25">(ff) formalities, IDs</change>  </listChange> </revisionDesc>
List of changes in the <revisionDesc> of the play Engel: Eid und Pflicht.
Content model
<content>
 <elementRef key="change" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element listChange
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute ordered { text }?,
   tei_change+
}

5.1.129. <listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [14.3.1. Basic Principles]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <event type="printwhen="1813">   <desc/>  </event>  <event type="premierewhen="1811">   <desc/>  </event>  <event type="writtenwhen="1811">   <desc>geschrieben wahrscheinlich im Winter 1811</desc>  </event> </listEvent>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.eventLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listEvent
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      ( ( tei_model.eventLike+, ( tei_relation | tei_listRelation )* )+ )
   )
}

5.1.130. <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Example
<profileDesc>  <particDesc>   <listPerson>    <person xml:id="michlsex="MALE">     <persName>Michl</persName>    </person>    <person xml:id="loislsex="MALE">     <persName>Loisl</persName>    </person>    <person xml:id="veitsex="MALE">     <persName>Veit</persName>    </person>    <person xml:id="martinsex="MALE">     <persName>Martin</persName>    </person>    <personGrp xml:id="die_bursche"     sex="MALE">     <name>Die Bursche</name>     <name type="variant">Alle Bursche</name>    </personGrp> <!-- ... -->   </listPerson>  </particDesc> </profileDesc>
Characters listed in the <particDesc> of the play Anzengruber: Die Kreuzelschreiber.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.personLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPerson"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPerson
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      (
         (
            ( tei_model.personLike | tei_listPerson )+,
            ( tei_relation | tei_listRelation )*
         )+
      )
   )
}

5.1.131. <listPrefixDef>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="prefixDef"/>
   <elementRef key="listPrefixDef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listPrefixDef
{
   tei_att.global.attributes,
   ( tei_desc*, ( tei_prefixDef | tei_listPrefixDef )+ )
}

5.1.132. <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [14.3.2.3. Personal Relationships]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
core: desc head p
linking: ab
Note

There are currently two types of <listRelation> evaluated by the DraCor API. One is the list of relations between characters. The other is the <listRelation> in <standOff> used to link a play to Wikidata (see Wikidata QID of a Play).

Example
<listRelation>  <relation name="spouses"   mutual="#contessa #conte"/>  <relation name="spouses"   mutual="#susanna #figaro"/>  <relation name="parent_of"   active="#antoniopassive="#barbarina"/>  <relation name="related_with"   active="#antoniopassive="#susanna"/> </listRelation>
Character relations in Le nozze di Figaro
Example
<listRelation>  <relation active="https://dracor.org/entity/ger000171"   passive="http://www.wikidata.org/entity/Q42187688name="wikidata"/> </listRelation>
Connect a DraCor play to Wikidata (Work).
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listRelation
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.pLike | ( tei_relation | tei_listRelation )+ )
   )
}

5.1.133. <m>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<m> (morpheme) represents a grammatical morpheme. [18.1. Linguistic Segment Categories]
Moduleanalysis — Schema
Attributes
baseFormsupplies the morpheme's base form.
StatusOptional
Datatypeteidata.word
Member of
Contained by
May contain
Note

The type attribute may be used to indicate the type of morpheme, taking values such as clitic, prefix, stem, etc. as appropriate.

Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.hiLike"/>
  <elementRef key="seg"/>
  <elementRef key="m"/>
  <elementRef key="c"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element m
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   attribute baseForm { text }?,
   (
      text
    | tei_model.gLike
    | tei_model.hiLike
    | tei_seg
    | tei_m
    | tei_c
    | tei_model.global
   )*
}

5.1.134. <measure>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Modulecore — Schema
Attributes
typespecifies the type of measurement in any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element measure
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.measurement.attributes,
   tei_att.ranging.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

5.1.135. <measureGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [11.3.4. Dimensions]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
character data
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.measureLike"/>
 </alternate>
</content>
    
Schema Declaration
element measureGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.measurement.attributes,
   tei_att.typed.attributes,
   ( text | tei_model.gLike | tei_model.measureLike )*
}

5.1.136. <media>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
Modulecore — Schema
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
Derived fromatt.internetMedia
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
core: desc
Note

The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element media
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.media.attribute.width,
   tei_att.media.attribute.height,
   tei_att.media.attribute.scale,
   tei_att.resourced.attributes,
   tei_att.timed.attributes,
   tei_att.typed.attributes,
   attribute mimeType { list { + } },
   tei_model.descLike*
}

5.1.137. <meeting>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<meeting> contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. [3.12.2.2. Titles, Authors, and Editors]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element meeting
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_macro.limitedContent
}

5.1.138. <mentioned>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mentioned
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.139. <milestone>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

The order in which <milestone> elements are given at a given point is not normally significant.

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element milestone
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.milestoneUnit.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.140. <monogr>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Schema
Attributes
Contained by
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

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

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1" maxOccurs="1">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title" minOccurs="1"
     maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="edition"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   tei_att.global.attributes,
   (
      (
         (
            ( tei_author | tei_editor | tei_meeting | tei_respStmt ),
            ( tei_author | tei_editor | tei_meeting | tei_respStmt )*,
            tei_title+,
            (
               tei_model.ptrLike
             | tei_idno
             | tei_textLang
             | tei_editor
             | tei_respStmt
            )*
         )
       | (
            ( tei_title | tei_model.ptrLike | tei_idno )+,
            (
               tei_textLang
             | tei_author
             | tei_editor
             | tei_meeting
             | tei_respStmt
            )*
         )
       | ( tei_authority, tei_idno )
      )?,
      tei_availability*,
      tei_model.noteLike*,
      (
         (
            tei_edition,
            (
               tei_idno
             | tei_model.ptrLike
             | tei_editor
             | tei_sponsor
             | tei_funder
             | tei_respStmt
            )*
         )*
      ),
      tei_imprint,
      ( tei_imprint | tei_extent | tei_biblScope )*
   )
}

5.1.141. <move>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<move> (movement) marks the actual movement of one or more characters. [7.2.4. Stage Directions]
Moduledrama — Schema
Attributes
typecharacterizes the movement, for example as an entrance or exit.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
entrance
character is entering the stage.
exit
character is exiting the stage.
onStage
character moves on stage
wherespecifies the direction of a stage movement.
StatusOptional
Datatype1–∞ occurrences of teidata.authority separated by whitespace
Sample values include:
L
(left) stage left
R
(right) stage right
C
(center) centre stage
Note

Full blocking information will normally require combinations of values, (for example ‘UL’ for ‘upper stage left’) and may also require more detailed encoding of speed, direction etc. Full documentation of any coding system used should be provided in the header. URIs may be used as values.

perf(performance) identifies the performance or performances in which this movement occurred as specified by pointing to one or more <performance> elements.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May containEmpty element
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element move
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   attribute type { "entrance" | "exit" | "onStage" }?,
   attribute where { list { + } }?,
   attribute perf { list { + } }?,
   empty
}

5.1.142. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore — Schema
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
variant
(variant name) Alternative name
Member of
Contained by
May contain
Note

Think about, why there is a need for <persName> and <name>.

ExampleUse <name> if encoding a group of characters with <personGrp>. type can be used, if more variants are present:
<personGrp xml:id="die_burschesex="MALE">  <name>Die Bursche</name>  <name type="variant">Alle Bursche</name> </personGrp>
Encoding of the name of a group of characters in the play Anzengruber: Die Kreuzelschreiber.
Example
<bibl type="digitalSource">  <name>Google Books</name>  <idno type="URL">https://books.google.com/books?id=q1PDO0ko1mcC&amp;pg=PA51</idno> <!-- ... --> </bibl>
Encoding of the name of the digital source of the play Solbrig: Die Dorfschule.
Example
<person xml:id="fausts_vatersex="MALE">  <persName>Fausts Vater</persName>  <name type="variant">Vater</name> </person>
This might be unintentional/an error in Voss: Faust. Element <name> should not appear in a <person>.
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.personal.attributes,
   attribute type { "variant" }?,
   tei_macro.phraseSeq
}

5.1.144. <namespace>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
Moduleheader — Schema
Attributes
namespecifies the full formal name of the namespace concerned.
StatusRequired
Datatype0–1 occurrences of teidata.namespace separated by whitespace
Contained by
header: tagsDecl
May contain
header: tagUsage
Content model
<content>
 <elementRef key="tagUsage" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element namespace
{
   tei_att.global.attributes,
   attribute name { ? },
   tei_tagUsage+
}

5.1.145. <normalization>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element normalization
{
   tei_att.global.attributes,
   attribute method { "silent" | "markup" }?,
   tei_model.pLike+
}

5.1.146. <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Example
<stage> Hinter der Szene lautes Schreien und Rufen; Gäste, Herren, und Damen kommen lebhaft miteinander sprechend auf die <pb n="62"/> Bühne, indem sie sich ängstlich umblicken, hinter ihnen Bernhardy mit zwei jungen Leoparden,<note place="foot">Ausgestopften    natürlich.</note> die er, in jeder Hand einen, im Genick hält. </stage>
A footnote in a stage direction in the play Carl Laufs u. Wilhelm Jacoby: Pension Schöller.
Example
<sp who="#thomas">  <speaker>THOMAS.</speaker>  <p> <!-- ... --> Na<note place="foot">Na = nein.</note>! Gelten    S'! – Kommen S', Frau Schwägerin!  </p>  <stage> Während er Herminen den Arm reicht, fällt der    Zwischenvorhang.  </stage> </sp>
A note in Ludwig Anzengruber: Heimg'funden that is rendered as a footnote in the source.
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_macro.specialPara
}

5.1.147. <noteGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<noteGrp> (note group) contains a group of notes. [3.9.1.1. Encoding Grouped Notes]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="note"/>
   <elementRef key="noteGrp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element noteGrp
{
   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_desc*, ( tei_note | tei_noteGrp )+ )
}

5.1.148. <notesStmt>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

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

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

Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.noteLike"/>
  <elementRef key="relatedItem"/>
 </alternate>
</content>
    
Schema Declaration
element notesStmt
{
   tei_att.global.attributes,
   ( tei_model.noteLike | tei_relatedItem )+
}

5.1.149. <num>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore — Schema
Attributes
typeindicates the type of numeric value.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
fraction
fraction, e.g. one half or three-quarters
percentage
a percentage
Note

If a different typology is desired, other values can be used for this attribute.

valuesupplies the value of the number in standard form.
StatusOptional
Datatypeteidata.numeric
Valuesa numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
Contained by
May contain
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The <num> element is intended for use in simple applications.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element num
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.ranging.attributes,
   attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" }?,
   attribute value { text }?,
   tei_macro.phraseSeq
}

5.1.150. <opener>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="dateline"/>
  <elementRef key="epigraph"/>
  <elementRef key="salute"/>
  <elementRef key="signed"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element opener
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_argument
    | tei_byline
    | tei_dateline
    | tei_epigraph
    | tei_salute
    | tei_signed
    | tei_model.global
   )*
}

5.1.151. <orgName>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.152. <orig>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.153. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Example
<sp who="#flora">  <speaker>FLORA.</speaker>  <p> Schad', daß du mit deiner Langsamkeit kein Stellwag'n worden    bist.  </p> </sp> <sp who="#plutzerkern">  <speaker>PLUTZERKERN.</speaker>  <p> Dazu fehlet mir die Pfiffigkeit. Ein Stellwagen is das    pfiffigste Wesen auf der Welt, weil er ohne Unterschied des    Standes jeden Menschen aufsitzen laßt.  </p> </sp>
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.fragmentable.attributes,
   tei_macro.paraContent
}

5.1.154. <particDesc>

<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]
Modulecorpus — Schema
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
linking: ab
Note

Explain, why we need <particDesc> and <castList>

Example
<profileDesc>  <particDesc>   <listPerson>    <person xml:id="michlsex="MALE">     <persName>Michl</persName>    </person>    <person xml:id="loislsex="MALE">     <persName>Loisl</persName>    </person>    <person xml:id="veitsex="MALE">     <persName>Veit</persName>    </person>    <person xml:id="martinsex="MALE">     <persName>Martin</persName>    </person>    <personGrp xml:id="die_bursche"     sex="MALE">     <name>Die Bursche</name>     <name type="variant">Alle Bursche</name>    </personGrp>    <person xml:id="steinklopferhanns"     sex="MALE">     <persName>Steinklopferhanns</persName>    </person>    <person xml:id="seppsex="MALE">     <persName>Sepp</persName>    </person>    <person xml:id="marthesex="FEMALE">     <persName>Marthe</persName>    </person>    <person xml:id="antonsex="MALE">     <persName>Anton</persName>    </person>    <person xml:id="lieselsex="FEMALE">     <persName>Liesel</persName>    </person>   </listPerson>  </particDesc> </profileDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.personLike"/>
   <elementRef key="listPerson"/>
   <elementRef key="listOrg"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element particDesc
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_model.personLike | tei_listPerson | listOrg )+ )
}

5.1.155. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself.

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

Example
<sp who="#anton">  <speaker>ANTON</speaker>  <stage>   <hi>steht gleichfalls auf.</hi>  </stage>  <p> Vor einer Stund habn s' 'n tot ausn Wildbach zogn. Weißt ja,    er hat gestern noch nach Grundldorf wolln; nachm Ort schon    zu, bei der Wegbeug, wo 's Ufer so hoch ansteigt und schroff    gegen 's Wasser abfallt, dort habn s' 'n gfunden.  <hi>Gewichtig.</hi> Du warst dabei, du mußt's wissen.    Steinklopfer, wie der alte Mon gestern gredt hat, ich hab    mer's nur verzähln lassen. – Er hat nit viel gtrunken und is    noch rüstig ausgschritten, und a Nacht <pb n="54"/>war auch,    so klar, daß man jed Blattel auf die Bäum hätt zähln können    – fehltreten is er nit! Er wird halt 'n Steig zwischen die    Büsch fortgangen sein – und wer weiß, wie ihm dabei ums Herz    war –, bis er auf einmal dort in die Lichtung treten is,    dort steht mer eh knapp am Rand – unten rauscht 's Wasser,    und gradüber am entern Ufer liegt unser Dörfel und nah, mir    meint, mer könnt's greifen, 's letzte Häusel davon, 'm    Brenninger seins. Dort hat er halt 'm Weg a End gmacht!  </p> </sp>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element pb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.156. <pc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [18.1.2. Below the Word Level 18.4.2. Lightweight Linguistic Annotation]
Moduleanalysis — Schema
Attributes
forceindicates the extent to which this punctuation mark conventionally separates words or phrases.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
strong
the punctuation mark is a word separator
weak
the punctuation mark is not a word separator
inter
the punctuation mark may or may not be a word separator
unitprovides a name for the kind of unit delimited by this punctuation mark.
StatusOptional
Datatypeteidata.enumerated
preindicates whether this punctuation mark precedes or follows the unit it delimits.
StatusOptional
Datatypeteidata.truthValue
Member of
Contained by
May contain
analysis: c
character data
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="c"/>
  <classRef key="model.pPart.edit"/>
 </alternate>
</content>
    
Schema Declaration
element pc
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.linguistic.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   attribute force { "strong" | "weak" | "inter" }?,
   attribute unit { text }?,
   attribute pre { text }?,
   ( text | tei_model.gLike | tei_c | tei_model.pPart.edit )*
}

5.1.157. <performance>

<performance> (performance) contains a section of front or back matter describing how a dramatic piece is to be performed in general or how it was performed on some specific occasion. [7.1.3. Records of Performances 7.1. Front and Back Matter ]
Moduledrama — Schema
Attributes
Member of
Contained by
textstructure: back front
May contain
Note

contains paragraphs and an optional cast list only.

Example
<performance>  <p>   <rs type="place">Gateway Theatre, Edinburgh</rs>, <date>6 September 1948</date>   <castList>    <castItem>     <role>Anath Bithiah</role>     <actor>Athene Seyler</actor>    </castItem>    <castItem>     <role>Shendi</role>     <actor>Robert Rietty</actor>    </castItem>   </castList>  </p>  <p>Directed by <name>E. Martin Browne</name>  </p> </performance>
Example
<performance>  <p>Cast of the original production at the <rs type="place">Savoy Theatre, London,</rs> on  <date>September 24, 1907</date>   <castList>    <castItem>Colonel Hope : Mr A.E.George</castItem>   </castList>  </p> </performance>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element performance
{
   tei_att.global.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      ( ( tei_model.common, tei_model.global* )+ ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

5.1.158. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates — Schema
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
variant
(Name variant) Alternative to the name of a person
pen
(Pen Name) Pseudonym used by writers or authors
nobility
(Noble Name) This refers to the official name adopted by royalty or other high-ranking individuals, often with an ordinal (like "Catherine the Great" or "Louis XIV") to denote their position in a lineage. OR: Dynastic Name: This refers more to a family or house name, like "Habsburg" or "Windsor," often indicating the royal house or lineage.
pseudo
(Pseudonym) Fictitious name used by a person, often an author or artist, to conceal their identity.
Note

See also this issue on GitHub.

Member of
Contained by
May contain
Note

Think about, why there is a need for <persName> and <name>.

ExampleUse <name> if encoding a group of characters with <personGrp>. type can be used, if more variants are present:
<listPerson>  <person xml:id="Vorotynskijsex="MALE">   <persName>Воротынский</persName>   <persName xml:lang="de">Vorotynskij</persName>  </person>  <person xml:id="Shujskijsex="MALE">   <persName>Шуйский</persName>   <persName xml:lang="de">Šujskij</persName>  </person>  <person xml:id="OdinIzNaroda_1sex="MALE">   <persName>Один (Красная площадь)</persName>   <persName xml:lang="de">Einer (Roter Platz)</persName>  </person> <!-- ... --> </listPerson>
Example
<personGrp xml:id="verschworenesex="MALE">  <name>Verschworene</name>  <persName type="variant">Alle</persName>  <persName type="variant">Einige Verschworene</persName> </personGrp>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.personal.attributes,
   attribute type { "variant" | "pen" | "nobility" | "pseudo" }?,
   tei_macro.phraseSeq
}

5.1.159. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description]
Modulenamesdates — Schema
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

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

sexspecifies the sex of the person.
StatusRecommended
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Suggested values include:
FEMALE
(female)
MALE
(male)
UNKNOWN
(unknown)
Note

Only the values FEMALE, MALE, UNKNOWN are supported by the DraCor-API. See also this issue on GitHub.

genderspecifies the gender of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

agespecifies an age group for the person.
StatusOptional
Datatypeteidata.enumerated
Note

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

Member of
Contained by
corpus: particDesc
namesdates: event listPerson
May contain
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example
<person xml:id="seppsex="MALE">  <persName>Sepp</persName> </person> <person xml:id="marthesex="FEMALE">  <persName>Marthe</persName> </person> <person xml:id="antonsex="MALE">  <persName>Anton</persName> </person> <person xml:id="lieselsex="FEMALE">  <persName>Liesel</persName> </person>
Schematron
<sch:rule context="tei:person[@sex]"  role="warning"  see="https://dracor.org/doc/odd#section-character-sex-gender"> <sch:assert test="@sex = ('FEMALE', 'MALE', 'UNKNOWN')"> The values for person/@sex supported by the DraCor API are <val>FEMALE</val>, <val>MALE</val> and <val>UNKNOWN</val>. </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <elementRef key="ptr"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element person
{
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.sortable.attributes,
   attribute xml:id { text },
   attribute role { list { + } }?,
   attribute sex { list { ( "FEMALE" | "MALE" | "UNKNOWN" )+ } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   (
      tei_model.pLike+
    | ( tei_model.personPart | tei_model.global | tei_ptr )*
   )
}

5.1.160. <personGrp>

<personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [16.2.2. The Participant Description]
Modulenamesdates — Schema
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
rolespecifies the role of this group of participants in the interaction.
StatusOptional
Datatypeteidata.enumerated
Note

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

sexspecifies the sex of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Suggested values include:
FEMALE
(female)
MALE
(male)
UNKNOWN
(unknown)
Note

Only the values FEMALE, MALE, UNKNOWN are supported by the DraCor-API. See also this issue on GitHub.

genderspecifies the gender of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

agespecifies the age group of the participants.
StatusOptional
Datatypeteidata.enumerated
Note

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

sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
corpus: particDesc
namesdates: event listPerson
May contain
Note

May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

Example
<personGrp xml:id="pg1role="audience"  sex="mixedsize="approx 50"/>
Schematron
<sch:rule context="tei:personGrp[@sex]"  role="warning"  see="https://dracor.org/doc/odd#section-character-sex-gender"> <sch:assert test="every $t in tokenize(@sex) satisfies $t = ('FEMALE', 'MALE', 'UNKNOWN')"> The values for personGrp/@sex supported by the DraCor API are <val>FEMALE</val>, <val>MALE</val> and <val>UNKNOWN</val>. </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element personGrp
{
   tei_att.global.attribute.n,
   tei_att.global.attribute.xmllang,
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.source.attribute.source,
   tei_att.sortable.attributes,
   attribute xml:id { text }?,
   attribute role { text }?,
   attribute sex { list { ( "FEMALE" | "MALE" | "UNKNOWN" )+ } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   attribute size { list { + } }?,
   ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
}

5.1.161. <phr>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<phr> (phrase) represents a grammatical phrase. [18.1. Linguistic Segment Categories]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to indicate the type of phrase, taking values such as noun, verb, preposition, etc. as appropriate.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element phr
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.162. <postBox>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

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

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

Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postBox { tei_att.global.attributes, text }

5.1.163. <postCode>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

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

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

Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postCode { tei_att.global.attributes, text }

5.1.164. <postscript>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.divTopPart"/>
  </alternate>
  <classRef key="model.common"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.common"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottomPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element postscript
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   (
      ( tei_model.global | tei_model.divTopPart )*,
      tei_model.common,
      ( tei_model.global | tei_model.common )*,
      ( ( tei_model.divBottomPart, tei_model.global* )* )
   )
}

5.1.165. <prefixDef>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader — Schema
Attributes
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatypeteidata.prefix
Note

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

Contained by
May contain
core: p
linking: ab
Note

The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element prefixDef
{
   tei_att.global.attributes,
   tei_att.patternReplacement.attributes,
   attribute ident { text },
   tei_model.pLike*
}

5.1.166. <principal>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element principal
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq.limited
}

5.1.167. <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
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 type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }

5.1.168. <projectDesc>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc { tei_att.global.attributes, tei_model.pLike+ }

5.1.169. <prologue>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<prologue> (prologue) contains the prologue to a drama, typically spoken by an actor out of character, possibly in association with a particular performance or venue. [7.1.2. Prologues and Epilogues 7.1. Front and Back Matter ]
Moduledrama — Schema
Attributes
Member of
Contained by
textstructure: back front
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element prologue
{
   tei_att.global.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      ( ( tei_model.common, tei_model.global* )+ ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

5.1.170. <ptr>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore — Schema
Attributes
Member of
Contained by
May containEmpty element
Note

The target and cRef attributes are mutually exclusive.

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.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   empty
}

5.1.171. <pubPlace>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Schema
Attributes
Member of
Contained by
textstructure: docImprint
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

5.1.172. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader — Schema
Attributes
Contained by
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 &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
SchematronThe identifier 'corpus name' (see Feature corpus_name) MUST be included in corpus.xml in an <idno> element of the type URI.
<sch:rule context="tei:publicationStmt[ancestor::tei:teiCorpus]"  role="critical"> <sch:assert test="tei:idno[@type eq 'URI']"> The identifier 'corpus name' of the corpus MUST be included as an element idno with the value 'URI' of the attribute 'type'. </sch:assert> </sch:rule>
SchematronThe URL of the corpus repository (see Feature corpus_repository) needs to be specified in corpus.xml as the content of an <idno> element with of the type repo in order to be able to load and update the corpus data from the repository.
<sch:rule context="tei:publicationStmt[ancestor::tei:teiCorpus]"  role="warning"> <sch:assert test="tei:idno[@type eq 'repo']"> Consider specifying the GitHub repository of the corpus using an idno element of the type 'repo'. </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   tei_att.global.attributes,
   (
      (
         (
            tei_model.publicationStmtPart.agency,
            tei_model.publicationStmtPart.detail*
         )+
      )
    | tei_model.pLike+
   )
}

5.1.173. <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore — Schema
Attributes
Member of
Contained by
textstructure: docImprint
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
}

5.1.174. <punctuation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
Moduleheader — Schema
Attributes
marksindicates whether or not punctation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no punctuation marks have been retained
some
some punctuation marks have been retained
all
all punctuation marks have been retained
placementindicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
internal
punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
external
punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element punctuation
{
   tei_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   attribute placement { "internal" | "external" }?,
   tei_model.pLike*
}

5.1.175. <q>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore — Schema
Attributes
type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
spoken
(spoken) representation of speech
thought
(thought) representation of thought, e.g. internal monologue
written
(written) quotation from a written source
soCalled
(so called) authorial distance
foreign
(foreign) foreign words
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(mentioned) refering to itself, not its normal referent
Member of
Contained by
May contain
Note

May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element q
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   tei_macro.specialPara
}

5.1.176. <quotation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no quotation marks have been retained
some
some quotation marks have been retained
all
all quotation marks have been retained
Member of
Contained by
May contain
core: p
linking: ab
Schematron
<sch:rule context="tei:quotation"> <sch:report test="not( @marks ) and not( tei:p )"> On <sch:name/>, either the @marks attribute should be used, or a paragraph of description provided </sch:report> </sch:rule>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element quotation
{
   tei_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   tei_model.pLike*
}

5.1.177. <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

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

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

5.1.178. <rb>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
Modulecore — Schema
Attributes
Contained by
core: ruby
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.179. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:rule context="tei:ref"> <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>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   tei_att.global.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.180. <refState>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<refState> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Moduleheader — Schema
Attributes
lengthspecifies the fixed length of the reference component.
StatusOptional
Datatypeteidata.count
Note

When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly. If no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.

delim(delimiter) supplies a delimiting string following the reference component.
StatusOptional
Datatypeteidata.text
Contained by
header: refsDecl
May containEmpty element
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element refState
{
   tei_att.global.attributes,
   tei_att.edition.attributes,
   tei_att.milestoneUnit.attributes,
   attribute length { text }?,
   attribute delim { text }?,
   empty
}

5.1.181. <refsDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="citeStructure"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="cRefPattern"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="refState" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element refsDecl
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | tei_citeStructure+ | tei_cRefPattern+ | tei_refState+ )
}

5.1.182. <reg>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.183. <region>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [14.2.3. Place Names]
Modulenamesdates — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element region
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.184. <relatedItem>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Modulecore — Schema
Attributes
targetpoints to the related bibliographic element by means of an absolute or relative URI reference.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Note

If the target attribute is used to reference the related bibliographic item, the element must be empty.

Schematron
<sch:rule context="tei:relatedItem"> <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the relatedItem element must be empty</sch:report> <sch:assert test="@target or child::*">A relatedItem element should have either a @target attribute or a child element to indicate the related bibliographic item</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0" maxOccurs="1">
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
    
Schema Declaration
element relatedItem
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute target { text }?,
   ( tei_model.biblLike | tei_model.ptrLike )?
}

5.1.185. <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [14.3.2.3. Personal Relationships]
Modulenamesdates — Schema
Attributes
namesupplies a name for the kind of relationship of which this is an instance.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
parent_of
(is parent of) A character whose ID is included in the active attribute is the parent of the character whose ID is listed in the passive attribute.
lover_of
(is lover of) A character whose ID is included in the active attribute is the lover of the character whose ID is listed in the passive attribute.
related_with
(is related with) Other family relations (e.g. uncles)
associated_with
(is associated with) For clearly associated characters (e.g., butlers)
siblings
(are siblings) Characters whose IDs are included in mutual have at least one parent in common
spouses
(are spouses) Characters whose IDs are included in mutual are married (or engaged)
friends
(are friends) Characters whose IDs are included in mutual are marked as being friend
wikidata
(corresponds to Wikidata entity) The entity whose URI is listed in the active attribute corresponds to the entity on Wikidata whose URI is listed in the passive attribute.
passiveidentifies the ‘passive’ participants in a non-mutual relationship.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mutualsupplies a list of participants amongst all of whom the relationship holds equally.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
core: desc
Note

Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

Example
<relation type="socialname="supervisor"  active="#p1passive="#p2 #p3 #p4"/>
This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.
Example
<relation type="personalname="friends"  mutual="#p2 #p3 #p4"/>
This indicates that p2, p3, and p4 are all friends.
Example
<relation type="CRM"  name="P89_falls_within"  active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"  passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.
Example
<relation resp="http://viaf.org/viaf/44335536/"  ref="http://purl.org/saws/ontology#isVariantOf"  active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"  passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
<sch:rule context="tei:relation"> <sch:assert test="@ref or @key or @name">One of the attributes @name, @ref or @key must be supplied</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@passive and not(@active)">the attribute @passive may be supplied only if the attribute @active is supplied</sch:report> </sch:rule>
Content model
<content>
 <elementRef key="desc" minOccurs="0"/>
</content>
    
Schema Declaration
element relation
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute name
   {
      "parent_of"
    | "lover_of"
    | "related_with"
    | "associated_with"
    | "siblings"
    | "spouses"
    | "friends"
    | "wikidata"
   }?,
   attribute passive { list { + } }?,
   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
   tei_desc?
}

5.1.186. <rendition>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader — Schema
Attributes
scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
first-line
styling applies to the first line of the target element
first-letter
styling applies to the first letter of the target element
before
styling should be applied immediately before the content of the target element
after
styling should be applied immediately after the content of the target element
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatypeteidata.text
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
Note

Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

While rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

Contained by
header: tagsDecl
May contain
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element rendition
{
   tei_att.global.attributes,
   tei_att.styleDef.attributes,
   attribute scope { text }?,
   attribute selector { text }?,
   tei_macro.limitedContent
}

5.1.187. <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Schema
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
}

5.1.188. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
core: name note resp
namesdates: orgName persName
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 minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   (
      (
         ( tei_resp+, tei_model.nameLike.agent+ )
       | ( tei_model.nameLike.agent+, tei_resp+ )
      ),
      tei_note*
   )
}

5.1.189. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Schema
Attributes
Contained by
header: teiHeader
linking: annotation
May contain
core: list
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-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="list" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="listChange"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   tei_att.global.attributes,
   ( tei_list+ | tei_listChange+ | tei_change+ )
}

5.1.190. <role>

<role> (role) contains the name of a dramatic role, as given in a cast list. [7.1.4. Cast Lists]
Moduledrama — Schema
Attributes
genderspecifies the gender of the role.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

Member of
Contained by
drama: castItem
May contain
Note

In DraCor do not link who attributes to <role> elements but to <person> or <personGrp> elements in the <particDesc>. See Characters.

Example
<role>Marinelli</role> <roleDesc>Kammerherr des Prinzen</roleDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element role
{
   tei_att.global.attributes,
   attribute gender { list { + } }?,
   tei_macro.phraseSeq
}

5.1.191. <roleDesc>

<roleDesc> (role description) describes a character's role in a drama. [7.1.4. Cast Lists]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Example
<roleDesc>gentlemen of leisure</roleDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element roleDesc { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.192. <rs>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.193. <rt>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
Modulecore — Schema
Attributes
targetsupplies a pointer to the base being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.
<sch:rule context="tei:rt/@target"> <sch:report test="../@from | ../@to">When target= is present, neither from= nor to= should be.</sch:report> </sch:rule>
Note

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

frompoints to the starting point of the span of text being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of to iff there is a from.
<sch:rule context="tei:rt/@from"> <sch:assert test="../@to">When from= is present, the to= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
topoints to the ending point of the span of text being glossed.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of from iff there is a to.
<sch:rule context="tei:rt/@to"> <sch:assert test="../@from">When to= is present, the from= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Contained by
core: ruby
May contain
Note

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

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rt
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute target { text }?,
   attribute from { text }?,
   attribute to { text }?,
   tei_macro.phraseSeq
}

5.1.194. <ruby>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
core: rb rt
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="rb" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="rt" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element ruby
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attributes,
   ( tei_rb, tei_rt+ )
}

5.1.195. <s>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<s> (s-unit) contains a sentence-like division of a text. [18.1. Linguistic Segment Categories 8.4.1. Segmentation]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
Note

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

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

Schematron
<sch:rule context="tei:s"> <sch:report test="tei:s">You may not nest one s element within another: use seg instead</sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element s
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.196. <said>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
Modulecore — Schema
Attributes
aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
StatusOptional
Datatypeteidata.xTruthValue
<p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;    I believe she would not accept him.</said> Celia felt that this was a pity. <!-- ... --> </p>
Note

The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
StatusOptional
Datatypeteidata.xTruthValue
Defaulttrue
<!-- in the header --><editorialDecl>  <quotation marks="none"/> </editorialDecl> <!-- ... --> <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>. The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>, but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said> </p>
Note

The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element said
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute aloud { text }?,
   attribute direct { text }?,
   tei_macro.specialPara
}

5.1.197. <salute>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element salute
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.198. <samplingDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl { tei_att.global.attributes, tei_model.pLike+ }

5.1.199. <schemaRef>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<schemaRef> (schema reference) describes or points to a related customization or schema file. [2.3.10. The Schema Specification]
Moduleheader — Schema
Attributes
keythe identifier used for the customization or schema.
StatusOptional
Datatypeteidata.xmlName
Member of
Contained by
header: encodingDesc
May contain
core: desc
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
    
Schema Declaration
element schemaRef
{
   tei_att.global.attributes,
   tei_att.resourced.attributes,
   tei_att.typed.attributes,
   attribute key { text }?,
   tei_model.descLike?
}

5.1.200. <scriptNote>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader — Schema
Attributes
Contained by
May contain
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element scriptNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

5.1.201. <seg>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
Modulelinking — Schema
Attributes
Member of
Contained by
May contain
Note

The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element seg
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

5.1.202. <segmentation>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<segmentation> (segmentation) describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element segmentation { tei_att.global.attributes, tei_model.pLike+ }

5.1.203. <series>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   tei_att.global.attributes,
   (
      text
    | tei_model.gLike
    | tei_title
    | tei_model.ptrLike
    | tei_editor
    | tei_respStmt
    | tei_biblScope
    | tei_idno
    | tei_textLang
    | tei_model.global
    | tei_availability
   )*
}

5.1.204. <seriesStmt>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader — Schema
Attributes
Contained by
May contain
header: idno
linking: ab
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="title" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element seriesStmt
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | (
         tei_title+,
         ( tei_editor | tei_respStmt )*,
         ( tei_idno | tei_biblScope )*
      )
   )
}

5.1.205. <set>

<set> (setting) contains a description of the setting, time, locale, appearance, etc., of the action of a play, typically found in the front matter of a printed performance text (not a stage direction). [7.1. Front and Back Matter ]
Moduledrama — Schema
Attributes
Member of
Contained by
textstructure: back front
May contain
Note

Contains paragraphs or phrase level tags.

This element should not be used outside the front or back matter; for similar contextual descriptions within the body of the text, use the <stage> element.

Example
<set>  <p>The action takes place on February 7th between the hours of noon and six in the    afternoon, close to the Trenartha Tin Plate Works, on the borders of England and Wales,    where a strike has been in progress throughout the winter.</p> </set>
Example
<set>  <head>SCENE</head>  <p>A Sub-Post Office on a late autumn evening</p> </set>
Example
<front> <!-- <titlePage>, <div type="Dedication">, etc. -->  <set>   <list type="gloss">    <label>TIME</label>    <item>1907</item>    <label>PLACE</label>    <item>East Coast village in England</item>   </list>  </set> </front>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element set
{
   tei_att.global.attributes,
   (
      ( tei_model.headLike | tei_model.global )*,
      ( ( tei_model.common, tei_model.global* )* )
   )
}

5.1.206. <sic>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.207. <signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Example
<signed>Thine to command <name>Humph. Moseley</name> </signed>
Example
<closer>  <signed>Sign'd and Seal'd,  <list>    <item>John Bull,</item>    <item>Nic. Frog.</item>   </list>  </signed> </closer>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element signed
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

5.1.208. <soCalled>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element soCalled
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

5.1.209. <sound>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<sound> (sound) describes a sound effect or musical sequence specified within a screen play or radio script. [7.3.1. Technical Information 7.3. Other Types of Performance Text]
Moduledrama — Schema
Attributes
typecategorizes the sound in some respect, e.g. as music, special effect, etc.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
discreteindicates whether the sound overlaps the surrounding speeches or interrupts them.
StatusOptional
Datatypeteidata.xTruthValue
Note

The value true indicates that the sound is heard between the surrounding speeches; the value false indicates that the sound overlaps one or more of the surrounding speeches.

Member of
Contained by
May contain
Note

A specialized form of stage direction.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sound
{
   tei_att.global.attributes,
   attribute type { text }?,
   attribute discrete { text }?,
   tei_macro.paraContent
}

5.1.210. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader — Schema
Attributes
Contained by
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>
SchematronChecks if a digital source is present in the <sourceDesc>
<sch:rule context="tei:sourceDesc"> <sch:assert test="tei:bibl[@type eq 'digitalSource']"> Digital source is missing </sch:assert> </sch:rule>
SchematronChecks if a original source for a digital source is available
<sch:rule context="tei:sourceDesc/tei:bibl[@type eq 'digitalSource']"> <sch:assert test="tei:bibl[@type eq 'originalSource']"> Original Source for digital source is missing </sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   tei_att.global.attributes,
   (
      tei_model.pLike+
    | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
   )
}

5.1.211. <sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Note

The who attribute on this element may be used either in addition to the <speaker> element or as an alternative.

Example
<sp>  <speaker>The reverend Doctor Opimian</speaker>  <p>I do not think I have named a single unpresentable fish.</p> </sp> <sp>  <speaker>Mr Gryll</speaker>  <p>Bream, Doctor: there is not much to be said for bream.</p> </sp> <sp>  <speaker>The Reverend Doctor Opimian</speaker>  <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>  <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I    will forbear [...]</p> </sp>
SchematronOnly speech acts <sp> with who attributes are used when extracting a network.
<sch:rule context="tei:sp" role="warning"> <sch:assert test="@who"> A speech 'sp' without an attribute '@who' is not used when extracting the network. SHOULD consider linking the speech act to a speaking character ('person') in the 'particDesc'. </sch:assert> </sch:rule>
SchematronSpeech acts <sp> SHOULD be linked to characters (<person> or <personGrp> elements in <particDesc>) by supplying the character's identifier in the attribute who as a pointer. A pointer is constructed by prepending the character ID with a hash '#'.
<sch:rule context="tei:sp[@who[not(contains(.,' '))]]"  role="warning"> <sch:let name="localID"  value="replace(@who/string(),'#','')"/> <sch:assert test="ancestor::tei:TEI//tei:particDesc//(tei:person|tei:personGrp)[@xml:id eq $localID]"  role="warning"> A speech act SHOULD link to a 'person' or 'personGrp' element in 'particDesc'. Use a valid character ID and provide it as a pointer by prepending it with a hash '#'." </sch:assert> </sch:rule> <sch:rule context="tei:sp[contains(@who,' ')]"> <sch:let name="allIDs"  value="./ancestor::tei:TEI//tei:particDesc//(tei:person|tei:personGrp)/@xml:id/string()"/> <sch:let name="localIDs"  value="tokenize(@who/string(),'\s+')"/> <sch:assert test="every $i in $localIDs satisfies replace($i,'#','') = $allIDs"  role="warning"> At least one character ID provided as the value of the attribute who '<xsl:value-of select="@who/string()"/>' has not been declared. A speech act SHOULD link to a 'person' or 'personGrp' element in 'particDesc'. </sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="speaker"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="lg"/>
    <classRef key="model.lLike"/>
    <classRef key="model.pLike"/>
    <classRef key="model.listLike"/>
    <classRef key="model.stageLike"/>
    <classRef key="model.attributable"/>
   </alternate>
   <alternate minOccurs="1" maxOccurs="1">
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="q"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element sp
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.placement.attributes,
   (
      tei_model.global*,
      ( ( tei_speaker, tei_model.global* )? ),
      (
         (
            (
               tei_lg
             | tei_model.lLike
             | tei_model.pLike
             | tei_model.listLike
             | tei_model.stageLike
             | tei_model.attributable
            ),
            ( tei_model.global* | tei_q )
         )+
      )
   )
}

5.1.212. <spGrp>

<spGrp> (speech group) contains a group of speeches or songs in a performance text presented in a source as constituting a single unit or ‘number’. [7.2.3. Grouped Speeches]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Example
<sp>  <speaker>FRAULEIN SCHNEIDER:</speaker>  <p> Herr Schultz! Can I believe what I see? <stage>(HERR SCHULTZ nods      proudly)</stage> But this is — too much to accept. So rare — so costly —    so luxurious. </p> </sp> <stage>(She sings)</stage> <spGrp n="4">  <sp>   <l>If you bought me diamonds, If you bought me pearls,</l>   <l>If you bought me roses like some other gents</l>   <l>Might bring to other girls,</l>   <l>It couldn't please me more</l>   <l>Than the gift I see -</l>   <stage>(She takes a large pineapple out of the bag)</stage>   <l>A pineapple for me!</l>  </sp>  <sp>   <speaker>SCHULTZ:</speaker>   <stage>(Singing) </stage>   <l>If, in your emotion, </l>   <l>You began to sway, </l>   <l>Went to get some air, </l>   <l>Or grabbed a chair </l>   <l>To keep from fainting dead away, </l>   <l>It couldn't please me more </l>   <l>Than to see you cling </l>   <l>To the pineapple I bring.</l>  </sp>  <sp>   <speaker>BOTH:</speaker>   <l>Ah, ah, ah, ah, ah, ah, ah, ah</l>  </sp> <!-- ... -->  <stage>(They dance)</stage> </spGrp> <sp>  <speaker>FRAULEIN SCHNEIDER: </speaker>  <p>But you must not bring me    any more pineapples! Do you hear? It is not proper. It is a gift a    young man would present to his lady love. It makes me blush!  </p> </sp>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <elementRef key="sp"/>
   <classRef key="model.stageLike"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element spGrp
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.typed.attributes,
   (
      tei_model.headLike*,
      ( tei_model.global | tei_sp | tei_model.stageLike )+
   )
}

5.1.213. <span>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<span> associates an interpretative annotation directly with a span of text. [18.3. Spans and Interpretations]
Moduleanalysis — Schema
Attributes
fromgives the identifier of the node which is the starting point of the span of text being annotated; if not accompanied by a to attribute, gives the identifier of the node of the entire span of text being annotated.
StatusOptional
Datatypeteidata.pointer
togives the identifier of the node which is the end-point of the span of text being annotated.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Schematron
<sch:rule context="tei:span"> <sch:report test="@from and @target"> Only one of the attributes @target and @from may be supplied on <sch:name/> </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="@to and @target"> Only one of the attributes @target and @to may be supplied on <sch:name/> </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="@to and not(@from)"> If @to is supplied on <sch:name/>, @from must be supplied as well </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="contains(normalize-space(@to),' ') or contains(normalize-space(@from),' ')"> The attributes @to and @from on <sch:name/> may each contain only a single value </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element span
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.interpLike.attributes,
   tei_att.pointing.attributes,
   attribute from { text }?,
   attribute to { text }?,
   tei_macro.phraseSeq.limited
}

5.1.214. <spanGrp>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<spanGrp> (span group) collects together span tags. [18.3. Spans and Interpretations]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
analysis: span
core: desc
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="span" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element spanGrp
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.interpLike.attributes,
   ( tei_model.descLike*, tei_span* )
}

5.1.215. <speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
Modulecore — Schema
Attributes
Contained by
core: sp
May contain
Note

This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an <sp> element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used.

Example
<sp who="#ni #rsa">  <speaker>Nancy and Robert</speaker>  <stage type="delivery">(speaking simultaneously)</stage>  <p>The future? ...</p> </sp> <list type="speakers">  <item xml:id="ni"/>  <item xml:id="rsa"/> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element speaker
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_macro.phraseSeq
}

5.1.216. <sponsor>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.

Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element sponsor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq.limited
}

5.1.217. <stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions]
Modulecore — Schema
Attributes
typeindicates the kind of stage direction.
StatusRecommended
Datatype0–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
setting
describes a setting.
entrance
describes an entrance.
exit
describes an exit.
business
describes stage business.
novelistic
is a narrative, motivating stage direction.
delivery
describes how a character speaks.
modifier
gives some detail about a character.
location
describes a location.
mixed
more than one of the above
Note

If the value mixed is used, it must be the only value. Multiple values may however be supplied if a single stage direction performs multiple functions, for example is both an entrance and a modifier.

Member of
Contained by
May contain
Note

The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

Example
<stage type="setting">A curtain being drawn.</stage> <stage type="setting">Music</stage> <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage> <!-- Middleton : Yorkshire Tragedy --> <stage type="exit">Exit pursued by a bear.</stage> <stage type="business">He quickly takes the stone out.</stage> <stage type="delivery">To Lussurioso.</stage> <stage type="novelistic">Having had enough, and embarrassed for the family.</stage> <!-- Lorraine Hansbury : a raisin in in the sun --> <stage type="modifier">Disguised as Ansaldo.</stage> <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage> <!-- Middleton: The Widow --> <stage type="location">At a window.</stage> <stage rend="inlinetype="delivery">Aside.</stage>
Example
<l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when    straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on    two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the  <hi>Prologue</hi> was spoken, which being ended, they descended in    order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element stage
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   attribute type
   {
      list
      {
         (
            "setting"
          | "entrance"
          | "exit"
          | "business"
          | "novelistic"
          | "delivery"
          | "modifier"
          | "location"
          | "mixed"
         )*
      }
   }?,
   tei_macro.specialPara
}

5.1.218. <standOff>

<standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [17.10. The standOff Container]
Modulelinking — Schema
Attributes
Member of
Contained by
core: teiCorpus
textstructure: TEI
May contain
Example
<standOff>  <listEvent>   <event type="printwhen="1813">    <desc/>   </event>   <event type="premierewhen="1811">    <desc/>   </event>   <event type="writtenwhen="1811">    <desc>geschrieben wahrscheinlich im Winter 1811</desc>   </event>  </listEvent>  <listRelation>   <relation active="https://dracor.org/entity/ger000171"    passive="http://www.wikidata.org/entity/Q42187688name="wikidata"/>  </listRelation> </standOff>
Discussion see Github Issue.
Schematron
<sch:rule context="tei:standOff"> <sch:assert test="@type or not(ancestor::tei:standOff)">This <sch:name/> element must have a @type attribute, since it is nested inside a <sch:name/> </sch:assert> </sch:rule>
Content model
<content>
 <classRef key="model.standOffPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element standOff
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_model.standOffPart+
}

5.1.219. <stdVals>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader — Schema
Attributes
Member of
Contained by
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element stdVals { tei_att.global.attributes, tei_model.pLike+ }

5.1.220. <street>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
Modulecore — Schema
Attributes
Member of
Contained by
core: address
May contain
Note

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

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element street { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.221. <styleDefDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element styleDefDecl
{
   tei_att.global.attributes,
   tei_att.styleDef.attributes,
   tei_model.pLike*
}

5.1.222. <surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names]
Modulenamesdates — Schema
Attributes
sort(sort) specifies the sort order of the name component in relation to others within the name.
Derived fromatt.personal
StatusOptional
Datatypeteidata.count
Note

Set value of this 1 to indicate on which <surname> to sort.

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.attribute.full,
   tei_att.naming.attribute.role,
   tei_att.naming.attribute.nymRef,
   tei_att.canonical.attribute.key,
   tei_att.canonical.attribute.ref,
   tei_att.typed.attributes,
   attribute sort { text }?,
   tei_macro.phraseSeq
}

5.1.223. <tagUsage>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
Moduleheader — Schema
Attributes
gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent <namespace> element.
StatusRequired
Datatypeteidata.name
occursspecifies the number of occurrences of this element within the text.
StatusRecommended
Datatypeteidata.count
withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
StatusRecommended
Datatypeteidata.count
Contained by
header: namespace
May contain
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element tagUsage
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   attribute gi { text },
   attribute occurs { text }?,
   attribute withId { text }?,
   tei_macro.limitedContent
}

5.1.224. <tagsDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader — Schema
Attributes
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatypeteidata.truthValue
Note

TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Member of
Contained by
header: encodingDesc
May contain
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   tei_att.global.attributes,
   attribute partial { text }?,
   ( tei_rendition*, tei_namespace* )
}

5.1.225. <taxonomy>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<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]
Moduleheader — Schema
Attributes
Contained by
May contain
Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.descLike"
      minOccurs="1" maxOccurs="1"/>
     <elementRef key="equiv" minOccurs="1"
      maxOccurs="1"/>
     <elementRef key="gloss" minOccurs="1"
      maxOccurs="1"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <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 | tei_gloss )+,
            ( tei_category | tei_taxonomy )*
         )
      )
    | ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
   )
}

5.1.226. <tech>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<tech> (technical stage direction) describes a special-purpose stage direction that is not meant for the actors. [7.3.1. Technical Information]
Moduledrama — Schema
Attributes
typecategorizes the technical stage direction.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
light
a lighting cue
sound
a sound cue
prop
a prop cue
block
a blocking instruction
perf(performance) points to one or more <performance> elements documenting the performance or performances to which this technical direction applies.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element tech
{
   tei_att.global.attributes,
   attribute type { "light" | "sound" | "prop" | "block" }?,
   attribute perf { list { + } }?,
   tei_macro.paraContent
}

5.1.227. <teiCorpus>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more <TEI> elements, each containing a single text header and a text. [4. Default Text Structure 16.1. Varieties of Composite Text]
Modulecore — Schema
Attributes
version(version) specifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

Member of
Contained by
core: teiCorpus
May contain
core: teiCorpus
header: teiHeader
linking: standOff
textstructure: TEI text
Note

Should contain one <teiHeader> for the corpus, and a series of <TEI> elements, one for each text.

As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <teiCorpus version="4.8.1" xml:lang="en" xmlns="http://www.tei-c.org/ns/1.0">.

Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.describedResource"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element teiCorpus
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute version { text }?,
   ( tei_teiHeader, tei_model.resource*, tei_model.describedResource+ )
}

5.1.228. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Moduleheader — Schema
Attributes
Contained by
core: teiCorpus
textstructure: TEI
May contain
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 minOccurs="1" maxOccurs="1">
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   tei_att.global.attributes,
   ( tei_fileDesc, tei_model.teiHeaderPart*, tei_revisionDesc? )
}

5.1.229. <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore — Schema
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 xml:id="TDPV1rend="sc">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="#TDPV2rend="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#TDPV2rend="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.pointing.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.230. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure — Schema
Attributes
Member of
Contained by
core: teiCorpus
textstructure: TEI group
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>
ExampleThe 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 minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <elementRef key="body" minOccurs="1"
   maxOccurs="1"/>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0" maxOccurs="1">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   (
      tei_model.global*,
      ( ( tei_front, tei_model.global* )? ),
      tei_body,
      tei_model.global*,
      ( ( tei_back, tei_model.global* )? )
   )
}

5.1.231. <textClass>

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

5.1.232. <textLang>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems]
Modulecore — Schema
Attributes
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
StatusOptional
Datatypeteidata.language
otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
StatusOptional
Datatype0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
May contain
Note

This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   tei_att.global.attributes,
   attribute mainLang { text }?,
   attribute otherLangs { list { * } }?,
   tei_macro.specialPara
}

5.1.233. <time>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element time
{
   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.typed.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

5.1.234. <timeline>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<timeline> (timeline) provides a set of ordered points in time which can be linked to elements of a spoken text to create a temporal alignment of that text. [17.4.2. Placing Synchronous Events in Time]
Modulelinking — Schema
Attributes
origindesignates the origin of the timeline, i.e. the time at which it begins.
StatusOptional
Datatypeteidata.pointer
Note

If this attribute is not supplied, the implication is that the time of origin is not known. If it is supplied, it must point either to one of the <when> elements in its content, or to another <timeline> element.

unitspecifies the unit of time corresponding to the interval value of the timeline or of its constituent points in time.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
d
(days)
h
(hours)
min
(minutes)
s
(seconds)
ms
(milliseconds)
intervalspecifies a time interval either as a positive integral value or using one of a set of predefined codes.
StatusOptional
Datatypeteidata.interval
Note

The value irregular indicates uncertainty about all the intervals in the timeline; the value regular indicates that all the intervals are evenly spaced, but the size of the intervals is not known; numeric values indicate evenly spaced values of the size specified. If individual points in time in the timeline are given different values for the interval attribute, those values locally override the value given in the timeline.

Member of
Contained by
May contain
linking: when
Content model
<content>
 <elementRef key="when" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element timeline
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute origin { text }?,
   attribute unit { "d" | "h" | "min" | "s" | "ms" }?,
   attribute interval { text }?,
   tei_when+
}

5.1.235. <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore — Schema
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
main
(Main Title)
sub
(Subtitle)
Note

The DraCor API supports the values main and sub to classify the title of a play (see also section on Encoding the title of a Play).

levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

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

Member of
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 type="main">Des Meeres und der Liebe Wellen</title>
Example
<title type="sub">Trauerspiel in fünf Aufzügen</title>
Example
<title type="main">Ревизор</title> <title type="mainxml:lang="eng">The Government Inspector</title> <title type="sub">Комедия в пяти действиях</title> <title type="subxml:lang="eng">A Comedy in Five Acts</title>
Main and subtitle of Gogol': Revisor in the original (Russian) and Eglish languages.
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,
   attribute type { "main" | "sub" }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   tei_macro.paraContent
}

5.1.236. <titlePage>

<titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
typeclassifies the title page according to any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

This attribute allows the same element to be used for volume title pages, series title pages, etc., as well as for the ‘main’ title page of a work.

Member of
Contained by
textstructure: back front
May contain
Example
<titlePage>  <docTitle>   <titlePart type="main">THOMAS OF Reading.</titlePart>   <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>  </docTitle>  <docEdition>Now the fourth time corrected and enlarged</docEdition>  <byline>By T.D.</byline>  <figure>   <head>TP</head>   <p>Thou shalt labor till thou returne to duste</p>   <figDesc>Printers Ornament used by TP</figDesc>  </figure>  <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>   <date>1612.</date>  </docImprint> </titlePage>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.titlepagePart"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.titlepagePart"/>
   <classRef key="model.global"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element titlePage
{
   tei_att.global.attributes,
   attribute type { text }?,
   (
      tei_model.global*,
      tei_model.titlepagePart,
      ( tei_model.titlepagePart | tei_model.global )*
   )
}

5.1.237. <titlePart>

<titlePart> (title part) contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages]
Moduletextstructure — Schema
Attributes
type(type) specifies the role of this subdivision of the title.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
main
(Main title) [Default]
sub
(Subtitle)
Member of
Contained by
textstructure: back docTitle front titlePage
May contain
Example
<titlePage>  <docAuthor>Ludwig Anzengruber</docAuthor>  <docTitle>   <titlePart type="main">Die Kreuzelschreiber</titlePart>   <titlePart type="sub">Bauernkomödie mit Gesang in drei Akten</titlePart>  </docTitle> </titlePage>
Encoding of the title page of the play Anzengruber: Die Kreuzelschreiber.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element titlePart
{
   tei_att.global.attributes,
   attribute type { "main" | "sub" }?,
   tei_macro.paraContent
}

5.1.238. <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader — Schema
Attributes
Contained by
May contain
Example
<titleStmt>  <title type="main">Des Meeres und der Liebe Wellen</title>  <title type="sub">Trauerspiel in fünf Aufzügen</title>  <author>   <persName>    <forename>Franz</forename>    <surname>Grillparzer</surname>   </persName>   <idno type="wikidata">Q154438</idno>   <idno type="pnd">118542192</idno>  </author> </titleStmt>
<titleStmt> of the play "Des Meeres und der Liebe Wellen" by Franz Grillparzer. The author has an entry on Wikidata which is identified by the URI http://www.wikidata.org/entity/Q154438. In the "Gemeinsame Normdatei" (GND) the author is identified by the URI https://d-nb.info/gnd/11854219. The identifiers are included in the <idno> elements.
Example
<titleStmt>  <title type="main">Ревизор</title>  <title type="mainxml:lang="eng">The Government Inspector</title>  <title type="sub">Комедия в пяти действиях</title>  <title type="subxml:lang="eng">A Comedy in Five Acts</title>  <author>   <persName>    <forename>Николай</forename>    <forename type="patronym">Васильевич</forename>    <surname>Гоголь</surname>   </persName>   <persName xml:lang="eng">    <forename>Nikolai</forename>    <surname>Gogol</surname>   </persName>   <idno type="wikidata">Q43718</idno>  </author> </titleStmt>
<titleStmt> of Gogol: Revizor. Titles and author names are given both in Russian and English.
SchematronThe title of the play (see Feature play_title) is retrieved from the first element <title> with the value main of the attribute type.
<sch:rule context="tei:titleStmt"  role="warning"> <sch:assert test="tei:title[@type eq 'main']"> For the DraCor API to include the title of the play in the response an element 'title' with the type-attribute value 'main' SHOULD be included. </sch:assert> </sch:rule>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <classRef key="model.respLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt
{
   tei_att.global.attributes,
   ( tei_title+, tei_model.respLike* )
}

5.1.239. <trailer>

<trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]
Moduletextstructure — Schema
Attributes
Member of
Contained by
May contain
Example
<trailer>Explicit pars tertia</trailer>
Example
<trailer>  <l>In stead of FINIS this advice <hi>I</hi> send,</l>  <l>Let Rogues and Thieves beware of <lb/>   <hi>Hamans</hi> END.</l> </trailer>
From EEBO A87070
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element trailer
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

5.1.240. <unclear>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Modulecore — Schema
Attributes
reasonindicates why the material is hard to transcribe.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
illegible
(illegible)
inaudible
(inaudible)
faded
(faded)
background_noise
(background noise)
eccentric_ductus
(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
<div>  <head>Rx</head>  <p>500 mg <unclear reason="illegible">placebo</unclear>  </p> </div>
Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility.

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.

Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
         )+
      }
   }?,
   attribute agent { text }?,
   tei_macro.paraContent
}

5.1.241. <unit>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<unit> contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. [3.6.3. Numbers and Measures]
Modulecore — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element unit
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.measurement.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

5.1.242. <unitDecl>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
Moduleheader — Schema
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: unitDef
Content model
<content>
 <elementRef key="unitDef" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element unitDecl
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_unitDef+
}

5.1.243. <unitDef>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
Moduleheader — Schema
Attributes
Contained by
header: unitDecl
May contain
header: conversion
namesdates: region
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.labelLike"
   minOccurs="1"/>
  <classRef key="model.placeNamePart"
   minOccurs="0"/>
  <elementRef key="conversion"
   minOccurs="0"/>
  <elementRef key="unit" minOccurs="0"/>
 </alternate>
</content>
    
Schema Declaration
element unitDef
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   (
      tei_model.labelLike
    | tei_model.placeNamePart?
    | tei_conversion?
    | tei_unit?
   )+
}

5.1.244. <view>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<view> (view) describes the visual context of some part of a screen play in terms of what the spectator sees, generally independent of any dialogue. [7.3.1. Technical Information 7.3. Other Types of Performance Text]
Moduledrama — Schema
Attributes
Member of
Contained by
May contain
Note

A view is a particular form of stage direction.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element view { tei_att.global.attributes, tei_macro.specialPara }

5.1.245. <w>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<w> (word) represents a grammatical (not necessarily orthographic) word. [18.1. Linguistic Segment Categories 18.4.2. Lightweight Linguistic Annotation]
Moduleanalysis — Schema
Attributes
Member of
Contained by
May contain
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="seg"/>
  <elementRef key="w"/>
  <elementRef key="m"/>
  <elementRef key="c"/>
  <elementRef key="pc"/>
  <classRef key="model.global"/>
  <classRef key="model.lPart"/>
  <classRef key="model.hiLike"/>
  <classRef key="model.pPart.edit"/>
 </alternate>
</content>
    
Schema Declaration
element w
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.linguistic.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   (
      text
    | tei_model.gLike
    | tei_seg
    | tei_w
    | tei_m
    | tei_c
    | tei_pc
    | tei_model.global
    | tei_model.lPart
    | tei_model.hiLike
    | tei_model.pPart.edit
   )*
}

5.1.246. <when>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<when> indicates a point in time either relative to other elements in the same timeline tag, or absolutely. [17.4.2. Placing Synchronous Events in Time]
Modulelinking — Schema
Attributes
absolutesupplies an absolute value for the time.
StatusOptional
Datatypeteidata.temporal.w3c
Note

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

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

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

Contained by
linking: timeline
May containEmpty element
Note

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

Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element when
{
   tei_att.global.attributes,
   attribute absolute { text }?,
   attribute unit { "d" | "h" | "min" | "s" | "ms" }?,
   attribute interval { text }?,
   attribute since { text }?,
   empty
}

5.1.247. <xenoData>

This element is currently not actively used in DraCor. See full documentation in TEI Guidelines.

<xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
Moduleheader — Schema
Attributes
Member of
Contained by
header: teiHeader
linking: standOff
May containANY
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <textNode/>
  <anyElement minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element xenoData
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( text | anyElement_xenoData_1+ )
}

5.2. Model classes

5.2.1. model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address.
Moduletei — Schema
Used by
Membersmodel.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName nameLink surname] model.placeStateLike[model.placeNamePart[region]] idno rs] addrLine postBox postCode street

5.2.2. model.addressLike

model.addressLike groups elements used to represent a postal or email address.
Moduletei — Schema
Used by
Membersaddress email

5.2.3. model.annotationLike

model.annotationLike groups elements used to represent annotations.
Moduletei — Schema
Used by
Membersannotation note

5.2.4. model.annotationPart.body

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

5.2.5. model.applicationLike

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

5.2.6. model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source.
Moduletei — Schema
Used by
Membersmodel.quoteLike[cit quote] floatingText said

5.2.7. model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement.
Moduletei — Schema
Used by
Memberslicence

5.2.8. model.biblLike

model.biblLike groups elements containing a bibliographic description.
Moduletei — Schema
Used by
Membersbibl biblFull biblStruct listBibl

5.2.9. model.biblPart

model.biblPart groups elements which represent components of a bibliographic description.
Moduletei — Schema
Used by
Membersmodel.imprintPart[biblScope distributor pubPlace publisher] model.respLike[author editor funder meeting principal respStmt sponsor] availability bibl citedRange edition extent listRelation quote relatedItem series textLang

5.2.10. model.castItemPart

model.castItemPart groups component elements of an entry in a cast list, such as dramatic role or actor's name.
Moduletei — Schema
Used by
Membersactor role roleDesc

5.2.11. model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation.
Moduletei — Schema
Used by
Membersabbr corr expan orig reg seg sic unclear

5.2.12. model.common

model.common groups common chunk- and inter-level elements.
Moduletei — Schema
Used by
Membersmodel.cmc model.divPart[model.lLike[l] model.pLike[ab p] lg sp spGrp] model.inter[model.attributable[model.quoteLike[cit quote] floatingText said] model.biblLike[bibl biblFull biblStruct listBibl] model.egLike model.labelLike[desc label] model.listLike[list listEvent listPerson listRelation] model.oddDecl model.stageLike[camera caption move sound stage tech view] castList] q
Note

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

5.2.13. model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Moduletei — Schema
Used by
Membersmodel.addressLike[address email] model.dateLike[date time] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[addName forename genName nameLink surname] model.placeStateLike[model.placeNamePart[region]] idno rs] note noteGrp

5.2.14. model.correspContextPart

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

5.2.15. model.correspDescPart

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

5.2.16. model.dateLike

model.dateLike groups elements containing temporal expressions.
Moduletei — Schema
Used by
Membersdate time

5.2.17. model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei — Schema
Used by
Membersdesc

5.2.18. model.describedResource

model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document.
Moduletei — Schema
Used by
MembersTEI teiCorpus

5.2.19. model.divBottom

model.divBottom groups elements appearing at the end of a text division.
Moduletei — Schema
Used by
Membersmodel.divBottomPart[closer postscript signed trailer] model.divWrapper[argument byline dateline docAuthor docDate epigraph meeting salute]

5.2.20. model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division.
Moduletei — Schema
Used by
Memberscloser postscript signed trailer

5.2.21. model.divGenLike

model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
Moduletei — Schema
Used by
MembersdivGen

5.2.22. model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei — Schema
Used by
Membersdiv

5.2.23. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions.
Moduletei — Schema
Used by
Membersmodel.lLike[l] model.pLike[ab p] lg sp spGrp
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.

5.2.24. model.divTop

model.divTop groups elements appearing at the beginning of a text division.
Moduletei — Schema
Used by
Membersmodel.divTopPart[model.headLike[head] opener signed] model.divWrapper[argument byline dateline docAuthor docDate epigraph meeting salute]

5.2.25. model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division.
Moduletei — Schema
Used by
Membersmodel.headLike[head] opener signed

5.2.26. model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division.
Moduletei — Schema
Used by
Membersargument byline dateline docAuthor docDate epigraph meeting salute

5.2.27. model.editorialDeclPart

model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times.
Moduletei — Schema
Used by
Memberscorrection hyphenation interpretation normalization punctuation quotation segmentation stdVals

5.2.28. model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed.
Moduletei — Schema
Used by
Membersdistinct emph foreign gloss mentioned soCalled term title

5.2.29. model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei — Schema
Used by
MembersappInfo classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl schemaRef styleDefDecl tagsDecl unitDecl

5.2.30. model.eventLike

model.eventLike groups elements which describe events.
Moduletei — Schema
Used by
Membersevent listEvent

5.2.31. model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter.
Moduletei — Schema
Used by
Membersmodel.frontPart.drama[castList epilogue performance prologue set] divGen listBibl titlePage

5.2.32. model.frontPart.drama

model.frontPart.drama groups elements which appear at the level of divisions within front or back matter of performance texts only.
Moduletei — Schema
Used by
MemberscastList epilogue performance prologue set

5.2.34. model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function.
Moduletei — Schema
Used by
Membersellipsis gap

5.2.35. model.global.meta

model.global.meta groups globally available elements which describe the status of other elements.
Moduletei — Schema
Used by
Membersalt altGrp index interp interpGrp join joinGrp link linkGrp span spanGrp timeline
Note

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

5.2.36. model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects.
Moduletei — Schema
Used by
MembersbinaryObject graphic media

5.2.37. model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei — Schema
Used by
Membershead

5.2.38. model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed.
Moduletei — Schema
Used by
Membershi q

5.2.39. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct.
Moduletei — Schema
Used by
Membersmodel.emphLike[distinct emph foreign gloss mentioned soCalled term title] model.hiLike[hi q]

5.2.40. model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints.
Moduletei — Schema
Used by
MembersbiblScope distributor pubPlace publisher

5.2.42. model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Moduletei — Schema
Used by
Membersl

5.2.43. model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei — Schema
Used by
Membersdesc label

5.2.45. model.listLike

model.listLike groups list-like elements.
Moduletei — Schema
Used by
Memberslist listEvent listPerson listRelation

5.2.46. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning.
Moduletei — Schema
Used by
Membersmeasure measureGrp num unit

5.2.47. model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems.
Moduletei — Schema
Used by
Membersanchor cb gb lb milestone pb

5.2.48. model.nameLike

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

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

5.2.49. model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies.
Moduletei — Schema
Used by
Membersname orgName persName
Note

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

5.2.50. model.noteLike

model.noteLike groups globally-available note-like elements.
Moduletei — Schema
Used by
Membersnote noteGrp

5.2.52. model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter.
Moduletei — Schema
Used by
Membersargument byline dateline docAuthor docDate docEdition docImprint docTitle epigraph head titlePart

5.2.53. model.pPart.data

5.2.54. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription.
Moduletei — Schema
Used by
Membersmodel.pPart.editorial[abbr choice expan] model.pPart.transcriptional[add corr del orig reg sic unclear]

5.2.55. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring.
Moduletei — Schema
Used by
Membersabbr choice expan

5.2.56. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials.
Moduletei — Schema
Used by
Membersadd corr del orig reg sic unclear

5.2.58. model.persNamePart

model.persNamePart groups elements which form part of a personal name.
Modulenamesdates — Schema
Used by
MembersaddName forename genName nameLink surname

5.2.59. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei — Schema
Used by
MemberspersName
Note

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

5.2.60. model.personLike

model.personLike groups elements which provide information about people and their relationships.
Moduletei — Schema
Used by
Membersperson personGrp

5.2.61. model.personPart

model.personPart groups elements which form part of the description of a person.
Moduletei — Schema
Used by
Membersmodel.biblLike[bibl biblFull biblStruct listBibl] model.eventLike[event listEvent] model.persStateLike[persName] idno name

5.2.63. model.placeNamePart

model.placeNamePart groups elements which form part of a place name.
Moduletei — Schema
Used by
Membersregion

5.2.64. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei — Schema
Used by
Membersmodel.placeNamePart[region]

5.2.65. model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei — Schema
Used by
Membersabstract calendarDesc correspDesc creation langUsage particDesc textClass

5.2.66. model.ptrLike

model.ptrLike groups elements used for purposes of location and reference.
Moduletei — Schema
Used by
Membersptr ref

5.2.67. model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent.
Moduletei — Schema
Used by
Membersauthority distributor publisher
Note

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

See also model.publicationStmtPart.detail.

5.2.68. model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header.
Moduletei — Schema
Used by
Membersmodel.ptrLike[ptr ref] address availability date idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

5.2.69. model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei — Schema
Used by
Memberscit quote

5.2.70. model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata.
Moduletei — Schema
Used by
MembersstandOff text

5.2.71. model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei — Schema
Used by
Membersauthor editor funder meeting principal respStmt sponsor

5.2.72. model.segLike

model.segLike groups elements used for arbitrary segmentation.
Moduletei — Schema
Used by
Membersc cl m pc phr s seg w
Note

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

5.2.73. model.stageLike

model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts.
Moduletei — Schema
Used by
Memberscamera caption move sound stage tech view
Note

Stage directions are members of class inter: that is, they can appear between or within component-level elements.

5.2.75. model.teiHeaderPart

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

5.2.76. model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>.
Moduletei — Schema
Used by
Membersargument binaryObject byline docAuthor docDate docEdition docImprint docTitle epigraph graphic imprimatur titlePart

5.3. Attribute classes

5.3.1. att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Moduletei — Schema
Membersnote noteGrp
Attributes
anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Note

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

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

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

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <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>

5.3.2. att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual.
Moduletei — Schema
Membersatt.ascribed.directed[move q said sp spGrp stage] change
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <role> elements in the <castList> using the who attribute.
<castItem type="role">  <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role">  <role xml:id="Francisco">Francisco</role>  <roleDesc>a soldier</roleDesc> </castItem> <sp who="#Barnardo">  <speaker>Bernardo</speaker>  <l n="1">Who's there?</l> </sp> <sp who="#Francisco">  <speaker>Francisco</speaker>  <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
Note

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

5.3.3. att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual.
Moduletei — Schema
Membersmove q said sp spGrp stage
Attributes
toWhomindicates the person, or group of people, to whom a speech act or action is directed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.
<castItem type="role">  <role xml:id="emil">Emilius.</role> </castItem> <castItem type="role">  <role xml:id="lov">Lovisa</role> </castItem> <castItem type="role">  <role xml:id="serv">A servant</role> </castItem> <sp who="#emil"  toWhom="#lov">  <speaker>Emil.</speaker>  <l n="1">My love!</l> </sp> <sp who="#lov"  toWhom="#emil">  <speaker>Lov.</speaker>  <l n="2">I have no Witness of my Noble Birth</l>  <stage who="emil"   toWhom="#serv">Pointing to her Woman.</stage>  <l>But that poor helpless wretch——</l> </sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

5.3.4. att.breaking

att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace.
Moduletei — Schema
Memberscb gb lb milestone pb
Attributes
breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
StatusRecommended
Datatypeteidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, the words lāðost and reord-berendum each start on one line and continue onto the next.
<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

5.3.5. att.cReferencing

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

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

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

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

5.3.6. att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs.
Moduletei — Schema
Membersdate docDate time
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

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

5.3.7. att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Moduletei — Schema
Membersatt.naming[att.personal[addName forename genName name orgName persName surname] author editor event pubPlace region rs] actor authority bibl biblFull biblStruct catDesc correspDesc date distributor docAuthor docTitle funder meeting principal publisher relation resp respStmt sponsor term time title unitDecl unitDef
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

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

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

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

ExampleIn this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

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

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

5.3.8. att.citeStructurePart

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

5.3.9. att.citing

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

5.3.10. att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei — Schema
Membersab abbr add addName address alt altGrp anchor argument bibl biblFull biblStruct binaryObject byline c cb choice cit cl closer corr date dateline del desc distinct docAuthor docDate email emph epigraph expan figure floatingText foreign forename gap gb genName gloss graphic head hi idno index interp interpGrp join joinGrp l label lb lg link linkGrp list listBibl listEvent listPerson listRelation m measure measureGrp media meeting mentioned milestone name nameLink note noteGrp num opener orgName orig p pb pc persName phr postscript ptr q quote ref reg region rs ruby s said salute seg sic signed soCalled span spanGrp stage surname term time timeline title trailer unclear unit w
Attributes
generatedBy(generated by) categorizes how the content of an element was generated in a CMC environment.
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:*[@generatedBy]"> <sch:assert test="ancestor-or-self::tei:post">The @generatedBy attribute is for use within a <post> element.</sch:assert> </sch:rule>
Suggested values include:
human
the content was ‘naturally’ typed or spoken by a human user
template
the content was generated after a human user activated a template for its insertion
system
the content was generated by the system, i.e. the CMC environment
bot
the content was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself
unspecified
the content was generated by an unknown or unspecified process
automatic system message in chat: user moves on to another chatroom
<post type="event"  generatedBy="system"  who="#system"  rend="color:blue">  <p>   <name type="nickname"    corresp="#A02">McMike</name> geht    in einen anderen Raum: <name type="roomname">Kreuzfahrt</name>  </p> </post>
automatic system message in chat: user enters a chatroom
<post type="event"  generatedBy="system">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> betritt    den Raum. </p> </post>
automatic system message in chat: user changes his font color
<post type="event"  generatedBy="system"  rend="color:red">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> hat die    Farbe gewechselt.  </p> </post>
An automatic signature of user including an automatic timestamp (Wikipedia discussion, anonymized). The specification of generatedBy at the inner element <signed> is meant to override the specification at the outer element <post>. This is generally possible when the outer generatedBy value is "human".
<post type="standard"  generatedBy="human"  indentLevel="2"  synch="#t00394407"  who="#WU00005582">  <p> Kurze Nachfrage: Die Hieros für den Goldnamen stammen    auch von Beckerath gem. Literatur ? Grüße —</p>  <signed generatedBy="template"   rend="inline">   <gap reason="signatureContent"/>   <time generatedBy="template">18:50, 22. Okt. 2008 (CEST)</time>  </signed> </post>
Wikipedia talk page: user signature
<post type="written"  generatedBy="human">  <signed generatedBy="template">   <gap reason="signatureContent"/>   <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>  </signed> </post>

5.3.11. att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
Moduletei — Schema
Membersapplication author change conversion creation date docDate editor event funder idno licence meeting name orgName persName principal region relation resp sponsor time title unitDecl unitDef
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s, or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

5.3.12. att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
Moduletei — Schema
Membersatt.datable[application author change conversion creation date docDate editor event funder idno licence meeting name orgName persName principal region relation resp sponsor time title unitDecl unitDef]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

5.3.13. att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them.
Moduletei — Schema
Membersatt.segLike[c cl m pc phr s seg w] category tagUsage taxonomy
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </f> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f name="POSfVal="#commonNoun"/> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol xml:id="commonNounvalue="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNounvalue="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
ExampleIn 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="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="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>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc>  <classDecl>   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category>   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
ExampleThe 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.
<encodingDesc>  <classDecl>   <taxonomy xml:id="domains">    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss/>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss/>      </catDesc>     </category>    </category>   </taxonomy>  </classDecl> </encodingDesc> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

5.3.14. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei — Schema
Membersadd date del ellipsis gap time unclear
Attributes
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

5.3.15. att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions.
Moduletei — Schema
Membersdiv lg
Attributes
org(organization) specifies how the content of the division is organized.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

5.3.16. att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Moduletei — Schema
Memberscb gb lb milestone pb refState
Attributes
ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>  <bibl xml:id="stapledon1937">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>  </bibl>  <bibl xml:id="stapledon1968">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>  </bibl> </listBibl> <p>Looking into the future aeons from the supreme moment of the cosmos, I saw the populations still with all their strength maintaining the<pb n="411edRef="#stapledon1968"/>essentials of their ancient culture, still living their personal lives in zest and endless novelty of action, … I saw myself still preserving, though with increasing difficulty, my lucid con-<pb n="291edRef="#stapledon1937"/>sciousness;</p>

5.3.17. att.formula

att.formula provides attributes for defining a mathematical formula.
Moduletei — Schema
Membersconversion
Attributes
formulaA formula is provided to describe a mathematical calculation such as a conversion between measurement systems.
StatusOptional
Datatypeteidata.xpath
Example
<encodingDesc>  <unitDecl>   <unitDef xml:id="stadiumtype="linear">    <label>stadium</label>    <placeName ref="#rome"/>    <conversion fromUnit="#pes"     toUnit="#stadiumformula="$fromUnit * 625"/>    <desc>The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<encodingDesc>  <unitDecl>   <unitDef xml:id="wmwtype="power">    <label>whatmeworry</label>    <conversion fromUnit="#hpk"     toUnit="#wmwformula="$fromUnit * 1"/>    <desc>In the Potrzebie system of measures as introduced by Donald Knuth, the whatmeworry unit of power is equivalent to one hah per kovac.</desc>   </unitDef>   <unitDef xml:id="kwmwtype="power">    <label>kilowhatmeworry</label>    <conversion fromUnit="#wmw"     toUnit="#kwmwformula="$fromUnit div 1000"/>    <desc>The kilowhatmeworry is equivalent to 1000 whatmeworries.</desc>   </unitDef>   <unitDef xml:id="aptype="power">    <label>kilowhatmeworry</label>    <conversion fromUnit="#kwmw"     toUnit="#apformula="$fromUnit div 100"/>    <desc>One unit of aeolipower (A.P.) is equivalent to 100 kilowhatmeworries.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<conversion fromUnit="#furlongsPerFortnight"  toUnit="#milesPerHour"  formula="$fromUnit cast as xs:decimal * 0.000372"/>
Example
<conversion fromUnit="#deciday"  toUnit="hour"  formula="$fromUnit cast as xs:decimal * 144 div 60"/>
Note

This attribute class provides formula for use in defining a value used in mathematical calculation. It can be used to store a mathematical operation needed to convert from one system of measurement to another. We use the teidata.xpath datatype to express this value in order to communicate mathematical operations on an XML node or nodes. The $fromUnit variable notation simplifies referencing of the fromUnit attribute on the parent <conversion> element. Note that ‘div’ is required to express the division operator in XPath.

5.3.18. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei — Schema
Membersatt.divLike[div lg] att.segLike[c cl m pc phr s seg w] ab l p
Attributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

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

5.3.19. att.global

att.global provides a set of attributes common to all elements in the tei_drama customization of the TEI encoding scheme.
Moduletei — Schema
MembersTEI ab abbr abstract actor add addName addrLine address alt altGrp analytic anchor annotation appInfo application argument author authority availability back bibl biblFull biblScope biblStruct binaryObject body byline c cRefPattern calendar calendarDesc camera caption castGroup castItem castList catDesc catRef category cb change choice cit citeData citeStructure citedRange cl classCode classDecl closer conversion corr correction correspAction correspContext correspDesc creation date dateline del desc distinct distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph epilogue event expan extent figure fileDesc floatingText foreign forename front funder gap gb genName geoDecl gloss graphic group handNote head headItem headLabel hi hyphenation idno imprimatur imprint index interp interpGrp interpretation item join joinGrp keywords l label langUsage language lb lg licence link linkGrp list listAnnotation listBibl listChange listEvent listPerson listPrefixDef listRelation m measure measureGrp media meeting mentioned milestone monogr move name nameLink namespace normalization note noteGrp notesStmt num opener orgName orig p particDesc pb pc performance persName person personGrp phr postBox postCode postscript prefixDef principal profileDesc projectDesc prologue ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation rendition resp respStmt revisionDesc role roleDesc rs rt ruby s said salute samplingDecl schemaRef scriptNote seg segmentation series seriesStmt set sic signed soCalled sound sourceDesc sp spGrp span spanGrp speaker sponsor stage standOff stdVals street styleDefDecl surname tagUsage tagsDecl taxonomy tech teiCorpus teiHeader term text textClass textLang time timeline title titlePage titlePart titleStmt trailer unclear unit unitDecl unitDef view w when xenoData
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

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

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

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

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

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

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

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

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

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

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

5.3.20. att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text.
Moduleanalysis — Schema
Membersatt.global[TEI ab abbr abstract actor add addName addrLine address alt altGrp analytic anchor annotation appInfo application argument author authority availability back bibl biblFull biblScope biblStruct binaryObject body byline c cRefPattern calendar calendarDesc camera caption castGroup castItem castList catDesc catRef category cb change choice cit citeData citeStructure citedRange cl classCode classDecl closer conversion corr correction correspAction correspContext correspDesc creation date dateline del desc distinct distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph epilogue event expan extent figure fileDesc floatingText foreign forename front funder gap gb genName geoDecl gloss graphic group handNote head headItem headLabel hi hyphenation idno imprimatur imprint index interp interpGrp interpretation item join joinGrp keywords l label langUsage language lb lg licence link linkGrp list listAnnotation listBibl listChange listEvent listPerson listPrefixDef listRelation m measure measureGrp media meeting mentioned milestone monogr move name nameLink namespace normalization note noteGrp notesStmt num opener orgName orig p particDesc pb pc performance persName person personGrp phr postBox postCode postscript prefixDef principal profileDesc projectDesc prologue ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation rendition resp respStmt revisionDesc role roleDesc rs rt ruby s said salute samplingDecl schemaRef scriptNote seg segmentation series seriesStmt set sic signed soCalled sound sourceDesc sp spGrp span spanGrp speaker sponsor stage standOff stdVals street styleDefDecl surname tagUsage tagsDecl taxonomy tech teiCorpus teiHeader term text textClass textLang time timeline title titlePage titlePart titleStmt trailer unclear unit unitDecl unitDef view w when xenoData]
Attributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

5.3.21. att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme.
Moduletei — Schema
Membersatt.global[TEI ab abbr abstract actor add addName addrLine address alt altGrp analytic anchor annotation appInfo application argument author authority availability back bibl biblFull biblScope biblStruct binaryObject body byline c cRefPattern calendar calendarDesc camera caption castGroup castItem castList catDesc catRef category cb change choice cit citeData citeStructure citedRange cl classCode classDecl closer conversion corr correction correspAction correspContext correspDesc creation date dateline del desc distinct distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph epilogue event expan extent figure fileDesc floatingText foreign forename front funder gap gb genName geoDecl gloss graphic group handNote head headItem headLabel hi hyphenation idno imprimatur imprint index interp interpGrp interpretation item join joinGrp keywords l label langUsage language lb lg licence link linkGrp list listAnnotation listBibl listChange listEvent listPerson listPrefixDef listRelation m measure measureGrp media meeting mentioned milestone monogr move name nameLink namespace normalization note noteGrp notesStmt num opener orgName orig p particDesc pb pc performance persName person personGrp phr postBox postCode postscript prefixDef principal profileDesc projectDesc prologue ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation rendition resp respStmt revisionDesc role roleDesc rs rt ruby s said salute samplingDecl schemaRef scriptNote seg segmentation series seriesStmt set sic signed soCalled sound sourceDesc sp spGrp span spanGrp speaker sponsor stage standOff stdVals street styleDefDecl surname tagUsage tagsDecl taxonomy tech teiCorpus teiHeader term text textClass textLang time timeline title titlePage titlePart titleStmt trailer unclear unit unitDecl unitDef view w when xenoData]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note

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

5.3.22. att.global.source

att.global.source provides attributes used by elements to point to an external source.
Moduletei — Schema
Membersatt.global[TEI ab abbr abstract actor add addName addrLine address alt altGrp analytic anchor annotation appInfo application argument author authority availability back bibl biblFull biblScope biblStruct binaryObject body byline c cRefPattern calendar calendarDesc camera caption castGroup castItem castList catDesc catRef category cb change choice cit citeData citeStructure citedRange cl classCode classDecl closer conversion corr correction correspAction correspContext correspDesc creation date dateline del desc distinct distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph epilogue event expan extent figure fileDesc floatingText foreign forename front funder gap gb genName geoDecl gloss graphic group handNote head headItem headLabel hi hyphenation idno imprimatur imprint index interp interpGrp interpretation item join joinGrp keywords l label langUsage language lb lg licence link linkGrp list listAnnotation listBibl listChange listEvent listPerson listPrefixDef listRelation m measure measureGrp media meeting mentioned milestone monogr move name nameLink namespace normalization note noteGrp notesStmt num opener orgName orig p particDesc pb pc performance persName person personGrp phr postBox postCode postscript prefixDef principal profileDesc projectDesc prologue ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation rendition resp respStmt revisionDesc role roleDesc rs rt ruby s said salute samplingDecl schemaRef scriptNote seg segmentation series seriesStmt set sic signed soCalled sound sourceDesc sp spGrp span spanGrp speaker sponsor stage standOff stdVals street styleDefDecl surname tagUsage tagsDecl taxonomy tech teiCorpus teiHeader term text textClass textLang time timeline title titlePage titlePart titleStmt trailer unclear unit unitDecl unitDef view w when xenoData]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> </p>
Example
<p>  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> </p> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="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"/>
Create a schema using components taken from the file mycompiledODD.xml.

5.3.23. att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written.
Moduletei — Schema
MembershandNote scriptNote
Attributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatypeteidata.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

5.3.24. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei — Schema
Membersatt.media[binaryObject graphic media] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn 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.

5.3.25. att.interpLike

att.interpLike provides attributes for elements which represent a formal analysis or interpretation.
Moduletei — Schema
Membersinterp interpGrp span spanGrp
Attributes
typeindicates what kind of phenomenon is being noted in the passage.
StatusRecommended
Datatypeteidata.enumerated
Sample values include:
image
identifies an image in the passage.
character
identifies a character associated with the passage.
theme
identifies a theme in the passage.
allusion
identifies an allusion to another text.
subtype(subtype) provides a sub-categorization of the phenomenon is being noted in the passage, if needed.
StatusOptional
Datatypeteidata.enumerated
Note

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

inst(instances) points to instances of the analysis or interpretation represented by the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The current element should be an analytic one. The element pointed at should be a textual one.

5.3.26. att.lexicographic.normalized

att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.
Moduleanalysis — Schema
Membersatt.linguistic[pc w]
Attributes
norm(normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form.
StatusOptional
Datatypeteidata.text
Normalization of part-of-speech information within a dictionary entry.
<gramGrp>  <pos norm="noun">n</pos> </gramGrp>
Normalization of a source form in a tokenized historical corpus.
<s>  <w>for</w>  <w norm="virtue's">vertues</w>  <w>sake</w> </s>
<s>  <w norm="persuasion">perswasion</w>  <w>of</w>  <w norm="Unity">Vnitie</w> </s>
Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.
<s>  <w norm="freiwillig">freywillig</w>  <pc norm=","   join="left">/</pc>  <w norm="unbedrängt">vnbedraͤngt</w>  <w norm="und">vnd</w>  <w norm="unverhindert">vnuerhindert</w> </s>
<w norm="Teil">Theyll</w>
<w norm="Freude">Frewde</w>
orig(original) gives the original string or is the empty string when the element does not appear in the source text.
StatusOptional
Datatypeteidata.text
Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:
<w orig="ntsa sia'i">ntsasia'i</w>
Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:
<w lemma="he"  pos="pns"  xml:id="b1afj-003-a-0950">he</w> <w lemma="have"  pos="vvz"  xml:id="b1afj-003-a-0960">hath</w> <w lemma="bring"  pos="vvn"  xml:id="b1afj-003-a-0970">brought</w> <w lemma="forth"  pos="av"  xml:id="b1afj-003-a-0980"  orig="sorth">forth</w>
An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:
<w lemma="commandment"  pos="n1"  norm="commandment"  xml:id="b9avr-018-a-7720"  orig="commandemēt">commandement</w>
Note

It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, <orig>, and <reg> needs to be employed.

5.3.27. att.linguistic

att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically <w> and <pc> in the analysis module.
Moduleanalysis — Schema
Memberspc w
Attributes
lemmaprovides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
StatusOptional
Datatypeteidata.text
<w lemma="wife">wives</w>
<w lemma="Arznei">Artzeneyen</w>
lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
StatusOptional
Datatypeteidata.pointer
<w type="verb"  lemma="hit"  lemmaRef="http://www.example.com/lexicon/hitvb.xml">hitt<m type="suffix">ing</m> </w>
pos(part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.).
StatusOptional
Datatypeteidata.text
The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).
<s>  <w pos="PPER">Wir</w>  <w pos="VVFIN">fahren</w>  <w pos="APPR">in</w>  <w pos="ART">den</w>  <w pos="NN">Urlaub</w>  <w pos="$.">.</w> </s>
The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).
<p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p>         
The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.
<p>  <w pos="PPIS2">We</w>  <w pos="VBR">'re</w>  <w pos="VVG">going</w>  <w pos="II">on</w>  <w pos="NN1">vacation</w>  <w pos="II">to</w>  <w pos="NP1">Brazil</w>  <w pos="IF">for</w>  <w pos="AT1">a</w>  <w pos="NNT1">month</w>  <pc pos="!">!</pc> </p>
msd(morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features).
StatusOptional
Datatypeteidata.text
<ab>  <w pos="PPER"   msd="1.Pl.*.Nom">Wir</w>  <w pos="VVFIN"   msd="1.Pl.Pres.Ind">fahren</w>  <w pos="APPR"   msd="--">in</w>  <w pos="ART"   msd="Def.Masc.Akk.Sg">den</w>  <w pos="NN"   msd="Masc.Akk.Sg">Urlaub</w>  <pc pos="$."   msd="--">.</pc> </ab>
joinwhen present, provides information on whether the token in question is adjacent to another, and if so, on which side.
StatusOptional
Datatypeteidata.text
Legal values are:
no
the token is not adjacent to another
left
there is no whitespace on the left side of the token
right
there is no whitespace on the right side of the token
both
there is no whitespace on either side of the token
overlap
the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream
The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.
<s>  <pc join="right">"</pc>  <w join="left">Friends</w>  <w>will</w>  <w>be</w>  <w join="right">friends</w>  <pc join="both">.</pc>  <pc join="left">"</pc> </s>
Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.
The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.
<p>  <w pos="PNP">We</w>  <w pos="VBB"   join="left">'re</w>  <w pos="VVG">going</w>  <w pos="PRP">on</w>  <w pos="NN1">vacation</w>  <pc pos="PUN"   join="left">.</pc> </p>
Note

The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.

Note

These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 18.4.2. Lightweight Linguistic Annotation for discussion.

5.3.28. att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places.
Moduletei — Schema
Membersconversion event
Attributes
whereindicates one or more locations by pointing to a <place> element or other canonical description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

5.3.29. att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei — Schema
Membersmeasure measureGrp unit
Attributes
unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
Ω
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
Å
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
Note

If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

unitRefpoints to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
StatusOptional
Datatypeteidata.pointer
quantity(quantity) specifies the number of the specified units that comprise the measurement
StatusOptional
Datatypeteidata.numeric
commodity(commodity) indicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron
<sch:rule context="tei:*[@unitRef]"> <sch:report test="@unit" role="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure quantity="0.5unit="gal"   commodity="ice cream">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure quantity="1.893unit="L"   commodity="ice cream">half    a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

5.3.30. att.media

att.media provides attributes for specifying display and related properties of external media.
Moduletei — Schema
MembersbinaryObject graphic media
Attributes
widthWhere the media are displayed, indicates the display width.
StatusOptional
Datatypeteidata.outputMeasurement
heightWhere the media are displayed, indicates the display height.
StatusOptional
Datatypeteidata.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size.
StatusOptional
Datatypeteidata.numeric

5.3.31. att.milestoneUnit

att.milestoneUnit provides attributes to indicate the type of section which is changing at a specific milestone.
Modulecore — Schema
Membersmilestone refState
Attributes
unitprovides a conventional name for the kind of section changing at this milestone.
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
page
physical page beginnings (synonymous with the <pb> element).
column
column beginnings.
line
line beginnings (synonymous with the <lb> element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
<milestone n="23"  ed="La"  unit="Dreissiger"/> ... <milestone n="24"  ed="AV"  unit="verse"/> ...
Note

If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next <milestone> tag for the edition in question is encountered.

In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

The type attribute may be used to characterize the unit boundary in any respect other than simply identifying the type of unit, for example as word-breaking or not.

5.3.32. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.
Moduletei — Schema
Membersatt.personal[addName forename genName name orgName persName surname] author editor event pubPlace region rs
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

5.3.33. att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei — Schema
Membersc cl listAnnotation m phr quote s seg w
Attributes
notationnames the notation used for the content of the element.
StatusOptional
Datatypeteidata.enumerated

5.3.34. att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement.
Moduleheader — Schema
MemberscRefPattern prefixDef
Attributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatypeteidata.pattern
Note

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.

replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
StatusRequired
Datatypeteidata.replacement
Note

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

5.3.35. att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name.
Moduletei — Schema
MembersaddName forename genName name orgName persName surname
Attributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

5.3.36. att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears.
Moduletei — Schema
Membersdiv figure head label note noteGrp postscript sp speaker stage trailer
Attributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

5.3.37. att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references.
Moduletei — Schema
Membersatt.pointing.group[altGrp joinGrp linkGrp] alt annotation calendar catRef citedRange gloss join licence link note noteGrp ptr ref span term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

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

targetspecifies the destination of the reference by supplying one or more URI References.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

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

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

5.3.38. att.pointing.group

att.pointing.group provides a set of attributes common to all elements which enclose groups of pointer elements.
Moduletei — Schema
MembersaltGrp joinGrp linkGrp
Attributes
domainsoptionally specifies the identifiers of the elements within which all elements indicated by the contents of this element lie.
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
Note

If this attribute is supplied every element specified as a target must be contained within the element or elements named by it. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but in the wrong context. If this attribute is not supplied, then target elements may appear anywhere within the target document.

targFunc(target function) describes the function of each of the values of the target attribute of the enclosed <link>, <join>, or <alt> tags.
StatusOptional
Datatype2–∞ occurrences of teidata.word separated by whitespace
Note

The number of separate values must match the number of values in the target attribute in the enclosed <link>, <join>, or <alt> tags (an intermediate <ptr> element may be needed to accomplish this). It should also match the number of values in the domains attribute, of the current element, if one has been specified.

5.3.39. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei — Schema
Membersatt.dimensions[add date del ellipsis gap time unclear] measure num
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatypeteidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegible"   extent="one or two lettersatLeast="1atMost="2unit="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="120000000unit="USD"  commodity="currency">more than $120m</measure> in aid to Ukrainians.

5.3.40. att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Moduletei — Schema
Membersgraphic media schemaRef
Attributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
StatusRequired
Datatypeteidata.pointer

5.3.41. att.scope

att.scope provides attributes to describe, in general terms, the scope of an element’s application.
Moduletei — Schema
Membersatt.handFeatures[handNote scriptNote] language
Attributes
scopeindicates the scope of application of the element
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sole
only this particular feature is used throughout the document
major
this feature is used through most of the document
minor
this feature is used occasionally through the document
<langUsage>  <language ident="en"   scope="major"/>  <language ident="es"   scope="minor"/>  <language ident="x-ww"   scope="minor">An invented language the children call <name>Wikwah</name>.</language> </langUsage>
<handNote scope="sole">  <p>Written in insular phase II half-uncial with    interlinear Old English gloss in an Anglo-Saxon    pointed minuscule.</p> </handNote>

5.3.42. att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation.
Moduletei — Schema
Membersc cl m pc phr s seg w
Attributes
function(function) characterizes the function of the segment.
StatusOptional
Datatypeteidata.enumerated
Note

Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

5.3.43. att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content.
Moduletei — Schema
Membersbibl biblFull biblStruct correspAction event idno item list listBibl listChange listEvent listPerson listRelation person personGrp relation term
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

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

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

5.3.44. att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it.
Moduletei — Schema
Memberscb gb index lb milestone pb
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatypeteidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element; however, this can only be tested if both this element and the one pointed to are in the same document.
<sch:rule context="tei:*[ starts-with( @spanTo, '#') ]"> <sch:assert test="id( substring( @spanTo, 2 ) ) >> .">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current <sch:name/> element </sch:assert> </sch:rule>
Note

The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

5.3.45. att.styleDef

att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
Moduletei — Schema
Membersrendition styleDefDecl
Attributes
schemeidentifies the language used to describe the rendition.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
css
Cascading Stylesheet Language
xslfo
Extensible Stylesheet Language Formatting Objects
free
Informal free text description
other
A user-defined rendition description language
Note

If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

schemeVersionsupplies a version number for the style language provided in scheme.
StatusOptional
Datatypeteidata.versionNumber
Schematron
<sch:rule context="tei:*[@schemeVersion]"> <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified. </sch:assert> </sch:rule>
Note

If schemeVersion is used, then scheme should also appear, with a value other than free.

5.3.46. att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map.
Moduletei — Schema
MembersbinaryObject ellipsis gap media
Attributes
startindicates the location within a temporal alignment at which this element begins.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

endindicates the location within a temporal alignment at which this element ends.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

5.3.47. att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way.
Moduletei — Schema
Membersatt.pointing.group[altGrp joinGrp linkGrp] TEI ab abbr add addName alt anchor application bibl biblStruct binaryObject c calendar camera castItem cb change cit cl corr correspAction correspDesc date del desc distinct div divGen event figure floatingText forename gb genName gloss graphic group head idno join label lb lg link list listAnnotation listBibl listChange listEvent listPerson listRelation m measure measureGrp media milestone move name nameLink note noteGrp num orgName pb pc persName phr ptr quote rb ref reg region relatedItem relation rs rt ruby s schemaRef seg sound spGrp standOff surname tech teiCorpus term text time title titlePage titlePart trailer unit unitDef w xenoData
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

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

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 .

5.4. Macros

5.4.1. macro.abContent

macro.abContent (anonymous block content) defines the content of anonymous block elements.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
  <elementRef key="ab"/>
 </alternate>
</content>
    
Declaration
tei_macro.abContent = ( text | tei_model.paraPart | tei_ab )*

5.4.2. macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
tei_macro.limitedContent =
   ( text | tei_model.limitedPhrase | tei_model.inter )*

5.4.3. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
tei_macro.paraContent = ( text | tei_model.paraPart )*

5.4.4. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

5.4.5. macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq.limited =
   ( text | tei_model.limitedPhrase | tei_model.global )*

5.4.6. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.specialPara =
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.divPart
    | tei_model.global
   )*

5.4.7. macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei — Schema
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    
Declaration
tei_macro.xtext = ( text | tei_model.gLike )*

5.5. Datatypes

5.5.1. teidata.authority

teidata.authority defines attribute values which derive from an authority list, which may be an enumerated list defined in the document's schema, a list or taxonomy elsewhere in the document, or an online taxonomy, gazetteer, or other authority.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef key="teidata.enumerated"/>
  <dataRef key="teidata.pointer"/>
 </alternate>
</content>
    
Declaration
tei_teidata.authority = teidata.enumerated | teidata.pointer
Note

Attribute values with this datatype should either come from a value list in the attribute specification (teidata.enumerated) or be a valid URI (teidata.pointer).

5.5.2. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei — Schema
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.

5.5.3. teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
tei_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

5.5.4. teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei — Schema
Used by
teidata.authority 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.

5.5.5. teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Moduletei — Schema
Used by
Element:
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).

5.5.6. teidata.interval

teidata.interval defines attribute values used to express an interval value.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <dataRef name="float"/>
  <valList>
   <valItem ident="regular"/>
   <valItem ident="irregular"/>
   <valItem ident="unknown"/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.interval = xsd:float | ( "regular" | "irregular" | "unknown" )
Note

Any value greater than zero or any one of the values regular, irregular, unknown.

5.5.7. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <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.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. There are currently only two extensions in use. Extension T indicates that the content was transformed. For example en-t-it could be used for content in English that was translated from Italian. Extension T is described in the informational RFC 6497. Extension U can be used to embed a variety of locale attributes. It is described in the informational RFC 6067.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

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

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

Examples include

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

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

5.5.8. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei — Schema
Used by
Element:
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.

5.5.9. teidata.namespace

teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
tei_teidata.namespace = xsd:anyURI { pattern = "\S+" }
Note

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

5.5.10. teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <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.

5.5.11. teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei — Schema
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="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
Note

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

5.5.12. teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Moduletei — Schema
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 H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

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.

5.5.13. teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei — Schema
Used by
teidata.authorityElement:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</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, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

5.5.14. teidata.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
tei_teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
Note

This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

5.5.15. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Moduletei — Schema
Used by
Element:
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.

5.5.16. teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Moduletei — Schema
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.replacement = text

5.5.17. teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Moduletei — Schema
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.

5.5.18. teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <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.

5.5.19. teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <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.

5.5.20. teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Moduletei — Schema
Used by
Element:
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.

5.5.21. teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei — Schema
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.

5.5.22. teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei — Schema
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.

5.5.23. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei — Schema
Used by
Element:
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}" }

5.5.24. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei — Schema
Used by
teidata.enumeratedElement:
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.

5.5.25. teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <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.

5.5.26. teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Moduletei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Declaration
tei_teidata.xmlName = xsd:NCName
Note

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

5.5.27. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei — Schema
Used by
Element:
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.

5.6. Constraints

SchematronEncoding Hint: Wikidata Identifier There are some common errors when connecting a play to the respective entity on Wikidata:
  • Use the wrong base-URI of the Wikidata entity. MUST be http://www.wikidata.org/entity/{QID} NOT https://www.wikidata.org/wiki/{QID}
  • The value of the attribute passive is NOT the self-URI of the play following the pattern "https://dracor.org/entity/{play_id}"
See also Wikidata QID of a play for details on how to correctly assign a Wikidata Identifier (QID). The equivalent API Feature that relies on the correct encoding is play_wikidata_id.
<sch:rule context="tei:TEI/tei:standOff/tei:listRelation/tei:relation[@name eq 'wikidata']"  role="warning"  see="https://dracor.org/doc/odd#section-play-wikidata"> <sch:let name="expected_play_uri"  value="concat('https://dracor.org/entity/',./ancestor::tei:TEI/@xml:id/string())"/> <sch:assert test="starts-with(./@passive/string(),'http://www.wikidata.org/entity/')"> The value of the attribute '@passive' MUST start with "http://www.wikidata.org/entity/" to be a valid Wikidata URI. </sch:assert> <sch:assert test="./@active/string() eq $expected_play_uri"> The value of the attribute '@active' SHOULD follow the pattern "https://dracor.org/entity/{play_id}. [Expected value: '<xsl:value-of select="$expected_play_uri"/>']" </sch:assert> </sch:rule>
SchematronFeature-Check: P2 play_id
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_id"> <sch:let name="play_id"  value="/tei:TEI/@xml:id/string()"/> <sch:report test="/tei:TEI/@xml:id"> Supported API feature: play_id [value: <sch:value-of select="$play_id"/>]</sch:report> </sch:rule>
SchematronFeature-Check: P6 play_subtitle
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_subtitle"> <sch:let name="play_subtitle"  value="/tei:TEI/tei:teiHeader/tei:fileDesc/tei:titleStmt/tei:title[@type = 'sub' and not(@xml:lang or ./ancestor::tei:TEI/@xml:lang = @xml:lang)]/normalize-space()"/> <sch:report test="tei:TEI/tei:teiHeader/tei:fileDesc/tei:titleStmt/tei:title[@type='sub']"> Supported API feature: play_subtitle [value: <sch:value-of select="$play_subtitle"/>] </sch:report> </sch:rule>
SchematronFeature-Check: P5 play_title
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_title"> <sch:let name="play_title"  value="/tei:TEI/tei:teiHeader/tei:fileDesc/tei:titleStmt/tei:title[not(@type = 'sub') and not(@xml:lang or ./ancestor::tei:TEI/@xml:lang = @xml:lang)]/normalize-space()"/> <sch:report test="/tei:TEI/tei:teiHeader/tei:fileDesc/tei:titleStmt/tei:title[not(@type = 'sub') and not(@xml:lang or ./ancestor::tei:TEI/@xml:lang = @xml:lang)]"> Supported API feature: play_title [value: <sch:value-of select="$play_title"/>] </sch:report> </sch:rule>
SchematronFeature-Check: P4 play_wikidata_id
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_wikidata_id"> <sch:let name="play_wikidata"  value="/tei:TEI/tei:standOff/tei:listRelation/tei:relation[@name eq 'wikidata']/@passive/string()"/> <sch:report test="/tei:TEI/tei:standOff/tei:listRelation/tei:relation[@name eq 'wikidata']/@passive[starts-with(.,'http://www.wikidata.org/entity/')]"> Supported API feature: play_wikidata_id [value: <sch:value-of select="substring-after($play_wikidata, 'http://www.wikidata.org/entity/')"/>] </sch:report> </sch:rule>
SchematronFeature-Check: P25 play_year_printed
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_year_printed"> <sch:let name="play_year_printed"  value="/tei:TEI/tei:standOff/tei:listEvent/tei:event[@type eq 'print']/@when/string()"/> <sch:report test="/tei:TEI/tei:standOff/tei:listEvent/tei:event[@type eq 'print']/@when"> Supported API feature: play_year_printed [value: <sch:value-of select="$play_year_printed"/>] </sch:report> </sch:rule>
SchematronFeature-Check: P24 play_year_written
<sch:rule context="/" role="information"  see="https://dracor.org/doc/odd#play_year_written"> <sch:let name="play_year_written"  value="/tei:TEI/tei:standOff/tei:listEvent/tei:event[@type eq 'written']/@when/string()"/> <sch:report test="/tei:TEI/tei:standOff/tei:listEvent/tei:event[@type eq 'written']/@when"> Supported API feature: play_year_written [value: <sch:value-of select="$play_year_written"/>] </sch:report> </sch:rule>

Appendix A Feature Tables

In the Report on Programmable Corpora (https://zenodo.org/records/7664964) we identified ‘features’ that are returned by the DraCor API. We include the adapted tables here for reference.

Appendix A.1 Corpus Features

C1corpus_name
C2corpus_uri
C3corpus_title
C4corpus_acronym
C5corpus_description
C6corpus_repository
C7corpus_licence
C8corpus_licence_url
C9corpus_num_of_plays
C10corpus_num_of_characters
C11corpus_num_of_characters_male
C12corpus_num_of_characters_female
C13corpus_num_of_tei_text_elements
C14corpus_num_of_sp
C15corpus_num_of_stage
C16corpus_num_of_word_tokens_in_text_elements
C17corpus_num_of_word_tokens_in_sp
C18corpus_num_of_word_tokens_in_stage
C19corpus_metrics_date_updated
C20corpus_play_objects

Appendix A.2 Play Features

P1play_corpus_name
P2play_id
P3play_name
P4play_wikidata_id
P5play_title
P6play_subtitle
P7play_title_en
P8play_subtitle_en
P9play_author_name
P10play_author_name_en
P11play_author_fullname
P12play_author_fullname_en
P13play_author_shortname
P14play_author_shortname_en
P15play_first_author_name
P16play_first_author_shortname
P17play_first_author_deprecation_warning
P18play_author_also_known_as
P19play_author_ref_external_id
P20play_author_ref_type
P21play_num_of_co_authors
P22play_genre_normalized
P23play_is_libretto
P24play_year_written
P25play_year_printed
P26play_year_premiered
P27play_year_normalized
P28play_digital_source_name
P29play_digital_source_url
P30play_original_source_full_citation
P31play_original_source_publisher
P32play_original_source_publication_place
P33play_original_source_publication_year
P34play_original_source_num_of_pages
P35play_num_of_wikipedia_links
P36play_segments
P37play_num_of_segments
P38play_num_of_acts
P39play_num_of_paragraphs
P40play_num_of_verse_lines
P41play_num_of_word_tokens_in_text_elements
P42play_num_of_word_tokens_in_sp
P43play_num_of_word_tokens_in_stage
P44play_characters
P45play_num_of_speakers
P46play_num_of_speakers_sex_female
P47play_num_of_speakers_sex_male
P48play_num_of_speakers_sex_unknown
P49play_num_of_person_groups
P50play_all_in_segment
P51play_all_in_index
P52play_character_relations
P53play_network_data_csv_url
P54play_network_nodes
P55play_network_size
P56play_network_num_edges
P57play_network_average_degree
P58play_network_density
P59play_network_diameter
P60play_network_average_path_length
P61play_network_average_clustering
P62play_network_num_connected_components
P63play_network_max_degree
P64play_network_max_degree_character_ids

Appendix A.3 Segment Features

S1segment_type
S2segment_number
S3segment_title
S4segment_speaking_characters

Appendix A.4 Character Features

Ch1character_id
Ch2character_name
Ch3character_is_group
Ch4character_sex
Ch5character_wikidata_id
Ch6character_node_betweenness
Ch7character_node_degree
Ch8character_node_closeness
Ch9character_node_eigenvector
Ch10character_node_weighted_degree
Ch11character_num_of_segments
Ch12character_num_of_sp
Ch13character_num_of_word_tokens
Ch14character_roles
Ch15character_spoken_text

Appendix B Additional Ressources on Encoding of DraCor files

Use these materials with care. The proposed solutions on how to encode might be outdated.

  1. Issues in the dracor-schema repository
  2. Fischer, F. (2019). RusDraCor Wiki. https://github.com/dracor-org/rusdracor/wiki
  3. Fischer, F. (2023). GerDraCor Wiki. https://github.com/dracor-org/gerdracor/wiki

Appendix C Bibliography

  1. Beshero-Bondar, E. E., Viglianti, R., Bermúdez-Sabel, H., & Jenstad, J., (2024) "Revising sex and gender in the TEI Guidelines", Journal of the Text Encoding Initiative [Online], Issue 17 | 2024. doi:10.4000/13utq
  2. Börner, I., & Trilcke, P. (2023). CLS INFRA D7.1 On Programmable Corpora. doi: 10.5281/zenodo.7664964
  3. Börner, I., & Trilcke, P. (2024) CLS INFRA D7.3 On Versioning Living and Programmable Corpora: (Executable) Report and Prototypes for Reproducible Research. doi:10.5281/ZENODO.11081934.
  4. Fischer, F., Börner, I., Göbel, M., Hechtl, A., Kittel, C., Milling, C., & Trilcke, P. (2019). Programmable Corpora: Introducing DraCor, an Infrastructure for the Research on European Drama. DH2019: »Complexities«. 9–12 July 2019. Book of Abstracts. DH2019 »Complexities«, Utrecht. doi: 10.5281/ZENODO.4284002
  5. Gavin, M. (2023) Literary mathematics. Quantitative theory for textual studies. Stanford text technologies. Stanford, California: Stanford University Press
  6. Trilcke, P. (2013). Social Network Analysis (SNA) als Methode einer textempirischen Literaturwissenschaft. In P. Ajouri, K. Mellmann, & C. Rauen (Eds.), Empirie in der Literaturwissenschaft (S. 201–247). Mentis
  7. Wiedmer, N., Pagel J., Reiter, N. (2020). "Romeo, Freund Des Mercutio: Semi- Automatische Extraktion von Beziehungen zwischen Dramatischen Figuren." DHd2020. Book of Abstracts. Paderborn, p. 194–200. doi:10.5281/zenodo.4621778.
Date: 2024-10-23
Version: 1.0.0-rc.1