I5: The IDS text model
Derivation from TEI P5 via ODD file
C. M. Sperberg-McQueen
31 December 2012
Modifications and Extensions by IDS 2012-present

This document provides a formal definition of I5, a derivation of the IDS/XCES vocabulary as a customization of TEI P5. It contains the various <specGrp> elements needed to specify a customization of TEI, together with accompanying prose explaining the logic of the customization.

IDS/XCES [4] is a DTD for corpus materials developed at the Institut für deutsche Sprache in Mannheim. It is based on XCES, an XML version of the Corpus Encoding Standard (CES) [2], [3], which in turn was based on version TEI P3 of the Text Encoding Initiative Guidelines [1].

The primary goal is to provide a definition of the IDS/XCES vocabulary on the basis of TEI P5 [7], and not (via XCES and CES) on the basis of TEI P3. TEI P3 customization involved the preparation of DTD files in tightly prescribed forms containing declarations which overrode the default declarations for the entities, elements, and attributes concerned. TEI P5 customization involves the preparation of an ODD (for one document does it all) document which describes changes to the base TEI vocabulary using a specialized vocabulary defined in chapter 22 of TEI P5.

A secondary goal is to document the structure of the customization, specifying what is included without change from TEI P5, what is excluded, and what is changed. Some differences between TEI P3 and IDS/XCES originated with CES or XCES and others were introduced when IDS/XCES was adapted from XCES; since those have different significance for further development and maintenance of the vocabulary, those two sets of differences are distinguished here. Another secondary goal is to provide at least rudimentary documentation for all elements in the vocabulary.

The first section below describes the vocabulary's use of the required TEI modules; the next section describes use of optional modules. There follows a section describing elements added by IDS/XCES, and a driver section which gathers together all the ODD fragments included earlier in the document. A final section describes some conformance and design issues which may need attention.

The brief descriptions of elements in the TEI and CES/XCES vocabularies are taken from the documentation for those encoding schemes; thanks are due to the authors and publishers of that documentation. Descriptions are included in the appendix for elements suppressed from modules which are otherwise included, in order to simplify review of the design and consideration of possible changes.

1. Required TEI Modules

This section of this ODD file includes a number of TEI P5 modules; eventually it will also describe differences between the P5 version of the elements involved and the older IDS/XCES versions.

reference #specgroup-tei
reference #specgroup-core
reference #specgroup-header
reference #specgroup-textstructure

A note on notation: this document is not a description of the ODD file which generates the I5 version of the TEI P5 vocabulary; it is the ODD document. Blocks labeled ‘Spec fragment’, like the one just shown, are used to specify selections from and modifications to the TEI P5 vocabulary. As may be seen, such spec fragments may include cross references to other spec fragments elsewhere in the document, which are included by reference in the set of modifications; ODD documents are thus a specialized form of ‘literate programming’ as defined by the computer scientist Donald Knuth and used in the publication of his TeX and MetaFont programs. The literate-programming structure allows the formal specification of changes to be embedded in prose documentation intended to explain what is happening.

1.1. The tei module

The tei module is required for any TEI profile. The following specification fragment includes the tei module and makes appropriate modifications to it.

Module tei
reference #specgroup-tei-redefinitions

1.2. The core module

The tei and core modules are required for any TEI profile. The following specification fragment includes the core module and makes appropriate modifications to it.

Module core
reference #specgroup-core-deletions
reference #specgroup-core-renamings
reference #specgroup-core-redefinitions

Numerous elements in the TEI core module are suppressed; for short descriptions of these elements see the appendix.

Element <add> delete
Element <binaryObject> delete
Element <cb> delete
Element <choice> delete
Element <del> delete
Element <divGen> delete
Element <expan> delete
Element <headItem> delete
Element <headLabel> delete
Element <index> delete
Element <listBibl> delete
Element <measureGrp> delete
Element <meeting> delete
Element <milestone> delete
Element <postBox> delete
Element <postCode> delete
Element <rs> delete
Element <said> delete
Element <series> delete
Element <sic> delete
Element <soCalled> delete
Element <street> delete
Element <unclear> delete

Some elements in the core modules are renamed in obvious ways. The <idsCorpus> element is renamed <idsCorpus>, and its content model is adjusted: <idsCorpus> contains a sequence of <idsDoc> elements, not <idsText> (~ <idsText>) elements, so the default content model is not appropriate.

Element <idsCorpus> change

The remainder of the elements in the core module are included in the IDS/XCES vocabulary; that remainder includes the elements listed below. (For the most part, these elements are also included in CES and XCES, but <editor>, <gloss>, <lb>, <orig>, and <pb> are not in XCES but are added back into the vocabulary by IDS/XCES.)

Some elements are included without change from TEI, at least in the sense that the same parameter entity or pattern names are used in the declarations. (The extension of some element classes in IDS/XCES does of course mean the effective content model is not actually the same. But we do not need to supply a different model in this ODD file.)

For other elements, IDS/XCES declares a content model which is a restriction of the content model in TEI P5. One simple way to move I5 closer to TEI P5 would be to drop these restrictions and use the TEI P5 declarations for these elements unchanged.

Finally, for some elements IDS/XCES declares a content model which extends or modifies the declarations in TEI P5. Sometimes the change consists merely in the addition of one or more attributes, or adding the element as a member of this or that class. In other cases the content model is rewritten.

The following specification fragment indicates which elements are changed from the TEI P5 declarations.

reference #add_abbr_to_token_class
reference #redefine_analytic
reference #add_date_to_token_class
reference #redefine_gap
reference #add_hi_to_basic_class
reference #redefine_imprint
reference #redefine_l_part_attribute
reference #add_lb_to_ids.milestones
reference #redefine_lg_part_attribute
reference #redefine_list
reference #redefine_monogr
reference #add_name_to_token_class
reference #add_num_to_token_class
reference #add_attributes_to_orig
reference #add_TEIform_to_pb
reference #ptr_as_milestone
reference #add_attributes_to_q
reference #redefine_sp
reference #add_term_to_token_class
reference #add_time_to_token_class
reference #redefine_corr
reference #redefine_reg
reference #redefine_foreign
reference #redefine_respStmt
reference #redefine_gloss
reference #redefine_p
reference #redefine_head
reference #redefine_item
reference #redefine_emph
reference #redefine_desc

Where possible, the list below notes the nature of the changes made.

  • <abbr> (abbreviation): contains an abbreviation of any sort.
    Element <abbr> change
  • <address>: contains a postal address, for example of a publisher, an organization, or an individual. (Not present in samples.)
  • <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. IDS/XCES modifies the content model to fit the three-level structure of IDS corpora.
    Element <analytic> change
    CES restricts the TEI content model and renames some elements; IDS/XCES extends the CES definition. The model given here is the same as for <monogr>.
  • <author>: in a bibliographic reference, contains the name(s) of the author(s), personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority.
  • <bibl> (bibliographic citation): contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • <biblScope> (scope of citation): defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work.
  • <biblStruct> (structured bibliographic citation): contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order.
  • <corr> (correction): contains the correct form of a passage apparently erroneous in the copy text. IDS-XCES adds the attribute @sic (which gives the original form) as e.g. occurring in hi1bb.xces.
    Element <corr> change
  • <date>: contains a date in any format. CES declares this element as a member of the token class.
    Element <date> change
  • <item>: adding att.typed for wiki talk HLU 2020-01-24 : Note that in the current TEI, desc has already @type
    Element <desc> change
  • <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.
  • <editor>: 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.
  • <item>: adding att.typed for wiki talk HLU 2020-01-24
    Element <emph> change
  • <foreign>: identifies a word or phrase as belonging to some language other than that of the surrounding text. IDS-XCES allows it to contain q, e.g. in loz-div-pub.xces
    Element <foreign> change
  • <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. (In TEI P5, the description of the gap has moved from a desc attribute to a <desc> child; we revert this change for compatibility with existing data.)
    Element <gap/> change
  • <gloss>: identifies a phrase or word used to provide a gloss or definition for some other word or phrase.
    Element <gloss> change
  • <head> (heading): contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. Changed 2020-01-21 such that it can contain <sigend>, for wiki talk.
    Element <head> change
  • <hi> (highlighted): marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.
    Element <hi> change
  • <imprint>: groups information relating to the publication or distribution of a bibliographic item. CES redefines this to use the <pubDate> element instead of <date>.
    Element <imprint> change
  • <item>: contains one component of a list. . Redefined to contain <signed> as well for wiki talk HLU 2020-01-02.
    Element <item> change
  • <l> (verse line): contains a single, possibly incomplete, line of verse. CES redefined the meaning and values of the part attribute.
    Element <l> change
  • <label>: contains the label associated with an item in a list; in glossaries, marks the term being defined.
  • <lb> (line break): marks the start of a new (typographic) line in some edition or version of a text. IDS-XCES adds @TEIform to the attribute list as used in fsp.xces and gr1.xces.
    Element <lb> change
  • <lg> (line group): contains a group of verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.
    Element <lg> change
  • <list>: contains any sequence of items organized as a list. IDS/XCES allows milestones and <xptr/> elements among the children.
    Element <list> change
  • <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.
  • <mentioned>: marks words or phrases mentioned, not used. (Not present in samples.)
  • <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). CES restricts the TEI content model and renames some elements; IDS/XCES extends the CES definition. The model given here is the same as for <analytic>.
    Element <monogr> change
  • <name> (name, proper noun): contains a proper noun or noun phrase.
    Element <name> change
  • <note>: contains a note or annotation.
  • <num> (number): contains a number, written in any form.
    Element <num> change
  • <orig> (original form): contains a reading which is marked as following the original, rather than being normalized or corrected. The reg attribute was dropped in TEI P5 and must be restored. CES also adds a regalt attribute which must be defined.
    Element <orig> change
  • <p> (paragraph): marks paragraphs in prose.
    Element <p> change
  • <pb> (page break): marks the boundary between one page of a text and the next in a standard reference system.
    Element <pb> change
  • <ptr> (pointer): defines a pointer to another location. IDS/XCES adds this element to the ids.milestones class.
    Element <ptr> change
  • <pubPlace> (publication place): contains the name of the place where a bibliographic item was published.
  • <publisher>: provides the name of the organization responsible for the publication or distribution of a bibliographic item.
  • <q> (separated from the surrounding text with quotation marks): contains material which is marked as (ostensibly) being somehow different than the surrounding text, 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. CES adds several attributes.
    Element <q> change
  • <quote> (quotation): contains a phrase or passage attributed by the narrator or author to some agency external to the text.
  • <ref> (reference): defines a reference to another location, possibly modified by additional text or comment. IDS-XCES adds @orig.
  • <reg> (regularization): contains a reading which has been regularized or normalized in some sense.
    Element <reg> change
  • <sp> (speech): An individual speech in a performance text, or a passage presented as such in a prose or verse text. CES restricts this content model severely; IDS/XCES brings it back closer to the TEI form, and adds the class of IDS milestones to the legal content.
    Element <sp> change
  • <speaker>: A specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.
  • <stage> (stage direction): contains any kind of stage direction within a dramatic text or fragment.
  • <term>: contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.
    Element <term> change
  • <time>: contains a phrase defining a time of day in any format.
    Element <time> change
  • <title>: contains a title for any kind of work.

1.3. The header module

The header module is also essential. We include it here:

Module header
reference #specgroup-header-renamings
reference #specgroup-header-deletions
reference #specgroup-header-redefinitions

The <idsHeader> element is renamed to <idsHeader>, and we add some attributes (the status attribute was in TEI P3 but seems to have disappeared from P5):

Element <idsHeader> change

Some elements in the TEI header module are suppressed; for short descriptions see the appendix.

Element <appInfo> delete
Element <application> delete
Element <authority> delete
Element <cRefPattern> delete
Element <geoDecl> delete
Element <handNote> delete
Element <interpretation> delete
Element <namespace> delete
Element <notesStmt> delete
Element <principal> delete
Element <refState> delete
Element <rendition> delete
Element <scriptNote> delete
Element <seriesStmt> delete
Element <sponsor> delete
Element <stdVals> delete
Element <typeNote> delete

The IDS/XCES vocabulary includes the elements listed below from the TEI header module, sometimes with content models which extend or otherwise modify the content models of TEI P5 in such a way that instances of the revised element type are not valid against the unmodified TEI P5 schema, and sometimes without change. In several cases, CES changes a content model from requiring a sequence of paragraphs to allowing just character data. In other cases, specialized child elements are added to the content model.

reference #modify_declarable_class
reference #redefine_availability
reference #redefine_creation
reference #redefine_correction_as_PCDATA
reference #redefine_edition
reference #redefine_editionStmt_as_PCDATA
reference #redefine_editorialDecl
reference #redefine_language
reference #redefine_normalization_as_PCDATA
reference #redefine_projectDesc_as_PCDATA_or_p
reference #redefine_publicationStmt
reference #redefine_quotation_as_PCDATA
reference #redefine_samplingDecl_as_PCDATA
reference #redefine_segmentation_as_PCDATA
reference #redefine_sourceDesc
reference #redefine_tagsDecl
reference #redefine_taxonomy
reference #redefine_textClass
reference #redefine_titleStmt
reference #redefine_encodingDesc
reference #redefine_catRef

In the attribute class declarable, CES renames one attribute from default to Default, and changes its values from yes and no to y and n.

Class att.declarable change

The elements included from the header module are these.

  • <availability>: supplies information about the availability of a text any restrictions on its use or distribution, its copyright status, etc.
    Element <availability> change

The IDS/XCES vocabulary includes the following elements from the TEI header module with content models which restrict the content models of TEI P5.

  • <biblFull> (fully-structured bibliographic citation): contains a fully-structured bibliographic citation, in which all components of the TEI file description are present.
  • <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.
  • <catRef> (category reference): specifies one or more defined categories within some taxonomy or text typology.
    Element <catRef> change
  • <category>: contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.
  • <change>: summarizes a particular change or correction made to a particular version of an electronic text which is shared between several researchers.
  • <classCode>
  • <classDecl> (classification declarations): contains one or more taxonomies defining any classificatory codes used elsewhere in the text.
  • <correction> (correction principles): states how and under what circumstances corrections have been made in the text.
    Element <correction> change
  • <creation>: contains information about the creation of a text.
    Element <creation> change
  • <distributor>: supplies the name of a person or other agency responsible for the distribution of a text.
  • <edition>: describes the particularities of one edition of a text.
    Element <edition> change
  • <editionStmt> (edition statement): groups information relating to one edition of a text.
    Element <editionStmt> change
  • <editorialDecl> (editorial practice declaration): provides details of editorial principles and practices applied during the encoding of a text. CES changes the set of children for this element from P3 (suppressing <interpretation> and <stdVals> and adding <transduction> and <conformance>); IDS/XCES adds <pagination> to the children.
    Element <editorialDecl> change
  • <encodingDesc> (encoding description): documents the relationship between an electronic text and the source or sources from which it was derived. IDS-XCES additionally allows an empty encodingDesc as used in dck.xces .
    Element <encodingDesc> change
  • <extent>: describes the approximate size of a text as stored on some carrier medium, whether digital or non-digital, specified in any convenient units.
  • <fileDesc> (file description): contains a full bibliographic description of an electronic file.
  • <hyphenation>: summarizes the way in which hyphenation in a source text has been treated in an encoded version of it.
  • <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.
  • <keywords>: contains a list of keywords or phrases identifying the topic or nature of a text.
  • <langUsage> (language usage): describes the languages, sublanguages, registers, dialects, etc. represented within a text.
  • <language>: characterizes a single language or sublanguage used within a text. TEI P5 uses an ident attribute, not id, to give the language code; IDS/XCES follows P3 in this.
    Element <language> change
  • <normalization>: indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form.
    Element <normalization> change
  • <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.
  • <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.
    Element <projectDesc> change
  • <publicationStmt> (publication statement): groups information concerning the publication or distribution of an electronic or other text.
    Element <publicationStmt> change
  • <quotation>: specifies editorial practice adopted with respect to quotation marks in the original.
    Element <quotation> change
  • <refsDecl> (references declaration): specifies how canonical references are constructed for this text.
  • <revisionDesc> (revision description): summarizes the revision history for a file.
  • <samplingDecl> (sampling declaration): contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.
    Element <samplingDecl> change
  • <segmentation>: describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.
    Element <segmentation> change
  • <sourceDesc> (source description): describes the source 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.
    Element <sourceDesc> change
  • <tagUsage>: supplies information about the usage of a specific element within a text.
  • <tagsDecl> (tagging declaration): provides detailed information about the tagging applied to a document. TEI P5 requires that the <tagUsage> elements in the <tagsDecl> element be wrapped in a <namespace> element; IDS/XCES follows P3.
    Element <tagsDecl> change
  • <taxonomy>: defines a typology used to classify texts either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.
    Element <taxonomy> change
  • <textClass> (text classification): groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.
    Element <textClass> change
  • <titleStmt> (title statement): groups information about the title of a work and those responsible for its intellectual content. IDS/XCES adjusts the content model here to use the specialized title elements it defines for the different corpus levels. An I5 corpus level-specific {c|d|t}.title element is obligatory, in addition, original TEI <title> elements with their suitable attributes may be specified, e.g. for specifying subtitles
    Element <titleStmt> change

1.4. The textstructure module

The TEI textstructure module is also included:

Module textstructure
reference #specgroup-text-structure-renamings
reference #specgroup-text-structure-deletions
reference #specgroup-text-structure-changes

The <idsText> element is renamed <idsText>:

  • <idsText> (TEI document): contains a single TEI-conformant document, comprising a TEI header and a text, either in isolation or as part of a <idsCorpus> element. This corresponds in essential ways to the IDS <idsText> element.

Element <idsText> change

Several elements in this module are suppressed. Descriptions of these elements are given in the appendix.

Element <argument> delete
Element <div1> delete
Element <div2> delete
Element <div3> delete
Element <div4> delete
Element <div5> delete
Element <div6> delete
Element <div7> delete
Element <docDate> delete
Element <floatingText> delete
Element <group> delete
Element <imprimatur> delete

The IDS/XCES vocabulary includes the elements listed below from the TEI textstructure module. A few of these are included in CES and XCES, with declarations which extend or otherwise modify those in the TEI. Others are omitted from CES and XCES and have been added back into the vocabulary by IDS. In some cases, the IDS/XCES declaration extends that of TEI.

reference #modify_attributes_for_div
reference #redefine_opener
reference #redefine_signed

  • <back> (back matter): contains any appendixes, etc. following the main part of a text.
  • <body> (text body): contains the whole body of a single unitary text, excluding any front or back matter.
  • <byline>: contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
  • <closer>: groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter.
  • <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.
  • <div> (text division): contains a subdivision of the front, body, or back of a text. IDS/XCES eliminates the internal structure of the declarations in TEI and CES and allows a mixture of children in any order. We additionally alow the element posting from the DeRik TEI-proposal for CMC.
    Element <div> change
  • <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).
  • <docEdition> (document edition): contains an edition statement as presented on a title page of a document.
  • <docImprint> (document imprint): contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page.
  • <docTitle> (document title): contains the title of a document, including all its constituents, as given on a title page.
  • <epigraph>: contains a quotation, anonymous or attributed, appearing at the start of a section or chapter, or on a title page.
  • <front> (front matter): contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body.
  • <opener>: groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. IDS-XCES adds gap to the content model.
    Element <opener> change
  • <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.
  • <signed> (signature): contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text.
    Element <signed> change
  • <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.
  • <titlePage> (title page): contains the title page of a text, appearing within the front or back matter.
  • <titlePart>: contains a subsection or division of the title of a work, as indicated on a title page.

2. Optional TEI modules

This section lists the optional TEI modules incorporated in whole or part into the IDS/XCES vocabular.

reference #specgroup-analysis
reference #specgroup-corpus
reference #specgroup-figures
reference #specgroup-namesdates
reference #specgroup-linking

2.1. The analysis module

The IDS/XCES vocabulary includes the following elements from the TEI analysis module:

  • <s> (s-unit): contains a sentence-like division of a text. CES and the existing IDS/XCES DTD define this using the parameter entity phrase.seq, but this relies on a different meaning for the phrase class than is present in TEI P5.
    Element <s> change
  • <w> (word): represents a grammatical (not necessarily orthographic) word.
    Element <w> change

The remaining elements in this module are suppressed:

Module analysis
reference #redefine_s
reference #add_w_to_token_class
Element <c> delete
Element <cl> delete
Element <interp> delete
Element <interpGrp> delete
Element <m> delete
Element <pc> delete
Element <phr> delete
Element <span> delete
Element <spanGrp> delete

See the appendix for brief descriptions.

2.2. The corpus module

The IDS/XCES vocabulary includes the following elements from the TEI corpus module:

  • <particDesc> (participation description): describes the identifiable speakers, voices, or other participants in any kind of text.

    <textDesc> (text description): provides a description of a text in terms of its situational parameters.

    Element <textDesc> change

The remaining elements in the module are suppressed.

Module corpus
reference #redefine_textDesc
Element <channel> delete
Element <constitution> delete
Element <derivation> delete
Element <domain> delete
Element <factuality> delete
Element <interaction> delete
Element <locale> delete
Element <preparedness> delete
Element <purpose> delete

2.3. The figures module

The IDS/XCES vocabulary includes the following elements from the TEI figures module:

  • <cell>: contains one cell of a table.
  • <figDesc> (description of figure): contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it.
  • <row>: contains one row of a table.
  • <table>: contains text displayed in tabular form, in rows and columns.

The following elements in the TEI figures module are redefined:

  • <figure>: groups elements representing or containing graphic information such as an illustration or figure. IDS-XCES adds ptr to the content model.
    Element <figure> change

<Figure> is redefined.

Module figures
reference #redefine_figure

2.4. The namesdates module

As a conservative extension, the I5 vocabulary now includes 11 elements from the namesdates module. The rest of the module might as well be included, but are suppressed because they do not seem to be needed for now.

The following specification fragment includes the namesdates module and makes appropriate modifications to it.

Module namesdates
Element <addName> delete
Element <affiliation> delete
Element <age> delete
Element <birth> delete
Element <bloc> delete
Element <climate> delete
Element <death> delete
Element <district> delete
Element <education> delete
Element <event> delete
Element <faith> delete
Element <floruit> delete
Element <genName> delete
Element <geo> delete
Element <geogFeat> delete
Element <langKnowledge> delete
Element <langKnown> delete
Element <listEvent> delete
Element <listNym> delete
Element <listPlace> delete
Element <listRelation> delete
Element <location> delete
Element <nameLink> delete
Element <nationality> delete
Element <nym> delete
Element <occupation> delete
Element <offset> delete
Element <org> delete
Element <personGrp> delete
Element <place> delete
Element <population> delete
Element <relation> delete
Element <relationGrp> delete
Element <residence> delete
Element <roleName> delete
Element <settlement> delete
Element <sex> delete
Element <socecStatus> delete
Element <state> delete
Element <terrain> delete
Element <trait> delete

2.5. The linking module

In DeReKo, the elements <ref>, <ptr>, and <xptr/> are used for linking. <ref> is already included in I5 through the core module. The elements <xref> and <xptr/> were declared in the linking module in TEI P3 and P4, but they are no longer part of TEI P5. From the TEI P5 linking module, only the elements <timeline> and <seg> are taken. They are needed for the encoding of CMC documents

The following specification fragment includes the linking module and makes and delete all elemente except <seg>, <timeline>, and <when>.

Module linking
Element <ab> delete
Element <anchor> delete
Element <alt> delete
Element <altGrp> delete
Element <join> delete
Element <joinGrp> delete
Element <link> delete
Element <linkGrp> delete

2.6. TEI modules not included

The following optional TEI modules are not included in this customization:

  • The certainty module (for recording points of uncertainty and dispute).

  • The dictionaries module (for print or electronic dictionaries).

  • The drama module. (N.B. the <caption> element of TEI P5 which is included in this module has nothing to do with the <caption> element introduced by CES as an extension of TEI, and retained by IDS/XCES.)

  • The gaiji module (for extending the Unicode / ISO 10646 universal character set).

  • The fs module (for the representation of feature structures for linguistic or other analysis).

  • The msdescription module for description of manuscript materials.

  • The nets module (for representation of graphs, networks, and trees).

  • The spoken module (for transcription of spoken materials).

  • The tagdocs module (for documentation of XML vocabularies).

  • The textcrit module (for the representation of text-critical apparatus as used in scholarly editions).

  • The transcr module (for markup of transcriptions of original source material).

  • The verse module (for markup of metrical phenomena in verse).

3. Models from cmc-core

Class model.floatP.cmc add
Class att.global.cmc add

4. Elements added by IDS

The elements described in this section are not direct equivalents of any individual TEI element. They fall into several categories, which are different primarily for purposes of vocabulary maintenance:

The following specification fragment includes each of these groups in turn:

reference #specgroup-XCES-unchanged
reference #specgroup-XCES-changed
reference #specgroup-renamings
reference #specgroup-TEI-P3
reference #specgroup-IDS-specific
reference #specgroup-DERIK
reference #specgroup-Correspondence

4.1. Elements taken over without change from CES and XCES

A number of elements in IDS/XCES are taken over from the CES and XCES vocabularies.

  • <annotation>: provides information about one external annotation document associated with the text. (Not present in samples.)
    Element <annotation> add
  • <annotations> (in file ids.xheader.elt): child of <profileDesc>. Groups <annotation> elements. (Not present in samples.)
    Element <annotations> add
  • <biblNote>: a descriptive note supplying additional information of any kind relating to a bibliographic item described within a corpus or text header.
    Element <biblNote> add
  • <byteCount>: contains the count of bytes in the file containing the text together with its markup. (Not present in samples.)
    Element <byteCount> add
  • <changeDate>: gives the date of a change (as child of <change>). (Not present in samples.)
    Element <changeDate> add
  • <conformance>: provides the CES level of conformance for the text or corpus. (Not present in samples.)
    Element <conformance> add
  • <eAddress>: gives an electronic address of the person or institution who distributes the text or corpus. Note that more than one occurrence of this tag can appear, so that multiple addresses (possibly of different types) can be included. (Not present in samples.)
    Element <eAddress> add
  • <extNote>: a descriptive note supplying additional information of any kind relating to an extent information provided within a corpus or text header. (Not present in samples.)
    Element <extNote> add
  • <fax>: gives the fax number of the person or institution who distributes the text or corpus, in format conformant to ITU-T/CCITT Recommendation E.123. (Not present in samples.)
    Element <fax> add
  • <h.author> in a bibliographic reference, contains the name of an author (personal or corporate) of a work; a context-specific renaming of TEI <author> element. CES specifies that names should be given in a canonical form, with surnames preceding forenames, but IDS practice is not consistent in this regard.
    Element <h.author> add
  • <h.bibl>: character data only, suitable for very simple citations.
    Element <h.bibl> add
  • <h.item>: (as child of <change> element) specifies the nature of the change(s). One or more occurrences of this element may appear within each <change> element. Context-dependent renaming of standard TEI <item>. (Not present in samples.)
    Element <h.item> add
  • <h.keywords>: contains a list of keywords or phrases identifying the topic or nature of a text, each of which is tagged as a term. (Renaming of TEI <keywords>, plus modified content model.)
    Element <h.keywords> add
  • <h.title>: the title of the electronic file, including alternative titles or subtitles. Context-specific renaming of TEI <title>.
    Element <h.title> add
  • <keyTerm> (in file ids.xheader.elt): child of <h.keywords>, encloses one keyword term describing the text. Context-specific renaming of standard TEI element <term>.
    Element <keyTerm> add
  • <pubAddress> (in file ids.xheader.elt): child of <publicationStmt>, provides address of distributor. Context-specific specialization of TEI <address> element; #PCDATA.
    Element <pubAddress> add
  • <pubDate> (in file ids.xheader.elt): child of <publicationStmt>, provides date of publication. Context-specific specialization of TEI <date> element; #PCDATA.
    Element <pubDate> add
  • <respName> (in file ids.xheader.elt): child of <respStmt> (where it is a context-dependent renaming of <name>) and <change>. Contains #PCDATA only.
    Element <respName> add
  • <respType> (in file ids.xheader.elt): child of <respStmt>; context-specific renaming of standard TEI <resp>
    Element <respType> add
  • <telephone> (in file ids.xheader.elt): child of <publicationStmt>, provides telephone number of distributor in CCITT E.123 form; #PCDATA.
    Element <telephone> add
  • <transduction>: (as child of <editorialDecl>) describes the principles according to which the text has been transduced, either in transcribing it from audio tape to written form, or in converting from an electronic original.
    Element <transduction> add
  • <translation> (in file ids.xheader.elt): child of <translations>. Gives information about one translation of the text.
    Element <translation> add
  • <translations> (in file ids.xheader.elt): child of <profileDesc>; groups <translation> elements.
    Element <translations> add
  • <translator> (in file ids.xheader.elt): identifies the translator responsible for one translation.
    Element <translator> add
  • <wordCount>: (as child of <extent>) contains the count of words in the text. (Not present in samples.)
    Element <wordCount> add
  • <writingSystem> (in file ids.xheader.elt): child of <wsdUsage>; describes one character set used in the document; can point to an external writing system declaration. (This element appears to be a survival from the SGML version of CES; in XML, character set issues are typically handled at a different level.) (Not present in samples.)
    Element <writingSystem> add
  • <wsdUsage>: groups information describing the character set(s) used within a text. (Not present in samples.)
    Element <wsdUsage> add

CES also defined some new classes for attribute inheritance and content models.

Class att.header add
Class att.text add
Class model.token add

CES moves the rend attribute from the list of global attributes to the text class; for now, we follow TEI here.

The following specification fragment incorporates all the descriptions for the elements just mentioned:

reference #ces-attribute-classes
reference #ids-header-annotation
reference #ids-header-annotations
reference #ids-header-biblNote
reference #ids-header-byteCount
reference #ids-header-changeDate
reference #ids-header-conformance
reference #ids-header-eAddress
reference #ids-header-extNote
reference #ids-header-fax
reference #ids-header-h.author
reference #ids-header-h.bibl
reference #ids-header-h.item
reference #ids-header-h.keywords
reference #ids-header-h.title
reference #ids-header-keyTerm
reference #ids-header-pubAddress
reference #ids-header-pubDate
reference #ids-header-respName
reference #ids-header-respType
reference #ids-header-telephone
reference #ids-header-transduction
reference #ids-header-translation
reference #ids-header-translations
reference #ids-header-translator
reference #ids-header-wordCount
reference #ids-header-writingSystem
reference #ids-header-wsdUsage

4.2. Elements defined by (X)CES and modified by IDS/XCES

  • <caption>: (1) a heading, title etc. attached to a picture or diagram (2) a "pull quote" or other text about or extracted from a text and superimposed upon it to draw attention to it. This element was added by CES; it conflicts (possibly unintentionally) with a different element also named <caption> defined by TEI P3 for text displayed in a film (or text in a screenplay intended for such display). IDS/XCES modifies the CES version by allowing IDS milestones in the content.
    Element <caption> add
  • <poem> (in file ids.xesdoc.dtd): contains a poem, or an extract from a poem, appearing within or between paragraphs; an inter-level element. IDS changes CES's definition to allow milestone elements among the children.
    Element <poem> add

IDS/XCES also redefines the base.seq parameter entity in such a way that it becomes not a sequence but an element class. To try to avoid confusion, it is here renamed basic.

Class model.basic add
Class model.ids.milestones add
reference #ids-doc-caption
reference #ids-doc-poem
reference #ids-basic-class

4.3. Renamings of TEI elements

Several IDS/XCES elements are esssentially renamings (or context-dependent renamings) of TEI elements.

  • <idsCorpus> (in file ids.xesdoc.dtd): renaming of <idsCorpus>, with slight difference in content model
  • <idsHeader> (in file ids.xheader.elt): renaming of <idsHeader>
  • <idsDoc> (in file ids.xesdoc.dtd): intermediate level between <idsText> and <idsCorpus>; conceptually similar to the <idsText> element, and structurally similar to <idsCorpus> but (just for that reason) cannot be declared as a renaming of either. HLU: For the time being, idsDoc is not put in the namespace http://www.ids-mannheim.de/i5 so that in an i5 document, it will work like idsCorpus, idsText and idsHeader. The latter are technical renamings of original TEI elements (using altIdent) and therefore cannot be put in a namespace other than the TEI namespace)
    Element <idsDoc> add
  • <idsText> (in file ids.xesdoc.dtd): renaming of <idsText> element
reference #ids-doc-idsDoc

4.4. TEI P3 elements no longer in P5

Some elements and attributes used by IDS/XCES were taken over from TEI P3, but are no longer present in TEI P5: <xptr/>, <xref>, <dateRange>, and <timeRange>.

Of these, only <xptr/> appears in the samples, so for now that's the only one we define.

Element <xptr/> add

TEI P5 has dropped the id attribute from the global class, and the targOrder attribute from the att.pointing class; these must be restored.

reference #p3-xptr-element
Class att.global change
Class att.pointing change
Class att.xPointer add

4.5. Elements and attributes added by IDS

The following elements are not present in the TEI or in CES/XCES, but have been added by IDS. All but one are intended to appear in the header.

reference #ids-header-appearance
reference #ids-header-c.title
reference #ids-header-column
reference #ids-header-creatDate
reference #ids-header-creatRef
reference #ids-header-creatRefShort
reference #ids-header-d.title
reference #ids-header-dokumentSigle
reference #ids-header-further
reference #ids-header-kind
reference #ids-header-korpusSigle
reference #ids-doc-numRange
reference #ids-header-pagination
reference #ids-header-reference
reference #ids-header-t.title
reference #ids-header-textDomain
reference #ids-header-textSigle
reference #ids-header-textType
reference #ids-header-textTypeArt
reference #ids-header-textTypeRef
reference #ids-header-x.title
reference #ids-derik-timestamp
reference #ids-cmc

4.6. Module, classes and elements from the TEI CMC SIG proposals " Beißwenger/Ermakova/Geyken/Lemnitzer/Storrer (2013): An XML Schema for the Representation of CMC Genres in TEI"

The following elements are not present in the TEI or in CES/XCES, but have been proposed as part of a TEI extension for Computer-mediated communication by BBAW and Dortmund Technical University. The part adopted here is the one that declares the posting structure

reference #posting
reference #autoSignature
reference #signatureContent
reference #timestamp
reference #emoticon
reference #interactionTerm
reference #interactionWord

4.7. Elements from the TEI Correspondence SIG proposal

Copied from the github site of the TEI Correspondence SIG, specifically from the file proposal.xml as of 2015-01-08

4.7.1. LICENSE for the correspondence Elements

Copyright (c) 2013, TEI-Correspondence-SIG

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

4.7.2. The following was copied from the file proposal.xml:

Class model.correspDescPart add
Class model.correspContextPart add
Class model.correspActionPart add
Element <correspDesc> add
Element <correspAction> add
Element <correspContext> add
Class model.nameLike change
Class model.dateLike change
Class model.ptrLike change
Class model.pLike change
Class model.addressLike change
Element <note> change

5. Top-level driver

5.1. Elements

5.1.1. <idsText>

<idsText> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <idsText> elements may be combined within a <idsText> (or <idsCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Namespace http://www.tei-c.org/ns/1.0
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
version specifies the version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype teidata.version
Note

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

Contained by
textstructure: idsText
May contain
header: idsHeader
linking: standOff
textstructure: idsText text
Note

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

Example
<idsText version="3.3.0">  <idsHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </idsHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </idsText>
Example
<idsText version="2.9.1">  <idsHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </idsHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </idsText>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<sch:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element idsText
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute version { text }?,
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

5.1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Namespace http://www.tei-c.org/ns/1.0
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
type (type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.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.

expan gives an expansion of the abbreviation.
Status Optional
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>.

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute [http://www.tei-c.org/ns/1.0]expan { text }?,
   tei_macro.phraseSeq
}

5.1.3. <abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: profileDesc
May contain
core: list p
figures: table
Note

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

Example
<profileDesc>  <abstract resp="#LB">   <p>Good database design involves the acquisition and deployment of      skills which have a wider relevance to the educational process. From      a set of more or less instinctive rules of thumb a formal discipline      or "methodology" of database design has evolved. Applying that      methodology can be of great benefit to a very wide range of academic      subjects: it requires fundamental skills of abstraction and      generalisation and it provides a simple mechanism whereby complex      ideas and information structures can be represented and manipulated,      even without the use of a computer. </p>  </abstract> </profileDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
 </alternate>
</content>
    
Schema Declaration
element abstract
{
   tei_att.global.attributes,
   ( tei_model.pLike | tei_model.listLike )+
}

5.1.4. <activity>

<activity> (activity) contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything. [15.2.3. The Setting Description]
Module corpus — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
corpus: setting
May contain
Note

For more fine-grained description of participant activities during a spoken text, the <event> element should be used.

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

5.1.5. <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.

Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }

5.1.6. <address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.

Example Using just the elements defined by the core module, an address could be represented as follows:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name>Italy</name> </address>
Example When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <settlement>Bologna</settlement>  <country>Italy</country> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   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_model.global*, ( tei_model.addrPart, tei_model.global* )+ )
}

5.1.7. <analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Namespace http://www.tei-c.org/ns/1.0
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content/>
    
Schema Declaration
element analytic
{
   tei_att.global.attributes,
   (
      h.title+,
      ( h.author | editor )*,
      ( biblScope | biblNote )*,
      ( edition, respStmt? )*,
      imprint+,
      idno*,
      ( biblNote | biblScope )*
   )
}

5.1.8. <annotation>

<annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container]
Module linking — Top-level driver
Attributes att.global (xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.cmc (@creation) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.responsibility (@cert, @resp) att.global.source (@source) att.pointing (target, @targOrder, @targType, @targetLang, @evaluate)
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
motivation
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
assessing
intent is to assess the target resource in some way, rather than simply make a comment about it
bookmarking
intent is to create a bookmark to the target or part thereof
classifying
intent is to classify the target in some way
commenting
intent is to comment about the target
describing
intent is to describe the target, rather than (for example) comment on it
editing
intent is to request an edit or a change to the target resource
highlighting
intent is to highlight the target resource or a segment thereof
identifying
intent is to assign an identity to the target
linking
intent is to link to a resource related to the target
moderating
intent is to assign some value or quality to the target
questioning
intent is to ask a question about the target
replying
intent is to reply to a previous statement, either an annotation or another resource
tagging
intent is to associate a tag with the target
Note

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

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

Member of
Contained by
ids-header: annotations
May contain
Example
<annotation xml:id="ann1"  motivation="linkingtarget="#Gallia"> <!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and https://www.w3.org/TR/annotation-model/#agents -->  <respStmt xml:id="fred">   <resp>creator</resp>   <persName>Fred Editor</persName>  </respStmt>  <revisionDesc>   <change status="created"    when="2020-05-21T13:59:00Zwho="#fred"/>   <change status="modified"    when="2020-05-21T19:48:00Zwho="#fred"/>  </revisionDesc> <!-- See https://www.w3.org/TR/annotation-model/#rights-information -->  <licence target="http://creativecommons.org/licenses/by/3.0/"/> <!-- Multiple bodies --> <!-- Pointers to sections of text in the same document -->  <ptr target="#string-range(c1p1s1,0,6)"/>  <ptr target="#string-range(c1p1s6,19,7)"/> </annotation>
Example
<annotation xml:id="TheCorrectTitle"  motivation="commentingtarget="#line1">  <note>The correct title of this specification, and the correct full name of XML, is    "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.    However, the abbreviation "XML" is not only correct but, appearing as it does in the title    of the specification, an official name of the Extensible Markup Language. </note> </annotation>
Content model
<content>
 <sequence>
  <elementRef key="respStmt" 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.cmc.attribute.creation,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.rendition.attribute.rendition,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.analytic.attribute.ana,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_att.pointing.attribute.targOrder,
   tei_att.pointing.attribute.targType,
   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.9. <annotation>

<annotation> provides information about one external annotation document associated with the text. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
type indicates the type of annotation.
Status Optional
Datatype
Sample values include:
segment
annotation file contains segmentation into words and sentences.
gram
annotation file contains morpho-syntactic category information for the words in the text.
align
annotation file contains alignment links to a parallel translation.
ann.loc provides information (path/file name, URL, etc.) about the location of the annotation file.
Status Optional
Datatype
trans.loc for annotation file containing alignment information, provides information (path/file name, URL, etc.) about the location of the file containing the aligned text.
Status Optional
Datatype
Contained by
ids-header: annotations
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element annotation
{
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type { text }?,
   attribute [http://www.tei-c.org/ns/1.0]ann.loc { text }?,
   attribute [http://www.tei-c.org/ns/1.0]trans.loc { text }?,
   text
}

5.1.10. <annotations>

<annotations> groups information about annotation documents associated with the text. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
ids-header: annotation
linking: annotation
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element annotations { tei_att.global.attributes, annotation+ }

5.1.11. <appearance>

<appearance> A child of <edition>. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: edition
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element appearance { tei_att.global.attributes, text }

5.1.12. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
core: bibl
header: titleStmt
May contain
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq
}

5.1.13. <autoSignature>

<autoSignature> is an empty element used for representing the position of the user signature position in a posting.
Namespace http://www.ids-mannheim.de/dk
Module derived-module-ids_v2a
Attributes att.pointing (@targOrder, @targType, @targetLang, @target, @evaluate) att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
type
Status Optional
Legal values are:
signed
indicates that the corresponding posting was explicitly signed by a registered user using a user signature mark up (e.g. ~~~~).
unsigned
indicates that the corresponding posting was marked by either a registered or unregistered user using the Unsigned or Help template.
user_contribution
"user_contribution" indicates that the corresponding posting was marked using a [[Special:Contributions/IP]] link (e.g by an unregistered user)
special_contribution
added 2019-06-14This is actually the same as "user_contribution""special_contribution" indicates that the corresponding posting was marked using a [[Special:Contributions/IP]] link (e.g by an unregistered user)
Member of
Contained by
May contain
analysis: s
derived-module-ids_v2a: timestamp
character data
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element autoSignature
{
   tei_att.pointing.attributes,
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type
   {
      "signed" | "unsigned" | "user_contribution" | "special_contribution"
   }?,
   ( text | s | timestamp )*
}

5.1.14. <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.]
Namespace http://www.tei-c.org/ns/1.0
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@Default)
region
Status Optional
Default world
label
Status Optional
Legal values are:
QAO-NC
QAO-NC-LOC:ids
QAO-NC-LOC:ids-NU:1
ACA-NC
ACA-NC-LC
CC-BY-SA
status (status) supplies a code identifying the current availability of the text.
Status Optional
Datatype teidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
core: bibl
May contain
core: p
header: licence
character data
Note

A consistent format should be adopted

Content model
<content/>
    
Schema Declaration
element availability
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute [http://www.tei-c.org/ns/1.0]region { text }?,
   attribute [http://www.tei-c.org/ns/1.0]label
   {
      "QAO-NC"
    | "QAO-NC-LOC:ids"
    | "QAO-NC-LOC:ids-NU:1"
    | "ACA-NC"
    | "ACA-NC-LC"
    | "CC-BY-SA"
   }?,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( text | model.availabilityPart | model.pLike )*
}

5.1.15. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
Contained by
textstructure: text
May contain
Note

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

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence>
  <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">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <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">
   <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_att.declaring.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.16. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@Default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Note

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

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.highlighted
    | tei_model.pPart.data
    | tei_model.pPart.edit
    | tei_model.segLike
    | tei_model.ptrLike
    | tei_model.biblPart
    | tei_model.global
   )*
}

5.1.17. <biblFull>

<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 15.3.2. Declarable Elements]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@Default) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Example
<biblFull>  <titleStmt>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>  </titleStmt>  <editionStmt>   <edition>UK edition</edition>  </editionStmt>  <extent>1231 pp</extent>  <publicationStmt>   <publisher>Yale University Press</publisher>   <pubPlace>New Haven and London</pubPlace>   <date>1990</date>  </publicationStmt>  <sourceDesc>   <p>No source: this is an original work</p>  </sourceDesc> </biblFull>
Content model
<content>
 <alternate>
  <sequence>
   <sequence>
    <elementRef key="titleStmt"/>
    <elementRef key="editionStmt"
     minOccurs="0"/>
    <elementRef key="extent" minOccurs="0"/>
    <elementRef key="publicationStmt"/>
    <elementRef key="seriesStmt"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="notesStmt"
     minOccurs="0"/>
   </sequence>
   <elementRef key="sourceDesc"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence>
   <elementRef key="fileDesc"/>
   <elementRef key="profileDesc"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element biblFull
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   (
      (
         (
            tei_titleStmt,
            tei_editionStmt?,
            tei_extent?,
            tei_publicationStmt,
            seriesStmt*,
            notesStmt?
         ),
         tei_sourceDesc*
      )
    | ( tei_fileDesc, tei_profileDesc )
   )
}

5.1.18. <biblNote>

<biblNote> child of <analytic> and <monogr>. #PCDATA, but otherwise roughly equivalent to TEI <note>. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element biblNote { tei_att.global.attributes, text }

5.1.19. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to)
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.

Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_macro.phraseSeq
}

5.1.20. <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@Default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
derived-module-ids_v2a: xptr
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Content model
<content>
 <sequence>
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   (
      tei_analytic*,
      ( tei_monogr, series* )+,
      (
         tei_model.noteLike
       | tei_model.ptrLike
       | tei_relatedItem
       | tei_citedRange
      )*
   )
}

5.1.21. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
Contained by
textstructure: text
May contain
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      tei_model.global*,
      ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )?,
      ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?,
      (
         ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
       | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+
       | (
            ( ( schemaSpec | tei_model.common ), tei_model.global* )+,
            (
               (
                  tei_model.divLike,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
             | (
                  tei_model.div1Like,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
            )?
         )
      ),
      ( tei_model.divBottom, tei_model.global* )*
   )
}

5.1.22. <byline>

<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]
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: lg
derived-module-ids_v2a: posting
figures: figure table
textstructure: back body div front titlePage
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.

Example
<byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline>
Example
<byline>Written from her own MEMORANDUMS</byline>
Example
<byline>By George Jones, Political Editor, in Washington</byline>
Example
<byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline>
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,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_docAuthor
    | tei_model.global
   )*
}

5.1.23. <byteCount>

<byteCount> child of <extent>; #PCDATA. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
units
Status Optional
Sample values include:
bytes
kb
[Default]
mb
gb
Contained by
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element byteCount
{
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]units { text }?,
   text
}

5.1.24. <c.title>

<c.title> child of <titleStmt>. #PCDATA only, otherwise a context-specific specialization of TEI <title>. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: titleStmt
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element c.title { tei_att.global.attributes, text }

5.1.25. <calendar>

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targOrder, @targType, @targetLang, @target, @evaluate)
Contained by
header: calendarDesc
May contain
core: p
Example
<calendarDesc>  <calendar xml:id="julianEngland">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
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_model.pLike+
}

5.1.26. <calendarDesc>

<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]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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

Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <elementRef key="calendar" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendarDesc { tei_att.global.attributes, tei_calendar+ }

5.1.27. <caption>

<caption> (1) a heading, title etc. attached to a picture or diagram; (2) a ‘pull quote’ or other text about or extracted from a text and superimposed upon it to draw attention to it. IDS-XCES adds ptr to the content model. []
Namespace http://www.ids-mannheim.de/xc
Module derived-module-ids_v2a
Attributes att.text (@wsd) (att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) )
type categorizes the caption
Status Optional
Sample values include:
byline
(caption containing authorship of an article)
display
(extra-textual caption (displayed box, etc.))
attached
(caption describing a figure, photograph, etc.)
unspec
(not specified or unknown) [Default]
Contained by
textstructure: div
May contain
derived-module-ids_v2a: xptr
figures: table
header: biblFull
ids-doc: poem
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element caption
{
   tei_att.text.attributes,
   attribute [http://www.tei-c.org/ns/1.0]type { text }?,
   ( head*, ( p | model.inter | model.ids.milestones )+ )
}

5.1.28. <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Contained by
header: category
May contain
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc> </catDesc>
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.29. <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Namespace http://www.tei-c.org/ns/1.0
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (target, @targOrder, @targType, @targetLang, @evaluate)
target the target of the pointer
Derived from att.pointing
Status Optional
Datatype IDREFS
Note

The original TEI target attribute of the class att.pointing comes out as of type CDATA from the ODD2DTD. (According to the TEI guidelines the type is 'datapointer' which stands for a single URI, which btw. correctly caused it to come out as xs:anyURI in the generated i5.xsd). But in the ids-xces.dtd it was IDREFS. Hence I include it here with an explicit specification of the IDREFS type.

scheme identifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
Status Optional
Datatype teidata.pointer
Contained by
header: textClass
May contain Empty element
Note

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

Example
<catRef scheme="#myTopics"  target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics">  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   tei_att.global.attributes,
   tei_att.pointing.attribute.targOrder,
   tei_att.pointing.attribute.targType,
   tei_att.pointing.attribute.targetLang,
   tei_att.pointing.attribute.evaluate,
   attribute target { xsd:IDREFS }?,
   attribute scheme { text }?,
   empty
}

5.1.30. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
core: desc gloss
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc" 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_catDesc+ | ( tei_model.descLike | equiv | tei_gloss )* ),
      tei_category*
   )
}

5.1.31. <cell>

<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
Module figures — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.tableDecoration (@role, @rows, @cols)
Contained by
figures: row
May contain
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element cell
{
   tei_att.global.attributes,
   tei_att.tableDecoration.attributes,
   tei_macro.specialPara
}

5.1.32. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Module header — Top-level driver
Attributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatus (@status) att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
target (target) points to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   tei_att.ascribed.attributes,
   tei_att.datable.attributes,
   tei_att.docStatus.attributes,
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

5.1.33. <changeDate>

<changeDate> child of <change>; #PCDATA; context-dependent specialization of TEI <date>. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
value
Status Optional
Datatype date
Contained by
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element changeDate
{
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]value { xsd:date }?,
   text
}

5.1.34. <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 9.3.5.1. Examples]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
May contain
derived-module-ids_v2a: xptr
header: biblFull
linking: timeline
Example
<cit>  <quote>and the breath of the whale is frequently attended with such an insupportable smell,    as to bring on disorder of the brain.</quote>  <bibl>Ulloa's South America</bibl> </cit>
Example
<entry>  <form>   <orth>horrifier</orth>  </form>  <cit type="translationxml:lang="en">   <quote>to horrify</quote>  </cit>  <cit type="example">   <quote>elle était horrifiée par la dépense</quote>   <cit type="translationxml:lang="en">    <quote>she was horrified at the expense.</quote>   </cit>  </cit> </entry>
Example
<cit type="example">  <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>  <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"   mimeType="audio/wav"/>  <cit type="translation">   <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>  </cit>  <cit type="translation">   <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>  </cit> </cit>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   tei_att.global.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
    | pc
    | tei_q
   )+
}

5.1.35. <citeData>

<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
property (property) A URI indicating a property definition.
Status Required
Datatype teidata.pointer
Contained by
May contain Empty element
Example
<citeStructure unit="book"  match="//body/divuse="@n">  <citeData property="http://purl.org/dc/terms/title"   use="head"/> </citeStructure>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element citeData
{
   tei_att.global.attributes,
   tei_att.citeStructurePart.attributes,
   attribute property { text },
   empty
}

5.1.36. <citeStructure>

<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
delim (delimiter) supplies a delimiting string preceding the structural component.
Status Optional
Datatype string
Schematron
<s:rule context="tei:citeStructure[parent::tei:citeStructure]"> <s:assert test="@delim">A <s:name/> with a parent <s:name/> must have a @delim attribute.</s:assert> </s:rule>
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>.
Status Required
Datatype teidata.xpath
Schematron
<s:rule context="tei:citeStructure[not(parent::tei:citeStructure)]"> <s:assert test="starts-with(@match,'/')">An XPath in @match on the outer <s:name/> must start with '/'.</s:assert> </s:rule>
Schematron
<s:rule context="tei:citeStructure[parent::tei:citeStructure]"> <s:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <s:name/>.</s:assert> </s:rule>
unit (unit) describes the structural unit indicated by the <citeStructure>.
Status Optional
Datatype teidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
May contain
core: desc
Example
<citeStructure unit="book"  match="//body/divuse="@n">  <citeStructure unit="chaptermatch="div"   use="position()delim=" ">   <citeStructure unit="versematch="div"    use="position()delim=":"/>  </citeStructure> </citeStructure>
Content model
<content>
 <sequence>
  <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.37. <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targOrder, @targType, @targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
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>.

Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.citing.attributes,
   tei_macro.phraseSeq
}

5.1.38. <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
scheme identifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
Status Required
Datatype teidata.pointer
Contained by
header: textClass
May contain
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element classCode
{
   tei_att.global.attributes,
   attribute scheme { text },
   tei_macro.phraseSeq.limited
}

5.1.39. <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { tei_att.global.attributes, tei_taxonomy+ }

5.1.40. <closer>

<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.written (@hand)
Member of
Contained by
core: lg
derived-module-ids_v2a: posting
figures: figure table
textstructure: back body div front postscript
May contain
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <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.written.attributes,
   (
      text
    | tei_model.gLike
    | tei_signed
    | tei_dateline
    | tei_salute
    | tei_model.phrase
    | tei_model.global
   )*
}

5.1.41. <column>

<column> child of <textDesc>. #PCDATA only. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
corpus: textDesc
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element column { tei_att.global.attributes, text }

5.1.42. <conformance>

<conformance> child of <editorialDecl>; #PCDATA plus level attribute. []
Namespace http://www.ids-mannheim.de/xc
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
level
Status Optional
Sample values include:
0
[Default]
1
2
3
Contained by
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element conformance
{
   tei_att.global.attributes,
   attribute [http://www.tei-c.org/ns/1.0]level { text }?,
   text
}

5.1.43. <conversion>

<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.formula (@formula) att.locatable (@where)
fromUnit indicates a source unit of measure that is to be converted into another unit indicated in toUnit.
Status Required
Datatype teidata.pointer
toUnit the target unit of measurement for a conversion from a source unit referenced in fromUnit.
Status Required
Datatype teidata.pointer
Contained by
header: unitDef
May contain Empty element
Note

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

Example
<conversion fromUnit="#shilling"  toUnit="#penceformula="$fromUnit * 12from="1707"  to="1971"/>
Example
<conversion fromUnit="#pound"  toUnit="#shillingformula="$fromUnit * 20from="1701"  to="1971"/>
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.44. <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Namespace http://www.tei-c.org/ns/1.0
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
sic from CES Dokumentation: "gives the original form"
Status Optional
Member of
Contained by
May contain
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   attribute [http://www.tei-c.org/ns/1.0]sic { text }?,
   tei_macro.paraContent
}

5.1.45. <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Namespace http://www.tei-c.org/ns/1.0
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@Default)
status indicates the degree of correction applied to the text.
Status Optional
Datatype teidata.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.
method indicates the method adopted to indicate corrections within the text.
Status Optional
Datatype teidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Contained by
May contain Character data only
Note

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

Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content/>
    
Schema Declaration
element correction
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   text
}

5.1.46. <correspAction>

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
type describes the nature of the action.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
Contained by
correspondence: correspDesc
header: correspDesc
May contain
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.sortable.attributes,
   attribute type
   {
      "sent" | "received" | "transmitted" | "redirected" | "forwarded"
   }?,
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

5.1.47. <correspAction>

<correspAction> 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
Namespace http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc
Module correspondence — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Recommended
Datatype
Sample values include:
sending
identifies a/the sending action of the message
receiving
identifies a/the receiving action of the message
transmitting
identifies a/the transmitting action of the message
redirecting
identifies a/the redirecting action of the message
forwarding
identifies a/the forwarding action of the message
Member of
Contained by
correspondence: correspDesc
header: correspDesc
May contain
Example
<ct:correspAction type="sending"    xmlns:ct="http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29">29 January 1807</date> </ct:correspAction>
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element correspAction
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.sortable.attributes,
   attribute type { data.enumerated }?,
   model.correspActionPart+
}

5.1.48. <correspContext>

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
correspondence: correspDesc
header: correspDesc
May contain
derived-module-ids_v2a: xptr
Example
<correspContext>  <ptr type="nextsubtype="toAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>  <ptr type="prevsubtype="fromAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/> </correspContext>
Example
<correspContext>  <ref type="prev"   target="http://weber-gesamtausgabe.de/A040962"> Previous letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1816-12-30">December 30, 1816</date>  </ref>  <ref type="next"   target="http://weber-gesamtausgabe.de/A041003"> Next letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1817-01-05">January 5, 1817</date>  </ref> </correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correspContext
{
   tei_att.global.attributes,
   tei_model.correspContextPart+
}

5.1.49. <correspContext>

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence
Namespace http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc
Module correspondence — Top-level driver
Member of
Contained by
correspondence: correspDesc
header: correspDesc
May contain
derived-module-ids_v2a: xptr
Example
<ct:correspContext    xmlns:ct="http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc">  <ptr type="nextsubtype="toAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>  <ptr type="prevsubtype="fromAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/> </ct:correspContext>
Example
<ct:correspContext    xmlns:ct="http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc">  <ref target="http://weber-gesamtausgabe.de/A040962">Previous letter of Carl    Maria von Weber to Caroline Brandt: December 30, 1816</ref>  <ref target="http://weber-gesamtausgabe.de/A041003">Next letter of Carl Maria    von Weber to Caroline Brandt: January 5, 1817</ref> </ct:correspContext>
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element correspContext { model.correspContextPart+ }

5.1.50. <correspDesc>

<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Module header — Top-level driver
Attributes att.declarable (@Default) att.canonical (@key, @ref) att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
header: profileDesc
May contain
Example
<correspDesc>  <correspAction type="sent">   <persName>Carl Maria von Weber</persName>   <settlement>Dresden</settlement>   <date when="1817-06-23">23 June 1817</date>  </correspAction>  <correspAction type="received">   <persName>Caroline Brandt</persName>   <settlement>Prag</settlement>  </correspAction>  <correspContext>   <ref type="prev"    target="http://www.weber-gesamtausgabe.de/A041209">Previous letter of   <persName>Carl Maria von Weber</persName>      to <persName>Caroline Brandt</persName>:   <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>   </ref>   <ref type="next"    target="http://www.weber-gesamtausgabe.de/A041217">Next letter of   <persName>Carl Maria von Weber</persName> to   <persName>Caroline Brandt</persName>:   <date when="1817-06-27">June 27, 1817</date>   </ref>  </correspContext> </correspDesc>
Content model
<content>
 <alternate>
  <classRef key="model.correspDescPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspDesc
{
   tei_att.declarable.attributes,
   tei_att.canonical.attributes,
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( tei_model.correspDescPart+ | tei_model.pLike+ )
}

5.1.51. <correspDesc>

<correspDesc> (correspondence description) a wrapper element for metadata pertaining to correspondence
Namespace http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc
Module correspondence — Top-level driver
Attributes att.declarable (@Default) att.canonical (@key, @ref) att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
header: profileDesc
May contain
Example
<ct:correspDesc    xmlns:ct="http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc">  <ct:correspAction type="sending">   <persName>Adelbert von Chamisso</persName>   <settlement>Vertus</settlement>   <date when="1807-01-29">29 January 1807</date>  </ct:correspAction>  <ct:correspAction type="receiving">   <persName>Louis de La Foye</persName>   <settlement>Caen</settlement>  </ct:correspAction>  <ct:correspContext>   <ref type="prev"    target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief023ChamissoandeLaFoye#1">Previous letter of Adelbert von Chamisso to Louis de La Foye: 16 January      1807</ref>   <ref type="next"    target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief025ChamissoandeLaFoye#1">Next letter of Adelbert von Chamisso to Louis de La Foye: 07 May      1810</ref>  </ct:correspContext> </ct:correspDesc>
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element correspDesc
{
   tei_att.declarable.attributes,
   tei_att.canonical.attributes,
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( model.correspDescPart+ | model.pLike+ )
}

5.1.52. <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Module namesdates — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
May contain
Note

The recommended source for codes to represent coded country names is ISO 3166.

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element country
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_macro.phraseSeq
}

5.1.53. <creatDate>

<creatDate> child of <creation> (in <profileDesc>). #PCDATA only. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: creation
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element creatDate { tei_att.global.attributes, text }

5.1.54. <creatRef>

<creatRef> child of <creation> (in <profileDesc>). #PCDATA only. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: creation
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element creatRef { tei_att.global.attributes, text }

5.1.55. <creatRefShort>

<creatRefShort> child of <creation> (in <profileDesc>). #PCDATA only. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: creation
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element creatRefShort { tei_att.global.attributes, text }

5.1.56. <creation>

<creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
Namespace http://www.tei-c.org/ns/1.0
Module header — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
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.

Example
<creation>  <date>Before 1987</date> </creation>
Example
<creation>  <date when="1988-07-10">10 July 1988</date> </creation>
Content model
<content/>
    
Schema Declaration
element creation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   ( creatDate, creatRef?, creatRefShort? )
}

5.1.57. <d.title>

<d.title> child of <titleStmt>. #PCDATA only, otherwise a context-specific specialization of TEI <title>. []
Namespace http://www.ids-mannheim.de/i5
Module ids-header
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: titleStmt
May contain Character data only
Content model
<content autoPrefix="true">
</content>
    
Schema Declaration
element d.title { tei_att.global.attributes, text }

5.1.58. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Namespace http://www.tei-c.org/ns/1.0
Module core — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

5.1.59. <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]
Module textstructure — Top-level driver
Attributes att.global (@id, @n, @xml:lang, @xml:base, @xml:space) (att.global.cmc (@creation)) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: lg
derived-module-ids_v2a: posting
figures: figure table
textstructure: back body closer div front opener
May contain
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <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,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global | docDate )*
}

5.1.60. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components]
Namespace http://www.tei-c.org/ns/1.0
Module core — Top-level driver
Attributes att.typed (type, @subtype)
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
deprecationInfo
(deprecation information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec 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
analysis: