From fb889b93e566d265720f4f961ca4bc9313520ffc Mon Sep 17 00:00:00 2001 From: Toma Tasovac Date: Sun, 26 Sep 2021 20:10:37 +0200 Subject: [PATCH] v0.9.0 (#148) * improve coverage for teiHeader - add monogr to core module (needed for biblStruct) - add forename and surname to namesdates for more fine-grained author/persName * add editorialDecl Needed for LexSeal-compatible information on encoding * add email for LexSeal-compatibility in teiHeader * make availability required in publicationStmt * allow biblStruct only in sourceDesc * make publicationStmtPart.agency unbound in publicationStmt we need this so that we can add both authority and publisher; we agreed that authority should be used for encoding various rights holders * add @role to so that we can specify what kind of authority we're talking about; for instance * changer requirements around langUsage - add @role and a closed value list to language (objectLanguage, workingLanguage, sourceLanguage, targetLanguage) - require language, langUsage and profileDesc * various improvements - specify suggested values for authority/@role - add narrative documentation for TEI Header - correct various misspellings - add different css style for - add Boris as contributor * temporarily remove VOLP example to clarify editorial roles and date of publication with Ana --- Schemas/TEILex0/TEILex0.odd | 43 +- Schemas/TEILex0/TEILex0.parts/015__header.xml | 225 +++ .../TEILex0.parts/01__introduction.xml | 5 +- Schemas/TEILex0/TEILex0.parts/02__entries.xml | 4 +- Schemas/TEILex0/TEILex0.parts/03__forms.xml | 2 +- .../TEILex0.parts/05__cross-references.xml | 2 +- .../TEILex0.parts/20__bibliography.xml | 30 + .../TEILex0.parts/40__specification.xml | 193 ++- Schemas/TEILex0/TEILex0.xpr | 28 +- Schemas/TEILex0/out/TEILex0.rng | 385 +++++- Schemas/TEILex0/stylesheets/TEILex0.xsl | 6 + Schemas/TEILex0/stylesheets/contributors.xsl | 75 +- docs/pages/TEILex0/TEILex0.html | 1228 ++++++++++++----- docs/pages/TEILex0/css/tei.lex0.web.css | 19 +- 14 files changed, 1758 insertions(+), 487 deletions(-) create mode 100644 Schemas/TEILex0/TEILex0.parts/015__header.xml diff --git a/Schemas/TEILex0/TEILex0.odd b/Schemas/TEILex0/TEILex0.odd index e3af2802..24d80b28 100644 --- a/Schemas/TEILex0/TEILex0.odd +++ b/Schemas/TEILex0/TEILex0.odd @@ -108,9 +108,15 @@ Hildenbrandt + + + Boris + Lehečka + + - + DARIAH Working Group on Lexical Resources @@ -123,6 +129,40 @@

Born digital

+ + + + add section on TEI + Header + correction of various misspellings + add monogr (needed for + biblStruct) + add forename and surname for more + fine-grained bibliographic information + add editorialDecl + add email to make possible contact information in + the header + require availability in publicationStmt to + provide licence + make sourceDesc optional + allow only biblStruct in + sourceDesc + make model.publicationStmtPart.agency unbound to allow both + publisher and authority in + publicationStmt + add role to authority with suggested + values: funder, sponsor, + rightsHolder + require language, langUsage and + profileDesc + add role to language with a closed list + of values: objectLanguage, workingLanguage, + sourceLanguage, targetLanguage + + + + @@ -131,6 +171,7 @@ + diff --git a/Schemas/TEILex0/TEILex0.parts/015__header.xml b/Schemas/TEILex0/TEILex0.parts/015__header.xml new file mode 100644 index 00000000..1fe74865 --- /dev/null +++ b/Schemas/TEILex0/TEILex0.parts/015__header.xml @@ -0,0 +1,225 @@ + + + +
+ Header +
+ General remarks +

A lexical resource encoded in TEI Lex-0 must, like any TEI file, start with a + teiHeader element. A TEI header contains information about the lexical resource + itself, its source(s), its encoding, and its revisions. Proper, structured metadata of this + kind is equally important for scholars using the resource, for software processing them, + and for cataloguers in libraries and archives.

+

The TEI header of a lexical resource has five major parts: + a file description, tagged fileDesc, provides a + full bibliographic description of the electronic lexical resource itself as well as + the source(s), analogue or digital, from which it may have been derived. For details, + see section File Description below. + an encoding description, tagged encodingDesc, + describes the relationship between the electronic resource and its source(s). It + allows for detailed description of whether (or how) the electronic resource was + produced, transcribed or normalized, how the encoder resolved ambiguities in the + source, what levels of encoding or analysis were applied etc. + a profile description, tagged profileDesc, + contains classificatory and contextual information about the lexical resource + including its object and working languages. + a container for external metadata, tagged + xenoData, contains metadata from non-TEI schemas, for instance Dublin Core, + MARCXML or MODS, if available. + a revision history, tagged revisionDesc, contains + a list of changes made during the development of the lexical resource, both before + and after its official release. +

+

Of these, two elements are required in TEI Lex-0: fileDesc and + profileDesc. It is highly recommended to include additional information in + encodingDesc. It is also an example of good practice to record changes in + revisionDesc.

+
+
+ File description +

The bibliographic description of the given machine-readable lexical resource is absolutely + essential for identifying the basic information about the resource itself, its creators and + publishers as well as the conditions under which it is made available to the public.

+

The elements that make up fileDesc are: + + + + + + + +

+

fileDesc is a mandatory element in plain TEI as well, but in TEI Lex-0 there are + some additional constraints and recommendations related to the content of this element.

+

+ + In titleStmt, TEI Lex-0 recommends the use of + type on title (with values either full or + abbr) to record both the full bibliographic title of the lexicographic + resource and the preferred abbreviated title for easy reference, should one exist. + In titleStmt, TEI Lex-0 recommends the use of + persName and orgName to distinguish between the names of persons + and organizations. This is especially important since in some cases, the name of an + institution is used to take up the collective authorship of a work. + When using persName, TEI Lex-0 recommends to + further structure the name with elements forename and + surname. + In publicationStmt, TEI Lex-0 requires the use of + availability to record the licence of the given lexicographic + resource. In other words, a TEI Lex-0 must include explicit + information on the conditions under which the given resource can be used. + In addition to publisher and distributor, the + publicationStmt in TEI Lex-0 may include + information on any other authority responsible for creating or making the + resource available. + If using authority, TEI Lex-0 requires the use of + role with values funder, sponsor or + rightsHolder. + In TEI Lex-0, sourceDesc is an optional element. Born-digital resources + or those which cannot be properly sourced do not require a sourceDesc. + If a resource is sourced, sourceDesc in TEI Lex-0 + requires the use of biblStruct for structuring bibliographic information + about the source(s). This is a departure from vanilla TEI which is more permissive in + this respect. + +

+ + + + + + + Etymologisches Wörterbuch des Deutschen: Die XML-Edition + EtymWB-XML + + + Wolfgang + Pfeifer + + + + + annotated by + + Oxana + Tsunykowa + + + + annotated by + + Yvonne + Wirkus + + + + restructured by + + Lothar + Lemnitzer + + + + restructured by + + Axel + Herold + + + + + + XML encoded version + 2006-11-17 + + + + Berlin-Brandenburgische Akademie der Wissenschaften + Digitales Wörterbuch der deutschen Sprache + Berlin-Brandenburgische Akademie der Wissenschaften + Berlin + 2009 + + Copyright 2002-2009 + + + + + + Wolfgang Pfeifer + Etymologisches Wörterbuch des Deutschen + 2 + + Akademie Verlag + Berlin + 1993 + with additional notes by the author + + + + + + + +
+
+ Profile description +

In plain TEI, profileDesc is an optional element, whereas in TEI Lex-0, it is + required. This is because the nature lexicographic resources is such that it is essential + to identify and record the language(s) used as part of the resource metadata.

+

That's why profileDesc requires langUsage and langUsage requires + at least one language element.

+

Regarding the use of the required attribute role and its possible values + (objectLanguage, workingLanguage, sourceLanguage or + targetLanguage), see the specification details for language.

+
+
diff --git a/Schemas/TEILex0/TEILex0.parts/01__introduction.xml b/Schemas/TEILex0/TEILex0.parts/01__introduction.xml index c1ce51b5..c82c1087 100644 --- a/Schemas/TEILex0/TEILex0.parts/01__introduction.xml +++ b/Schemas/TEILex0/TEILex0.parts/01__introduction.xml @@ -32,7 +32,7 @@
DARIAH Working Group

The DARIAH Working Group on Lexical Resources is a self-organized scholarly community - working under the auspicies of the pan-European Digital Research Infrastructure for + working under the auspices of the pan-European Digital Research Infrastructure for Arts and Humanities (DARIAH-EU). The goals of the WG are: to explore, assess and recommend standard tools and methods for the creation, application and dissemination of born-digital and retro-digitized @@ -141,7 +141,7 @@ the support of the German Ministry of Education and Research (BMBF), CLARIN and DARIAH-DE. For an overview, check out this blog post. - Lexcal Data Masterclass + Lexical Data Masterclass 2018. Co-organized by DARIAH, the Berlin Brandenburg Academy of Sciences (BBAW), Inria and the Belgrade Center for Digital Humanities, with the support of the German Ministry of Education and Research (BMBF), French @@ -218,6 +218,7 @@ The guidelines +

diff --git a/Schemas/TEILex0/TEILex0.parts/02__entries.xml b/Schemas/TEILex0/TEILex0.parts/02__entries.xml index 4253bd48..648e7d44 100644 --- a/Schemas/TEILex0/TEILex0.parts/02__entries.xml +++ b/Schemas/TEILex0/TEILex0.parts/02__entries.xml @@ -62,8 +62,8 @@ - Mixtepec Mixtec - Yucanany Mixtec + Mixtepec Mixtec + Yucanany Mixtec diff --git a/Schemas/TEILex0/TEILex0.parts/03__forms.xml b/Schemas/TEILex0/TEILex0.parts/03__forms.xml index 3340c86f..285a85ca 100644 --- a/Schemas/TEILex0/TEILex0.parts/03__forms.xml +++ b/Schemas/TEILex0/TEILex0.parts/03__forms.xml @@ -147,7 +147,7 @@ indistinguishable from entry itself. Eventually, the new content model of entry, which allows nesting, was adopted by TEI itself (Tasovac 2020).

-

TODO: explain different types of mwe's from a dict. model perspective refering to TODO: explain different types of mwe's from a dict. model perspective referring to Tasovac 2020)

Collocations diff --git a/Schemas/TEILex0/TEILex0.parts/05__cross-references.xml b/Schemas/TEILex0/TEILex0.parts/05__cross-references.xml index 0b63be5d..50d6623d 100644 --- a/Schemas/TEILex0/TEILex0.parts/05__cross-references.xml +++ b/Schemas/TEILex0/TEILex0.parts/05__cross-references.xml @@ -106,7 +106,7 @@ Related

The default reference to another lexical unit when no more granular information about the type of relationship is available.

-

In TEI Lex-0, cross-references are by default enoded as <xr +

In TEI Lex-0, cross-references are by default encoded as <xr type="related"></xr>.

diff --git a/Schemas/TEILex0/TEILex0.parts/20__bibliography.xml b/Schemas/TEILex0/TEILex0.parts/20__bibliography.xml index dc2f1d68..c93ac090 100644 --- a/Schemas/TEILex0/TEILex0.parts/20__bibliography.xml +++ b/Schemas/TEILex0/TEILex0.parts/20__bibliography.xml @@ -178,6 +178,23 @@ + + + EtymWB-XML + Wörterbuch des Deutschen: Die XML-Edition + + + Berlin + Berlin-Brandenburgische Akademie der Wissenschaften + 2009 + + + @@ -366,6 +383,19 @@ + diff --git a/Schemas/TEILex0/TEILex0.parts/40__specification.xml b/Schemas/TEILex0/TEILex0.parts/40__specification.xml index 7616db14..c07cce32 100644 --- a/Schemas/TEILex0/TEILex0.parts/40__specification.xml +++ b/Schemas/TEILex0/TEILex0.parts/40__specification.xml @@ -20,9 +20,11 @@ but I'm leaving it for now, in case we need it in the header--> + + + citedRange imprint analytic monogr publisher pubPlace ref date hi editor respStmt name num resp term note graphic p email"/> + + include="teiHeader fileDesc profileDesc titleStmt editionStmt extent publicationStmt sourceDesc encodingDesc revisionDesc xenoData editorialDecl projectDesc seriesStmt + notesStmt authority distributor idno edition availability licence appInfo classDecl namespace tagUsage tagsDecl rendition"/> - + + @@ -426,8 +430,7 @@ - + @@ -441,6 +444,26 @@ + + + + + + + + + Old Church Slavic + Latin + (Premodern) Greek + + + + + + + + + @@ -460,6 +483,96 @@ + + + + + + Object language is the "language being described." (ISO + 16642:2017) + + + Working language is the "language used to describe objects." (ISO + 16642:2017) + + + Source language is the language of the content to be translated. + (ISO 17100:215) + + + Target language is the language of the content into which source + language content is translated. (ISO 17100:215) + + + + + + + + Русский литературный язык XIX века + Современный русский язык + 19th-century literary Russian + Modern Russian + + + + + + + Old Church Slavic + Latin + (Premodern) Greek + + + + +

In a monolingual dictionary, where the object language and the working language + are the same, one should list each as a separate language element with + a specific role attribute. A human-readable, informal prose + characterization should be supplied as content for the element. When the + human-readable name(s) of languages are provided in multiple languages, the + attribute xml:lang should be used to indicate what language is used + to name the given object or working language.

+

A bilingual dictionary could be documented as having two object languages. In + those cases, however, it is recommended -- and more precise -- to describe each + object language as either a source language or a target language.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -523,6 +636,74 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Miklosich + Franz + Lexicon Palaeoslovenico-Graeco-Latinum + + Guilelmus Braumueller + Vindobonae + 1862 + + + + + + + + + + + + + The full title of a lexicographic resource, such as The Oxford English Dictionary. + + + The preferred abbreviated title of a lexicographic resource, such as the OED. + + + + + diff --git a/Schemas/TEILex0/TEILex0.xpr b/Schemas/TEILex0/TEILex0.xpr index c1ae7375..a5443734 100644 --- a/Schemas/TEILex0/TEILex0.xpr +++ b/Schemas/TEILex0/TEILex0.xpr @@ -7211,7 +7211,7 @@ ${caret} - xproc/teilex0.xpl + TEILex0.parts/40__specification.xml @@ -7234,7 +7234,7 @@ ${caret} - stylesheets/TEILex0.xsl + TEILex0.odd @@ -7254,36 +7254,39 @@ ${caret} - xproc/teilex0-alt.xpl + xproc/teilex0.xpl + TEILex0: ODD to RELAX NG (XML syntax) TEILex0: Generate documentation + ANT XPROC 2 + 2 - TEILex0.examples/examples.xml + stylesheets/TEILex0.xsl - TEI Stripper (NS prep for inclusion into main odd file) + TEILex0: Generate documentation - XML + XPROC @@ -7294,7 +7297,7 @@ ${caret} - stylesheets/contributors.xsl + xproc/teilex0-alt.xpl @@ -7314,16 +7317,16 @@ ${caret} - TEILex0.odd + TEILex0.examples/examples.xml - TEILex0: Generate documentation + TEI Stripper (NS prep for inclusion into main odd file) - XPROC + XML @@ -7334,24 +7337,21 @@ ${caret} - TEILex0.parts/40__specification.xml + stylesheets/contributors.xsl - TEILex0: ODD to RELAX NG (XML syntax) TEILex0: Generate documentation - ANT XPROC 2 - 2 diff --git a/Schemas/TEILex0/out/TEILex0.rng b/Schemas/TEILex0/out/TEILex0.rng index b4dd470d..2ad25da8 100644 --- a/Schemas/TEILex0/out/TEILex0.rng +++ b/Schemas/TEILex0/out/TEILex0.rng @@ -5,7 +5,7 @@ xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes" ns="http://www.tei-c.org/ns/1.0"> - + - + - - + @@ -28,60 +26,55 @@ - - + , - - - + + + and - + , . - + - : - + . - - + Contributors - contributors - + contributors + - How to cite these guidelines - - Full citation + Full citation @@ -98,7 +91,6 @@ . - Short citation @@ -117,15 +109,44 @@ . - - - + + + + Revision history + Changes to the TEI Lex-0 + specification up to version 0.8.6 were included in comments inside the ODD file + itself. Starting with version 0.9.0, we're listing a summary of the changes in this + list for easier reference. + + + + + + underline + Version: + + + ( + + ) + + + + + + + + + + + + + + - - diff --git a/docs/pages/TEILex0/TEILex0.html b/docs/pages/TEILex0/TEILex0.html index 98aba6fe..b080e8e6 100644 --- a/docs/pages/TEILex0/TEILex0.html +++ b/docs/pages/TEILex0/TEILex0.html @@ -1,6 +1,77 @@ -TEI Lex-0 — A baseline encoding for lexicographic data

TEI Lex-0

— A baseline encoding for lexicographic data

1. Introduction

1.1. TEI Lex-0 in a nutshell

TEI Lex-0 is both a technical specification and a set of community-based recommendations for encoding machine-readable dictionaries. It is rooted in the Guidelines of the Text Encoding Initiative (TEI) and delivered as a customization of the TEI schema.

Following the spirit of TEI Analytics, developed in the context of the MONK project (Zillig 2009), TEI Lex-0 aims at establishing a baseline encoding and a target format to facilitate the interoperability of heterogeneously encoded lexical resources. This is important both in the context of building lexical infrastructures as such (Ermolaev and Tasovac 2012) and in the context of developing generic TEI-aware tools such as dictionary viewers and profilers.

1.2. The community

Preliminary work for the establishment of TEI Lex-0 started in the Working Group "Retrodigitised Dictionaries" lead by Toma Tasovac and Vera Hildenbrandt as part of the COST Action European Network of e-Lexicography (ENeL). Upon the completion of the COST Action, the work on TEI Lex-0 was taken up by the DARIAH Working Group "Lexical Resources". Currently, the work on TEI Lex-0 is also supported by the H2020-funded European Lexicographic Infrastructure (ELEXIS).

1.2.1. DARIAH Working Group

The DARIAH Working Group on Lexical Resources is a self-organized scholarly community working under the auspicies of the pan-European Digital Research Infrastructure for Arts and Humanities (DARIAH-EU). The goals of the WG are:

  • to explore, assess and recommend standard tools and methods for the creation, application and dissemination of born-digital and retro-digitized lexical resources (dictionaries, lexicons, thesauri, word lists etc.) as well as other, similar kinds of structured data (gazetteers, almanacs, encyclopaedias etc.); and
  • to foster, develop and publicize digitally-enabled lexicographic research from a cross-disciplinary and transnational perspective.

The WG focuses on the application and explication of existing standards, both onomasiological (TMF, TBX and SKOS) and semasiological (LMF, TEI, and Ontolex); draws upon the expertise of various DARIAH partners who are active in this field; and collaborates with relevant external projects and associations, such as the European Lexicographic Infrastructure (ELEXIS) and CLARIN in order to ascertain the widest possible reach of the Working Group’s results.

At the same time, the WG pursues a strong research-driven agenda on the diversity of European lexicographic heritage. In addition to investigating pan-European vocabularies and multiple dimensions of lexical borrowing, the working group evaluates current practices and formulates guidelines on data enrichment and mutual linking of existing electronic dictionaries in view of their common European heritage.

WG Chairs

Laurent Romary is Directeur de Recherche at Inria (team ALMAnaCH (France)). He received a PhD degree in computational linguistics in 1989 and his Habilitation in 1999. He carries out research on the modelling of semi-structured documents, with a specific emphasis on texts and linguistic resources. He has been active in standardisation activities with ISO, as chair of committee ISO/TC 37/SC 4 (2002-2014), chair of ISO/TC 37 (2016-) and the Text Encoding Initiative, as member (2001-2011) and chair (2008-2011) of its Technical Council. He also has a long-standing implication in open science related activities.

Toma Tasovac is Director of the Belgrade Center for Digital Humanities (BCDH) and DARIAH-EU. He was educated at Harvard University, Princeton University and Trinity College Dublin. His areas of interest include lexicography, data modeling, TEI, digital editions and research infrastructures. He previously served as the National Coordinator of DARIAH-RS and Chair of the National Coordinators' Committee at DARIAH-EU. Under Toma's leadership, BCDH has received funding from various national and international granting bodies, including Erasmus Plus and Horizon 2020.

DigiLex Blog

The working group runs a blog called DigiLex: Legacy Dictionaries Reloaded as a platform for sharing tips, raising questions and discussing methods for the creation of lexical resources.

1.2.2. ELEXIS

ELEXIS is a H2020-funded project which proposes to integrate, extend and harmonise national and regional efforts in the field of lexicography, both modern and historical, with the goal of creating a sustainable infrastructure which will (1) enable efficient access to high-quality lexical data in the digital age, and (2) bridge the gap between more advanced and lesser-resourced scholarly communities working on lexicographic resources.

1.2.3. Contributors

  • Piotr Banski
  • Jack Bowers
  • Jesse de Does
  • Katrien Depuydt
  • Tomaž Erjavec
  • Alexander Geyken
  • Axel Herold
  • Vera Hildenbrandt
  • Mohamed Khemakhem
  • Snežana Petrović
  • Laurent Romary
  • Ana Salgado
  • Toma Tasovac
  • Andreas Witt

1.2.4. Meetings

The Working Group has organized a number of working meetings dedicated to the development of TEI Lex-0. These include:

  • Toward Best Practice Guidelines for Encoding Legacy Dictionaries: An ENeL-DARIAH-PARTHENOS Expert Workshop. Preußische Staatsbibliothek, Berlin (17-19 November 2016).
  • Overview of Retrodigitized Dictionaries and Best-Practice Guidelines For Encoding Legacy Dictionaries. ENeL Annual Meeting, Budapest (24 February 2017).
  • TEI Lex-0 @DARIAH WG "Lexical Resources". Harnack Haus, Freie Universität Berlin (27 April 2017).
  • TEI Lex-0 @DARIAH WG "Lexical Resources". Austrian Center for Digital Humanities, Austrian Academy of Sciences, Vienna (26 June 2017).
  • TEI Lex-0: From Best-Practice Guidelines to a TEI Schema. DARIAH-EU Coordination Office, Berlin (2-3 May 2018). Funded by DARIAH-EU's Working Groups Funding Scheme and ELEXIS.
  • TEI Lex-0 and Beyond: A Workshop. University of Ljubljana (16 July 2018). Funded by DARIAH-EU's Working Group Funding Scheme and ELEXIS.
  • TEI Lex-0 Meeting. DARIAH-EU Coordination Office, Berlin (30 January 2019).
  • Joint TEI Lex-0 / Ontolex-Lemon Meeting. Collocated with eLex 2019. Sintra, Portugal (4 October 2019). Funded by ELEXIS.
  • Toward a TEI Lex-0 Publisher: A Workshop, DARIAH-EU Coordination Office, Berlin (16-17 December 2019). Funded by the Belgrade Center for Digital Humanities.

1.2.5. Training measures

TEI Lex-0 and best practices in lexical data modeling have been introduced to large number of young scholars at various training events, including:

The European Digital Humanities Masterclass 2020 had to be postponed due to the Corona pandemic.

A picture is worth a thousand words

1.3. The rationale

To what extent can we achieve consistent encoding within a given community of practice by following the TEI Guidelines? The topic is of particular importance for lexical data if we think of the potential wealth of content we could gain from pooling together the information available in the variety of highly structured, historical and contemporary lexical resources. The encoding possibilities offered by the Dictionaries Chapter in the Guidelines are too numerous and too flexible to guarantee sufficient interoperability and a coherent model for searching, visualising or enriching multiple lexical resources.

TEI Lex-0 should not be thought of as a replacement of the Dictionaries Chapter in the TEI Guidelines or as the format that must be necessarily used for editing or managing individual resources, especially in those projects and/or institutions that already have established workflows based on their own flavors of TEI. TEI Lex-0 should be primarily seen as a format that existing TEI dictionaries can be unequivocally transformed to in order to be queried, visualised, or mined in a uniform way. At the same time, however, there is no reason why TEI Lex-0 could not or should not be used as a best-practice example in educational settings or as a foundation of new TEI-based projects. This is especially true considering the fact that TEI Lex-0 aims to to stay as aligned as possible with the TEI subset developed in conjunction with the revision of the ISO LMF (Lexical Markup Framework) standard (cf. Romary 2015)

1.4. The guidelines

1.4.1. How to cite these guidelines

Full citation

Toma Tasovac, Laurent Romary, Piotr Banski, Jack Bowers, Jesse de Does, Katrien Depuydt, Tomaž Erjavec, Alexander Geyken, Axel Herold, Vera Hildenbrandt, Mohamed Khemakhem, Snežana Petrović, Ana Salgado and Andreas Witt. 2018. TEI Lex-0: A baseline encoding for lexicographic data. Version 0.8.6. DARIAH Working Group on Lexical Resources. https://dariah-eric.github.io/lexicalresources/pages/TEILex0/TEILex0.html.

Short citation

Toma Tasovac, Laurent Romary et al. 2018. TEI Lex-0: A baseline encoding for lexicographic data. Version 0.8.6. DARIAH Working Group on Lexical Resources. https://dariah-eric.github.io/lexicalresources/pages/TEILex0/TEILex0.html.

2. Entries

2.1. General remarks

An <entry> is a basic reference unit in a dictionary: it groups together all the information related to a particular lemma. For instance:

    <entry xml:id="OALD.competitor" type="mainEntry" xml:lang="en">
+TEI Lex-0 — A baseline encoding for lexicographic data
    TEI Lex-0
     — A baseline encoding for lexicographic data
    1. Introduction
    1.1. TEI Lex-0 in a nutshell
    TEI Lex-0 is both a technical specification and a set of community-based recommendations for encoding machine-readable dictionaries. It is rooted in the Guidelines of the Text Encoding Initiative (TEI) and delivered as a customization of the TEI schema.
    Following the spirit of TEI Analytics, developed in the context of the MONK project (Zillig 2009), TEI Lex-0 aims at establishing a baseline encoding and a target format to facilitate the interoperability of heterogeneously encoded lexical resources. This is important both in the context of building lexical infrastructures as such (Ermolaev and Tasovac 2012) and in the context of developing generic TEI-aware tools such as dictionary viewers and profilers.
    1.2. The community
    Preliminary work for the establishment of TEI Lex-0 started in the Working Group "Retrodigitised Dictionaries" lead by Toma Tasovac and Vera Hildenbrandt as part of the COST Action European Network of e-Lexicography (ENeL). Upon the completion of the COST Action, the work on TEI Lex-0 was taken up by the DARIAH Working Group "Lexical Resources". Currently, the work on TEI Lex-0 is also supported by the H2020-funded European Lexicographic Infrastructure (ELEXIS).
    1.2.1. DARIAH Working Group
    The DARIAH Working Group on Lexical Resources is a self-organized scholarly community working under the auspices of the pan-European Digital Research Infrastructure for Arts and Humanities (DARIAH-EU). The goals of the WG are: 
    • to explore, assess and recommend standard tools and methods for the creation, application and dissemination of born-digital and retro-digitized lexical resources (dictionaries, lexicons, thesauri, word lists etc.) as well as other, similar kinds of structured data (gazetteers, almanacs, encyclopaedias etc.); and
    • to foster, develop and publicize digitally-enabled lexicographic research from a cross-disciplinary and transnational perspective.
    The WG focuses on the application and explication of existing standards, both onomasiological (TMF, TBX and SKOS) and semasiological (LMF, TEI, and Ontolex); draws upon the expertise of various DARIAH partners who are active in this field; and collaborates with relevant external projects and associations, such as the European Lexicographic Infrastructure (ELEXIS) and CLARIN in order to ascertain the widest possible reach of the Working Group’s results.
    At the same time, the WG pursues a strong research-driven agenda on the diversity of European lexicographic heritage. In addition to investigating pan-European vocabularies and multiple dimensions of lexical borrowing, the working group evaluates current practices and formulates guidelines on data enrichment and mutual linking of existing electronic dictionaries in view of their common European heritage.
    WG Chairs
     Laurent Romary is Directeur de Recherche at Inria (team ALMAnaCH (France)). He received a PhD degree in computational linguistics in 1989 and his Habilitation in 1999. He carries out research on the modelling of semi-structured documents, with a specific emphasis on texts and linguistic resources. He has been active in standardisation activities with ISO, as chair of committee ISO/TC 37/SC 4 (2002-2014), chair of ISO/TC 37 (2016-) and the Text Encoding Initiative, as member (2001-2011) and chair (2008-2011) of its Technical Council. He also has a long-standing implication in open science related activities.
    Toma Tasovac is Director of the Belgrade Center for Digital Humanities (BCDH) and DARIAH-EU. He was educated at Harvard University, Princeton University and Trinity College Dublin. His areas of interest include lexicography, data modeling, TEI, digital editions and research infrastructures. He previously served as the National Coordinator of DARIAH-RS and Chair of the National Coordinators' Committee at DARIAH-EU. Under Toma's leadership, BCDH has received funding from various national and international granting bodies, including Erasmus Plus and Horizon 2020.
    DigiLex Blog
    The working group runs a blog called DigiLex: Legacy Dictionaries Reloaded as a platform for sharing tips, raising questions and discussing methods for the creation of lexical resources.
    1.2.2. ELEXIS
    ELEXIS is a H2020-funded project which proposes to integrate, extend and harmonise national and regional efforts in the field of lexicography, both modern and historical, with the goal of creating a sustainable infrastructure which will (1) enable efficient access to high-quality lexical data in the digital age, and (2) bridge the gap between more advanced and lesser-resourced scholarly communities working on lexicographic resources.
    1.2.3. Contributors
    •  Piotr Banski
    •  Jack Bowers
    •  Jesse de Does
    •  Katrien Depuydt
    •  Tomaž Erjavec
    •  Alexander Geyken
    •  Axel Herold
    •  Vera Hildenbrandt
    •  Mohamed Khemakhem
    •  Boris Lehečka
    •  Snežana Petrović
    •  Laurent Romary
    •  Ana Salgado
    •  Toma Tasovac
    •  Andreas Witt
    1.2.4. Meetings
    The Working Group has organized a number of working meetings dedicated to the development of TEI Lex-0. These include: 
    • Toward Best Practice Guidelines for Encoding Legacy Dictionaries: An ENeL-DARIAH-PARTHENOS Expert Workshop. Preußische Staatsbibliothek, Berlin (17-19 November 2016).
    • Overview of Retrodigitized Dictionaries and Best-Practice Guidelines For Encoding Legacy Dictionaries. ENeL Annual Meeting, Budapest (24 February 2017). 
    • TEI Lex-0 @DARIAH WG "Lexical Resources". Harnack Haus, Freie Universität Berlin (27 April 2017).
    • TEI Lex-0 @DARIAH WG "Lexical Resources". Austrian Center for Digital Humanities, Austrian Academy of Sciences, Vienna (26 June 2017).
    • TEI Lex-0: From Best-Practice Guidelines to a TEI Schema. DARIAH-EU Coordination Office, Berlin (2-3 May 2018). Funded by DARIAH-EU's Working Groups Funding Scheme and ELEXIS.
    • TEI Lex-0 and Beyond: A Workshop. University of Ljubljana (16 July 2018). Funded by DARIAH-EU's Working Group Funding Scheme and ELEXIS.
    • TEI Lex-0 Meeting. DARIAH-EU Coordination Office, Berlin (30 January 2019).
    • Joint TEI Lex-0 / Ontolex-Lemon Meeting. Collocated with eLex 2019. Sintra, Portugal (4 October 2019). Funded by ELEXIS.
    • Toward a TEI Lex-0 Publisher: A Workshop, DARIAH-EU Coordination Office, Berlin (16-17 December 2019). Funded by the Belgrade Center for Digital Humanities.
    1.2.5. Training measures
    TEI Lex-0 and best practices in lexical data modeling have been introduced to large number of young scholars at various training events, including: 
    The European Digital Humanities Masterclass 2020 had to be postponed due to the Corona pandemic.
    A picture is worth a thousand words
    1.3. The rationale
    To what extent can we achieve consistent encoding within a given community of practice by following the TEI Guidelines? The topic is of particular importance for lexical data if we think of the potential wealth of content we could gain from pooling together the information available in the variety of highly structured, historical and contemporary lexical resources. The encoding possibilities offered by the Dictionaries Chapter in the Guidelines are too numerous and too flexible to guarantee sufficient interoperability and a coherent model for searching, visualising or enriching multiple lexical resources.
    TEI Lex-0 should not be thought of as a replacement of the Dictionaries Chapter in the TEI Guidelines or as the format that must be necessarily used for editing or managing individual resources, especially in those projects and/or institutions that already have established workflows based on their own flavors of TEI. TEI Lex-0 should be primarily seen as a format that existing TEI dictionaries can be unequivocally transformed to in order to be queried, visualised, or mined in a uniform way. At the same time, however, there is no reason why TEI Lex-0 could not or should not be used as a best-practice example in educational settings or as a foundation of new TEI-based projects. This is especially true considering the fact that TEI Lex-0 aims to to stay as aligned as possible with the TEI subset developed in conjunction with the revision of the ISO LMF (Lexical Markup Framework) standard (cf. Romary 2015)
    1.4. The guidelines
    1.4.1. How to cite these guidelines
    Full citation
    Toma Tasovac, Laurent Romary, Piotr Banski, Jack Bowers, Jesse de Does, Katrien Depuydt, Tomaž Erjavec, Alexander Geyken, Axel Herold, Vera Hildenbrandt, Mohamed Khemakhem, Boris Lehečka, Snežana Petrović, Ana Salgado and Andreas Witt. 2018. TEI Lex-0: A baseline encoding for lexicographic data. Version 0.9.0. DARIAH Working Group on Lexical Resources. https://dariah-eric.github.io/lexicalresources/pages/TEILex0/TEILex0.html.
    Short citation
    Toma Tasovac, Laurent Romary et al. 2018. TEI Lex-0: A baseline encoding for lexicographic data. Version 0.9.0. DARIAH Working Group on Lexical Resources. https://dariah-eric.github.io/lexicalresources/pages/TEILex0/TEILex0.html.
    1.4.2. Revision history
    Changes to the TEI Lex-0 specification up to version 0.8.6 were included in comments inside the ODD file itself. Starting with version 0.9.0, we're listing a summary of the changes in this list for easier reference. 
    Version: 0.9.0 (2021-09-27)
    3. Entries
    3.1. General remarks
    An <entry> is a basic reference unit in a dictionary: it groups together all the information related to a particular lemma. For instance:
      <entry xml:id="OALD.competitor" type="mainEntry" xml:lang="en">
   <form type="lemma">
      <orth>competitor</orth>
      <hyph>com|peti|tor</hyph>
@@ -12,7 +83,7 @@
   <sense xml:id="OALD.competitor.1">
      <def>person who competes.</def>
   </sense>
-</entry>OALD (1974) 
      <entry xml:id="MM.RSSKJ.круна" xml:lang="sr">
+</entry>OALD (1974) 
      <entry xml:id="MM.RSSKJ.круна" xml:lang="sr">
   <form type="lemma">
      <orth>кру̏на</orth>
   </form>
@@ -57,12 +128,12 @@
      <usg type="meaningType" expand="фигуративно" norm="figurative">фиг.</usg>
      <def>врхунац, највиши домет неког рада, забаве.</def>
   </sense>
-</entry>Московљевић (1990) 
    2.2. Mandatory attributes
    The TEI Lex-0 schema prescribes two mandatory attributes on <entry>:
    • xml:id uniquely identifies the element it is associated with;
    • xml:lang identifies the object language of the element it is associated with.
    In XML, xml:lang is inherited from the immediately enclosing element or from its closest ancestor that has this attribute. This means that in XML not every element needs to have the xml:lang attribute.
    TEI Lex-0 recommends that xml:lang be attached to so-called container elements (such as <entry> and <cit>) rather than individual <form> elements.
    In addition, TEI Lex-0 privileges <entry> as the dictionary’s central textual component by requiring both a unique identifier (xml:id) as well as xml:lang.
      xml:lang identifies the object language of the element it is associated with. The language ‘tag’ (i.e. the value of this attribute) must follow IETF BCP 47, the Internet Engineering Task Force's best-practice document outlining standard identifiers for labeling language content. To learn more about what language tag is appropriate for your project, check out W3C's useful resource on choosing language tags.
      If the language or language variety you are working on is not covered by BCP 47, make sure to follow the syntax of Private Use Tags described in BCP 47 Section 2.2.7 when creating one. Do this only if you are absolutely certain that no standard tag exists for your object language.
      If you have created a "private" language tag, you can validate it (in terms of its structural well-formedness and validity) using the BCP 47 validator.
      Language tags containing private-use subtags should be documented in the TEI header, specifically using one or more <language> elements grouped under <langUsage> inside <profileDesc>:
      <profileDesc>
+</entry>Московљевић (1990) 
    3.2. Mandatory attributes
    The TEI Lex-0 schema prescribes two mandatory attributes on <entry>:
    • xml:id uniquely identifies the element it is associated with;
    • xml:lang identifies the object language of the element it is associated with.
    In XML, xml:lang is inherited from the immediately enclosing element or from its closest ancestor that has this attribute. This means that in XML not every element needs to have the xml:lang attribute.
    TEI Lex-0 recommends that xml:lang be attached to so-called container elements (such as <entry> and <cit>) rather than individual <form> elements.
    In addition, TEI Lex-0 privileges <entry> as the dictionary’s central textual component by requiring both a unique identifier (xml:id) as well as xml:lang.
      xml:lang identifies the object language of the element it is associated with. The language ‘tag’ (i.e. the value of this attribute) must follow IETF BCP 47, the Internet Engineering Task Force's best-practice document outlining standard identifiers for labeling language content. To learn more about what language tag is appropriate for your project, check out W3C's useful resource on choosing language tags.
      If the language or language variety you are working on is not covered by BCP 47, make sure to follow the syntax of Private Use Tags described in BCP 47 Section 2.2.7 when creating one. Do this only if you are absolutely certain that no standard tag exists for your object language.
      If you have created a "private" language tag, you can validate it (in terms of its structural well-formedness and validity) using the BCP 47 validator.
      Language tags containing private-use subtags should be documented in the TEI header, specifically using one or more <language> elements grouped under <langUsage> inside <profileDesc>:
      <profileDesc>
   <langUsage>
-     <language ident="mix">Mixtepec Mixtec</language>
-     <language ident="mix-x-YCNY">Yucanany Mixtec</language>
+     <language ident="mix" role="objectLanguage">Mixtepec Mixtec</language>
+     <language ident="mix-x-YCNY" role="objectLanguage">Yucanany Mixtec</language>
   </langUsage>
-</profileDesc>
    2.3. Grammatical properties
    2.3.1. General remarks
    Grammatical properties of lexical entries should be specified in entry/gramGrp/gram. This <gram> element will typically specify the part-of-speech of the entry:
      <entry xml:lang="en" type="mainEntry" xml:id="on">
+</profileDesc>

3.3. Grammatical properties

3.3.1. General remarks

Grammatical properties of lexical entries should be specified in entry/gramGrp/gram. This <gram> element will typically specify the part-of-speech of the entry:

    <entry xml:lang="en" type="mainEntry" xml:id="on">
   <form type="lemma">
      <orth>on</orth>
   </form>
@@ -70,23 +141,23 @@
      <gram type="pos">prep</gram>
   </gramGrp>
   <!--...-->
-</entry>

Notes:

  1. Grammatical properties of the entry as a whole should not be specified in entry/form[@type="lemma"]/gramGrp.
  2. entry/form/gramGrp should be used only if a particular form (a dialectal variant, for instance) has different grammatical properties from the lemma; or to indicate the grammatical properties of the inflected form which clearly deviate from the lemma.
  3. For entries which group grammatical homonyms inside single entries (e.g. in English dictionaries which do not have separate entries for conversion pairs of nouns and verbs, such as run or aid see the discussion under Nested entries vs. multiple-senses.

2.3.2. Typology of gram

The TEI Guidelines define:

  • seven specific elements which can be used to mark up particular grammatical properties:<case>, <gen> (for gender), <iType> (for inflection type), <mood>, <number>, <per> (for person) and <tns> (for tense); and
  • one general element (<gram>) which can be used to encode different kinds of grammatical properties.

The Guidelines themselves do not explain the reasoning behind having two different mechanisms for encoding the same kind of information. The two mechanisms are treated as fully interchangeable: see, for instance, the first two examples in Section 9.3.2.

While it is perfectly understandable why marking up grammatical information using a number of specific, granular elements can be considered desirable, the current situation is less than perfect:

  • if both <pos>prep</pos> and <gram type="pos">prep</gram> are possible, and if both mean exactly the same thing, the choice about how to encode grammatical information will always be partially arbitrary;
  • the specific grammatical elements in TEI cover some important grammatical categories, but are certainly not exhaustive: for instance, Slavic dictionaries will, as a rule, indicate aspect (imperfective or perfective) as the defining grammatical property of verbs, yet there is no specific element for: <aspect> in TEI.
  • if there are no specific elements for every possible grammatical category, mixing specific and general elements (for instance <pos>v.</pos> and <gram type="aspect">imperf.</gram> within the same entry and/or dictionary will most likely further complicate data processing and data interoperability.

Considering the goals of TEI Lex-0 to serve as a common baseline and target format for transforming and comparing different lexical resources, we have decided to do away with the specific elements for grammatical properties. Instead, we recommend the use of typed <gram> elements. This is a decision that wasn't taken lightly and one which solicited a great deal of discussion. It goes without saying that TEI itself will continue to support both mechanisms and that an XSLT transformation from <pos>prep</pos> to <gram type="pos">prep</gram> for those who want to convert their dictionaries to TEI Lex-0 would be easily accomplished.

The following table shows a mapping between the specific TEI elements and the typed <gram> elements in TEI Lex-0:

Mapping between specific elements in TEI and the generalized mechanism in TEI Lex-0
TEITEI Lex-0
<pos>n.</pos><gram type="pos">n.</gram>
<case>acc.</case><gram type="case">acc.</gram>
<gen>f.</gen><gram type="gender">f.</gram>
<iType>7</iType><gram type="inflectionType">7</gram>
<mood>indic.</mood><gram type="mood">indic.</gram>
<number>sg.</number><gram type="number">sg.</gram>
<per>3rd</per><gram type="person">3rd</gram>
<tns>aorist</tns><gram type="tense">aorist</gram>
-<gram type="aspect">imperf.</gram>
-<gram type="transitivity">intr.</gram>

Note: See also section on Collocates.

The attribute values for gram/@type are a semi-closed list: this means that we will discuss and adopt additional values as demonstrated by examples from dictionaries that are encoded by members of our community.

If your dictionary has grammatical labels that do not fit into the above categories, do let us know by filing a ticket on GitHub.

2.3.3. Collocates

The TEI Guidelines define a specific element <colloc> (collocate) for marking up "any sequence of words that co-occur with the headword with significant frequency." The prototypical example from the Guidelines is this: 
    <entry>
+</entry>

Notes:

  1. Grammatical properties of the entry as a whole should not be specified in entry/form[@type="lemma"]/gramGrp.
  2. entry/form/gramGrp should be used only if a particular form (a dialectal variant, for instance) has different grammatical properties from the lemma; or to indicate the grammatical properties of the inflected form which clearly deviate from the lemma.
  3. For entries which group grammatical homonyms inside single entries (e.g. in English dictionaries which do not have separate entries for conversion pairs of nouns and verbs, such as run or aid see the discussion under Nested entries vs. multiple-senses.

3.3.2. Typology of gram

The TEI Guidelines define:

  • seven specific elements which can be used to mark up particular grammatical properties:<case>, <gen> (for gender), <iType> (for inflection type), <mood>, <number>, <per> (for person) and <tns> (for tense); and
  • one general element (<gram>) which can be used to encode different kinds of grammatical properties.

The Guidelines themselves do not explain the reasoning behind having two different mechanisms for encoding the same kind of information. The two mechanisms are treated as fully interchangeable: see, for instance, the first two examples in Section 9.3.2.

While it is perfectly understandable why marking up grammatical information using a number of specific, granular elements can be considered desirable, the current situation is less than perfect:

  • if both <pos>prep</pos> and <gram type="pos">prep</gram> are possible, and if both mean exactly the same thing, the choice about how to encode grammatical information will always be partially arbitrary;
  • the specific grammatical elements in TEI cover some important grammatical categories, but are certainly not exhaustive: for instance, Slavic dictionaries will, as a rule, indicate aspect (imperfective or perfective) as the defining grammatical property of verbs, yet there is no specific element for: <aspect> in TEI.
  • if there are no specific elements for every possible grammatical category, mixing specific and general elements (for instance <pos>v.</pos> and <gram type="aspect">imperf.</gram> within the same entry and/or dictionary will most likely further complicate data processing and data interoperability.

Considering the goals of TEI Lex-0 to serve as a common baseline and target format for transforming and comparing different lexical resources, we have decided to do away with the specific elements for grammatical properties. Instead, we recommend the use of typed <gram> elements. This is a decision that wasn't taken lightly and one which solicited a great deal of discussion. It goes without saying that TEI itself will continue to support both mechanisms and that an XSLT transformation from <pos>prep</pos> to <gram type="pos">prep</gram> for those who want to convert their dictionaries to TEI Lex-0 would be easily accomplished.

The following table shows a mapping between the specific TEI elements and the typed <gram> elements in TEI Lex-0:

Mapping between specific elements in TEI and the generalized mechanism in TEI Lex-0
TEITEI Lex-0
<pos>n.</pos><gram type="pos">n.</gram>
<case>acc.</case><gram type="case">acc.</gram>
<gen>f.</gen><gram type="gender">f.</gram>
<iType>7</iType><gram type="inflectionType">7</gram>
<mood>indic.</mood><gram type="mood">indic.</gram>
<number>sg.</number><gram type="number">sg.</gram>
<per>3rd</per><gram type="person">3rd</gram>
<tns>aorist</tns><gram type="tense">aorist</gram>
-<gram type="aspect">imperf.</gram>
-<gram type="transitivity">intr.</gram>

Note: See also section on Collocates.

The attribute values for gram/@type are a semi-closed list: this means that we will discuss and adopt additional values as demonstrated by examples from dictionaries that are encoded by members of our community.

If your dictionary has grammatical labels that do not fit into the above categories, do let us know by filing a ticket on GitHub.

3.3.3. Collocates

The TEI Guidelines define a specific element <colloc> (collocate) for marking up "any sequence of words that co-occur with the headword with significant frequency." The prototypical example from the Guidelines is this: 
    <entry>
   <form>
      <orth>médire</orth>
   </form>
   <gramGrp>
      <colloc>de</colloc>
   </gramGrp>
-</entry>
In line with the simplification of the elements used to describe grammatical properties in dictionaries, TEI Lex-0 recommends the use of <gram type="collocate"></gram> to encode these phenomena, i.e.: 
    <entry xml:lang="fr" xml:id="DDLF.médire">
+</entry>
In line with the simplification of the elements used to describe grammatical properties in dictionaries, TEI Lex-0 recommends the use of <gram type="collocate"></gram> to encode these phenomena, i.e.: 
    <entry xml:lang="fr" xml:id="DDLF.médire">
   <form type="lemma">
      <orth>médire</orth>
   </form>
   <gramGrp>
      <gram type="collocate">de</gram>
   </gramGrp>
-</entry>
In addition to marking up "sequences of words", gram/@type="collocate" is also used in TEI Lex-0 for encoding various types of grammatical relations (differently referred to in the literature as valency, rection, dependency etc.): 
    <gramGrp>
+</entry>
In addition to marking up "sequences of words", gram/@type="collocate" is also used in TEI Lex-0 for encoding various types of grammatical relations (differently referred to in the literature as valency, rection, dependency etc.): 
    <gramGrp>
   <gram type="collocate">[+ conj.]</gram>
-</gramGrp>

2.4. Deprecated entry-like elements

The current TEI Guidelines define five different container elements that may serve as grouping devices for entry-level lexical information:

  • <entry>: contains a single structured entry in any kind of lexical resource, such as a dictionary or lexicon.
  • <entryFree>: contains a single unstructured entry in any kind of lexical resource, such as a dictionary or lexicon.
  • <superEntry>: groups a sequence of entries within any kind of lexical resource, such as a dictionary or lexicon which function as a single unit, for example a set of homographs.
  • <re>: (related entry) contains a dictionary entry for a lexical item related to the headword, such as a compound phrase or derived form, embedded inside a larger entry.
  • <hom>: (homograph) groups information relating to one homograph within an entry

These five elements can be used to distinguish different types of entries along two conceptual axes:

  • Structured vs. unstructured entries, i. e. entries that can readily be represented (in the lexical view) in the spirit of the TEI Guideline’s Dictionary Chapter (<entry>, <re>) vs. entries that for some reason violate the generic content model of <entry> or <re> and thus have to be represented more freely (<entryFree>). A third category in this respect are entries that exhibit a highly reduced amount of lexical content while this content is still of essentially entry-like nature (<superEntry>).
  • Containing vs. contained entries: entries may contain additional lexical information that can be conceived as an additional dictionary entry in its own right. Specifically, <superEntry> may contain <entry>, and <entry> in turn may contain <re> to represent the embedding of lexical entries on three distinct levels. Due to <re> being allowed to be used recursively, the number of levels for representing entry-like lexical information inside other such blocks is effectively unrestricted. At the same time, two different mechanism can be used to create homographic entries: <superEntry> containing multiple <entry> elements; or <entry> containing multiple <hom> elements.

2.4.1. hom

Making a clear difference between a situation where an entry has to be split into two or more homonyms and one where these differences correspond to a semantic alternation is lexicographically difficult. Still, the main danger in keeping both possibilities in the representation of a lexical entry in a digital lexicon is to introduce a systematic structural ambiguity as to where the appropriate information is to be found. We thus deprecate <hom> altogether in the present recommendation and have this element be replaced by the nested <entry> construct. For instance, the following example from the TEI Guidelines:

    <entry>
+</gramGrp>

3.4. Deprecated entry-like elements

The current TEI Guidelines define five different container elements that may serve as grouping devices for entry-level lexical information:

  • <entry>: contains a single structured entry in any kind of lexical resource, such as a dictionary or lexicon.
  • <entryFree>: contains a single unstructured entry in any kind of lexical resource, such as a dictionary or lexicon.
  • <superEntry>: groups a sequence of entries within any kind of lexical resource, such as a dictionary or lexicon which function as a single unit, for example a set of homographs.
  • <re>: (related entry) contains a dictionary entry for a lexical item related to the headword, such as a compound phrase or derived form, embedded inside a larger entry.
  • <hom>: (homograph) groups information relating to one homograph within an entry

These five elements can be used to distinguish different types of entries along two conceptual axes:

  • Structured vs. unstructured entries, i. e. entries that can readily be represented (in the lexical view) in the spirit of the TEI Guideline’s Dictionary Chapter (<entry>, <re>) vs. entries that for some reason violate the generic content model of <entry> or <re> and thus have to be represented more freely (<entryFree>). A third category in this respect are entries that exhibit a highly reduced amount of lexical content while this content is still of essentially entry-like nature (<superEntry>).
  • Containing vs. contained entries: entries may contain additional lexical information that can be conceived as an additional dictionary entry in its own right. Specifically, <superEntry> may contain <entry>, and <entry> in turn may contain <re> to represent the embedding of lexical entries on three distinct levels. Due to <re> being allowed to be used recursively, the number of levels for representing entry-like lexical information inside other such blocks is effectively unrestricted. At the same time, two different mechanism can be used to create homographic entries: <superEntry> containing multiple <entry> elements; or <entry> containing multiple <hom> elements.

3.4.1. hom

Making a clear difference between a situation where an entry has to be split into two or more homonyms and one where these differences correspond to a semantic alternation is lexicographically difficult. Still, the main danger in keeping both possibilities in the representation of a lexical entry in a digital lexicon is to introduce a systematic structural ambiguity as to where the appropriate information is to be found. We thus deprecate <hom> altogether in the present recommendation and have this element be replaced by the nested <entry> construct. For instance, the following example from the TEI Guidelines:

    <entry>
   <form>
      <orth>bray</orth>
      <pron>breI</pron>
@@ -108,7 +179,7 @@
         <def>make a cry or sound of this kind.</def>
      </sense>
   </hom>
-</entry>

would in TEI Lex-0 be represented as:

    <entry type="mainEntry" xml:id="bray" xml:lang="en">
+</entry>

would in TEI Lex-0 be represented as:

    <entry type="mainEntry" xml:id="bray" xml:lang="en">
   <form type="lemma">
      <orth>bray</orth>
      <pron>brel</pron>
@@ -136,7 +207,7 @@
      </sense>
      <pc>.</pc>
   </entry>
-</entry>

2.4.2. superEntry

By making <entry> recursive, TEI Lex-0 has eliminated the need for grouping entries with <superEntry>.

This is especially important for traditional root-based dictionaries, which start with the root as the main headword, followed by full-fledged lexicographic entries of derived headwords.

    <entry type="wordFamily" xml:lang="ar" xml:id="syj">
+</entry>

3.4.2. superEntry

By making <entry> recursive, TEI Lex-0 has eliminated the need for grouping entries with <superEntry>.

This is especially important for traditional root-based dictionaries, which start with the root as the main headword, followed by full-fledged lexicographic entries of derived headwords.

    <entry type="wordFamily" xml:lang="ar" xml:id="syj">
   <form type="root">
      <orth>سيج</orth>
   </form>
@@ -203,7 +274,7 @@
         <def>نوع من السمك</def>
      </sense>
   </entry>
-</entry>Almonjid (2014) 
    <entry type="wordFamily" xml:lang="ar" xml:id="shahama">
+</entry>Almonjid (2014) 
    <entry type="wordFamily" xml:lang="ar" xml:id="shahama">
   <form type="root">
      <orth>شهم</orth>
   </form>
@@ -350,7 +421,7 @@
         </sense>
      </entry>
   </entry>
-</entry>Almonjid (2014) 

See also Section on grammatical properties in senses.

3. Forms

The current TEI Guidelines allows for an extremely wide range of encoding possibilities for written and spoken forms. In the discussion which follows, we suggest ways in which the elements, in particular <form>, can be constrained. We give examples of use types not covered by the Guidelines, and propose some extensions.

3.1. A note on inheritance

We assume that in order to determine the complete properties of an element inside the entry tree, the principle of default inheritance applies, e.g. grammatical properties of a form are determined by collecting the sibling <gramGrp> of the ancestor-or-self of the focus element, where the superordinate grammatical properties can be overwritten by the lower-level properties. This principle is relatively straightforward in the case of grammatical properties, but more complex for the word paradigm, esp. in cases of variant forms. For more information c.f. Ide et al. (2000) and Erjavec et al. (2000).

3.2. Lemmas

The form element should always be qualified by its type. The lemma (i.e. headword) form should be encoded as form[@type="lemma"].

If it is necessary to specify the grammatical properties of the lemma form itself (as opposed to the grammatical properties of the entry), this is described by entry/form[@type="lemma"]/gramGrp.

3.3. Inflected forms

Dictionaries often include additional forms next to the lemma. In English, these are used to specify irregular forms, such as “corpus / corpora” or “take / took”, whereas in inflectionally rich languages they are often used to help the user determine the correct paradigm of the word.

Such inflected forms should be encoded in entry/form[@type="inflected"], e.g.:

See also Section on grammatical properties in senses.

4. Forms

The current TEI Guidelines allows for an extremely wide range of encoding possibilities for written and spoken forms. In the discussion which follows, we suggest ways in which the elements, in particular <form>, can be constrained. We give examples of use types not covered by the Guidelines, and propose some extensions.

4.1. A note on inheritance

We assume that in order to determine the complete properties of an element inside the entry tree, the principle of default inheritance applies, e.g. grammatical properties of a form are determined by collecting the sibling <gramGrp> of the ancestor-or-self of the focus element, where the superordinate grammatical properties can be overwritten by the lower-level properties. This principle is relatively straightforward in the case of grammatical properties, but more complex for the word paradigm, esp. in cases of variant forms. For more information c.f. Ide et al. (2000) and Erjavec et al. (2000).

4.2. Lemmas

The form element should always be qualified by its type. The lemma (i.e. headword) form should be encoded as form[@type="lemma"].

If it is necessary to specify the grammatical properties of the lemma form itself (as opposed to the grammatical properties of the entry), this is described by entry/form[@type="lemma"]/gramGrp.

4.3. Inflected forms

Dictionaries often include additional forms next to the lemma. In English, these are used to specify irregular forms, such as “corpus / corpora” or “take / took”, whereas in inflectionally rich languages they are often used to help the user determine the correct paradigm of the word.

Such inflected forms should be encoded in entry/form[@type="inflected"], e.g.:

    <entry xml:lang="en" xml:id="CH.go1">
   <form type="lemma">
      <orth>go</orth>
      <pron>gō</pron>
@@ -398,7 +469,7 @@
   </form>
   <pc>;</pc>
   <!--...-->
-</entry>Chambers (2011) 

Or take this example: abeceda, -y: in Czech, "-y" is a genitive singular suffix for feminine nouns. We can mark-up the grammatical properties of the suffix, while providing the full form of the noun as well:

    <entry type="mainEntry" xml:lang="cz" xml:id="en000008">
+</entry>Chambers (2011) 

Or take this example: abeceda, -y: in Czech, "-y" is a genitive singular suffix for feminine nouns. We can mark-up the grammatical properties of the suffix, while providing the full form of the noun as well:

    <entry type="mainEntry" xml:lang="cz" xml:id="en000008">
   <form type="lemma" xml:id="en000008.hw1">
      <orth>abeceda</orth>
   </form>
@@ -412,7 +483,7 @@
      <orth extent="suffix" expand="abecedy">-y</orth>
   </form>
   <!--...-->
-</entry>

3.4. Paradigms

When several inflected forms can be present next to the lemma, these can be embedded into entry/form[@type="paradigm"]. The decision on whether to use this extra element depends on the particular dictionary and language.

The other use case for paradigms is when the full inflectional paradigm of the word is embedded in the entry, i.e. when the dictionary also includes all the word-forms of the words covered, which can be useful for example in machine processing.

An entry may contain several paradigms, e.g. a partial one for humans and a full one for machines, or one for each stem of a verb. Each paradigm type should be distinguished by the subtype attribute.

    <entry xml:id="perder" xml:lang="es">
+</entry>

4.4. Paradigms

When several inflected forms can be present next to the lemma, these can be embedded into entry/form[@type="paradigm"]. The decision on whether to use this extra element depends on the particular dictionary and language.

The other use case for paradigms is when the full inflectional paradigm of the word is embedded in the entry, i.e. when the dictionary also includes all the word-forms of the words covered, which can be useful for example in machine processing.

An entry may contain several paradigms, e.g. a partial one for humans and a full one for machines, or one for each stem of a verb. Each paradigm type should be distinguished by the subtype attribute.

    <entry xml:id="perder" xml:lang="es">
   <form type="lemma">
      <orth>perder</orth>
   </form>
@@ -449,7 +520,7 @@
      </gramGrp>
   </form>
   <!--... -->
-</entry>

3.5. Variants

The representation of variation within a form is highly dependant upon the specifics of the features of the variation and the way in which they vary. However, as a general principle, variation may be encoded as form[@type="variant"] and embedded within the parent element for which a subordinate feature exhibits variation.

3.5.1. Orthographic variation

Several kinds of orthographic variation may be distinguished. Below, we present some of the options with the corresponding examples.

Spelling variation due to change in language’s orthography convention:

    <entry xml:id="Flussschifffahrt" xml:lang="de" type="compound">
+</entry>

4.5. Variants

The representation of variation within a form is highly dependant upon the specifics of the features of the variation and the way in which they vary. However, as a general principle, variation may be encoded as form[@type="variant"] and embedded within the parent element for which a subordinate feature exhibits variation.

4.5.1. Orthographic variation

Several kinds of orthographic variation may be distinguished. Below, we present some of the options with the corresponding examples.

Spelling variation due to change in language’s orthography convention:

    <entry xml:id="Flussschifffahrt" xml:lang="de" type="compound">
   <form type="lemma">
      <orth type="segmeted">
         <seg>Fluss</seg>
@@ -474,7 +545,7 @@
      </gramGrp>
   </form>
   <!--...-->
-</entry>

The following example is from American English in which due to the lack of official conventions for transliteration of Arabic orthography to the English (Latin) script, the initial vowel in the surname ‘Osama Bin Laden’ varies between ‘O’ and ‘U’:

    <entry xml:id="Osama" xml:lang="en">
+</entry>

The following example is from American English in which due to the lack of official conventions for transliteration of Arabic orthography to the English (Latin) script, the initial vowel in the surname ‘Osama Bin Laden’ varies between ‘O’ and ‘U’:

    <entry xml:id="Osama" xml:lang="en">
   <form type="lemma">
      <pron notation="ipa">
         <seg xml:id="ousma" corresp="#usma #osma">ow."sa.ma</seg>
@@ -497,7 +568,7 @@
      </form>
   </form>
   <!--...-->
-</entry>

3.5.2. Phonetic variation

In this example, the entry contains the single orthographic form as a direct child of the lemma and phonetic transcriptions of the two roughly equally used variant pronunciations of the word 'caramel' from American English.

    <entry xml:id="caramel-en" xml:lang="en-US">
+</entry>

4.5.2. Phonetic variation

In this example, the entry contains the single orthographic form as a direct child of the lemma and phonetic transcriptions of the two roughly equally used variant pronunciations of the word 'caramel' from American English.

    <entry xml:id="caramel-en" xml:lang="en-US">
   <form type="lemma">
      <orth>caramel</orth>
      <form type="variant">
@@ -511,7 +582,7 @@
      <gram type="pos">noun</gram>
   </gramGrp>
   <!-- ... -->
-</entry>

    In the example above, one could have chosen to mark up two different pronunciations using two <pron> elements inside the form[@type="lemma"]. Considering, however, that each individual pronunciation could, in theory, be further qualified, for instance, by a <usg> note, indicating the geographic area in which the said pronunciation is used, TEI Lex-0 recommends that multiple variants, whether orthographic or orthoepic, be contained each in its own <form> element.

3.5.3. Regional or dialectal variation

In the following example from Mixtepec-Mixtec, there is variation in the form of the word for the city of Oaxaca between speakers from the village of Yucanany and the rest of the speakers. Since the Yucanany variety makes up only a small portion of the speakers of the language, this case of variation is represented as an embedded form[@type="variant"] within the lemma. Note the use of usg[@type="geographic"]/placeName to explicitly specify this feature in addition to the use of the private language subtag (@xml:lang="mix-x-YCNY") as per BCP 47.

    <entry xml:id="Oaxaca-MIX" xml:lang="mix" type="compound">
+</entry>

    In the example above, one could have chosen to mark up two different pronunciations using two <pron> elements inside the form[@type="lemma"]. Considering, however, that each individual pronunciation could, in theory, be further qualified, for instance, by a <usg> note, indicating the geographic area in which the said pronunciation is used, TEI Lex-0 recommends that multiple variants, whether orthographic or orthoepic, be contained each in its own <form> element.

4.5.3. Regional or dialectal variation

In the following example from Mixtepec-Mixtec, there is variation in the form of the word for the city of Oaxaca between speakers from the village of Yucanany and the rest of the speakers. Since the Yucanany variety makes up only a small portion of the speakers of the language, this case of variation is represented as an embedded form[@type="variant"] within the lemma. Note the use of usg[@type="geographic"]/placeName to explicitly specify this feature in addition to the use of the private language subtag (@xml:lang="mix-x-YCNY") as per BCP 47.

    <entry xml:id="Oaxaca-MIX" xml:lang="mix" type="compound">
   <form type="lemma">
      <orth>
         <seg>Ñuu</seg>
@@ -533,7 +604,7 @@
      <gram type="pos">locationNoun</gram>
   </gramGrp>
   <!--...-->
-</entry>

3.6. Multiword expressions

The Dictionary Chapter of the TEI Guidelines is very sparse when it comes to recommendations for encoding polylexical units. The only mention of the adjective “multi-word” appears in the definition of the element <term>: “contains a single-word, multi-word, or symbolic designation which is regarded as a technical term” but this is not relevant for the encoding of polylexical units in general-purpose dictionaries.

TEI includes an element <colloc> (collocate), which is defined as containing “any sequence of words that co-occur with the headword with significant frequency” but, in a different example, “colloc” is used as an attribute value for the element <usg> (usage). It is precisely this type of ambiguity that TEI Lex-0 is trying to resolve.

The TEI Guidelines recommend the use of <re> (related entry) to encode “related entries for direct derivatives or inflected forms of the entry word, or for compound words, phrases, collocations, and idioms containing the entry word” with barely any useful examples, or discussion of how to encode different types of polylexical units. TEI Lex-0, on the other hand, does not include <re>. In TEI Lex-0, <entry> was made recursive in order to account for nestable entry-like structures without the need to resort to <re>, a differently named element whose content model would be indistinguishable from <entry> itself. Eventually, the new content model of <entry>, which allows nesting, was adopted by TEI itself (Tasovac 2020).

TODO: explain different types of mwe's from a dict. model perspective refering to Tasovac 2020)

3.6.1. Collocations

TODO: explain "lexicographically transparent"

    <entry xml:id="DLPC.descalçar" xml:lang="pt">
+</entry>

4.6. Multiword expressions

The Dictionary Chapter of the TEI Guidelines is very sparse when it comes to recommendations for encoding polylexical units. The only mention of the adjective “multi-word” appears in the definition of the element <term>: “contains a single-word, multi-word, or symbolic designation which is regarded as a technical term” but this is not relevant for the encoding of polylexical units in general-purpose dictionaries.

TEI includes an element <colloc> (collocate), which is defined as containing “any sequence of words that co-occur with the headword with significant frequency” but, in a different example, “colloc” is used as an attribute value for the element <usg> (usage). It is precisely this type of ambiguity that TEI Lex-0 is trying to resolve.

The TEI Guidelines recommend the use of <re> (related entry) to encode “related entries for direct derivatives or inflected forms of the entry word, or for compound words, phrases, collocations, and idioms containing the entry word” with barely any useful examples, or discussion of how to encode different types of polylexical units. TEI Lex-0, on the other hand, does not include <re>. In TEI Lex-0, <entry> was made recursive in order to account for nestable entry-like structures without the need to resort to <re>, a differently named element whose content model would be indistinguishable from <entry> itself. Eventually, the new content model of <entry>, which allows nesting, was adopted by TEI itself (Tasovac 2020).

TODO: explain different types of mwe's from a dict. model perspective referring to Tasovac 2020)

4.6.1. Collocations

TODO: explain "lexicographically transparent"

    <entry xml:id="DLPC.descalçar" xml:lang="pt">
   <!--etc.-->
   <sense xml:id="DLPC.descalçar.1">
      <!--etc.-->
@@ -586,7 +657,7 @@
      </form>
      <pc>.</pc>
   </sense>
-</entry>DLPC (2001) 

3.6.2. Idiomatic expressions

TODO text ("lexicographically non-transparent")

    <entry xml:lang="pt" xml:id="DLPC.bombeiro" type="mainEntry">
+</entry>DLPC (2001) 

4.6.2. Idiomatic expressions

TODO text ("lexicographically non-transparent")

    <entry xml:lang="pt" xml:id="DLPC.bombeiro" type="mainEntry">
   <form type="lemma">
      <orth>bombeiro</orth>
   </form>
@@ -621,7 +692,7 @@
      </entry>
   </sense>
   <!--etc.-->
-</entry>DLPC (2001) 

4. Senses

4.1. General remarks

In the current TEI Dictionary Chapter, the content model of <entry> allows one to have sense-related information directly within <entry>. TEI Lex-0 proscribes a stricter use of these elements so that sense-related information is grouped within the <sense> element, in accordance with the underlying semasiological model implemented in the TEI Guidelines.

<sense> should be therefore considered mandatory for any dictionary entry that actually provides sense information for the headword. Further in this document, we consider some additional specific cases e.g. “referencing” entries (entries that simply point to other entries) and inflectional lexica (dictionaries that describe word forms only), where <sense> is not a mandatory child of <entry>.

As a consequence of making the use of <sense> more systematic within <entry>, we have seen (see section on <entry>) that some elements are no longer allowed as children of <entry>. We provide here a specific background for each of them:

  • <def> is clearly intended to provide a prose description of a meaning within a <sense> element and should not appear in any other context;
  • In the same way, it is recommended that <cit> be used exclusively as a child of <sense>, or when necessary within <dictScrap>;
  • The case of <hom> is peculiar since it provides a subordinate organization to an entry which is redundant in relation to what <sense> allows one to represent. <hom> is not allowed in TEI Lex-0.

Note: In the case one has to deal with information that does not fit a <sense>-based organization, for instance in the process of retro-digitizing an existing dictionary source, the use of <dictScrap> is recommended. Further step in the encoding of the lexical content may lead to a more precise encoding in a second phase.

In TEI Lex-0, <sense> has a mandatory xml:id.

4.2. Limiting contexts for def

In the current TEI Guidelines, <def> is allowed within the following elements:

TEI Lex-0 allows the use of <def> in <sense> only. All other existing contexts would be implemented by embedding <def> within a <sense>.

4.3. Glosses

4.3.1. Gloss vs. definition?

In the lexicographic literature, gloss is a rather amorphous category. Zgusta, in his classic Manual of Lexicography (1971), defines it as "any descriptive or explanatory note within the entry" which includes "short comments, explanatory remarks, semantic characteristics or qualifications" (270). Atkins and Rundell (2008) see the gloss as "a more informal explanation of the meaning of a multiword expression or example (or even part of one) in the entry,[...] chiefly used in monolingual dictionaries for learners, to help understanding" (209). While one could argue about the statement that this type of lexicographic construct is used "chiefly... in monolingual dictionaries for learners", it is certainly the case that glosses are expected to help users better understand or more easily locate the particular meaning of a word that they are looking up.

In other words, the prototypical gloss contextualizes and clarifies the meaning of the word. Take this example from Zgusta:
  1. fugitive (of persons)
  2. fugitive (verses)
Here, glosses are used to signal the meaning of fugitive: in the first sense "fugitive" refers to persons, and in the second example, to verses. In TEI Lex-0, this could be represented as: 
    <entry xml:id="ED.fugitive" xml:lang="en">
+</entry>DLPC (2001) 

5. Senses

5.1. General remarks

In the current TEI Dictionary Chapter, the content model of <entry> allows one to have sense-related information directly within <entry>. TEI Lex-0 proscribes a stricter use of these elements so that sense-related information is grouped within the <sense> element, in accordance with the underlying semasiological model implemented in the TEI Guidelines.

<sense> should be therefore considered mandatory for any dictionary entry that actually provides sense information for the headword. Further in this document, we consider some additional specific cases e.g. “referencing” entries (entries that simply point to other entries) and inflectional lexica (dictionaries that describe word forms only), where <sense> is not a mandatory child of <entry>.

As a consequence of making the use of <sense> more systematic within <entry>, we have seen (see section on <entry>) that some elements are no longer allowed as children of <entry>. We provide here a specific background for each of them:

  • <def> is clearly intended to provide a prose description of a meaning within a <sense> element and should not appear in any other context;
  • In the same way, it is recommended that <cit> be used exclusively as a child of <sense>, or when necessary within <dictScrap>;
  • The case of <hom> is peculiar since it provides a subordinate organization to an entry which is redundant in relation to what <sense> allows one to represent. <hom> is not allowed in TEI Lex-0.

Note: In the case one has to deal with information that does not fit a <sense>-based organization, for instance in the process of retro-digitizing an existing dictionary source, the use of <dictScrap> is recommended. Further step in the encoding of the lexical content may lead to a more precise encoding in a second phase.

In TEI Lex-0, <sense> has a mandatory xml:id.

5.2. Limiting contexts for def

In the current TEI Guidelines, <def> is allowed within the following elements:

TEI Lex-0 allows the use of <def> in <sense> only. All other existing contexts would be implemented by embedding <def> within a <sense>.

5.3. Glosses

5.3.1. Gloss vs. definition?

In the lexicographic literature, gloss is a rather amorphous category. Zgusta, in his classic Manual of Lexicography (1971), defines it as "any descriptive or explanatory note within the entry" which includes "short comments, explanatory remarks, semantic characteristics or qualifications" (270). Atkins and Rundell (2008) see the gloss as "a more informal explanation of the meaning of a multiword expression or example (or even part of one) in the entry,[...] chiefly used in monolingual dictionaries for learners, to help understanding" (209). While one could argue about the statement that this type of lexicographic construct is used "chiefly... in monolingual dictionaries for learners", it is certainly the case that glosses are expected to help users better understand or more easily locate the particular meaning of a word that they are looking up.

In other words, the prototypical gloss contextualizes and clarifies the meaning of the word. Take this example from Zgusta:
  1. fugitive (of persons)
  2. fugitive (verses)
Here, glosses are used to signal the meaning of fugitive: in the first sense "fugitive" refers to persons, and in the second example, to verses. In TEI Lex-0, this could be represented as: 
    <entry xml:id="ED.fugitive" xml:lang="en">
   <form type="lemma">
      <orth>fugitive</orth>
   </form>
@@ -631,7 +702,7 @@
   <sense n="2">
      <gloss>(verses)</gloss>
   </sense>
-</entry>
Glosses, however, are not definitions: one can imagine the above two senses to contain proper lexicographic definitions as well: 
    <entry xml:id="ED.fugitive" xml:lang="en">
+</entry>
Glosses, however, are not definitions: one can imagine the above two senses to contain proper lexicographic definitions as well: 
    <entry xml:id="ED.fugitive" xml:lang="en">
   <form type="lemma">
      <orth>fugitive</orth>
   </form>
@@ -643,7 +714,7 @@
      <gloss>(verses)</gloss>
      <def>concerned or dealing with subjects of passing interest; ephemeral, occasional.</def>
   </sense>
-</entry>
Zgusta notes a certain amount of overlapping between glosses and other categories, "the most important probably being that of the examples" (ibid.) This is especially evident in sense no. 2 above where "fugitive verses" or "~ verses" could have been used as an example. The absence of the lemma or lemma reference in "(verses)" as well as the brackets are a clear indicator that the whole construct is not to be read as an example, but rather as a semantic signpost for the given sense.

On sense-distinguishing grammatical properties, see section Grammatical properties in senses

4.3.2. Glossing examples

Semantic glosses can occur at different levels of the entry hierarchy. In the previous section, we saw examples in which glosses were used as a kind of semantic shorthand for an individual sense. They can, however, be used to further qualify individual examples in the entry. Take, for instance, this entry from the Longman Dictionary of Contemporary English (2003):

living /... / adj 1 alive now [...] | The sun affects all living things (=people, animals, and plants). | A living language (=one that people still use) [….]

In TEI Lex-0, this entry would be represented as:

    <entry xml:id="LDOCE.living" xml:lang="en" type="mainEntry">
+</entry>
Zgusta notes a certain amount of overlapping between glosses and other categories, "the most important probably being that of the examples" (ibid.) This is especially evident in sense no. 2 above where "fugitive verses" or "~ verses" could have been used as an example. The absence of the lemma or lemma reference in "(verses)" as well as the brackets are a clear indicator that the whole construct is not to be read as an example, but rather as a semantic signpost for the given sense.

On sense-distinguishing grammatical properties, see section Grammatical properties in senses

5.3.2. Glossing examples

Semantic glosses can occur at different levels of the entry hierarchy. In the previous section, we saw examples in which glosses were used as a kind of semantic shorthand for an individual sense. They can, however, be used to further qualify individual examples in the entry. Take, for instance, this entry from the Longman Dictionary of Contemporary English (2003):

living /... / adj 1 alive now [...] | The sun affects all living things (=people, animals, and plants). | A living language (=one that people still use) [….]

In TEI Lex-0, this entry would be represented as:

    <entry xml:id="LDOCE.living" xml:lang="en" type="mainEntry">
   <form type="lemma">
      <orth>living</orth>
   </form>
@@ -668,7 +739,7 @@
         </quote>
      </cit>
   </sense>
-</entry>Gadsby (ed.) (2003) 

4.4. Grammatical properties

In some dictionaries, individual dictionary senses may be associated with grammatical properties, such as part of speech or gender, that differ from the rest of the entry: for instance, a particular sense of a countable noun may be used only in plural. In such cases, <gramGrp> will be naturally placed inside the given <sense>:

Consider, for instance, the second sense of this entry:

5.4. Grammatical properties

In some dictionaries, individual dictionary senses may be associated with grammatical properties, such as part of speech or gender, that differ from the rest of the entry: for instance, a particular sense of a countable noun may be used only in plural. In such cases, <gramGrp> will be naturally placed inside the given <sense>:

Consider, for instance, the second sense of this entry:

    <sense xml:id="DLPC.antepassado_b_2" n="2" xml:lang="pt">
   <gramGrp>
      <gram type="number">pl.</gram>
   </gramGrp>
@@ -685,7 +756,7 @@
   <cit type="example">
      <quote>Culto dos antepassados.</quote>
   </cit>
-</sense>DLPC (2001) 

4.4.1. Grammatical glosses?

Zgusta also uses "gloss" to describe "grammatical indications in the broadest sense of the word" (1971, 240), using an example familiar from Latin (and many other) dictionaries:

  1. petere aliquid ab aliquo [to ask for something from somebody]
  2. petere Romam [to rush to Rome]

In theory, one could choose to encode such phenomena using <gloss>, but TEI Lex-0 recommends a clear separation of roles: <gloss> should be used for semantic or pragmatic information, whereas grammatical information should be encoded using the familiar gramGrp/gram constructs:

    <sense n="1" xml:id="LD.peto.1">
+</sense>DLPC (2001) 

5.4.1. Grammatical glosses?

Zgusta also uses "gloss" to describe "grammatical indications in the broadest sense of the word" (1971, 240), using an example familiar from Latin (and many other) dictionaries:

  1. petere aliquid ab aliquo [to ask for something from somebody]
  2. petere Romam [to rush to Rome]

In theory, one could choose to encode such phenomena using <gloss>, but TEI Lex-0 recommends a clear separation of roles: <gloss> should be used for semantic or pragmatic information, whereas grammatical information should be encoded using the familiar gramGrp/gram constructs:

    <sense n="1" xml:id="LD.peto.1">
   <gramGrp>
      <gram type="rection">aliquid ab aliquo</gram>
   </gramGrp>
@@ -694,7 +765,7 @@
   <gramGrp>
      <gram type="rection">Romam</gram>
   </gramGrp>
-</sense>

Here, too, it is important to note the possibility of ambiguity: unlike "petere aliquid ab aliquo", "petere Romam" could be interpreted as an example. The decision on such ambiguous cases should never be taken in isolation: editors of a digital edition need to consider the conventions of the dictionary as a whole before advising encoders on how to mark up such ambiguous cases.

4.4.2. Nested entries vs. multiple senses

While TEI Lex-0 has been created to simplify the choices available for encoding various lexicographic components, certain levels of ambiguity remain, often due to the highly condensed nature of dictionary content.

Consider, for instance, this entry:

Is this an entry with two senses? Or are these two entries that were on the account of typographic density merged into one?

The answer is as much in the eyes of the beholder, as it is in the eyes of the lexicographers behind the dictionary that the entry stems from, in this case The Chambers Dictionary. Both the encoder and lexicographers, however, are influenced by lexicographic and linguistic traditions in which they operate. For an overview of the homonymy-polysemy dilemma, see, for instance, Zöfgen 1989.

It can't be stressed enough that the goal of dictionary encoding is not to resolve linguistic disputes or evaluate lexicographic traditions but rather to create consistent, if abstracted, representations of lexicographic architectures.

So, what can we do in this particular case? Should we encode gash as an entry consisting of senses, each with a different part of speech, like this:

    <entry xml:id="CHDOEL.gash2" xml:lang="en">
+</sense>

Here, too, it is important to note the possibility of ambiguity: unlike "petere aliquid ab aliquo", "petere Romam" could be interpreted as an example. The decision on such ambiguous cases should never be taken in isolation: editors of a digital edition need to consider the conventions of the dictionary as a whole before advising encoders on how to mark up such ambiguous cases.

5.4.2. Nested entries vs. multiple senses

While TEI Lex-0 has been created to simplify the choices available for encoding various lexicographic components, certain levels of ambiguity remain, often due to the highly condensed nature of dictionary content.

Consider, for instance, this entry:

Is this an entry with two senses? Or are these two entries that were on the account of typographic density merged into one?

The answer is as much in the eyes of the beholder, as it is in the eyes of the lexicographers behind the dictionary that the entry stems from, in this case The Chambers Dictionary. Both the encoder and lexicographers, however, are influenced by lexicographic and linguistic traditions in which they operate. For an overview of the homonymy-polysemy dilemma, see, for instance, Zöfgen 1989.

It can't be stressed enough that the goal of dictionary encoding is not to resolve linguistic disputes or evaluate lexicographic traditions but rather to create consistent, if abstracted, representations of lexicographic architectures.

So, what can we do in this particular case? Should we encode gash as an entry consisting of senses, each with a different part of speech, like this:

    <entry xml:id="CHDOEL.gash2" xml:lang="en">
   <!--this, as we'll explain later, is valid but not the preferred encoding-->
   <form type="lemma">
      <orth>gash</orth>
@@ -724,7 +795,7 @@
      <def>rubbish, waste</def>
      <pc>.</pc>
   </sense>
-</entry>

This is surely valid TEI Lex-0. There is conceptually nothing wrong with this encoding: it adequately represents the structure implied by the source text.

We should, however, try to look at the issue at hand from a broader, comparative, perspective.

  • In the Portuguese polysemous entry antepassado above, we had a case in which one particular sense (used in plural only) deviated from the other senses (which are used in both singular and plural). Since the senses were numbered in the original, there was never any doubt about how we would encode this. It was clear from the outset:
    • that the semantic information in that entry was grouped by a construct called <sense>;
    • that senses inherited grammatical properties from the entry as a whole (i.e. entry/gramGrp);
    • that, implicitly, we could assume that each sense can be used with the noun in both singular and plural; and
    • that the plural-only sense was grammatically exceptional, hence entry/sense/gramGrp/).
  • The English example is different: gash as a verb and as a noun are grammatical homonyms. If we encode them, as we did above, as two senses within one entry, we end up with an entry in which there is no inheritance (of grammatical properties) and only exceptions (at each sense-level).

Because TEI Lex-0 is aimed at creating a baseline encoding to facilitate data exchange and comparison between different dictionaries, we, therefore, recommend to encode grammatical homonyms in TEI Lex-0 as nested entries and to use <gramGrp> in <sense> constructs to mark up sense-specific deviations from the rule of grammatical inheritance.

For that reason, our preferred encoding of gash as a verb and a noun would be:

    <entry xml:id="CH.gash2" xml:lang="en">
+</entry>

This is surely valid TEI Lex-0. There is conceptually nothing wrong with this encoding: it adequately represents the structure implied by the source text.

We should, however, try to look at the issue at hand from a broader, comparative, perspective.

  • In the Portuguese polysemous entry antepassado above, we had a case in which one particular sense (used in plural only) deviated from the other senses (which are used in both singular and plural). Since the senses were numbered in the original, there was never any doubt about how we would encode this. It was clear from the outset:
    • that the semantic information in that entry was grouped by a construct called <sense>;
    • that senses inherited grammatical properties from the entry as a whole (i.e. entry/gramGrp);
    • that, implicitly, we could assume that each sense can be used with the noun in both singular and plural; and
    • that the plural-only sense was grammatically exceptional, hence entry/sense/gramGrp/).
  • The English example is different: gash as a verb and as a noun are grammatical homonyms. If we encode them, as we did above, as two senses within one entry, we end up with an entry in which there is no inheritance (of grammatical properties) and only exceptions (at each sense-level).

Because TEI Lex-0 is aimed at creating a baseline encoding to facilitate data exchange and comparison between different dictionaries, we, therefore, recommend to encode grammatical homonyms in TEI Lex-0 as nested entries and to use <gramGrp> in <sense> constructs to mark up sense-specific deviations from the rule of grammatical inheritance.

For that reason, our preferred encoding of gash as a verb and a noun would be:

    <entry xml:id="CH.gash2" xml:lang="en">
   <form type="lemma">
      <orth>gash</orth>
      <pron>gash</pron>
@@ -757,7 +828,7 @@
         <pc>.</pc>
      </sense>
   </entry>
-</entry>

For an example in which grammatical homonyms have themselves multiple senses, one of which is grammatically constrained, see, for instance: 

    <entry xml:id="ED.aid" xml:lang="en">
+</entry>

For an example in which grammatical homonyms have themselves multiple senses, one of which is grammatically constrained, see, for instance: 

    <entry xml:id="ED.aid" xml:lang="en">
   <form type="lemma">
      <orth>aid</orth>
      <pron>/ed/</pron>
@@ -822,7 +893,7 @@
         <def>to help someone</def>
      </sense>
   </entry>
-</entry>

5. Translations

5.1. Translation equivalents

TEI Guidelines:

    <entry>
+</entry>

6. Translations

6.1. Translation equivalents

TEI Guidelines:

    <entry>
   <form>
      <orth>horrifier</orth>
   </form>
@@ -838,7 +909,7 @@
         <quote>she was horrified at the expense.</quote>
      </cit>
   </cit>
-</entry>

TEI Lex-0:

    <entry xml:id="horrifier" type="mainEntry" xml:lang="fr">
+</entry>

TEI Lex-0:

    <entry xml:id="horrifier" type="mainEntry" xml:lang="fr">
   <form type="lemma">
      <orth>horrifier</orth>
   </form>
@@ -858,7 +929,7 @@
         </cit>
      </cit>
   </sense>
-</entry>
    <entry type="mainEntry" xml:lang="en" xml:id="aid">
+</entry>
    <entry type="mainEntry" xml:lang="en" xml:id="aid">
   <form type="lemma">
      <orth>Aid</orth>
   </form>
@@ -1013,7 +1084,7 @@
         </cit>
      </sense>
   </entry>
-</entry>

6. Cross-references

6.1. General remarks

The current TEI Guidelines provide several mechanisms by means of which one item of lexical information can refer to another, e.g.:

  • <gloss> for the provision of simple (non refined) translation equivalents of the head word
  • <usg type="synonym"/> for synonym references
  • <cit type="translation"><quote><!--...--></quote></cit> for translation equivalents in bilingual or translation dictionaries
  • <oRef> and <pRef> for the resolution of “~" headword placeholders in quotations and other dictionary text
  • <xr> and <ref> as a general cross-referencing mechanism
  • <ptr/> as a pointer to another location
  • <link/> element
  • <mentioned/> in the etymology section
  • <term/> for mentions of technical terms

In keeping with the approach of the TEI Lex-0, and considering that links/relations between lexical data elements are an essential part of the core lexical data model rather than mere convenience pointers for dictionary users, we need a more unified and more constrained mechanism for lexical references, whether they point to an existing lexical entity in some dictionary or lexicon, or in a more general way to lexical objects without a target reference.

The proposed mechanism has the following properties

  1. It applies only to references with a clear linguistic meaning.
  2. The number of arbitrary (or context-dependent) choices for the encoder is minimal; the semantics of the reference should not depend on context
  3. The relation between representing dictionary content and the underlying/implied lexical data model should be as transparent as possible
  4. No drastic changes to the TEI Guidelines are needed.

In the following section, we first present the recommended encoding, and then elicit how existing alternatives can be replaced accordingly.

6.2. xr vs. ref

In TEI Lex-0, we use <ref> as the general element for a lexical reference and <xr> as the enclosing element that groups all information related to this reference, including explicit labels such as "Syn.", "Cf.", "See also" etc. The reference may be internal to a dictionary or pointing to an external source, even when the actual target lexical object is not explicitly known. In the latter case, <ref> can be used without an explicit pointing attribute. Furthermore, the intended target of the reference can be a full entry, but, sometimes, also a specific sense.

For all such uses, the following attributes may be used on <xr> and <ref>:

  • type is a mandatory attribute on <xr> for a lexical reference. Its default value is "related". This attribute can be used to indicate the lexical relation between the headword of the entry and the object referred to (see next section)
  • ref/@type is required; it indicates the target object category (entry, sense); the type attribute on <ref> is also needed to distinguish lexicographic from bibliographic references..
  • xml:lang on <xr> is required when <ref> contains an explicit lexical form in a language which is different from the source language
  • ref/@target to point to the URI of a lexical object. The value of this attribute is a machine-readable link to your cross-reference.
  • ref/@notation indicates, like we currently do on <orth> or <pron>, the notation used for the explicit lexical form, where applicable

Explicit dictionary labels which indicate the type of relationship between the current lexical item and the cross-reference should be encoded as <lbl> inside of <xr>.

6.2.1. Values of ref/@target

  • If the reference has no explicit target, no target is used.
  • As per TEI pointing mechanisms, the value of target must be an URI reference.
  • For internal references (references to the same dictionary), TEI Lex-0 enforces the use of explicit pointers to the xml:id of an element being pointed to, preceded by #. See Section "Pointing Locally" in the TEI Guidelines.
  • TEI pointers should not be used in TEI Lex-0.

6.3. Cross-reference typology

6.3.1. Related

The default reference to another lexical unit when no more granular information about the type of relationship is available.

In TEI Lex-0, cross-references are by default enoded as <xr type="related"></xr>.

    <entry xml:lang="nl" xml:id="borcht">
+</entry>

7. Cross-references

7.1. General remarks

The current TEI Guidelines provide several mechanisms by means of which one item of lexical information can refer to another, e.g.:

  • <gloss> for the provision of simple (non refined) translation equivalents of the head word
  • <usg type="synonym"/> for synonym references
  • <cit type="translation"><quote><!--...--></quote></cit> for translation equivalents in bilingual or translation dictionaries
  • <oRef> and <pRef> for the resolution of “~" headword placeholders in quotations and other dictionary text
  • <xr> and <ref> as a general cross-referencing mechanism
  • <ptr/> as a pointer to another location
  • <link/> element
  • <mentioned/> in the etymology section
  • <term/> for mentions of technical terms

In keeping with the approach of the TEI Lex-0, and considering that links/relations between lexical data elements are an essential part of the core lexical data model rather than mere convenience pointers for dictionary users, we need a more unified and more constrained mechanism for lexical references, whether they point to an existing lexical entity in some dictionary or lexicon, or in a more general way to lexical objects without a target reference.

The proposed mechanism has the following properties

  1. It applies only to references with a clear linguistic meaning.
  2. The number of arbitrary (or context-dependent) choices for the encoder is minimal; the semantics of the reference should not depend on context
  3. The relation between representing dictionary content and the underlying/implied lexical data model should be as transparent as possible
  4. No drastic changes to the TEI Guidelines are needed.

In the following section, we first present the recommended encoding, and then elicit how existing alternatives can be replaced accordingly.

7.2. xr vs. ref

In TEI Lex-0, we use <ref> as the general element for a lexical reference and <xr> as the enclosing element that groups all information related to this reference, including explicit labels such as "Syn.", "Cf.", "See also" etc. The reference may be internal to a dictionary or pointing to an external source, even when the actual target lexical object is not explicitly known. In the latter case, <ref> can be used without an explicit pointing attribute. Furthermore, the intended target of the reference can be a full entry, but, sometimes, also a specific sense.

For all such uses, the following attributes may be used on <xr> and <ref>:

  • type is a mandatory attribute on <xr> for a lexical reference. Its default value is "related". This attribute can be used to indicate the lexical relation between the headword of the entry and the object referred to (see next section)
  • ref/@type is required; it indicates the target object category (entry, sense); the type attribute on <ref> is also needed to distinguish lexicographic from bibliographic references..
  • xml:lang on <xr> is required when <ref> contains an explicit lexical form in a language which is different from the source language
  • ref/@target to point to the URI of a lexical object. The value of this attribute is a machine-readable link to your cross-reference.
  • ref/@notation indicates, like we currently do on <orth> or <pron>, the notation used for the explicit lexical form, where applicable

Explicit dictionary labels which indicate the type of relationship between the current lexical item and the cross-reference should be encoded as <lbl> inside of <xr>.

7.2.1. Values of ref/@target

  • If the reference has no explicit target, no target is used.
  • As per TEI pointing mechanisms, the value of target must be an URI reference.
  • For internal references (references to the same dictionary), TEI Lex-0 enforces the use of explicit pointers to the xml:id of an element being pointed to, preceded by #. See Section "Pointing Locally" in the TEI Guidelines.
  • TEI pointers should not be used in TEI Lex-0.

7.3. Cross-reference typology

7.3.1. Related

The default reference to another lexical unit when no more granular information about the type of relationship is available.

In TEI Lex-0, cross-references are by default encoded as <xr type="related"></xr>.

    <entry xml:lang="nl" xml:id="borcht">
   <form type="lemma">
      <orth>borcht</orth>
   </form>
@@ -1021,7 +1092,7 @@
      <lbl>Cf.</lbl>
      <ref target="#M012340" type="entry">burcht</ref>
   </xr>
-</entry>

6.3.2. Synonymy

Relation between two lexical units X and Y which are syntactically identical and have the property that any declarative sentence S containing X has equivalent truth conditions to another sentence S’ which is identical to S, except that X is replaced by Y. (Adapted from Cruse 1986.)

Synonymy is the linguistic parallel of the identity relation between classes. Synonyms differ in peripheral traits, related for example to stylistic, dialectal or diachronic variations.

Examples: [de] {Hund, Köter}, [en] {flashlight, torch}, [en] {glad, joyful, happy}, [en] {violin, fiddle} [en] He plays the violin very well/He plays the fiddle very well.

In TEI Lex-0, synonyms are encoded inside <xr type="synonymy"></xr>

    <entry xml:id="arbeitsunfähig" xml:lang="de" type="mainEntry">
+</entry>

7.3.2. Synonymy

Relation between two lexical units X and Y which are syntactically identical and have the property that any declarative sentence S containing X has equivalent truth conditions to another sentence S’ which is identical to S, except that X is replaced by Y. (Adapted from Cruse 1986.)

Synonymy is the linguistic parallel of the identity relation between classes. Synonyms differ in peripheral traits, related for example to stylistic, dialectal or diachronic variations.

Examples: [de] {Hund, Köter}, [en] {flashlight, torch}, [en] {glad, joyful, happy}, [en] {violin, fiddle} [en] He plays the violin very well/He plays the fiddle very well.

In TEI Lex-0, synonyms are encoded inside <xr type="synonymy"></xr>

    <entry xml:id="arbeitsunfähig" xml:lang="de" type="mainEntry">
   <form type="lemma">
      <orth>arbeitsunfähig</orth>
   </form>
@@ -1057,7 +1128,7 @@
      </xr>
      <pc>.</pc>
   </sense>
-</entry>Duden (2007) 

6.3.3. Hyperonymy

Relation between lexical heads X and Y characterised by the property that the sentence This is a(n) Y entails, but is not entailed by the sentence This is a(n) X. (Adapted from Cruse 1986.)

Hyperonymy is the converse of hyponymy.

Example: dog/animal (animal is a hypernym of dog)

In TEI Lex-0, hyperonyms are encoded inside <xr type="hyperonymy"></xr>.

    <entry xml:id="XY.dog" xml:lang="en" type="mainEntry">
+</entry>Duden (2007) 

7.3.3. Hyperonymy

Relation between lexical heads X and Y characterised by the property that the sentence This is a(n) Y entails, but is not entailed by the sentence This is a(n) X. (Adapted from Cruse 1986.)

Hyperonymy is the converse of hyponymy.

Example: dog/animal (animal is a hypernym of dog)

In TEI Lex-0, hyperonyms are encoded inside <xr type="hyperonymy"></xr>.

    <entry xml:id="XY.dog" xml:lang="en" type="mainEntry">
   <form type="lemma">
      <orth>dog</orth>
   </form>
@@ -1067,7 +1138,7 @@
   <xr type="hypernymy">
      <ref type="entry">mammal</ref>
   </xr>
-</entry>

6.3.4. Hyponymy

Relation between lexical units X and Y characterised by the property that the sentence This is a(n) X entails, but is not entailed by the sentence This is a(n) Y. (Adapted from Cruse 1986.)

Hyponymy and its converse hypernymy are the linguistic parallels of the relation of inclusion between two classes.

Examples: [en] animal/dog, red/scarlet, to kill/to murder

In TEI Lex-0, hyponyms are encoded inside <xr type="hyponymy"></xr>.

6.3.5. Meronymy

An inclusion relation between lexical heads X and Y which reflect a potential part-whole relation between their referents in discourse. (Adapted from Cruse 2011, p. 140)

Example: finger:hand (finger is said to be a meronym of hand, and hand is said to be the holonym of finger).

In TEI Lex-0, meornyms are encoded inside <xr type="meronymy"></xr>.

6.3.6. Antonymy

Relation between lexical units of opposite meaning.

In TEI Lex-0, antonyms are encoded inside <xr type="antonymy"></xr>.

    <sense xml:id="DLPC.antepassado_a_1" xml:lang="pt">
+</entry>

7.3.4. Hyponymy

Relation between lexical units X and Y characterised by the property that the sentence This is a(n) X entails, but is not entailed by the sentence This is a(n) Y. (Adapted from Cruse 1986.)

Hyponymy and its converse hypernymy are the linguistic parallels of the relation of inclusion between two classes.

Examples: [en] animal/dog, red/scarlet, to kill/to murder

In TEI Lex-0, hyponyms are encoded inside <xr type="hyponymy"></xr>.

7.3.5. Meronymy

An inclusion relation between lexical heads X and Y which reflect a potential part-whole relation between their referents in discourse. (Adapted from Cruse 2011, p. 140)

Example: finger:hand (finger is said to be a meronym of hand, and hand is said to be the holonym of finger).

In TEI Lex-0, meornyms are encoded inside <xr type="meronymy"></xr>.

7.3.6. Antonymy

Relation between lexical units of opposite meaning.

In TEI Lex-0, antonyms are encoded inside <xr type="antonymy"></xr>.

    <sense xml:id="DLPC.antepassado_a_1" xml:lang="pt">
   <def>Que pertence ou viveu numa época anterior.</def>
   <xr type="synonymy">
      <ref type="sense">antecessor</ref>
@@ -1081,7 +1152,7 @@
   <xr type="antonymy">
      <ref type="sense">sucessor</ref>
   </xr>
-</sense>

6.4. Cross-references in definitions

In TEI, it is impossible to have a cross-reference inside a definition, yet some dictionaries do use this mechanism. In TEI Lex-0, <xr> is allowed within <def>:

    <entry xml:id="VSK.SR.грдомајчић" xml:lang="sr">
+</sense>

7.4. Cross-references in definitions

In TEI, it is impossible to have a cross-reference inside a definition, yet some dictionaries do use this mechanism. In TEI Lex-0, <xr> is allowed within <def>:

    <entry xml:id="VSK.SR.грдомајчић" xml:lang="sr">
   <form type="lemma">
      <orth>грдо́ма̑јчић</orth>
   </form>
@@ -1113,7 +1184,7 @@
      </cit>
      <pc>.</pc>
   </sense>
-</entry>

6.5. Further examples

6.5.1. More complex example including quotations

    <entry xml:id="dog" xml:lang="en">
+</entry>

7.5. Further examples

7.5.1. More complex example including quotations

    <entry xml:id="dog" xml:lang="en">
   <form type="lemma">
      <orth>dog</orth>
   </form>
@@ -1160,7 +1231,7 @@
         </cit>
      </cit>
   </sense>
-</entry>

6.5.2. Antepassado

    <entry xml:lang="pt" xml:id="DLPC.antepassado_a">
+</entry>

7.5.2. Antepassado

    <entry xml:lang="pt" xml:id="DLPC.antepassado_a">
   <form type="lemma">
      <orth>antepassado</orth>
      <pron>ɐ̃tɨpɐsˈadu</pron>
@@ -1211,7 +1282,7 @@
         <ref type="sense">sucessor</ref>
      </xr>
   </sense>
-</entry>

6.5.3. Cross-references inside definitions

Allowed in TEI Lex-0. See this issue on GitHub.

7. Usage

Usage labels is a procedure which indicates that “a certain lexical item deviates in a certain respect from the main bulk of items described in a dictionary and that its use is subject to some kind of restriction”

In the current TEI guidelines, <usg> is defined as an element which marks up “usage information in a dictionary entry”. Prototypically, usage information is a label which can be attached at various points in the entry hierarchy in order to signal restrictions in terms of geographic regions, domains of specialized language or stylistic properties for the particular lexical item that it is attached to.

7.1. Label-like vs. narrative usage descriptions

Usage information ca be provided in dictionaries both in the form of label-like descriptors (often abbreviated) and as fuller narrative expressions.

Consider, for instance, the following senses taken from a German entry for Pflaume “plum” where usage information is provided by labels taken from fixed sets of values for stylistic and diatopic properties:

    <entry xml:id="pflaume" xml:lang="de" type="mainEntry">
+</entry>

7.5.3. Cross-references inside definitions

Allowed in TEI Lex-0. See this issue on GitHub.

8. Usage

Usage labels is a procedure which indicates that “a certain lexical item deviates in a certain respect from the main bulk of items described in a dictionary and that its use is subject to some kind of restriction”

In the current TEI guidelines, <usg> is defined as an element which marks up “usage information in a dictionary entry”. Prototypically, usage information is a label which can be attached at various points in the entry hierarchy in order to signal restrictions in terms of geographic regions, domains of specialized language or stylistic properties for the particular lexical item that it is attached to.

8.1. Label-like vs. narrative usage descriptions

Usage information ca be provided in dictionaries both in the form of label-like descriptors (often abbreviated) and as fuller narrative expressions.

Consider, for instance, the following senses taken from a German entry for Pflaume “plum” where usage information is provided by labels taken from fixed sets of values for stylistic and diatopic properties:

    <entry xml:id="pflaume" xml:lang="de" type="mainEntry">
   <form type="lemma">
      <orth>Pflaume</orth>
   </form>
@@ -1236,11 +1307,11 @@
      <def xml:lang="de">anzügliche, leicht boshafte Bemerkung</def>
      <def xml:lang="en">offensive, slightly mischievous remark</def>
   </sense>
-</entry>

In contrast to the example above, the following sample features an occurrence of a more verbose usage description that does not rely on a fixed vocabulary. The sample is taken from a Serbian dialect dictionary. The quote in the dialect is further qualified by a usage hint: “(said by a peasant woman in the field in hot weather)” which provides a particular context in which the quote was recorded.

    <cit type="example" xml:lang="sr">
+</entry>

In contrast to the example above, the following sample features an occurrence of a more verbose usage description that does not rely on a fixed vocabulary. The sample is taken from a Serbian dialect dictionary. The quote in the dialect is further qualified by a usage hint: “(said by a peasant woman in the field in hot weather)” which provides a particular context in which the quote was recorded.

    <cit type="example" xml:lang="sr">
   <quote>„Ду́ни, ве́тре, се́јче леб да пе́че”</quote>
   <usg type="hint">(рекла сељанка на њиви за време врућине)</usg>
   <bibl>(<placeName>Дубница</placeName>).</bibl>
-</cit>Златановић (2017) 

7.2. Types of usage

In TEI Lex-0, <usg> is a typed element and type is a mandatory attribute. The default value is: <usg type="hint"></usg>. The default attribute value should be used when it is not possible to otherwise classify the usage label. The type of a <usg> should be thought of as a conceptual axis (independent from other types) along which the given value of the element is located.

The following list of label types and their definitions is adapted from Salgado et al. 2019b:

  • temporal label: marker which identifies the use of a given lexical unit on a scale from old to new. Syn: diachronic marking; diachronic information; time label. 
    <usg type="time"/>
  • geographic label: marker which identifies the place or region where a lexical unit is mainly used. Some dictionaries do not identify a specific place but identify that the word is not used generally in every geographic area (e.g., regionalismo in Portuguese, or покр. (abbrev. for покрајински) in Serbian). Syn: diatopic marking; diatopic information; region label. 
    <usg type="geographic"/>
  • domain label: marker which identifies the specialized field of knowledge in which a lexical unit is mainly used. Syn: diatechnical marking; domain label; field label; subject field label; topic label. 
    <usg type="domain"/>
  • frequency label: marker which identifies the relative rate of occurrence of a lexical unit in a given textual context. Syn: diafrequential marking; diafrequential information 
      <usg type="frequency"/>
  • textType label: marker which identifies the typical use of a lexical unit in a particular discourse type or genre Syn: diatextual information. 
    <usg type="textType"/>
  • attitude label: marker which identifies the speaker’s subjective point of view, positive or negative, regarding the object referred to by a given lexical unit. Syn: diaevaluative marking; diaevaluative information. 
    <usg type="attitude"/>
  • socioCultural label: marker which identifies the use of a given lexical unit by particular social groups and/or in certain types of communicative situations depending on their level of formality Syn: diaphasic marking; diaphasic information. 
    <usg type="socioCultural"/>
  • meaningType label: marker which identifies a semantic extension of the sense of a given lexical unit. 
    <usg type="meaningType"/>
  • normativity label: marker which identifies the use of a given lexical unit which is in some aspect considered to be non-standard or incorrect. 
    <usg type="normativity"/>

The TEI Guidelines offer a range of sample values for types to illustrate potential uses of <usg>, but not al of them have been carried over to TEI Lex-0. The following table shows the differences between suggested values of type in TEI and the required values of type in TEI Lex-0:

TEI P5 (suggested types)TEI Lex-0 (required types)Еxample values
timetemporalarchaic, old
geogeographicAmE., dial.
domdomainMed., Biol., Phys.
plevfrequencyrare, occas.
-textTypebibl., poet., admin., journalese
-attitudederog., euph.
regsocioCulturalslang, vulgar, formal
stylemeaningTypefig. (=figurative), lit. (= literal)
-normativitynon-standard, incorrect
lang-
gram-
syn-
hyper-
colloc-
comp-
obj-
subj-
verb-
hinthint

In TEI-Lex-0:

  1. The type attribute is made mandatory.
  2. The element <usg> is used in a narrower sense than is currently the case in the TEI Guidelines.
  3. The norm attribute is encouraged.

Justification:

  1. Without type attribute, <usg> would be an underspecified element. Usage labels describe a wide range of linguistic phenomena. Classifying them should be considered a good practice.
  2. Currently, the TEI Guidelines contain an overuse of <usg> for describing phenomena that could be covered by alternative, more narrowly defined TEI elements. It should be considered a good practice to use the most specific TEI element available. See table above and the next section Restricting the scope of <usg>
  3. It is good practice to normalize the values of the <usg> elements because dictionaries are not always consistent in the way they use their usage labels. For instance, abbreviated and unabbreviated labels can appear in the same dictionary: they should be normalized to a single value. Normalization should be only restricted to a single dictionary. A global normalization effort is currently beyond the scope of TEI Lex-0.

7.3. Restricting the scope of usg

  1. Do not use <usg type="lang"> to mark up the name of a language in an etymological or other discussion. The recommended way to encode this information is using <lang> element within <etym>.

    INCORRECT

8.2. Types of usage

In TEI Lex-0, <usg> is a typed element and type is a mandatory attribute. The default value is: <usg type="hint"></usg>. The default attribute value should be used when it is not possible to otherwise classify the usage label. The type of a <usg> should be thought of as a conceptual axis (independent from other types) along which the given value of the element is located.

The following list of label types and their definitions is adapted from Salgado et al. 2019b:

  • temporal label: marker which identifies the use of a given lexical unit on a scale from old to new. Syn: diachronic marking; diachronic information; time label. 
    <usg type="time"/>
  • geographic label: marker which identifies the place or region where a lexical unit is mainly used. Some dictionaries do not identify a specific place but identify that the word is not used generally in every geographic area (e.g., regionalismo in Portuguese, or покр. (abbrev. for покрајински) in Serbian). Syn: diatopic marking; diatopic information; region label. 
    <usg type="geographic"/>
  • domain label: marker which identifies the specialized field of knowledge in which a lexical unit is mainly used. Syn: diatechnical marking; domain label; field label; subject field label; topic label. 
    <usg type="domain"/>
  • frequency label: marker which identifies the relative rate of occurrence of a lexical unit in a given textual context. Syn: diafrequential marking; diafrequential information 
      <usg type="frequency"/>
  • textType label: marker which identifies the typical use of a lexical unit in a particular discourse type or genre Syn: diatextual information. 
    <usg type="textType"/>
  • attitude label: marker which identifies the speaker’s subjective point of view, positive or negative, regarding the object referred to by a given lexical unit. Syn: diaevaluative marking; diaevaluative information. 
    <usg type="attitude"/>
  • socioCultural label: marker which identifies the use of a given lexical unit by particular social groups and/or in certain types of communicative situations depending on their level of formality Syn: diaphasic marking; diaphasic information. 
    <usg type="socioCultural"/>
  • meaningType label: marker which identifies a semantic extension of the sense of a given lexical unit. 
    <usg type="meaningType"/>
  • normativity label: marker which identifies the use of a given lexical unit which is in some aspect considered to be non-standard or incorrect. 
    <usg type="normativity"/>

The TEI Guidelines offer a range of sample values for types to illustrate potential uses of <usg>, but not al of them have been carried over to TEI Lex-0. The following table shows the differences between suggested values of type in TEI and the required values of type in TEI Lex-0:

TEI P5 (suggested types)TEI Lex-0 (required types)Еxample values
timetemporalarchaic, old
geogeographicAmE., dial.
domdomainMed., Biol., Phys.
plevfrequencyrare, occas.
-textTypebibl., poet., admin., journalese
-attitudederog., euph.
regsocioCulturalslang, vulgar, formal
stylemeaningTypefig. (=figurative), lit. (= literal)
-normativitynon-standard, incorrect
lang-
gram-
syn-
hyper-
colloc-
comp-
obj-
subj-
verb-
hinthint

In TEI-Lex-0:

  1. The type attribute is made mandatory.
  2. The element <usg> is used in a narrower sense than is currently the case in the TEI Guidelines.
  3. The norm attribute is encouraged.

Justification:

  1. Without type attribute, <usg> would be an underspecified element. Usage labels describe a wide range of linguistic phenomena. Classifying them should be considered a good practice.
  2. Currently, the TEI Guidelines contain an overuse of <usg> for describing phenomena that could be covered by alternative, more narrowly defined TEI elements. It should be considered a good practice to use the most specific TEI element available. See table above and the next section Restricting the scope of <usg>
  3. It is good practice to normalize the values of the <usg> elements because dictionaries are not always consistent in the way they use their usage labels. For instance, abbreviated and unabbreviated labels can appear in the same dictionary: they should be normalized to a single value. Normalization should be only restricted to a single dictionary. A global normalization effort is currently beyond the scope of TEI Lex-0.

8.3. Restricting the scope of usg

  1. Do not use <usg type="lang"> to mark up the name of a language in an etymological or other discussion. The recommended way to encode this information is using <lang> element within <etym>.

    INCORRECT

      <entryFree xml:id="MZ.RGJS.сајдисльк_1">
   <form type="lemma">
      <orth>сајдисль́к</orth>
   </form>
@@ -1250,7 +1321,7 @@
   <usg type="lang">тур.</usg>
   <sense>
      <def>уважавање.</def> … </sense>
-</entryFree>

    CORRECT

      <entry xml:id="MZ.RGJS.сајдисльк_2" xml:lang="sr">
+</entryFree>

    CORRECT

      <entry xml:id="MZ.RGJS.сајдисльк_2" xml:lang="sr">
   <form type="lemma">
      <orth>сајдисль́к</orth>
   </form>
@@ -1265,7 +1336,7 @@
      <def>уважавање.</def>
      <!--...-->
   </sense>
-</entry>
  2. Do not use <usg type="hyper"></usg> or <usg type="syn"/> to mark lexical relations such as hyperonymy or synonymy. The recommended way to encode lexical relations in TEI Lex-0 the reference mechanism provided by <xr>. See the secion on the typology of cross-references..
  3. Do not use <usg type="colloc"></usg> or for that matter "comp.", "obj.", "subj.", "verb" etc., to encode collocations or rection information. See TODO.
  4. <usg type="hint"></usg> should be used as fallback for cases where the usage information does not fall into one of the recognized cases discussed above; or as an intermediate solution during the process of encoding the dictionary automatically.
  5. Frequency information on lexicographic entities may differ from other types of usage information in that it often cannot be interpreted without further context. In phrases such as “mostly biology” or “rarely used in American English” it serves the purpose of a modifier (quantifier) to another usage information (or other lexical information). Such use calls for modeling the frequency information as an attribute to the usg element modified. For frequency information provided explicitly (e.g. corpus frequencies), a separate element should be introduced. TODO

Also TODO:

  • Frequency and source corpus? ie. source attribute <usg type=”frequency” unit=???? source= “this_and_that_corpus”>12</usg>

8. Etymology

This section needs to be transferred from Jack's and Laurent's paper.

9. Patterns

9.1. Inheritance of xml:lang

Some elements in TEI Lex-0, like <entry>, for instance, have a required attribute xml:lang; others like <form> or <quote> do not. In general, TEI Lex-0, unlike TEI, recommends that the xml:lang be attached to so-called container elements (for instance, <entry> and <cit>) rather than on individual word forms or textual segments.

TODO: Add some examples

So how can we extract all orthographic forms in a particular language? We can use an XPath expression like this: //orth[ancestor-or-self::*[@xml:lang][1][@xml:lang='en']] .

This XPath expression identifies:

  • each orth element, regardless of where it is in the document (//)
  • but only if it itself or one of its ancestors has the @xml:lang attribute ([ancestor-or-self::*[@xml:lang]])
  • when looking for ancestors with the @xml:lang attribute, we stop at the first such ancestor (i.e. we look for the nearest ancestors) ([1])
  • finally, we filter out only those selected elements with the @xml:lang attribute whose value is 'en'

If your dictionary uses multiple language tags for one language (as in 'en', 'en-GB' and 'en-US') and you want to capture all language varieties with one XPath expression, you can use the XPath lang() function as in: //orth[ancestor-or-self::*[@xml:lang][1][lang('en')]].

While the predicate [@xml:lang='en'] will match only those elements whose xml:lang is exactly equal to 'en', the predicate with the function [lang('en')] will match all the elements whose language is tagged as either English (i.e. 'en') or one of its 'sublanguages' such as 'en-GB'.

If you are new to XPath, you can check out a DARIAH-Campus tutorial XPath for Dictionary Nerds.

10. Bibliography

  1. Almonjid. 2014. The Dictionary of [Arabic] Language and Proper Nouns. Dar el-Machreq: Beirut.
  2. Atkins Rundell, B. T. S. Michael. 2008. The Oxford Guide to Practical Lexicography. Oxford University Press: Oxford; New York. ISBN callNumber: 9780199277711 P327 .A88 2008.
  3. Chambers. 2011. The Chambers Dictionary. 12th Edition. Chambers Harrap Publishers: London. ISBN: 9780550102379.
  4. Cruse, D. A.. 1986. Lexical semantics. Cambridge University Press: Cambridge and New York. ISBN: 9780521276436.
  5. Cruse, D. A.. 2011. Meaning in language: an introduction to semantics and pragmatics. 3rd ed. Oxford University Press: Oxford. ISBN: 9780199559466.
  6. DLPC. 2001. Dicionário da Língua Portuguesa Contemporânea. Editorial Verbo: Lisboa.
  7. Du Cange, Charles. 1688. Glossarium ad Scriptores Mediae et Infimae Graecitatis. Apud Amissonios: Lugduni.
  8. Duden. 2007. Das Synonymwörterbuch. Dudenverlag: Mannheim.
  9. Erjavec, Tomaž, Roger Evans, Nancy Ide and Adam Kilgarriff. 2000. "The CONCEDE Model for Lexical Databases." Proceedings of the Second Language Resources and Evaluation Conference (LREC), 355-62.
  10. Ermolaev, Natalia and Toma Tasovac. 2012. "Building a Lexicographic Infrastructure for Serbian Digital Libraries." Libraries in the Digital Age (LIDA) Proceedings.
  11. Ide, Nancy, Adam Kilgarriff and Laurent Romary. 2000. "A Formal Model of Dictionary Structure and Content." Proceedings of Euralex 2000, 113-126. arxiv: 0707.3270.
  12. LDOCE. 2003. Longman Dictionary of Contemporary English. 4th Edition. Longman: Harlow. ISBN: 0582776465.
  13. OALD. 1974. Oxford Advanced Learner's Dictionary of Current English. Oxford University Press: Oxford.
  14. Romary, Laurent. 2015. "TEI and LMF crosswalks." Journal for language technology and computational linguistics. HAL: hal-00762664.
  15. Romary, Laurent and Toma Tasovac. 2018. "TEI Lex-0: A Target Format for TEI-Encoded Dictionaries and Lexical Resources." TEI Conference.
  16. Salgado, Ana, Rute Costa, Toma Tasovac and Alberto Simões. 2019. "TEI Lex-0 In Action: Improving the Encoding of the Dictionary of the Academia das Ciências de Lisboa." eLex 2019, 417-433.
  17. Salgado, Ana, Rute Costa and Toma Tasovac. 2019. "Improving the Consistency of Usage Labelling in Dictionaries with TEI Lex-0." Lexicography 6: 133–156. DOI: 10.1007/s40607-019-00061-x.
  18. Svensén, Bo. 2009. A handbook of lexicography: the theory and practice of dictionary-making. Cambridge University Press: New York. ISBN: 9780521881807.
  19. Tasovac, Toma, Ana Salgado and Rute Costa. 2020 (in print). "Encoding Polylexical Units with TEI Lex-0: A Case Study." Slovenšcina 2.0.
  20. Zgusta, Ladislav. 1971. Manual of Lexicography. Academia: Prague. ISBN: 9783111980461.
  21. Zillig, Brian L Pytlik. 2009. "TEI Analytics: converting documents into a TEI format for cross-collection text analysis." Literary and Linguistic Computing 24: 187–192. DOI: 10.1093/llc/fqp005.
  22. Zöfgen, Ekkehard. 1989. "Homonymie und Polysemie im allgemeinen einsprachigen Wörterbuch." Wörterbücher. Ein internationales Handbuch zur Lexikographie. I: 425-464.
  23. Златановић, Момчило. 2017. Речник говора јужне Србије: електронско издање. Институт за српски језик САНУ и Центар за дигиталне хуманистичке науке: Београд.
  24. Московљевић, Милош С.. 1990. Речник савременог српскохрватског књижевног језика с књижевним саветником. Аполон: Београд.

11. Specification

11.1. Elements

11.1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]

Moduletextstructure — Specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
+</entry>
  • Do not use <usg type="hyper"></usg> or <usg type="syn"/> to mark lexical relations such as hyperonymy or synonymy. The recommended way to encode lexical relations in TEI Lex-0 the reference mechanism provided by <xr>. See the secion on the typology of cross-references..
  • Do not use <usg type="colloc"></usg> or for that matter "comp.", "obj.", "subj.", "verb" etc., to encode collocations or rection information. See TODO.
  • <usg type="hint"></usg> should be used as fallback for cases where the usage information does not fall into one of the recognized cases discussed above; or as an intermediate solution during the process of encoding the dictionary automatically.
  • Frequency information on lexicographic entities may differ from other types of usage information in that it often cannot be interpreted without further context. In phrases such as “mostly biology” or “rarely used in American English” it serves the purpose of a modifier (quantifier) to another usage information (or other lexical information). Such use calls for modeling the frequency information as an attribute to the usg element modified. For frequency information provided explicitly (e.g. corpus frequencies), a separate element should be introduced. TODO

    • Also TODO:

    • Frequency and source corpus? ie. source attribute <usg type=”frequency” unit=???? source= “this_and_that_corpus”>12</usg>

    9. Etymology

    This section needs to be transferred from Jack's and Laurent's paper.

    10. Patterns

    10.1. Inheritance of xml:lang

    Some elements in TEI Lex-0, like <entry>, for instance, have a required attribute xml:lang; others like <form> or <quote> do not. In general, TEI Lex-0, unlike TEI, recommends that the xml:lang be attached to so-called container elements (for instance, <entry> and <cit>) rather than on individual word forms or textual segments.

    TODO: Add some examples

    So how can we extract all orthographic forms in a particular language? We can use an XPath expression like this: //orth[ancestor-or-self::*[@xml:lang][1][@xml:lang='en']] .

    This XPath expression identifies:

    • each orth element, regardless of where it is in the document (//)
    • but only if it itself or one of its ancestors has the @xml:lang attribute ([ancestor-or-self::*[@xml:lang]])
    • when looking for ancestors with the @xml:lang attribute, we stop at the first such ancestor (i.e. we look for the nearest ancestors) ([1])
    • finally, we filter out only those selected elements with the @xml:lang attribute whose value is 'en'

    If your dictionary uses multiple language tags for one language (as in 'en', 'en-GB' and 'en-US') and you want to capture all language varieties with one XPath expression, you can use the XPath lang() function as in: //orth[ancestor-or-self::*[@xml:lang][1][lang('en')]].

    While the predicate [@xml:lang='en'] will match only those elements whose xml:lang is exactly equal to 'en', the predicate with the function [lang('en')] will match all the elements whose language is tagged as either English (i.e. 'en') or one of its 'sublanguages' such as 'en-GB'.

    If you are new to XPath, you can check out a DARIAH-Campus tutorial XPath for Dictionary Nerds.

    11. Bibliography

    1. Almonjid. 2014. The Dictionary of [Arabic] Language and Proper Nouns. Dar el-Machreq: Beirut.
    2. Atkins Rundell, B. T. S. Michael. 2008. The Oxford Guide to Practical Lexicography. Oxford University Press: Oxford; New York. ISBN callNumber: 9780199277711 P327 .A88 2008.
    3. Chambers. 2011. The Chambers Dictionary. 12th Edition. Chambers Harrap Publishers: London. ISBN: 9780550102379.
    4. Cruse, D. A.. 1986. Lexical semantics. Cambridge University Press: Cambridge and New York. ISBN: 9780521276436.
    5. Cruse, D. A.. 2011. Meaning in language: an introduction to semantics and pragmatics. 3rd ed. Oxford University Press: Oxford. ISBN: 9780199559466.
    6. DLPC. 2001. Dicionário da Língua Portuguesa Contemporânea. Editorial Verbo: Lisboa.
    7. Du Cange, Charles. 1688. Glossarium ad Scriptores Mediae et Infimae Graecitatis. Apud Amissonios: Lugduni.
    8. Duden. 2007. Das Synonymwörterbuch. Dudenverlag: Mannheim.
    9. Erjavec, Tomaž, Roger Evans, Nancy Ide and Adam Kilgarriff. 2000. "The CONCEDE Model for Lexical Databases." Proceedings of the Second Language Resources and Evaluation Conference (LREC), 355-62.
    10. Ermolaev, Natalia and Toma Tasovac. 2012. "Building a Lexicographic Infrastructure for Serbian Digital Libraries." Libraries in the Digital Age (LIDA) Proceedings.
    11. EtymWB-XML. 2009. Wörterbuch des Deutschen: Die XML-Edition. Berlin-Brandenburgische Akademie der Wissenschaften: Berlin.
    12. Ide, Nancy, Adam Kilgarriff and Laurent Romary. 2000. "A Formal Model of Dictionary Structure and Content." Proceedings of Euralex 2000, 113-126. arxiv: 0707.3270.
    13. LDOCE. 2003. Longman Dictionary of Contemporary English. 4th Edition. Longman: Harlow. ISBN: 0582776465.
    14. OALD. 1974. Oxford Advanced Learner's Dictionary of Current English. Oxford University Press: Oxford.
    15. Romary, Laurent. 2015. "TEI and LMF crosswalks." Journal for language technology and computational linguistics. HAL: hal-00762664.
    16. Romary, Laurent and Toma Tasovac. 2018. "TEI Lex-0: A Target Format for TEI-Encoded Dictionaries and Lexical Resources." TEI Conference.
    17. Salgado, Ana, Rute Costa, Toma Tasovac and Alberto Simões. 2019. "TEI Lex-0 In Action: Improving the Encoding of the Dictionary of the Academia das Ciências de Lisboa." eLex 2019, 417-433.
    18. Salgado, Ana, Rute Costa and Toma Tasovac. 2019. "Improving the Consistency of Usage Labelling in Dictionaries with TEI Lex-0." Lexicography 6: 133–156. DOI: 10.1007/s40607-019-00061-x.
    19. Svensén, Bo. 2009. A handbook of lexicography: the theory and practice of dictionary-making. Cambridge University Press: New York. ISBN: 9780521881807.
    20. Tasovac, Toma, Ana Salgado and Rute Costa. 2020 (in print). "Encoding Polylexical Units with TEI Lex-0: A Case Study." Slovenšcina 2.0.
    21. Zgusta, Ladislav. 1971. Manual of Lexicography. Academia: Prague. ISBN: 9783111980461.
    22. Zillig, Brian L Pytlik. 2009. "TEI Analytics: converting documents into a TEI format for cross-collection text analysis." Literary and Linguistic Computing 24: 187–192. DOI: 10.1093/llc/fqp005.
    23. Zöfgen, Ekkehard. 1989. "Homonymie und Polysemie im allgemeinen einsprachigen Wörterbuch." Wörterbücher. Ein internationales Handbuch zur Lexikographie. I: 425-464.
    24. Златановић, Момчило. 2017. Речник говора јужне Србије: електронско издање. Институт за српски језик САНУ и Центар за дигиталне хуманистичке науке: Београд.
    25. Московљевић, Милош С.. 1990. Речник савременог српскохрватског књижевног језика с књижевним саветником. Аполон: Београд.

    12. Specification

    12.1. Elements

    12.1.1. <TEI>

    <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    versionspecifies the version number of the TEI Guidelines against which this document is valid.
    StatusOptional
    Datatypeteidata.version
    Note

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

    Contained by
    textstructure: TEI
    May contain
    header: teiHeader
    textstructure: TEI text
    Note

    This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

    Example
    <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
   <teiHeader>
      <fileDesc>
         <titleStmt>
@@ -1285,7 +1356,7 @@
         <p>This is about the shortest TEI document imaginable.</p>
      </body>
   </text>
-</TEI>
    Example
    <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
+</TEI>
    Example
    <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
   <teiHeader>
      <fileDesc>
         <titleStmt>
@@ -1334,7 +1405,7 @@
    att.typed.attributes,
    attribute version { text }?,
    ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
-}

    11.1.2. <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.11.2.1. Analytic, Monographic, and Series Levels]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    core: biblStruct
    May contain
    core: author date editor ref respStmt title
    header: availability idno
    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>
+}

    12.1.2. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    core: biblStruct
    May contain
    core: author date editor ref respStmt title
    header: availability idno
    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>
@@ -1377,7 +1448,7 @@
     | idno
     | availability
    )*
-}

    11.1.3. <appInfo>

    <appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May containEmpty element
    Example
    <appInfo>
+}

    12.1.3. <appInfo>

    <appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May containEmpty element
    Example
    <appInfo>
   <application version="1.24" ident="Xaira">
      <label>XAIRA Indexer</label>
      <ptr target="#P1"/>
@@ -1388,7 +1459,7 @@
   minOccurs="1" maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
-element appInfo { att.global.attributes, model.applicationLike+ }

    11.1.4. <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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    Member of
    model.respLike
    Contained by
    core: analytic bibl
    header: editionStmt titleStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    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>
+element appInfo { att.global.attributes, model.applicationLike+ }

    12.1.4. <author>

    <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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
    model.respLike
    Contained by
    core: analytic bibl monogr
    header: editionStmt titleStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    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>
@@ -1408,8 +1479,9 @@
 {
    att.global.attributes,
    att.naming.attributes,
+   att.datable.attributes,
    macro.phraseSeq
-}

    11.1.5. <authority>

    <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.publicationStmtPart.agency
    Contained by
    header: publicationStmt
    May contain
    core: date gloss hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    header: idno
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <authority>John Smith</authority>
    Content model
    
+}

    12.1.5. <authority>

    <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    role
    StatusOptional
    Suggested values include:
    funder
    sponsor
    rightsHolder
    Member of
    model.publicationStmtPart.agency
    Contained by
    core: monogr
    header: publicationStmt
    May contain
    core: date email gloss hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    header: idno
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <authority>John Smith</authority>
    Content model
    
 <content>
  <macroRef key="macro.phraseSeq.limited"/>
 </content>
@@ -1418,8 +1490,9 @@
 {
    att.global.attributes,
    att.canonical.attributes,
+   attribute role { "funder" | "sponsor" | "rightsHolder" | xsd:Name }?,
    macro.phraseSeq.limited
-}

    11.1.6. <availability>

    <availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    statussupplies a code identifying the current availability of the text.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    free
    the text is freely available.
    unknown
    the status of the text is unknown.
    restricted
    the text is not freely available.
    Member of
    model.biblPart model.publicationStmtPart.detail
    Contained by
    core: analytic bibl
    header: publicationStmt
    May contain
    core: p
    header: licence
    Note

    A consistent format should be adopted

    Example
    <availability status="restricted">
+}

    12.1.6. <availability>

    <availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    status(status) supplies a code identifying the current availability of the text.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    free
    (free) the text is freely available.
    unknown
    (unknown) the status of the text is unknown.
    restricted
    (restricted) the text is not freely available.
    Member of
    model.biblPart model.publicationStmtPart.detail
    Contained by
    core: analytic bibl monogr
    header: publicationStmt
    May contain
    core: p
    header: licence
    Note

    A consistent format should be adopted

    Example
    <availability status="restricted">
   <p>Available for academic research purposes only.</p>
 </availability>
 <availability status="free">
@@ -1427,7 +1500,7 @@
 </availability>
 <availability status="restricted">
   <p>Available under licence from the publishers.</p>
-</availability>
    Example
    <availability>
+</availability>
    Example
    <availability>
   <licence target="http://opensource.org/licenses/MIT">
      <p>The MIT License
            applies to this document.</p>
@@ -1463,7 +1536,7 @@
    att.declarable.attributes,
    attribute status { "free" | "unknown" | "restricted" }?,
    ( model.availabilityPart | model.pLike )+
-}

    11.1.7. <back>

    <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: head listBibl note p
    figures: figure
    textstructure: div
    transcr: metamark
    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>
+}

    12.1.7. <back>

    <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: head listBibl note p
    figures: figure
    textstructure: div
    transcr: metamark
    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
@@ -1564,13 +1637,13 @@
       )?,
       ( model.divBottomPart, ( model.divBottomPart | model.global )* )?
    )
-}

    11.1.8. <bibl>

    <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
    Member of
    model.biblLike model.biblPart
    Contained by
    core: bibl cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition sourceDesc tagUsage
    linking: seg
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: author bibl biblScope citedRange date editor gloss hi name note pubPlace publisher ref respStmt term title
    dictionaries: lang lbl
    figures: figure
    gaiji: g
    header: availability distributor edition extent funder idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    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>
+}

    12.1.8. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
    Member of
    model.biblLike model.biblPart
    Contained by
    core: bibl cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition tagUsage
    linking: seg
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: author bibl biblScope citedRange date editor email gloss hi name note pubPlace publisher ref respStmt term title
    dictionaries: lang lbl
    figures: figure
    gaiji: g
    header: availability distributor edition extent idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

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

    Example
    <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
+ 1990)</bibl>
    Example
    <bibl>
   <title level="a">The Interesting story of the Children in the Wood</title>. In
 <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
 <publisher>OUP</publisher>
   <date>1968</date>. 
-</bibl>
    Example
    <bibl type="article" subtype="book_chapter" xml:id="carlin_2003">
+</bibl>
    Example
    <bibl type="article" subtype="book_chapter" xml:id="carlin_2003">
   <author>
      <name>
         <surname>Carlin</surname>
@@ -1631,7 +1704,7 @@
     | model.biblPart
     | model.global
    )*
-}

    11.1.9. <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.11.2.5. Scopes and Ranges in Bibliographic Citations]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to)
    Member of
    model.imprintPart
    Contained by
    core: bibl imprint
    header: seriesStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    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>
+}

    12.1.9. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to)
    Member of
    model.imprintPart
    Contained by
    core: bibl imprint monogr
    header: seriesStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    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="page" from="12" to="34"/>
 <biblScope unit="volume">II</biblScope>
 <biblScope unit="page">12</biblScope>
    Content model
    
@@ -1644,7 +1717,7 @@
    att.global.attributes,
    att.citing.attributes,
    macro.phraseSeq
-}

    11.1.10. <biblStruct>

    <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
    Member of
    model.biblLike
    Contained by
    core: cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition sourceDesc tagUsage
    linking: seg
    textstructure: body div
    transcr: metamark
    May contain
    core: analytic citedRange note ref
    Example
    <biblStruct>
+}

    12.1.10. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
    Member of
    model.biblLike
    Contained by
    core: cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition sourceDesc tagUsage
    linking: seg
    textstructure: body div
    transcr: metamark
    May contain
    core: analytic citedRange monogr note ref
    Example
    <biblStruct>
   <monogr>
      <author>Blain, Virginia</author>
      <author>Clements, Patricia</author>
@@ -1691,7 +1764,7 @@
       ( monogr, series* )+,
       ( model.noteLike | model.ptrLike | relatedItem | citedRange )*
    )
-}

    11.1.11. <body>

    <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: bibl biblStruct cit head listBibl note p quote
    dictionaries: entry xr
    figures: figure
    textstructure: div
    transcr: metamark
    Example
    <body>
+}

    12.1.11. <body>

    <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: bibl biblStruct cit head listBibl note p quote
    dictionaries: entry xr
    figures: figure
    textstructure: div
    transcr: metamark
    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>
@@ -1800,7 +1873,7 @@
       ),
       ( model.divBottom, model.global* )*
    )
-}

    11.1.12. <c>

    <c> (character) represents a character. [17.1. Linguistic Segment Categories]

    Moduleanalysis — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
    Member of
    model.segLike
    Contained by
    analysis: pc
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    gaiji: g
    character data
    Note

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

    Example
    <phr>
+}

    12.1.12. <c>

    <c> (character) represents a character. [17.1. Linguistic Segment Categories]

    Moduleanalysis — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
    Member of
    model.segLike
    Contained by
    analysis: pc
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    gaiji: g
    character data
    Note

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

    Example
    <phr>
   <c>M</c>
   <c>O</c>
   <c>A</c>
@@ -1821,7 +1894,7 @@
    att.typed.attributes,
    att.notated.attributes,
    macro.xtext
-}

    11.1.13. <char>

    <char> (character) provides descriptive information about a character. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charDecl
    May contain
    core: graphic note
    figures: figure
    gaiji: charName charProp localProp mapping unicodeProp unihanProp
    Example
    <char xml:id="circledU4EBA">
+}

    12.1.13. <char>

    <char> (character) provides descriptive information about a character. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charDecl
    May contain
    core: graphic note
    figures: figure
    gaiji: charName charProp localProp mapping unicodeProp unihanProp
    Example
    <char xml:id="circledU4EBA">
   <localProp name="Name" value="CIRCLED IDEOGRAPH 4EBA"/>
   <localProp name="daikanwa" value="36"/>
   <unicodeProp name="Decomposition_Mapping" value="circle"/>
@@ -1858,7 +1931,7 @@
     | model.noteLike
     | model.descLike
    )*
-}

    11.1.14. <charDecl>

    <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    gaiji: char glyph
    Example
    <charDecl>
+}

    12.1.14. <charDecl>

    <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    gaiji: char glyph
    Example
    <charDecl>
   <char xml:id="aENL">
      <charName>LATIN LETTER ENLARGED SMALL A</charName>
      <mapping type="standard">a</mapping>
@@ -1875,12 +1948,12 @@
  </sequence>
 </content>
    Schema Declaration
    
-element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) }

    11.1.15. <charName>

    <charName> (character name) contains the name of a character, expressed following Unicode conventions. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: char
    May containCharacter data only
    Note

    The name must follow Unicode conventions for character naming. Projects working in similar fields are recommended to coordinate and publish their list of <charName>s to facilitate data exchange.

    Example
    <charName>CIRCLED IDEOGRAPH 4EBA</charName>
    Content model
    
+element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) }

    12.1.15. <charName>

    <charName> (character name) contains the name of a character, expressed following Unicode conventions. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: char
    May containCharacter data only
    Note

    The name must follow Unicode conventions for character naming. Projects working in similar fields are recommended to coordinate and publish their list of <charName>s to facilitate data exchange.

    Example
    <charName>CIRCLED IDEOGRAPH 4EBA</charName>
    Content model
    
 <content>
  <textNode/>
 </content>
    Schema Declaration
    
-element charName { att.global.attributes, text }

    11.1.16. <charProp>

    <charProp> (character property) provides a name and value for some property of the parent character or glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    Contained by
    gaiji: char glyph
    May contain
    gaiji: unicodeName value
    Note

    If the property is a Unicode Normative Property, then its <unicodeName> must be supplied. Otherwise, its name must be specied by means of a <localName>.

    Example
    <charProp>
+element charName { att.global.attributes, text }

    12.1.16. <charProp>

    <charProp> (character property) provides a name and value for some property of the parent character or glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    Contained by
    gaiji: char glyph
    May contain
    gaiji: unicodeName value
    Note

    If the property is a Unicode Normative Property, then its <unicodeName> must be supplied. Otherwise, its name must be specied by means of a <localName>.

    Example
    <charProp>
   <unicodeName>Decomposition_Mapping</unicodeName>
   <value>circle</value>
 </charProp>
@@ -1903,11 +1976,11 @@
    att.global.attributes,
    att.typed.attributes,
    ( ( unicodeName | localName ), value )
-}

    11.1.17. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
    type
    StatusRequired
    Legal values are:
    example
    translation
    translationEquivalent
    etymon
    cognate
    cognateSet
    Member of
    model.entryPart.top model.quoteLike model.sensePart
    Contained by
    core: author biblScope cit citedRange editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit gloss listBibl note quote ref
    dictionaries: etym form gramGrp hyph lang lbl orth pron sense syll usg xr
    figures: figure
    linking: seg
    transcr: metamark
    Example
    <cit>
+}

    12.1.17. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
    type
    StatusRequired
    Legal values are:
    example
    translation
    translationEquivalent
    etymon
    cognate
    cognateSet
    Member of
    model.entryPart.top model.quoteLike model.sensePart
    Contained by
    core: author biblScope cit citedRange editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit gloss listBibl note quote ref
    dictionaries: etym form gramGrp hyph lang lbl orth pron sense syll usg xr
    figures: figure
    linking: seg
    transcr: metamark
    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>
+</cit>
    Example
    <entry>
   <form>
      <orth>horrifier</orth>
   </form>
@@ -1920,7 +1993,7 @@
         <quote>she was horrified at the expense.</quote>
      </cit>
   </cit>
-</entry>
    Example
    <cit type="example">
+</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"/>
@@ -1970,10 +2043,10 @@
     | lang
     | gloss
    )+
-}

    11.1.18. <citedRange>

    <citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.5. Scopes and Ranges in Bibliographic Citations]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
    Member of
    model.biblPart
    Contained by
    core: bibl biblStruct
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    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>.

    Example
    <citedRange>pp 12–13</citedRange>
+}

    12.1.18. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
    Member of
    model.biblPart
    Contained by
    core: bibl biblStruct
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    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="page" from="12" to="13"/>
 <citedRange unit="volume">II</citedRange>
-<citedRange unit="page">12</citedRange>
    Example
    <bibl>
+<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
    
@@ -1987,7 +2060,7 @@
    att.pointing.attributes,
    att.citing.attributes,
    macro.phraseSeq
-}

    11.1.19. <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]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May containEmpty element
    Example
    <classDecl>
+}

    12.1.19. <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]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May containEmpty element
    Example
    <classDecl>
   <taxonomy xml:id="LCSH">
      <bibl>Library of Congress Subject Headings</bibl>
   </taxonomy>
@@ -2005,9 +2078,9 @@
   maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
-element classDecl { att.global.attributes, taxonomy+ }

    11.1.20. <date>

    <date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.7. Dates and Times]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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
    model.dateLike model.publicationStmtPart.detail
    Contained by
    core: analytic author bibl biblScope citedRange date editor gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence publicationStmt rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: date gloss graphic hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <date when="1980-02">early February 1980</date>
    Example
    Given on the <date when="1977-06-12">Twelfth Day
+element classDecl { att.global.attributes, taxonomy+ }

    12.1.20. <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]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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
    model.dateLike model.publicationStmtPart.detail
    Contained by
    core: analytic author bibl biblScope citedRange date editor email gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence publicationStmt rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: date email gloss graphic hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    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
    
+ 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">
@@ -2027,7 +2100,7 @@
    att.dimensions.attributes,
    att.typed.attributes,
    ( text | model.gLike | model.phrase | model.global )*
-}

    11.1.21. <def>

    <def> (definition) contains definition text in a dictionary entry. [9.3.3.1. Definitions]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    Member of
    model.sensePart
    Contained by
    dictionaries: etym sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <entry>
+}

    12.1.21. <def>

    <def> (definition) contains definition text in a dictionary entry. [9.3.3.1. Definitions]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    Member of
    model.sensePart
    Contained by
    dictionaries: etym sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <entry>
   <form>
      <orth>competitor</orth>
      <hyph>com|peti|tor</hyph>
@@ -2047,7 +2120,7 @@
    att.global.attributes,
    att.lexicographic.attributes,
    macro.paraContent
-}

    11.1.22. <dictScrap>

    <dictScrap> (dictionary scrap) encloses a part of a dictionary entry in which other phrase-level dictionary elements are freely combined. [9.1. Dictionary Body and Overall Structure 9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.entryPart.top
    Contained by
    dictionaries: entry
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: etym form gram gramGrp hyph lang lbl orth pron sense syll usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    May contain any dictionary elements in any combination.

    This element is used to mark part of a dictionary entry in which lower level dictionary elements appear, but which does not itself form an identifiable structural unit.

    Example
    <entry>
+}

    12.1.22. <dictScrap>

    <dictScrap> (dictionary scrap) encloses a part of a dictionary entry in which other phrase-level dictionary elements are freely combined. [9.1. Dictionary Body and Overall Structure 9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.entryPart.top
    Contained by
    dictionaries: entry
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: etym form gram gramGrp hyph lang lbl orth pron sense syll usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    May contain any dictionary elements in any combination.

    This element is used to mark part of a dictionary entry in which lower level dictionary elements appear, but which does not itself form an identifiable structural unit.

    Example
    <entry>
   <dictScrap>
      <orth>biryani</orth> or <orth>biriani</orth>
      <pron>(%bIrI"A:nI)</pron>
@@ -2080,7 +2153,7 @@
     | model.inter
     | model.global
    )*
-}

    11.1.23. <distributor>

    <distributor> supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.imprintPart model.publicationStmtPart.agency
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <distributor>Oxford Text Archive</distributor>
+}

    12.1.23. <distributor>

    <distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.imprintPart model.publicationStmtPart.agency
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <distributor>Oxford Text Archive</distributor>
 <distributor>Redwood and Burn Ltd</distributor>
    Content model
    
 <content>
  <macroRef key="macro.phraseSeq"/>
@@ -2091,7 +2164,7 @@
    att.global.attributes,
    att.canonical.attributes,
    macro.phraseSeq
-}

    11.1.24. <div>

    <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.divLike
    Contained by
    textstructure: back body div front
    May contain
    core: bibl biblStruct cit head listBibl note p quote
    dictionaries: entry xr
    figures: figure
    textstructure: div
    transcr: metamark
    Example
    <body>
+}

    12.1.24. <div>

    <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.divLike
    Contained by
    textstructure: back body div front
    May contain
    core: bibl biblStruct cit head listBibl note p quote
    dictionaries: entry xr
    figures: figure
    textstructure: div
    transcr: metamark
    Example
    <body>
   <div type="part">
      <head>Fallacies of Authority</head>
      <p>The subject of which is Authority in various shapes, and the object, to repress all
@@ -2112,9 +2185,9 @@
      </div>
   </div>
 </body>
    Schematron
    
-<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div.
+<s:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
 </s:report>
    Schematron
    
-<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div.
+<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
 </s:report>
    Content model
    
 <content>
  <sequence>
@@ -2180,20 +2253,20 @@
          ( model.divBottom, model.global* )*
       )?
    )
-}

    11.1.25. <edition>

    <edition> describes the particularities of one edition of a text. [2.2.2. The Edition Statement]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.biblPart
    Contained by
    core: bibl
    header: editionStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <edition>First edition <date>Oct 1990</date>
+}

    12.1.25. <edition>

    <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.biblPart
    Contained by
    core: bibl monogr
    header: editionStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <edition>First edition <date>Oct 1990</date>
 </edition>
 <edition n="S2">Students' edition</edition>
    Content model
    
 <content>
  <macroRef key="macro.phraseSeq"/>
 </content>
    Schema Declaration
    
-element edition { att.global.attributes, macro.phraseSeq }

    11.1.26. <editionStmt>

    <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: author editor p respStmt
    header: edition funder
    Example
    <editionStmt>
+element edition { att.global.attributes, macro.phraseSeq }

    12.1.26. <editionStmt>

    <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: author editor p respStmt
    header: edition
    Example
    <editionStmt>
   <edition n="S2">Students' edition</edition>
   <respStmt>
      <resp>Adapted by </resp>
      <name>Elizabeth Kirk</name>
   </respStmt>
-</editionStmt>
    Example
    <editionStmt>
+</editionStmt>
    Example
    <editionStmt>
   <p>First edition, <date>Michaelmas Term, 1991.</date>
   </p>
 </editionStmt>
    Content model
    
@@ -2213,7 +2286,7 @@
 {
    att.global.attributes,
    ( model.pLike+ | ( edition, model.respLike* ) )
-}

    11.1.27. <editor>

    <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. Titles, Authors, and Editors]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    Member of
    model.respLike
    Contained by
    core: analytic bibl
    header: editionStmt seriesStmt titleStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    A consistent format should be adopted.

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

    Example
    <editor role="Technical_Editor">Ron Van den Branden</editor>
+}

    12.1.27. <editor>

    <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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
    model.respLike
    Contained by
    core: analytic bibl monogr
    header: editionStmt seriesStmt titleStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    A consistent format should be adopted.

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

    Example
    <editor role="Technical_Editor">Ron Van den Branden</editor>
 <editor role="Editor-in-Chief">John Walsh</editor>
 <editor role="Managing_Editor">Anne Baillot</editor>
    Content model
    
 <content>
@@ -2224,8 +2297,38 @@
 {
    att.global.attributes,
    att.naming.attributes,
+   att.datable.attributes,
    macro.phraseSeq
-}

    11.1.28. <encodingDesc>

    <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.teiHeaderPart
    Contained by
    header: teiHeader
    May contain
    core: p
    gaiji: charDecl
    header: appInfo classDecl projectDesc tagsDecl
    Example
    <encodingDesc>
+}

    12.1.28. <editorialDecl>

    <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    core: p
    Example
    <editorialDecl>
+  <normalization>
+     <p>All words converted to Modern American spelling using
+           Websters 9th Collegiate dictionary
+     </p>
+  </normalization>
+  <quotation marks="all">
+     <p>All opening quotation marks converted to “ all closing
+           quotation marks converted to &amp;cdq;.</p>
+  </quotation>
+</editorialDecl>
    Content model
    
+<content>
+ <alternate minOccurs="1"
+  maxOccurs="unbounded">
+  <classRef key="model.pLike"/>
+  <classRef key="model.editorialDeclPart"/>
+ </alternate>
+</content>
+
    Schema Declaration
    
+element editorialDecl
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   ( model.pLike | model.editorialDeclPart )+
+}

    12.1.29. <email>

    <email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.addressLike
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

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

    Example
    <email>membership@tei-c.org</email>
    Content model
    
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+
    Schema Declaration
    
+element email { att.global.attributes, macro.phraseSeq }

    12.1.30. <encodingDesc>

    <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: teiHeader
    May contain
    core: p
    gaiji: charDecl
    header: appInfo classDecl editorialDecl projectDesc tagsDecl
    Example
    <encodingDesc>
   <p>Basic encoding, capturing lexical information only. All
      hyphenation, punctuation, and variant spellings normalized. No
      formatting or layout information preserved.</p>
@@ -2242,7 +2345,7 @@
 {
    att.global.attributes,
    ( model.encodingDescPart | model.pLike )+
-}

    11.1.29. <entry>

    <entry> contains a single structured entry in any kind of lexical resource, such as a dictionary or lexicon. [9.1. Dictionary Body and Overall Structure 9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.sortable (@sortKey) att.global (xml:id, xml:lang, @n) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    Derived fromatt.global
    StatusRequired
    DatatypeID
    xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
    Derived fromatt.global
    StatusRequired
    Datatypeteidata.language
    type
    StatusRecommended
    Suggested values include:
    mainEntry
    [Default]
    wordFamily
    homonymicEntry
    relatedEntry
    Member of
    model.entryLike model.entryPart.top model.sensePart
    Contained by
    dictionaries: entry sense
    figures: figure
    textstructure: body div
    May contain
    analysis: pc
    core: bibl biblStruct cit listBibl note num ref
    dictionaries: dictScrap entry etym form gramGrp lbl sense usg xr
    figures: figure
    transcr: metamark
    Note

    Like all elements, <entry> inherits an xml:id attribute from the class global. No restrictions are placed on the method used to construct xml:ids; one convenient method is to use the orthographic form of the headword, appending a disambiguating number where necessary. Identification codes are sometimes included on machine-readable tapes of dictionaries for in-house use.

    It is recommended to use the <sense> element even for an entry that has only one sense to group together all parts of the definition relating to the word sense since this leads to more consistent encoding across entries.

    Example
    <entry>
+}

    12.1.31. <entry>

    <entry> (entry) contains a single structured entry in any kind of lexical resource, such as a dictionary or lexicon. [9.1. Dictionary Body and Overall Structure 9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.sortable (@sortKey) att.global (xml:id, xml:lang, @n) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    Derived fromatt.global
    StatusRequired
    DatatypeID
    xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
    Derived fromatt.global
    StatusRequired
    Datatypeteidata.language
    type
    StatusRecommended
    Suggested values include:
    mainEntry
    [Default]
    wordFamily
    homonymicEntry
    relatedEntry
    Member of
    model.entryLike model.entryPart.top model.sensePart
    Contained by
    dictionaries: entry sense
    figures: figure
    textstructure: body div
    May contain
    analysis: pc
    core: bibl biblStruct cit listBibl note num ref
    dictionaries: dictScrap entry etym form gramGrp lbl sense usg xr
    figures: figure
    transcr: metamark
    Note

    Like all elements, <entry> inherits an xml:id attribute from the class global. No restrictions are placed on the method used to construct xml:ids; one convenient method is to use the orthographic form of the headword, appending a disambiguating number where necessary. Identification codes are sometimes included on machine-readable tapes of dictionaries for in-house use.

    It is recommended to use the <sense> element even for an entry that has only one sense to group together all parts of the definition relating to the word sense since this leads to more consistent encoding across entries.

    Example
    <entry>
   <form>
      <orth>disproof</orth>
      <pron>dIs"pru:f</pron>
@@ -2296,7 +2399,7 @@
       "mainEntry" | "wordFamily" | "homonymicEntry" | "relatedEntry" | xsd:Name
    }?,
    ( sense | pc | model.entryPart.top | model.global | model.ptrLike )+
-}

    11.1.30. <etym>

    <etym> (etymology) encloses the etymological information in a dictionary entry. [9.3.4. Etymological Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRecommended
    Legal values are:
    borrowing
    inheritance
    metaphor
    metonymy
    compounding
    grammaticalization
    derivation
    Member of
    model.entryPart model.entryPart.top model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: def etym gramGrp lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    May contain character data mixed with any other elements defined in the dictionary tag set.

    There is no consensus on the internal structure of etymologies, or even on whether such a structure is appropriate. The <etym> element accordingly simply contains prose, within which names of languages, cited words, or parts of words, glosses, and examples will typically be prominent. The tagging of such internal objects is optional.

    Example
    <entry>
+}

    12.1.32. <etym>

    <etym> (etymology) encloses the etymological information in a dictionary entry. [9.3.4. Etymological Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRecommended
    Legal values are:
    borrowing
    inheritance
    metaphor
    metonymy
    compounding
    grammaticalization
    derivation
    Member of
    model.entryPart model.entryPart.top model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: def etym gramGrp lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    May contain character data mixed with any other elements defined in the dictionary tag set.

    There is no consensus on the internal structure of etymologies, or even on whether such a structure is appropriate. The <etym> element accordingly simply contains prose, within which names of languages, cited words, or parts of words, glosses, and examples will typically be prominent. The tagging of such internal objects is optional.

    Example
    <entry>
   <form>
      <orth>publish</orth> ... </form>
   <etym>
@@ -2307,7 +2410,7 @@
      <mentioned>publicare,
            publicatum</mentioned>. <xr>See <ref>public</ref>; cf. 2d <ref>-ish</ref>.</xr>
   </etym>
-</entry> (From: Webster's Second International)
    Example
    <entry>
+</entry> (From: Webster's Second International)
    Example
    <entry>
   <form>
      <orth>Handschuh</orth> ... </form>
   <etym type="compounding">
@@ -2364,9 +2467,9 @@
     | usg
     | xr
    )*
-}

    11.1.31. <extent>

    <extent> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.biblPart
    Contained by
    core: bibl
    header: fileDesc
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <extent>3200 sentences</extent>
+}

    12.1.33. <extent>

    <extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.biblPart
    Contained by
    core: bibl monogr
    header: fileDesc
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <extent>3200 sentences</extent>
 <extent>between 10 and 20 Mb</extent>
-<extent>ten 3.5 inch high density diskettes</extent>
    ExampleThe <measure> element may be used to supply normalised or machine tractable versions of the size or sizes concerned.
    <extent>
+<extent>ten 3.5 inch high density diskettes</extent>
    ExampleThe <measure> element may be used to supply normalised or machine tractable versions of the size or sizes concerned.
    <extent>
   <measure unit="MiB" quantity="4.2">About four megabytes</measure>
   <measure unit="pages" quantity="245">245 pages of source
      material</measure>
@@ -2375,7 +2478,7 @@
  <macroRef key="macro.phraseSeq"/>
 </content>
    Schema Declaration
    
-element extent { att.global.attributes, macro.phraseSeq }

    11.1.32. <figDesc>

    <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. [14.4. Specific Elements for Graphic Images]

    Modulefigures — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    figures: figure
    May contain
    core: bibl biblStruct cit date gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: orgName persName placeName
    character data
    Note

    This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

    Example
    <figure>
+element extent { att.global.attributes, macro.phraseSeq }

    12.1.34. <figDesc>

    <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. [14.4. Specific Elements for Graphic Images]

    Modulefigures — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    figures: figure
    May contain
    core: bibl biblStruct cit date email gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: forename orgName persName placeName surname
    character data
    Note

    This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

    Example
    <figure>
   <graphic url="emblem1.png"/>
   <head>Emblemi d'Amore</head>
   <figDesc>A pair of naked winged cupids, each holding a
@@ -2385,7 +2488,7 @@
  <macroRef key="macro.limitedContent"/>
 </content>
    Schema Declaration
    
-element figDesc { att.global.attributes, macro.limitedContent }

    11.1.33. <figure>

    <figure> groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]

    Modulefigures — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.global
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: authority distributor edition extent funder licence
    linking: seg
    namesdates: orgName persName placeName
    textstructure: back body div front text
    transcr: metamark
    May contain
    core: bibl biblStruct cit graphic head listBibl note p quote
    dictionaries: entry xr
    figures: figDesc figure
    transcr: metamark
    Example
    <figure>
+element figDesc { att.global.attributes, macro.limitedContent }

    12.1.35. <figure>

    <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]

    Modulefigures — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.global
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: authority distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: back body div front text
    transcr: metamark
    May contain
    core: bibl biblStruct cit graphic head listBibl note p quote
    dictionaries: entry xr
    figures: figDesc figure
    transcr: metamark
    Example
    <figure>
   <head>The View from the Bridge</head>
   <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
      series of buoys strung out between them.</figDesc>
@@ -2417,7 +2520,7 @@
     | model.global
     | model.divBottom
    )*
-}

    11.1.34. <fileDesc>

    <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: teiHeader
    May contain
    header: editionStmt extent notesStmt publicationStmt seriesStmt sourceDesc titleStmt
    Note

    The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

    Example
    <fileDesc>
+}

    12.1.36. <fileDesc>

    <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: teiHeader
    May contain
    header: editionStmt extent notesStmt publicationStmt seriesStmt sourceDesc titleStmt
    Note

    The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

    Example
    <fileDesc>
   <titleStmt>
      <title>The shortest possible TEI document</title>
   </titleStmt>
@@ -2429,8 +2532,8 @@
   </sourceDesc>
 </fileDesc>
    Content model
    
 <content>
- <sequence>
-  <sequence>
+ <sequence minOccurs="1" maxOccurs="1">
+  <sequence minOccurs="1" maxOccurs="1">
    <elementRef key="titleStmt"/>
    <elementRef key="editionStmt"
     minOccurs="0"/>
@@ -2442,7 +2545,7 @@
     minOccurs="0"/>
   </sequence>
   <elementRef key="sourceDesc"
-   minOccurs="1" maxOccurs="unbounded"/>
+   minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </content>
    Schema Declaration
    
@@ -2458,9 +2561,24 @@
          seriesStmt*,
          notesStmt?
       ),
-      sourceDesc+
+      sourceDesc*
    )
-}

    11.1.35. <form>

    <form> (form information group) groups all the information on the written and spoken forms of one headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    typeclassifies form as simple, compound, etc.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    simple
    single free lexical item
    lemma
    the headword itself
    variant
    a variant form
    compound
    word formed from simple lexical items
    derivative
    word derived from headword
    inflected
    word in other than usual dictionary form
    phrase
    multiple-word lexical item
    Member of
    model.entryPart model.entryPart.top model.formPart model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry form sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <form>
+}

    12.1.37. <forename>

    <forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.persNamePart
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <persName>
+  <roleName>Ex-President</roleName>
+  <forename>George</forename>
+  <surname>Bush</surname>
+</persName>
    Content model
    
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+
    Schema Declaration
    
+element forename
+{
+   att.global.attributes,
+   att.personal.attributes,
+   att.typed.attributes,
+   macro.phraseSeq
+}

    12.1.38. <form>

    <form> (form information group) groups all the information on the written and spoken forms of one headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    typeclassifies form as simple, compound, etc.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    simple
    single free lexical item
    lemma
    the headword itself
    variant
    a variant form
    compound
    word formed from simple lexical items
    derivative
    word derived from headword
    inflected
    word in other than usual dictionary form
    phrase
    multiple-word lexical item
    Member of
    model.entryPart model.entryPart.top model.formPart model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry form sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <form>
   <orth>zaptié</orth>
   <orth>zaptyé</orth>
 </form>
    (from TLFi)
    Content model
    
@@ -2499,7 +2617,7 @@
     | model.formPart
     | model.global
    )*
-}

    11.1.36. <front>

    <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: head listBibl note p
    figures: figure
    textstructure: div
    transcr: metamark
    Note

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

    Example
    <front>
+}

    12.1.39. <front>

    <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: text
    May contain
    core: head listBibl note p
    figures: figure
    textstructure: div
    transcr: metamark
    Note

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

    Example
    <front>
   <epigraph>
      <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla
            pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί
@@ -2510,7 +2628,7 @@
      <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
      </p>
   </div>
-</front>
    Example
    <front>
+</front>
    Example
    <front>
   <div type="dedication">
      <p>To our three selves</p>
   </div>
@@ -2520,7 +2638,7 @@
            author has used names that may suggest a reference to living persons
            she has done so inadvertently. ...</p>
   </div>
-</front>
    Example
    <front>
+</front>
    Example
    <front>
   <div type="abstract">
      <div>
         <head> BACKGROUND:</head>
@@ -2625,22 +2743,9 @@
          ( model.divBottom, ( model.divBottom | model.global )* )?
       )?
    )
-}

    11.1.37. <funder>

    <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.respLike
    Contained by
    core: bibl
    header: editionStmt titleStmt
    May contain
    core: date gloss hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    header: idno
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

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

    Example
    <funder>The National Endowment for the Humanities, an independent federal agency</funder>
-<funder>Directorate General XIII of the Commission of the European Communities</funder>
-<funder>The Andrew W. Mellon Foundation</funder>
-<funder>The Social Sciences and Humanities Research Council of Canada</funder>
    Content model
    
-<content>
- <macroRef key="macro.phraseSeq.limited"/>
-</content>
-
    Schema Declaration
    
-element funder
-{
-   att.global.attributes,
-   att.canonical.attributes,
-   macro.phraseSeq.limited
-}

    11.1.38. <g>

    <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    refpoints to a description of the character or glyph intended.
    StatusOptional
    Datatypeteidata.pointer
    Member of
    model.gLike
    Contained by
    analysis: c pc
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    gaiji: mapping value
    header: distributor edition extent idno licence
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May containCharacter data only
    Note

    The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

    Example
    <g ref="#ctlig">ct</g>
    This example points to a <glyph> element with the identifier ctlig like the following: 
    <glyph xml:id="ctlig">
+}

    12.1.40. <g>

    <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    refpoints to a description of the character or glyph intended.
    StatusOptional
    Datatypeteidata.pointer
    Member of
    model.gLike
    Contained by
    analysis: c pc
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    gaiji: mapping value
    header: distributor edition extent idno licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May containCharacter data only
    Note

    The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

    Example
    <g ref="#ctlig">ct</g>
    This example points to a <glyph> element with the identifier ctlig like the following: 
    <glyph xml:id="ctlig">
   <!-- here we describe the particular ct-ligature intended -->
-</glyph>
    Example
    <g ref="#per-glyph">per</g>
    The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows: 
    <glyph xml:id="per-glyph">
+</glyph>
    Example
    <g ref="#per-glyph">per</g>
    The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows: 
    <glyph xml:id="per-glyph">
   <!-- ... -->
 </glyph>
    Content model
    
 <content>
@@ -2653,7 +2758,7 @@
    att.typed.attributes,
    attribute ref { text }?,
    text
-}

    11.1.39. <gloss>

    <gloss> identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. Terms, Glosses, Equivalents, and Descriptions 22.4.1. Description of Components]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.translatable (@versionDate) att.typed (@type, @subtype) att.pointing (@targetLang, @target, @evaluate) att.cReferencing (@cRef)
    Member of
    model.emphLike
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The target and cRef attributes are mutually exclusive.

    Example
    We may define <term xml:id="tdpv" rend="sc">discoursal point of view</term> as 
+}

    12.1.41. <gloss>

    <gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.pointing (@targetLang, @target, @evaluate) att.cReferencing (@cRef)
    Member of
    model.emphLike
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The target and cRef attributes are mutually exclusive.

    Example
    We may define <term xml:id="tdpv" rend="sc">discoursal point of view</term> as 
 <gloss target="#tdpv">the relationship, expressed
  through discourse structure, between the implied author or some other addresser, and the
  fiction.</gloss>
    Content model
    
@@ -2664,12 +2769,11 @@
 element gloss
 {
    att.global.attributes,
-   att.translatable.attributes,
    att.typed.attributes,
    att.pointing.attributes,
    att.cReferencing.attributes,
    macro.phraseSeq
-}

    11.1.40. <glyph>

    <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charDecl
    May contain
    core: graphic note
    figures: figure
    gaiji: charProp glyphName localProp mapping unicodeProp unihanProp
    Example
    <glyph xml:id="rstroke">
+}

    12.1.42. <glyph>

    <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charDecl
    May contain
    core: graphic note
    figures: figure
    gaiji: charProp glyphName localProp mapping unicodeProp unihanProp
    Example
    <glyph xml:id="rstroke">
   <localProp name="Name" value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>
   <localProp name="entity" value="rstroke"/>
   <figure>
@@ -2707,13 +2811,13 @@
     | model.noteLike
     | model.descLike
    )*
-}

    11.1.41. <glyphName>

    <glyphName> (character glyph name) contains the name of a glyph, expressed following Unicode conventions for character names. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: glyph
    May containCharacter data only
    Note

    For characters of non-ideographic scripts, a name following the conventions for Unicode names should be chosen. For ideographic scripts, an Ideographic Description Sequence (IDS) as described in Chapter 10.1 of the Unicode Standard is recommended where possible. Projects working in similar fields are recommended to coordinate and publish their list of <glyphName>s to facilitate data exchange.

    Example
    <glyphName>CIRCLED IDEOGRAPH
+}

    12.1.43. <glyphName>

    <glyphName> (character glyph name) contains the name of a glyph, expressed following Unicode conventions for character names. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: glyph
    May containCharacter data only
    Note

    For characters of non-ideographic scripts, a name following the conventions for Unicode names should be chosen. For ideographic scripts, an Ideographic Description Sequence (IDS) as described in Chapter 10.1 of the Unicode Standard is recommended where possible. Projects working in similar fields are recommended to coordinate and publish their list of <glyphName>s to facilitate data exchange.

    Example
    <glyphName>CIRCLED IDEOGRAPH
  4EBA</glyphName>
    Content model
    
 <content>
  <textNode/>
 </content>
    Schema Declaration
    
-element glyphName { att.global.attributes, text }

    11.1.42. <gram>

    <gram> (grammatical information) within an entry in a dictionary or a terminological data file, contains grammatical information relating to a term, word, or form. [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRequired
    Suggested values include:
    pos
    aspect
    case
    gender
    inflectionType
    mood
    number
    tense
    transitivity
    collocate
    rection
    Member of
    model.morphLike
    Contained by
    dictionaries: dictScrap form gramGrp
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <entry>
+element glyphName { att.global.attributes, text }

    12.1.44. <gram>

    <gram> (grammatical information) within an entry in a dictionary or a terminological data file, contains grammatical information relating to a term, word, or form. [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRequired
    Suggested values include:
    pos
    aspect
    case
    gender
    inflectionType
    mood
    number
    tense
    transitivity
    collocate
    rection
    Member of
    model.morphLike
    Contained by
    dictionaries: dictScrap form gramGrp
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <entry>
   <form>
      <orth>pamplemousse</orth>
   </form>
@@ -2747,7 +2851,7 @@
     | xsd:Name
    },
    macro.paraContent
-}

    11.1.43. <gramGrp>

    <gramGrp> (grammatical information group) groups morpho-syntactic information about a lexical item, e.g. <pos>, <gen>, <number>, <case>, or <iType> (inflectional class). [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (@type, @subtype)
    Member of
    model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym form gramGrp sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: gram gramGrp lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <entry>
+}

    12.1.45. <gramGrp>

    <gramGrp> (grammatical information group) groups morpho-syntactic information about a lexical item, e.g. <pos>, <gen>, <number>, <case>, or <iType> (inflectional class). [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (@type, @subtype)
    Member of
    model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym form gramGrp sense
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: gram gramGrp lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <entry>
   <form>
      <orth>luire</orth>
   </form>
@@ -2781,12 +2885,12 @@
     | model.gramPart
     | model.global
    )*
-}

    11.1.44. <graphic>

    <graphic> indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.9. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url)
    Member of
    model.graphicLike
    Contained by
    core: author biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: distributor edition extent licence
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May containEmpty element
    Note

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

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

    Example
    <figure>
+}

    12.1.46. <graphic>

    <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url)
    Member of
    model.graphicLike
    Contained by
    core: author biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May containEmpty element
    Note

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

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

    Example
    <figure>
   <graphic url="fig1.png"/>
   <head>Figure One: The View from the Bridge</head>
   <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
      series of buoys strung out between them.</figDesc>
-</figure>
    Example
    <facsimile>
+</figure>
    Example
    <facsimile>
   <surfaceGrp n="leaf1">
      <surface>
         <graphic url="page1.png"/>
@@ -2808,7 +2912,7 @@
    att.media.attributes,
    att.resourced.attributes,
    model.descLike*
-}

    11.1.45. <head>

    <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
    Member of
    model.headLike model.pLike.front
    Contained by
    core: listBibl
    figures: figure
    textstructure: back body div front
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

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

    ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
    <div1 n="I" type="book">
+}

    12.1.47. <head>

    <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
    Member of
    model.headLike model.pLike.front
    Contained by
    core: listBibl
    figures: figure
    textstructure: back body div front
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

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

    ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
    <div1 n="I" type="book">
   <head>In the name of Christ here begins the first book of the ecclesiastical history of
      Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
   <div2 type="section">
@@ -2819,7 +2923,7 @@
      <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
            years from the beginning of the world down to the death of Saint Martin.</trailer>
   </div2>
-</div1>
    ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
    <div type="subsection">
+</div1>
    ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
    <div type="subsection">
   <head place="margin">Secunda conclusio</head>
   <p>
      <lb n="1251"/>
@@ -2828,7 +2932,7 @@
      <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
      [...]
   </p>
-</div>
    ExampleThe <head> element is also used to mark headings of other units, such as lists:
    With a few exceptions, connectives are equally
+</div>
    ExampleThe <head> element is also used to mark headings of other units, such as lists:
    With a few exceptions, connectives are equally
  useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
   <head>Connectives</head>
   <item>above</item>
@@ -2868,14 +2972,14 @@
     | model.lLike
     | model.global
    )*
-}

    11.1.46. <hi>

    <hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.written (@hand)
    Member of
    model.hiLike
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <hi rend="gothic">And this Indenture further witnesseth</hi>
+}

    12.1.48. <hi>

    <hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.written (@hand)
    Member of
    model.hiLike
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <hi rend="gothic">And this Indenture further witnesseth</hi>
  that the said <hi rend="italic">Walter Shandy</hi>, merchant,
  in consideration of the said intended marriage ...
    Content model
    
 <content>
  <macroRef key="macro.paraContent"/>
 </content>
    Schema Declaration
    
-element hi { att.global.attributes, att.written.attributes, macro.paraContent }

    11.1.47. <hyph>

    <hyph> (hyphenation) contains a hyphenated form of a dictionary headword, or hyphenation information in some other form. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <entry>
+element hi { att.global.attributes, att.written.attributes, macro.paraContent }

    12.1.49. <hyph>

    <hyph> (hyphenation) contains a hyphenated form of a dictionary headword, or hyphenation information in some other form. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <entry>
   <form>
      <orth>competitor</orth>
      <hyph>com|peti|tor</hyph>
@@ -2892,7 +2996,7 @@
    att.lexicographic.attributes,
    att.notated.attributes,
    macro.paraContent
-}

    11.1.48. <idno>

    <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
    typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    ISBN
    International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
    ISSN
    International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
    DOI
    Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
    URI
    Uniform Resource Identifier: a string of characters to uniquely identify a resource which usually contains indication of the means of accessing that resource, the name of its host, and its filepath.
    VIAF
    A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
    ESTC
    English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
    OCLC
    OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
    Member of
    model.nameLike model.publicationStmtPart.detail
    Contained by
    core: analytic author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder idno licence publicationStmt rendition seriesStmt tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    gaiji: g
    header: idno
    character data
    Note

    <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

    Example
    <idno type="ISBN">978-1-906964-22-1</idno>
+}

    12.1.50. <idno>

    <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
    typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    ISBN
    International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
    ISSN
    International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
    DOI
    Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
    URI
    Uniform Resource Identifier: a string of characters to uniquely identify a resource which usually contains indication of the means of accessing that resource, the name of its host, and its filepath.
    VIAF
    A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
    ESTC
    English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
    OCLC
    OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
    Member of
    model.nameLike model.publicationStmtPart.detail
    Contained by
    core: analytic author bibl biblScope citedRange date editor email gloss head hi monogr name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent idno licence publicationStmt rendition seriesStmt tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    gaiji: g
    header: idno
    character data
    Note

    <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

    Example
    <idno type="ISBN">978-1-906964-22-1</idno>
 <idno type="ISSN">0143-3385</idno>
 <idno type="DOI">10.1000/123</idno>
 <idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
@@ -2922,7 +3026,7 @@
       "ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
    }?,
    ( text | model.gLike | idno )*
-}

    11.1.49. <imprint>

    <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    —
    May contain
    core: biblScope date note pubPlace publisher respStmt
    figures: figure
    header: distributor
    transcr: metamark
    Example
    <imprint>
+}

    12.1.51. <imprint>

    <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    core: monogr
    May contain
    core: biblScope date note pubPlace publisher respStmt
    figures: figure
    header: distributor
    transcr: metamark
    Example
    <imprint>
   <pubPlace>Oxford</pubPlace>
   <publisher>Clarendon Press</publisher>
   <date>1987</date>
@@ -2955,7 +3059,7 @@
       ( classCode | catRef )*,
       ( ( model.imprintPart | model.dateLike ), respStmt*, model.global* )+
    )
-}

    11.1.50. <lang>

    <lang> (language name) contains the name of a language mentioned in etymological or other linguistic discussion. [9.3.4. Etymological Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    Member of
    model.nameLike
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    May contain character data mixed with phrase-level elements.

    Example
    <cit type="cognate">
+}

    12.1.52. <lang>

    <lang> (language name) contains the name of a language mentioned in etymological or other linguistic discussion. [9.3.4. Etymological Information]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    Member of
    model.nameLike
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    May contain character data mixed with phrase-level elements.

    Example
    <cit type="cognate">
   <lang>dän.</lang>
   <form>
      <orth xml:lang="da">indgang</orth>
@@ -2990,30 +3094,45 @@
    att.global.attributes,
    att.lexicographic.attributes,
    macro.paraContent
-}

    11.1.51. <langUsage>

    <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]

    Moduleheader — Specification
    Member of
    model.profileDescPart
    Contained by
    header: profileDesc
    May contain
    core: p
    header: language
    Example
    <langUsage>
-  <language ident="fr-CA" usage="60">Québecois</language>
-  <language ident="en-CA" usage="20">Canadian business English</language>
-  <language ident="en-GB" usage="20">British English</language>
+}

    12.1.53. <langUsage>

    <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]

    Moduleheader — Specification
    Member of
    model.profileDescPart
    Contained by
    header: profileDesc
    May contain
    core: p
    header: language
    Example
    <langUsage>
+  <language ident="chu" role="sourceLanguage">Old Church Slavic</language>
+  <language ident="la" role="targetLanguage">Latin</language>
+  <language ident="grc" role="targetLanguage">(Premodern) Greek</language>
 </langUsage>
    Content model
    
 <content>
- <alternate minOccurs="1" maxOccurs="1">
-  <classRef key="model.pLike" minOccurs="1"
-   maxOccurs="unbounded"/>
-  <elementRef key="language" minOccurs="1"
-   maxOccurs="unbounded"/>
- </alternate>
+ <classRef key="model.pLike" minOccurs="0"
+  maxOccurs="unbounded"/>
+ <elementRef key="language" minOccurs="1"
+  maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
-element langUsage { model.pLike+ | language+ }

    11.1.52. <language>

    <language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

    Moduleheader — Specification
    AttributesAttributes
    ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
    StatusRequired
    Datatypeteidata.language
    usagespecifies the approximate percentage (by volume) of the text which uses this language.
    StatusOptional
    DatatypenonNegativeInteger
    Contained by
    header: langUsage
    May containCharacter data only
    Note

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

    Example
    <langUsage>
-  <language ident="en-US" usage="75">modern American English</language>
-  <language ident="i-az-Arab" usage="20">Azerbaijani in Arabic script</language>
-  <language ident="x-lap" usage="05">Pig Latin</language>
+element langUsage { model.pLike*, language+ }

    12.1.54. <language>

    <language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

    Moduleheader — Specification
    AttributesAttributes
    role
    StatusRequired
    Legal values are:
    objectLanguage
    Object language is the "language being described." (ISO 16642:2017)
    workingLanguage
    Working language is the "language used to describe objects." (ISO 16642:2017)
    sourceLanguage
    Source language is the language of the content to be translated. (ISO 17100:215)
    targetLanguage
    Target language is the language of the content into which source language content is translated. (ISO 17100:215)
    ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
    StatusRequired
    Datatypeteidata.language
    usagespecifies the approximate percentage (by volume) of the text which uses this language.
    StatusOptional
    DatatypenonNegativeInteger
    Contained by
    header: langUsage
    May containCharacter data only
    Note

    In a monolingual dictionary, where the object language and the working language are the same, one should list each as a separate <language> element with a specific role attribute. A human-readable, informal prose characterization should be supplied as content for the element. When the human-readable name(s) of languages are provided in multiple languages, the attribute xml:lang should be used to indicate what language is used to name the given object or working language.

    A bilingual dictionary could be documented as having two object languages. In those cases, however, it is recommended -- and more precise -- to describe each object language as either a source language or a target language.

    Example
    <langUsage>
+  <language ident="ru" role="objectLanguage" xml:lang="ru">Русский литературный язык XIX века</language>
+  <language ident="ru" role="workingLanguage" xml:lang="ru">Современный русский язык</language>
+  <language ident="ru" role="objectLanguage" xml:lang="en">19th-century literary Russian</language>
+  <language ident="ru" role="workingLanguage" xml:lang="en">Modern Russian</language>
+</langUsage>
    Example
    <langUsage>
+  <language ident="chu" role="sourceLanguage">Old Church Slavic</language>
+  <language ident="la" role="targetLanguage">Latin</language>
+  <language ident="grc" role="targetLanguage">(Premodern) Greek</language>
 </langUsage>
    Content model
    
 <content>
  <textNode/>
 </content>
    Schema Declaration
    
-element language { attribute ident { text }, attribute usage { text }?, text }

    11.1.53. <lbl>

    <lbl> (label) contains a label for a form, example, translation, or other piece of information, e.g. abbreviation for, contraction of, literally, approximately, synonyms:, etc. [9.3.1. Information on Written and Spoken Forms 9.3.3.2. Translation Equivalents 9.3.5.3. Cross-References to Other Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    typeclassifies the label using any convenient typology.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    model.emphLike model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    Labels specifically relating to usage should be tagged with the special-purpose <usg> element rather than with the generic<lbl> element.

    Example
    <entry>
+element language
+{
+   attribute role
+   {
+      "objectLanguage"
+    | "workingLanguage"
+    | "sourceLanguage"
+    | "targetLanguage"
+   },
+   attribute ident { text },
+   attribute usage { text }?,
+   text
+}

    12.1.55. <lbl>

    <lbl> (label) contains a label for a form, example, translation, or other piece of information, e.g. abbreviation for, contraction of, literally, approximately, synonyms:, etc. [9.3.1. Information on Written and Spoken Forms 9.3.3.2. Translation Equivalents 9.3.5.3. Cross-References to Other Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    typeclassifies the label using any convenient typology.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    model.emphLike model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    Labels specifically relating to usage should be tagged with the special-purpose <usg> element rather than with the generic<lbl> element.

    Example
    <entry>
   <form type="abbrev">
      <orth>MTBF</orth>
   </form>
@@ -3033,8 +3152,8 @@
    att.lexicographic.attributes,
    attribute type { text }?,
    macro.paraContent
-}

    11.1.54. <licence>

    <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) 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
    model.availabilityPart
    Contained by
    header: availability
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

    Example
    <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
-</licence>
    Example
    <availability>
+}

    12.1.56. <licence>

    <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) 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
    model.availabilityPart
    Contained by
    header: availability
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

    Example
    <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
+</licence>
    Example
    <availability>
   <licence target="http://creativecommons.org/licenses/by/3.0/"
    notBefore="2013-01-01">
      <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
@@ -3052,7 +3171,7 @@
    att.pointing.attributes,
    att.datable.attributes,
    macro.specialPara
-}

    11.1.55. <listBibl>

    <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
    Member of
    model.biblLike model.frontPart
    Contained by
    core: cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition sourceDesc tagUsage
    linking: seg
    textstructure: back body div front
    transcr: metamark
    May contain
    core: bibl biblStruct head listBibl
    Example
    <listBibl>
+}

    12.1.57. <listBibl>

    <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
    Member of
    model.biblLike model.frontPart
    Contained by
    core: cit head hi listBibl note p quote ref title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: licence rendition tagUsage
    linking: seg
    textstructure: back body div front
    transcr: metamark
    May contain
    core: bibl biblStruct head listBibl
    Example
    <listBibl>
   <head>Works consulted</head>
   <bibl>Blain, Clements and Grundy: Feminist Companion to
      Literature in English (Yale, 1990)
@@ -3077,16 +3196,29 @@
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
-  <alternate minOccurs="1"
-   maxOccurs="unbounded">
-   <classRef key="model.biblLike"/>
-   <classRef key="model.milestoneLike"/>
-  </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
-   <elementRef key="relation"/>
-   <elementRef key="listRelation"/>
+   <classRef key="model.milestoneLike"
+    minOccurs="1" maxOccurs="1"/>
+   <elementRef key="relation" minOccurs="1"
+    maxOccurs="1"/>
+   <elementRef key="listRelation"
+    minOccurs="1" maxOccurs="1"/>
   </alternate>
+  <sequence minOccurs="1"
+   maxOccurs="unbounded">
+   <classRef key="model.biblLike"
+    minOccurs="1" maxOccurs="unbounded"/>
+   <alternate minOccurs="0"
+    maxOccurs="unbounded">
+    <classRef key="model.milestoneLike"
+     minOccurs="1" maxOccurs="1"/>
+    <elementRef key="relation"
+     minOccurs="1" maxOccurs="1"/>
+    <elementRef key="listRelation"
+     minOccurs="1" maxOccurs="1"/>
+   </alternate>
+  </sequence>
  </sequence>
 </content>
    Schema Declaration
    
@@ -3099,10 +3231,10 @@
    (
       model.headLike*,
       desc*,
-      ( model.biblLike | model.milestoneLike )+,
-      ( relation | listRelation )*
+      ( model.milestoneLike | relation | listRelation )*,
+      ( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+
    )
-}

    11.1.56. <localProp>

    <localProp> (locally defined property) provides a locally defined character (or glyph) property. [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (@name, @value, @version)
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    No definitive list of local names is proposed. However, the name entity is recommended as a means of naming the property identifying the recommended character entity name for this character or glyph.

    Example
    <char xml:id="daikanwaU4EBA">
+}

    12.1.58. <localProp>

    <localProp> (locally defined property) provides a locally defined character (or glyph) property. [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (@name, @value, @version)
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    No definitive list of local names is proposed. However, the name entity is recommended as a means of naming the property identifying the recommended character entity name for this character or glyph.

    Example
    <char xml:id="daikanwaU4EBA">
   <localProp name="name" value="CIRCLED IDEOGRAPH 4EBA"/>
   <localProp name="entity" value="daikanwa"/>
   <unicodeProp name="Decomposition_Mapping" value="circle"/>
@@ -3112,13 +3244,13 @@
  <empty/>
 </content>
    Schema Declaration
    
-element localProp { att.global.attributes, att.gaijiProp.attributes, empty }

    11.1.57. <mapping>

    <mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    Contained by
    gaiji: char glyph
    May contain
    gaiji: g
    character data
    Note

    Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph>element or contain a character that is intended to be the target of this mapping.

    Example
    <mapping type="modern">r</mapping>
+element localProp { att.global.attributes, att.gaijiProp.attributes, empty }

    12.1.59. <mapping>

    <mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
    Contained by
    gaiji: char glyph
    May contain
    gaiji: g
    character data
    Note

    Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph>element or contain a character that is intended to be the target of this mapping.

    Example
    <mapping type="modern">r</mapping>
 <mapping type="standard">人</mapping>
    Content model
    
 <content>
  <macroRef key="macro.xtext"/>
 </content>
    Schema Declaration
    
-element mapping { att.global.attributes, att.typed.attributes, macro.xtext }

    11.1.58. <metamark>

    <metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks]

    Moduletranscr — Specification
    AttributesAttributes att.spanning (@spanTo) att.placement (@place) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
    StatusOptional
    Datatypeteidata.word
    targetidentifies one or more elements to which the metamark applies.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Member of
    model.global
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    header: authority distributor edition extent funder licence
    linking: seg
    namesdates: orgName persName placeName
    textstructure: back body div front text
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <surface>
+element mapping { att.global.attributes, att.typed.attributes, macro.xtext }

    12.1.60. <metamark>

    <metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks]

    Moduletranscr — Specification
    AttributesAttributes att.spanning (@spanTo) att.placement (@place) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
    StatusOptional
    Datatypeteidata.word
    targetidentifies one or more elements to which the metamark applies.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Member of
    model.global
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi imprint name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    header: authority distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: back body div front text
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <surface>
   <metamark function="used" rend="line" target="#X2"/>
   <zone xml:id="zone-X2">
      <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>
@@ -3147,7 +3279,143 @@
    attribute function { text }?,
    attribute target { list { + } }?,
    macro.specialPara
-}

    11.1.59. <name>

    <name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (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)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

    Example
    <name type="person">Thomas Hoccleve</name>
+}

    12.1.61. <monogr>

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

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    core: biblStruct
    May contain
    core: author biblScope editor imprint note ref respStmt title
    header: authority availability edition extent idno
    Note

    May contain specialized bibliographic elements, in a prescribed order.

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

    Example
    <biblStruct>
+  <analytic>
+     <author>Chesnutt, David</author>
+     <title>Historical Editions in the States</title>
+  </analytic>
+  <monogr>
+     <title level="j">Computers and the Humanities</title>
+     <imprint>
+        <date when="1991-12">(December, 1991):</date>
+     </imprint>
+     <biblScope>25.6</biblScope>
+     <biblScope unit="page" from="377" to="380">377–380</biblScope>
+  </monogr>
+</biblStruct>
    Example
    <biblStruct type="book">
+  <monogr>
+     <author>
+        <persName>
+           <forename>Leo Joachim</forename>
+           <surname>Frachtenberg</surname>
+        </persName>
+     </author>
+     <title type="main" level="m">Lower Umpqua Texts</title>
+     <imprint>
+        <pubPlace>New York</pubPlace>
+        <publisher>Columbia University Press</publisher>
+        <date>1914</date>
+     </imprint>
+  </monogr>
+  <series>
+     <title type="main" level="s">Columbia University Contributions to
+           Anthropology</title>
+     <biblScope unit="volume">4</biblScope>
+  </series>
+</biblStruct>
    Content model
    
+<content>
+ <sequence>
+  <alternate minOccurs="0">
+   <sequence>
+    <alternate>
+     <elementRef key="author"/>
+     <elementRef key="editor"/>
+     <elementRef key="meeting"/>
+     <elementRef key="respStmt"/>
+    </alternate>
+    <alternate minOccurs="0"
+     maxOccurs="unbounded">
+     <elementRef key="author"/>
+     <elementRef key="editor"/>
+     <elementRef key="meeting"/>
+     <elementRef key="respStmt"/>
+    </alternate>
+    <elementRef key="title" minOccurs="1"
+     maxOccurs="unbounded"/>
+    <alternate minOccurs="0"
+     maxOccurs="unbounded">
+     <classRef key="model.ptrLike"/>
+     <elementRef key="idno"/>
+     <elementRef key="textLang"/>
+     <elementRef key="editor"/>
+     <elementRef key="respStmt"/>
+    </alternate>
+   </sequence>
+   <sequence>
+    <alternate minOccurs="1"
+     maxOccurs="unbounded">
+     <elementRef key="title"/>
+     <classRef key="model.ptrLike"/>
+     <elementRef key="idno"/>
+    </alternate>
+    <alternate minOccurs="0"
+     maxOccurs="unbounded">
+     <elementRef key="textLang"/>
+     <elementRef key="author"/>
+     <elementRef key="editor"/>
+     <elementRef key="meeting"/>
+     <elementRef key="respStmt"/>
+    </alternate>
+   </sequence>
+   <sequence>
+    <elementRef key="authority"/>
+    <elementRef key="idno"/>
+   </sequence>
+  </alternate>
+  <elementRef key="availability"
+   minOccurs="0" maxOccurs="unbounded"/>
+  <classRef key="model.noteLike"
+   minOccurs="0" maxOccurs="unbounded"/>
+  <sequence minOccurs="0"
+   maxOccurs="unbounded">
+   <elementRef key="edition"/>
+   <alternate minOccurs="0"
+    maxOccurs="unbounded">
+    <elementRef key="idno"/>
+    <classRef key="model.ptrLike"/>
+    <elementRef key="editor"/>
+    <elementRef key="sponsor"/>
+    <elementRef key="funder"/>
+    <elementRef key="respStmt"/>
+   </alternate>
+  </sequence>
+  <elementRef key="imprint"/>
+  <alternate minOccurs="0"
+   maxOccurs="unbounded">
+   <elementRef key="imprint"/>
+   <elementRef key="extent"/>
+   <elementRef key="biblScope"/>
+  </alternate>
+ </sequence>
+</content>
+
    Schema Declaration
    
+element monogr
+{
+   att.global.attributes,
+   (
+      (
+         (
+            ( author | editor | meeting | respStmt ),
+            ( author | editor | meeting | respStmt )*,
+            title+,
+            ( model.ptrLike | idno | textLang | editor | respStmt )*
+         )
+       | (
+            ( title | model.ptrLike | idno )+,
+            ( textLang | author | editor | meeting | respStmt )*
+         )
+       | ( authority, idno )
+      )?,
+      availability*,
+      model.noteLike*,
+      (
+         edition,
+         ( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
+      )*,
+      imprint,
+      ( imprint | extent | biblScope )*
+   )
+}

    12.1.62. <name>

    <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (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)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

    Example
    <name type="person">Thomas Hoccleve</name>
 <name type="place">Villingaholt</name>
 <name type="org">Vetus Latina Institut</name>
 <name type="person" ref="#HOC001">Occleve</name>
    Content model
    
@@ -3163,7 +3431,7 @@
    att.editLike.attributes,
    att.typed.attributes,
    macro.phraseSeq
-}

    11.1.60. <namespace>

    <namespace> supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    namespecifies the full formal name of the namespace concerned.
    StatusRequired
    Datatypeteidata.namespace
    Contained by
    header: tagsDecl
    May contain
    header: tagUsage
    Example
    <namespace name="http://www.tei-c.org/ns/1.0">
+}

    12.1.63. <namespace>

    <namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    namespecifies the full formal name of the namespace concerned.
    StatusRequired
    Datatypeteidata.namespace
    Contained by
    header: tagsDecl
    May contain
    header: tagUsage
    Example
    <namespace name="http://www.tei-c.org/ns/1.0">
   <tagUsage gi="hi" occurs="28" withId="2"> Used only to mark English words
      italicized in the copy text </tagUsage>
 </namespace>
    Content model
    
@@ -3172,7 +3440,7 @@
   maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
-element namespace { att.global.attributes, attribute name { text }, tagUsage+ }

    11.1.61. <note>

    <note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand)
    anchoredindicates whether the copy text shows the exact place of reference for the note.
    StatusOptional
    Datatypeteidata.truthValue
    Defaulttrue
    Note

    In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

    targetEndpoints to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().

    Member of
    model.noteLike
    Contained by
    core: author bibl biblScope biblStruct cit citedRange date editor gloss head hi imprint name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: authority distributor edition extent funder licence notesStmt
    linking: seg
    namesdates: orgName persName placeName
    textstructure: back body div front text
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
    And yet it is not only
+element namespace { att.global.attributes, attribute name { text }, tagUsage+ }

    12.1.64. <note>

    <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
    Member of
    model.noteLike
    Contained by
    core: author bibl biblScope biblStruct cit citedRange date editor email gloss head hi imprint monogr name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figure
    gaiji: char glyph
    header: authority distributor edition extent licence notesStmt
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: back body div front text
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
    And yet it is not only
  in the great line of Italian renaissance art, but even in the
  painterly <note place="bottom" type="gloss" resp="#MDMH">
   <term xml:lang="de">Malerisch</term>. This word has, in the German, two
@@ -3189,7 +3457,7 @@
 <respStmt xml:id="MDMH">
   <resp>translation from German to English</resp>
   <name>Hottinger, Marie Donald Mackie</name>
-</respStmt>
    For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
    ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
    Mevorakh b. Saadya's mother, the matriarch of the
+</respStmt>
    For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
    ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
    Mevorakh b. Saadya's mother, the matriarch of the
  family during the second half of the eleventh century, <note n="126" anchored="true"> The
  alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
  Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
@@ -3205,10 +3473,9 @@
    att.pointing.attributes,
    att.typed.attributes,
    att.written.attributes,
-   attribute anchored { text }?,
-   attribute targetEnd { list { + } }?,
+   att.anchoring.attributes,
    macro.specialPara
-}

    11.1.62. <notesStmt>

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

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: note
    Note

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

    Example
    <notesStmt>
+}

    12.1.65. <notesStmt>

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

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: note
    Note

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

    Example
    <notesStmt>
   <note>Historical commentary provided by Mark Cohen</note>
   <note>OCR scanning done at University of Toronto</note>
 </notesStmt>
    Content model
    
@@ -3220,7 +3487,7 @@
  </alternate>
 </content>
    Schema Declaration
    
-element notesStmt { att.global.attributes, ( model.noteLike | relatedItem )+ }

    11.1.63. <num>

    <num> (number) contains a number, written in any form. [3.5.3. Numbers and Measures]

    Modulecore — Specification
    AttributesAttributes
    valuesupplies the value of the number in standard form.
    StatusOptional
    Datatypeteidata.numeric
    Valuesa numeric value.
    Note

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

    Member of
    model.entryPart.top model.sensePart
    Contained by
    dictionaries: entry sense
    May containCharacter data only
    Note

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

    Example
    <p>I reached <num type="cardinal" value="21">twenty-one</num> on
+element notesStmt { att.global.attributes, ( model.noteLike | relatedItem )+ }

    12.1.66. <num>

    <num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]

    Modulecore — Specification
    AttributesAttributes
    valuesupplies the value of the number in standard form.
    StatusOptional
    Datatypeteidata.numeric
    Valuesa numeric value.
    Note

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

    Member of
    model.entryPart.top model.sensePart
    Contained by
    dictionaries: entry sense
    May containCharacter data only
    Note

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

    Example
    <p>I reached <num type="cardinal" value="21">twenty-one</num> on
  my <num type="ordinal" value="21">twenty-first</num> birthday</p>
 <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
   </num> cm per second.</p>
    Content model
    
@@ -3228,7 +3495,7 @@
  <textNode/>
 </content>
    Schema Declaration
    
-element num { attribute value { text }?, text }

    11.1.64. <orgName>

    <orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
+element num { attribute value { text }?, text }

    12.1.67. <orgName>

    <orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    About a year back, a question of considerable interest was agitated in the <orgName key="PAS1" type="voluntary">
   <placeName key="PEN">Pennsyla.</placeName> Abolition Society
 </orgName> [...]
    Content model
    
 <content>
@@ -3243,11 +3510,11 @@
    att.personal.attributes,
    att.typed.attributes,
    macro.phraseSeq
-}

    11.1.65. <orth>

    <orth> (orthographic form) gives the orthographic form of a dictionary headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.partials (@extent) att.notated (@notation) att.typed (type, @subtype)
    typegives the type of spelling.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <form type="infl">
+}

    12.1.68. <orth>

    <orth> (orthographic form) gives the orthographic form of a dictionary headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.partials (@extent) att.notated (@notation) att.typed (type, @subtype)
    typegives the type of spelling.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <form type="infl">
   <orth>brags</orth>
   <orth>bragging</orth>
   <orth>bragged</orth>
-</form>
    Example
    <form>
+</form>
    Example
    <form>
   <orth type="standard" xml:lang="ko-Hang">치다</orth>
   <orth type="transliterated" xml:lang="ko-Latn">chida</orth>
 </form>
    Content model
    
@@ -3265,7 +3532,7 @@
    att.notated.attributes,
    attribute type { text }?,
    macro.paraContent
-}

    11.1.66. <p>

    <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.fragmentable (@part) att.written (@hand)
    Member of
    model.pLike
    Contained by
    core: note quote
    figures: figure
    header: availability editionStmt encodingDesc langUsage licence projectDesc publicationStmt seriesStmt sourceDesc
    textstructure: back body div front
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
+}

    12.1.69. <p>

    <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.fragmentable (@part) att.written (@hand)
    Member of
    model.pLike
    Contained by
    core: note quote
    figures: figure
    header: availability editionStmt editorialDecl encodingDesc langUsage licence projectDesc seriesStmt
    textstructure: back body div front
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
      done?</q>
 </p>
 <p>
@@ -3282,7 +3549,8 @@
  |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp 
  |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
 </s:report>
    Schematron
    
-<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab.
+<s:report test="(ancestor::tei:l or ancestor::tei:lg) and not(parent::tei:figure or 
+ parent::tei:note or ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText.
 </s:report>
    Content model
    
 <content>
  <macroRef key="macro.paraContent"/>
@@ -3294,12 +3562,12 @@
    att.fragmentable.attributes,
    att.written.attributes,
    macro.paraContent
-}

    11.1.67. <pc>

    <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]

    Moduleanalysis — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig))
    forceindicates the extent to which this punctuation mark conventionally separates words or phrases
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    strong
    the punctuation mark is a word separator
    weak
    the punctuation mark is not a word separator
    inter
    the punctuation mark may or may not be a word separator
    unitprovides a name for the kind of unit delimited by this punctuation mark.
    StatusOptional
    Datatypeteidata.enumerated
    preindicates whether this punctuation mark precedes or follows the unit it delimits.
    StatusOptional
    Datatypeteidata.truthValue
    Member of
    model.segLike
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c
    gaiji: g
    character data
    Example
    <phr>
+}

    12.1.70. <pc>

    <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]

    Moduleanalysis — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig))
    forceindicates the extent to which this punctuation mark conventionally separates words or phrases
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    strong
    the punctuation mark is a word separator
    weak
    the punctuation mark is not a word separator
    inter
    the punctuation mark may or may not be a word separator
    unitprovides a name for the kind of unit delimited by this punctuation mark.
    StatusOptional
    Datatypeteidata.enumerated
    preindicates whether this punctuation mark precedes or follows the unit it delimits.
    StatusOptional
    Datatypeteidata.truthValue
    Member of
    model.segLike
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c
    gaiji: g
    character data
    Example
    <phr>
   <w>do</w>
   <w>you</w>
   <w>understand</w>
   <pc type="interrogative">?</pc>
-</phr>
    ExampleExample encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [[undefined AILALW]].
    <s>
+</phr>
    ExampleExample encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [[undefined AILALW]].
    <s>
   <w pos="PPER" msd="1.Pl.*.Nom">Wir</w>
   <w pos="VVFIN" msd="1.Pl.Pres.Ind">fahren</w>
   <w pos="APPR" msd="--">in</w>
@@ -3327,7 +3595,7 @@
    attribute unit { text }?,
    attribute pre { text }?,
    ( text | model.gLike | c | model.pPart.edit )*
-}

    11.1.68. <persName>

    <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <persName>
+}

    12.1.71. <persName>

    <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.nameLike.agent
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp respStmt term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <persName>
   <forename>Edward</forename>
   <forename>George</forename>
   <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
@@ -3346,13 +3614,13 @@
    att.personal.attributes,
    att.typed.attributes,
    macro.phraseSeq
-}

    11.1.69. <placeName>

    <placeName> contains an absolute or relative place name. [13.2.3. Place Names]

    Modulenamesdates — Specification
    AttributesAttributes 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.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.placeNamePart
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <placeName>
+}

    12.1.72. <placeName>

    <placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]

    Modulenamesdates — Specification
    AttributesAttributes 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.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.placeNamePart
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <placeName>
   <settlement>Rochester</settlement>
   <region>New York</region>
-</placeName>
    Example
    <placeName>
+</placeName>
    Example
    <placeName>
   <geogName>Arrochar Alps</geogName>
   <region>Argylshire</region>
-</placeName>
    Example
    <placeName>
+</placeName>
    Example
    <placeName>
   <measure>10 miles</measure>
   <offset>Northeast of</offset>
   <settlement>Attica</settlement>
@@ -3369,7 +3637,7 @@
    att.personal.attributes,
    att.typed.attributes,
    macro.phraseSeq
-}

    11.1.70. <profileDesc>

    <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Member of
    model.teiHeaderPart
    Contained by
    header: teiHeader
    May contain
    header: langUsage
    Note

    Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

    Example
    <profileDesc>
+}

    12.1.73. <profileDesc>

    <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: teiHeader
    May contain
    header: langUsage
    Note

    Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

    Example
    <profileDesc>
   <langUsage>
      <language ident="fr">French</language>
   </langUsage>
@@ -3393,10 +3661,10 @@
 </profileDesc>
    Content model
    
 <content>
  <classRef key="model.profileDescPart"
-  minOccurs="0" maxOccurs="unbounded"/>
+  minOccurs="1" maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
-element profileDesc { att.global.attributes, model.profileDescPart* }

    11.1.71. <projectDesc>

    <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    core: p
    Example
    <projectDesc>
+element profileDesc { att.global.attributes, model.profileDescPart+ }

    12.1.74. <projectDesc>

    <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    core: p
    Example
    <projectDesc>
   <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
 </projectDesc>
    Content model
    
 <content>
@@ -3409,7 +3677,7 @@
    att.global.attributes,
    att.declarable.attributes,
    model.pLike+
-}

    11.1.72. <pron>

    <pron> (pronunciation) contains the pronunciation(s) of the word. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation) att.partials (@extent) att.typed (@type, @subtype)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The values used to specify the notation may be taken from any appropriate project-defined list of values. Typical values might be IPA, Murray, for example.

    Example
    <entry>
+}

    12.1.75. <pron>

    <pron> (pronunciation) contains the pronunciation(s) of the word. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation) att.partials (@extent) att.typed (@type, @subtype)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The values used to specify the notation may be taken from any appropriate project-defined list of values. Typical values might be IPA, Murray, for example.

    Example
    <entry>
   <form>
      <orth>obverse</orth>
      <pron>'äb-`ərs</pron>,
@@ -3418,7 +3686,7 @@
   <gramGrp>
      <pos>n</pos>
   </gramGrp>
-</entry>
    Example
    <entry>
+</entry>
    Example
    <entry>
   <form>
      <orth>transcription</orth>
      <pron notation="IPA">trænskrɪpʃən</pron>
@@ -3440,7 +3708,7 @@
    att.partials.attributes,
    att.typed.attributes,
    macro.paraContent
-}

    11.1.73. <pubPlace>

    <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    Member of
    model.imprintPart model.publicationStmtPart.detail
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <publicationStmt>
+}

    12.1.76. <pubPlace>

    <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    Member of
    model.imprintPart model.publicationStmtPart.detail
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <publicationStmt>
   <publisher>Oxford University Press</publisher>
   <pubPlace>Oxford</pubPlace>
   <date>1989</date>
@@ -3454,18 +3722,18 @@
    att.global.attributes,
    att.naming.attributes,
    macro.phraseSeq
-}

    11.1.74. <publicationStmt>

    <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: date p pubPlace publisher ref
    header: authority availability distributor idno
    Note

    Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

    Example
    <publicationStmt>
+}

    12.1.77. <publicationStmt>

    <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: date pubPlace publisher ref
    header: authority availability distributor idno
    Note

    Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

    Example
    <publicationStmt>
   <publisher>C. Muquardt </publisher>
   <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
   <date when="1846"/>
-</publicationStmt>
    Example
    <publicationStmt>
+</publicationStmt>
    Example
    <publicationStmt>
   <publisher>Chadwyck Healey</publisher>
   <pubPlace>Cambridge</pubPlace>
   <availability>
      <p>Available under licence only</p>
   </availability>
   <date when="1992">1992</date>
-</publicationStmt>
    Example
    <publicationStmt>
+</publicationStmt>
    Example
    <publicationStmt>
   <publisher>Zea Books</publisher>
   <pubPlace>Lincoln, NE</pubPlace>
   <date>2017</date>
@@ -3475,26 +3743,24 @@
   <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
 </publicationStmt>
    Content model
    
 <content>
- <alternate>
-  <sequence minOccurs="1"
-   maxOccurs="unbounded">
-   <classRef key="model.publicationStmtPart.agency"/>
-   <classRef key="model.publicationStmtPart.detail"
-    minOccurs="0" maxOccurs="unbounded"/>
-  </sequence>
-  <classRef key="model.pLike" minOccurs="1"
-   maxOccurs="unbounded"/>
- </alternate>
+ <sequence minOccurs="1" maxOccurs="1">
+  <classRef key="model.publicationStmtPart.agency"
+   minOccurs="1" maxOccurs="unbounded"/>
+  <classRef key="model.publicationStmtPart.detail"
+   minOccurs="0" maxOccurs="unbounded"/>
+  <elementRef key="availability"/>
+ </sequence>
 </content>
    Schema Declaration
    
 element publicationStmt
 {
    att.global.attributes,
    (
-      ( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+
-    | model.pLike+
+      model.publicationStmtPart.agency+,
+      model.publicationStmtPart.detail*,
+      availability
    )
-}

    11.1.75. <publisher>

    <publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.imprintPart model.publicationStmtPart.agency
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

    Example
    <imprint>
+}

    12.1.78. <publisher>

    <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.imprintPart model.publicationStmtPart.agency
    Contained by
    core: bibl imprint
    header: publicationStmt
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

    Example
    <imprint>
   <pubPlace>Oxford</pubPlace>
   <publisher>Clarendon Press</publisher>
   <date>1987</date>
@@ -3508,7 +3774,7 @@
    att.global.attributes,
    att.canonical.attributes,
    macro.phraseSeq
-}

    11.1.76. <quote>

    <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.notated (@notation)
    Member of
    model.quoteLike
    Contained by
    core: author biblScope cit citedRange editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

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

    Example
    Lexicography has shown little sign of being affected by the
+}

    12.1.79. <quote>

    <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.notated (@notation)
    Member of
    model.quoteLike
    Contained by
    core: author biblScope cit citedRange editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note p quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

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

    Example
    Lexicography has shown little sign of being affected by the
  work of followers of J.R. Firth, probably best summarized in his
  slogan, <quote>You shall know a word by the company it
  keeps</quote>
@@ -3523,8 +3789,8 @@
    att.typed.attributes,
    att.notated.attributes,
    macro.specialPara
-}

    11.1.77. <ref>

    <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]

    Modulecore — Specification
    AttributesAttributes att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation) att.scoped (@scope) att.cReferencing (@cRef) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (type, @subtype)
    type
    StatusRequired
    Suggested values include:
    entry
    sense
    bibliography
    Member of
    model.ptrLike
    Contained by
    core: analytic author bibl biblScope biblStruct cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence publicationStmt rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The target and cRef attributes are mutually exclusive.

    Example
    See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
- sentence</ref>
    Example
    See also <ref target="#locution">s.v. <term>locution</term>
+}

    12.1.80. <ref>

    <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]

    Modulecore — Specification
    AttributesAttributes att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation) att.scoped (@scope) att.cReferencing (@cRef) att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (type, @subtype)
    type
    StatusRequired
    Suggested values include:
    entry
    sense
    bibliography
    Member of
    model.ptrLike
    Contained by
    core: analytic author bibl biblScope biblStruct cit citedRange date editor email gloss head hi monogr name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence publicationStmt rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The target and cRef attributes are mutually exclusive.

    Example
    See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
+ sentence</ref>
    Example
    See also <ref target="#locution">s.v. <term>locution</term>
 </ref>.
    Schematron
    
 <s:report test="@target and @cRef">Only one of the
  attributes @target' and @cRef' may be supplied on <s:name/>
@@ -3545,12 +3811,12 @@
    att.typed.attribute.subtype,
    attribute type { "entry" | "sense" | "bibliography" | xsd:Name },
    macro.paraContent
-}

    11.1.78. <rendition>

    <rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.styleDef (@scheme, @schemeVersion)
    scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    first-line
    styling applies to the first line of the target element
    first-letter
    styling applies to the first letter of the target element
    before
    styling should be applied immediately before the content of the target element
    after
    styling should be applied immediately after the content of the target element
    selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
    StatusOptional
    Datatypeteidata.text
    <rendition scheme="css"
+}

    12.1.81. <rendition>

    <rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.styleDef (@scheme, @schemeVersion)
    scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    first-line
    styling applies to the first line of the target element
    first-letter
    styling applies to the first letter of the target element
    before
    styling should be applied immediately before the content of the target element
    after
    styling should be applied immediately after the content of the target element
    selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
    StatusOptional
    Datatypeteidata.text
    <rendition scheme="css"
  selector="text, front, back, body, div, p, ab"> 
  display: block;
-</rendition>
    <rendition scheme="css"
+</rendition>
    <rendition scheme="css"
  selector="*[rend*=italic]"> font-style: italic;
-</rendition>
    Note

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

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

    Contained by
    header: tagsDecl
    May contain
    core: bibl biblStruct cit date gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: orgName persName placeName
    character data
    Example
    <tagsDecl>
+</rendition>
    Note

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

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

    Contained by
    header: tagsDecl
    May contain
    core: bibl biblStruct cit date email gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: forename orgName persName placeName surname
    character data
    Example
    <tagsDecl>
   <rendition xml:id="r-center" scheme="css">text-align: center;</rendition>
   <rendition xml:id="r-small" scheme="css">font-size: small;</rendition>
   <rendition xml:id="r-large" scheme="css">font-size: large;</rendition>
@@ -3567,7 +3833,7 @@
    attribute scope { text }?,
    attribute selector { text }?,
    macro.limitedContent
-}

    11.1.79. <resp>

    <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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))
    Contained by
    core: respStmt
    May contain
    core: date gloss hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    header: idno
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

    Example
    <respStmt>
+}

    12.1.82. <resp>

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

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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))
    Contained by
    core: respStmt
    May contain
    core: date email gloss hi name note ref term title
    dictionaries: lang lbl
    figures: figure
    header: idno
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

    Example
    <respStmt>
   <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
   <name>Edward Child</name>
 </respStmt>
    Content model
    
@@ -3581,10 +3847,10 @@
    att.canonical.attributes,
    att.datable.attributes,
    macro.phraseSeq.limited
-}

    11.1.80. <respStmt>

    <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.respLike
    Contained by
    core: analytic bibl imprint
    header: editionStmt seriesStmt titleStmt
    May contain
    core: name note resp
    namesdates: orgName persName
    Example
    <respStmt>
+}

    12.1.83. <respStmt>

    <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
    Member of
    model.respLike
    Contained by
    core: analytic bibl imprint monogr
    header: editionStmt seriesStmt titleStmt
    May contain
    core: name note resp
    namesdates: orgName persName
    Example
    <respStmt>
   <resp>transcribed from original ms</resp>
   <persName>Claus Huitfeldt</persName>
-</respStmt>
    Example
    <respStmt>
+</respStmt>
    Example
    <respStmt>
   <resp>converted to XML encoding</resp>
   <name>Alan Morrison</name>
 </respStmt>
    Content model
    
@@ -3617,10 +3883,27 @@
       ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
       note*
    )
-}

    11.1.81. <seg>

    <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]

    Modulelinking — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.written (@hand) att.notated (@notation)
    Member of
    model.segLike
    Contained by
    core: author bibl biblScope cit citedRange date editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

    Example
    <seg>When are you leaving?</seg>
-<seg>Tomorrow.</seg>
    Example
    <s>
+}

    12.1.84. <revisionDesc>

    <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.docStatus (@status)
    Contained by
    header: teiHeader
    May containEmpty element
    Note

    If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.

    Example
    <revisionDesc status="embargoed">
+  <change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
+</revisionDesc>
    Content model
    
+<content>
+ <alternate>
+  <elementRef key="list"/>
+  <elementRef key="listChange"/>
+  <elementRef key="change" minOccurs="1"
+   maxOccurs="unbounded"/>
+ </alternate>
+</content>
+
    Schema Declaration
    
+element revisionDesc
+{
+   att.global.attributes,
+   att.docStatus.attributes,
+   ( list | listChange | change+ )
+}

    12.1.85. <seg>

    <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]

    Modulelinking — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.written (@hand) att.notated (@notation)
    Member of
    model.segLike
    Contained by
    core: author bibl biblScope cit citedRange date editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    header: distributor edition extent licence
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

    Example
    <seg>When are you leaving?</seg>
+<seg>Tomorrow.</seg>
    Example
    <s>
   <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield. 
-</s>
    Example
    <seg type="preamble">
+</s>
    Example
    <seg type="preamble">
   <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
   <seg>Sinfiotli was the eldest of his sons ...</seg>
   <seg>Borghild, Sigmund's wife, had a brother ... </seg>
@@ -3637,7 +3920,7 @@
    att.written.attributes,
    att.notated.attributes,
    macro.paraContent
-}

    11.1.82. <sense>

    <sense> groups together all information relating to one word sense in a dictionary entry, for example definitions, examples, and translation equivalents. [9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.global (xml:id, @n, @xml:lang) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    Derived fromatt.global
    StatusRequired
    DatatypeID
    Member of
    model.entryPart model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry sense
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note num ref term title
    dictionaries: def entry etym form gramGrp lang lbl sense usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    Note

    May contain character data mixed with any other elements defined in the dictionary tag set.

    Example
    <sense n="2">
+}

    12.1.86. <sense>

    <sense> groups together all information relating to one word sense in a dictionary entry, for example definitions, examples, and translation equivalents. [9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.global (xml:id, @n, @xml:lang) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    Derived fromatt.global
    StatusRequired
    DatatypeID
    Member of
    model.entryPart model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry sense
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note num ref term title
    dictionaries: def entry etym form gramGrp lang lbl sense usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    Note

    May contain character data mixed with any other elements defined in the dictionary tag set.

    Example
    <sense n="2">
   <usg type="time">Vx.</usg>
   <def>Vaillance, bravoure (spécial., au combat)</def>
   <cit type="example">
@@ -3681,7 +3964,7 @@
    att.lexicographic.attributes,
    attribute xml:id { text },
    ( model.gLike | model.sensePart | model.phrase | model.global )*
-}

    11.1.83. <seriesStmt>

    <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Contained by
    header: fileDesc
    May contain
    core: biblScope editor p respStmt title
    header: idno
    Example
    <seriesStmt>
+}

    12.1.87. <seriesStmt>

    <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Contained by
    header: fileDesc
    May contain
    core: biblScope editor p respStmt title
    header: idno
    Example
    <seriesStmt>
   <title>Machine-Readable Texts for the Study of Indian Literature</title>
   <respStmt>
      <resp>ed. by</resp>
@@ -3716,37 +3999,33 @@
    att.global.attributes,
    att.declarable.attributes,
    ( model.pLike+ | ( title+, ( editor | respStmt )*, ( idno | biblScope )* ) )
-}

    11.1.84. <sourceDesc>

    <sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Contained by
    header: fileDesc
    May contain
    core: bibl biblStruct listBibl p
    Example
    <sourceDesc>
-  <bibl>
-     <title level="a">The Interesting story of the Children in the Wood</title>. In
-  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
-  <publisher>OUP</publisher>
-     <date>1968</date>. </bibl>
-</sourceDesc>
    Example
    <sourceDesc>
-  <p>Born digital: no previous source exists.</p>
+}

    12.1.88. <sourceDesc>

    <sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
    Contained by
    header: fileDesc
    May contain
    core: biblStruct
    Example
    <sourceDesc>
+  <biblStruct>
+     <monogr>
+        <author>
+           <surname>Miklosich</surname>
+           <forename>Franz</forename>
+        </author>
+        <title>Lexicon Palaeoslovenico-Graeco-Latinum</title>
+        <imprint>
+           <publisher>Guilelmus Braumueller</publisher>
+           <pubPlace>Vindobonae</pubPlace>
+           <date>1862</date>
+        </imprint>
+     </monogr>
+  </biblStruct>
 </sourceDesc>
    Content model
    
 <content>
- <alternate>
-  <classRef key="model.pLike" minOccurs="1"
-   maxOccurs="unbounded"/>
-  <alternate minOccurs="1"
-   maxOccurs="unbounded">
-   <classRef key="model.biblLike"/>
-   <classRef key="model.sourceDescPart"/>
-   <classRef key="model.listLike"/>
-  </alternate>
- </alternate>
+ <elementRef key="biblStruct" minOccurs="1"
+  maxOccurs="unbounded"/>
 </content>
    Schema Declaration
    
 element sourceDesc
 {
    att.global.attributes,
    att.declarable.attributes,
-   (
-      model.pLike+
-    | ( model.biblLike | model.sourceDescPart | model.listLike )+
-   )
-}

    11.1.85. <stress>

    <stress> contains the stress pattern for a dictionary headword, if given separately. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.notated (@notation)
    Member of
    model.formPart
    Contained by
    dictionaries: form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    Usually stress information is included within pronunciation information.

    Example
    <form>
+   biblStruct+
+}

    12.1.89. <stress>

    <stress> (stress) contains the stress pattern for a dictionary headword, if given separately. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.notated (@notation)
    Member of
    model.formPart
    Contained by
    dictionaries: form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    Usually stress information is included within pronunciation information.

    Example
    <form>
   <orth>alternating current</orth>
   <stress>,....'..</stress>
 </form>
    Content model
    
@@ -3759,7 +4038,18 @@
    att.global.attributes,
    att.notated.attributes,
    macro.paraContent
-}

    11.1.86. <syll>

    <syll> (syllabification) contains the syllabification of the headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <form>
+}

    12.1.90. <surname>

    <surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]

    Modulenamesdates — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
    Member of
    model.persNamePart
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <surname type="combine">St John Stevas</surname>
    Content model
    
+<content>
+ <macroRef key="macro.phraseSeq"/>
+</content>
+
    Schema Declaration
    
+element surname
+{
+   att.global.attributes,
+   att.personal.attributes,
+   att.typed.attributes,
+   macro.phraseSeq
+}

    12.1.91. <syll>

    <syll> (syllabification) contains the syllabification of the headword. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
    Member of
    model.entryPart model.formPart
    Contained by
    core: cit
    dictionaries: dictScrap form
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <form>
   <orth>area</orth>
   <hyph>ar|ea</hyph>
   <syll>ar|e|a</syll>
@@ -3774,7 +4064,7 @@
    att.lexicographic.attributes,
    att.notated.attributes,
    macro.paraContent
-}

    11.1.87. <tagUsage>

    <tagUsage> documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent <namespace> element.
    StatusRequired
    Datatypeteidata.name
    occursspecifies the number of occurrences of this element within the text.
    StatusRecommended
    Datatypeteidata.count
    withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
    StatusRecommended
    Datatypeteidata.count
    Contained by
    header: namespace
    May contain
    core: bibl biblStruct cit date gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: orgName persName placeName
    character data
    Example
    <tagsDecl partial="true">
+}

    12.1.92. <tagUsage>

    <tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent <namespace> element.
    StatusRequired
    Datatypeteidata.name
    occursspecifies the number of occurrences of this element within the text.
    StatusRecommended
    Datatypeteidata.count
    withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
    StatusRecommended
    Datatypeteidata.count
    Contained by
    header: namespace
    May contain
    core: bibl biblStruct cit date email gloss hi listBibl name quote ref term title
    dictionaries: lang lbl xr
    header: idno
    namesdates: forename orgName persName placeName surname
    character data
    Example
    <tagsDecl partial="true">
   <rendition xml:id="it" scheme="css" selector="foreign, hi"> font-style: italic; </rendition>
   <!-- ... -->
   <namespace name="http://www.tei-c.org/ns/1.0">
@@ -3794,7 +4084,7 @@
    attribute occurs { text }?,
    attribute withId { text }?,
    macro.limitedContent
-}

    11.1.88. <tagsDecl>

    <tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
    StatusRecommended
    Datatypeteidata.truthValue
    Note

    TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    header: namespace rendition
    Example
    <tagsDecl partial="true">
+}

    12.1.93. <tagsDecl>

    <tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
    StatusRecommended
    Datatypeteidata.truthValue
    Note

    TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

    Member of
    model.encodingDescPart
    Contained by
    header: encodingDesc
    May contain
    header: namespace rendition
    Example
    <tagsDecl partial="true">
   <rendition xml:id="rend-it" scheme="css" selector="emph, hi, name, title">font-style: italic;</rendition>
   <namespace name="http://www.tei-c.org/ns/1.0">
      <tagUsage gi="hi" occurs="467"/>
@@ -3818,7 +4108,7 @@
    att.global.attributes,
    attribute partial { text }?,
    ( rendition*, namespace* )
-}

    11.1.89. <teiHeader>

    <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: TEI
    May contain
    header: encodingDesc fileDesc profileDesc
    Note

    One of the few elements unconditionally required in any TEI document.

    Example
    <teiHeader>
+}

    12.1.94. <teiHeader>

    <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    textstructure: TEI
    May contain
    header: encodingDesc fileDesc profileDesc revisionDesc xenoData
    Note

    One of the few elements unconditionally required in any TEI document.

    Example
    <teiHeader>
   <fileDesc>
      <titleStmt>
         <title>Shakespeare: the first folio (1623) in electronic form</title>
@@ -3891,10 +4181,13 @@
   </revisionDesc>
 </teiHeader>
    Content model
    
 <content>
- <sequence>
+ <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="fileDesc"/>
-  <classRef key="model.teiHeaderPart"
-   minOccurs="0" maxOccurs="unbounded"/>
+  <elementRef key="encodingDesc"
+   minOccurs="0"/>
+  <elementRef key="profileDesc"
+   minOccurs="1"/>
+  <elementRef key="xenoData" minOccurs="0"/>
   <elementRef key="revisionDesc"
    minOccurs="0"/>
  </sequence>
@@ -3903,16 +4196,16 @@
 element teiHeader
 {
    att.global.attributes,
-   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
-}

    11.1.90. <term>

    <term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
    Member of
    model.emphLike
    Contained by
    core: author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

    In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

    As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

    Example
    A computational device that infers structure
+   ( fileDesc, encodingDesc?, profileDesc, xenoData?, revisionDesc? )
+}

    12.1.95. <term>

    <term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
    Member of
    model.emphLike
    Contained by
    core: author bibl biblScope citedRange date editor email gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: cit date email gloss graphic hi name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

    In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

    As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

    Example
    A computational device that infers structure
  from grammatical strings of words is known as a <term>parser</term>, and much of the history
- of NLP over the last 20 years has been occupied with the design of parsers.
    Example
    We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as 
+ of NLP over the last 20 years has been occupied with the design of parsers.
    Example
    We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as 
 <gloss target="#TDPV1">the relationship, expressed
  through discourse structure, between the implied author or some other addresser, and the
- fiction.</gloss>
    Example
    We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as 
+ fiction.</gloss>
    Example
    We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as 
 <gloss xml:id="TDPV2">the relationship, expressed
  through discourse structure, between the implied author or some other addresser, and the
- fiction.</gloss>
    Example
    We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
    Content model
    
+ fiction.</gloss>
    Example
    We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
    Content model
    
 <content>
  <macroRef key="macro.phraseSeq"/>
 </content>
@@ -3926,7 +4219,7 @@
    att.sortable.attributes,
    att.cReferencing.attributes,
    macro.phraseSeq
-}

    11.1.91. <text>

    <text> contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.resource
    Contained by
    textstructure: TEI
    May contain
    core: note
    figures: figure
    textstructure: back body front
    transcr: metamark
    Note

    This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

    Example
    <text>
+}

    12.1.96. <text>

    <text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]

    Moduletextstructure — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand)
    Member of
    model.resource
    Contained by
    textstructure: TEI
    May contain
    core: note
    figures: figure
    textstructure: back body front
    transcr: metamark
    Note

    This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

    Example
    <text>
   <front>
      <docTitle>
         <titlePart>Autumn Haze</titlePart>
@@ -3936,7 +4229,7 @@
      <l>Is it a dragonfly or a maple leaf</l>
      <l>That settles softly down upon the water?</l>
   </body>
-</text>
    ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
    <text>
+</text>
    ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
    <text>
   <front>
      <!-- front matter for the whole group -->
   </front>
@@ -3984,10 +4277,10 @@
       model.global*,
       ( back, model.global* )?
    )
-}

    11.1.92. <title>

    <title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.typed (type, @subtype)
    typeclassifies the title according to some convenient typology.
    Derived fromatt.typed
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    main
    main title
    sub
    (subordinate) subtitle, title of part
    alt
    (alternate) alternate title, often in another language, by which the work is also known
    short
    abbreviated form of title
    desc
    (descriptive) descriptive paraphrase of the work functioning as a title
    Note

    This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.

    levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    a
    (analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
    m
    (monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
    j
    (journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
    s
    (series) the title applies to a series of otherwise distinct publications such as a collection
    u
    (unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
    Note

    The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

    Member of
    model.emphLike
    Contained by
    core: analytic author bibl biblScope citedRange date editor gloss head hi name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent funder licence rendition seriesStmt tagUsage titleStmt
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Note

    The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

    Example
    <title>Information Technology and the Research Process: Proceedings of
+}

    12.1.97. <title>

    <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]

    Modulecore — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.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.typed (type, @subtype)
    type
    StatusRecommended
    Sample values include
    full
    The full title of a lexicographic resource, such as 
    <title type="full">The Oxford English Dictionary</title>
    .
    abbr
    The preferred abbreviated title of a lexicographic resource, such as the 
    <title type="abbr">OED</title>
    .
    levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    a
    (analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
    m
    (monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
    j
    (journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
    s
    (series) the title applies to a series of otherwise distinct publications such as a collection
    u
    (unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
    Note

    The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

    Member of
    model.emphLike
    Contained by
    core: analytic author bibl biblScope citedRange date editor email gloss head hi monogr name note p pubPlace publisher quote ref resp term title
    dictionaries: def dictScrap etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc
    header: authority distributor edition extent licence rendition seriesStmt tagUsage titleStmt
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Note

    The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

    Example
    <title>Information Technology and the Research Process: Proceedings of
  a conference held at Cranfield Institute of Technology, UK,
- 18–21 July 1989</title>
    Example
    <title>Hardy's Tess of the D'Urbervilles: a machine readable
- edition</title>
    Example
    <title type="full">
+ 18–21 July 1989</title>
    Example
    <title>Hardy's Tess of the D'Urbervilles: a machine readable
+ edition</title>
    Example
    <title type="full">
   <title type="main">Synthèse</title>
   <title type="sub">an international journal for
      epistemology, methodology and history of
@@ -4006,7 +4299,7 @@
    attribute type { text }?,
    attribute level { "a" | "m" | "j" | "s" | "u" }?,
    macro.paraContent
-}

    11.1.93. <titleStmt>

    <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: author editor respStmt title
    header: funder
    Example
    <titleStmt>
+}

    12.1.98. <titleStmt>

    <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    header: fileDesc
    May contain
    core: author editor respStmt title
    Example
    <titleStmt>
   <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
   <respStmt>
      <resp>compiled by</resp>
@@ -4022,7 +4315,7 @@
  </sequence>
 </content>
    Schema Declaration
    
-element titleStmt { att.global.attributes, ( title+, model.respLike* ) }

    11.1.94. <unicodeName>

    <unicodeName> (Unicode property name) contains the name of a registered Unicode normative or informative property. [5.2.1. Character Properties]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    versionspecifies the version number of the Unicode Standard in which this property name is defined.
    StatusOptional
    Datatypeteidata.version
    Contained by
    gaiji: charProp
    May containCharacter data only
    Note

    A definitive list of current Unicode property names is provided in The Unicode Standard.

    Example
    <unicodeName>Decomposition_Mapping</unicodeName>
+element titleStmt { att.global.attributes, ( title+, model.respLike* ) }

    12.1.99. <unicodeName>

    <unicodeName> (Unicode property name) contains the name of a registered Unicode normative or informative property. [5.2.1. Character Properties]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    versionspecifies the version number of the Unicode Standard in which this property name is defined.
    StatusOptional
    Datatypeteidata.version
    Contained by
    gaiji: charProp
    May containCharacter data only
    Note

    A definitive list of current Unicode property names is provided in The Unicode Standard.

    Example
    <unicodeName>Decomposition_Mapping</unicodeName>
 <unicodeName>General_Category</unicodeName>
    Content model
    
 <content>
  <textNode/>
@@ -4033,7 +4326,7 @@
    att.global.attributes,
    attribute version { text }?,
    text
-}

    11.1.95. <unicodeProp>

    <unicodeProp> (unicode property) provides a Unicode property for a character (or glyph). [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
    namespecifies the normalized name of a Unicode property.
    StatusRequired
    Datatypeteidata.xmlName
    Legal values are:
    Age
    AHex
    Alpha
    Alphabetic
    ASCII_Hex_Digit
    bc
    Bidi_C
    Bidi_Class
    Bidi_Control
    Bidi_M
    Bidi_Mirrored
    Bidi_Mirroring_Glyph
    Bidi_Paired_Bracket
    Bidi_Paired_Bracket_Type
    blk
    Block
    bmg
    bpb
    bpt
    Canonical_Combining_Class
    Case_Folding
    Case_Ignorable
    Cased
    ccc
    CE
    cf
    Changes_When_Casefolded
    Changes_When_Casemapped
    Changes_When_Lowercased
    Changes_When_NFKC_Casefolded
    Changes_When_Titlecased
    Changes_When_Uppercased
    CI
    Comp_Ex
    Composition_Exclusion
    CWCF
    CWCM
    CWKCF
    CWL
    CWT
    CWU
    Dash
    Decomposition_Mapping
    Decomposition_Type
    Default_Ignorable_Code_Point
    Dep
    Deprecated
    DI
    Dia
    Diacritic
    dm
    dt
    ea
    East_Asian_Width
    EqUIdeo
    Equivalent_Unified_Ideograph
    Expands_On_NFC
    Expands_On_NFD
    Expands_On_NFKC
    Expands_On_NFKD
    Ext
    Extender
    FC_NFKC
    FC_NFKC_Closure
    Full_Composition_Exclusion
    gc
    GCB
    General_Category
    Gr_Base
    Gr_Ext
    Gr_Link
    Grapheme_Base
    Grapheme_Cluster_Break
    Grapheme_Extend
    Grapheme_Link
    Hangul_Syllable_Type
    Hex
    Hex_Digit
    hst
    Hyphen
    ID_Continue
    ID_Start
    IDC
    Ideo
    Ideographic
    IDS
    IDS_Binary_Operator
    IDS_Trinary_Operator
    IDSB
    IDST
    Indic_Positional_Category
    Indic_Syllabic_Category
    InPC
    InSC
    isc
    ISO_Comment
    Jamo_Short_Name
    jg
    Join_C
    Join_Control
    Joining_Group
    Joining_Type
    JSN
    jt
    kAccountingNumeric
    kCompatibilityVariant
    kIICore
    kIRG_GSource
    kIRG_HSource
    kIRG_JSource
    kIRG_KPSource
    kIRG_KSource
    kIRG_MSource
    kIRG_TSource
    kIRG_USource
    kIRG_VSource
    kOtherNumeric
    kPrimaryNumeric
    kRSUnicode
    lb
    lc
    Line_Break
    LOE
    Logical_Order_Exception
    Lower
    Lowercase
    Lowercase_Mapping
    Math
    na
    na1
    Name
    Name_Alias
    NChar
    NFC_QC
    NFC_Quick_Check
    NFD_QC
    NFD_Quick_Check
    NFKC_Casefold
    NFKC_CF
    NFKC_QC
    NFKC_Quick_Check
    NFKD_QC
    NFKD_Quick_Check
    Noncharacter_Code_Point
    nt
    Numeric_Type
    Numeric_Value
    nv
    OAlpha
    ODI
    OGr_Ext
    OIDC
    OIDS
    OLower
    OMath
    Other_Alphabetic
    Other_Default_Ignorable_Code_Point
    Other_Grapheme_Extend
    Other_ID_Continue
    Other_ID_Start
    Other_Lowercase
    Other_Math
    Other_Uppercase
    OUpper
    Pat_Syn
    Pat_WS
    Pattern_Syntax
    Pattern_White_Space
    PCM
    Prepended_Concatenation_Mark
    QMark
    Quotation_Mark
    Radical
    Regional_Indicator
    RI
    SB
    sc
    scf
    Script
    Script_Extensions
    scx
    SD
    Sentence_Break
    Sentence_Terminal
    Simple_Case_Folding
    Simple_Lowercase_Mapping
    Simple_Titlecase_Mapping
    Simple_Uppercase_Mapping
    slc
    Soft_Dotted
    stc
    STerm
    suc
    tc
    Term
    Terminal_Punctuation
    Titlecase_Mapping
    uc
    UIdeo
    Unicode_1_Name
    Unified_Ideograph
    Upper
    Uppercase
    Uppercase_Mapping
    Variation_Selector
    Vertical_Orientation
    vo
    VS
    WB
    White_Space
    Word_Break
    WSpace
    XID_Continue
    XID_Start
    XIDC
    XIDS
    XO_NFC
    XO_NFD
    XO_NFKC
    XO_NFKD
    valuespecifies the value of a named Unicode property.
    StatusRequired
    Datatypeteidata.text
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    A definitive list of current Unicode property names is provided in The Unicode Standard.

    Example
    <char xml:id="U4EBA_circled">
+}

    12.1.100. <unicodeProp>

    <unicodeProp> (unicode property) provides a Unicode property for a character (or glyph). [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
    namespecifies the normalized name of a Unicode property.
    StatusRequired
    Datatypeteidata.xmlName
    Legal values are:
    Age
    AHex
    Alpha
    Alphabetic
    ASCII_Hex_Digit
    bc
    Bidi_C
    Bidi_Class
    Bidi_Control
    Bidi_M
    Bidi_Mirrored
    Bidi_Mirroring_Glyph
    Bidi_Paired_Bracket
    Bidi_Paired_Bracket_Type
    blk
    Block
    bmg
    bpb
    bpt
    Canonical_Combining_Class
    Case_Folding
    Case_Ignorable
    Cased
    ccc
    CE
    cf
    Changes_When_Casefolded
    Changes_When_Casemapped
    Changes_When_Lowercased
    Changes_When_NFKC_Casefolded
    Changes_When_Titlecased
    Changes_When_Uppercased
    CI
    Comp_Ex
    Composition_Exclusion
    CWCF
    CWCM
    CWKCF
    CWL
    CWT
    CWU
    Dash
    Decomposition_Mapping
    Decomposition_Type
    Default_Ignorable_Code_Point
    Dep
    Deprecated
    DI
    Dia
    Diacritic
    dm
    dt
    ea
    East_Asian_Width
    EqUIdeo
    Equivalent_Unified_Ideograph
    Expands_On_NFC
    Expands_On_NFD
    Expands_On_NFKC
    Expands_On_NFKD
    Ext
    Extender
    FC_NFKC
    FC_NFKC_Closure
    Full_Composition_Exclusion
    gc
    GCB
    General_Category
    Gr_Base
    Gr_Ext
    Gr_Link
    Grapheme_Base
    Grapheme_Cluster_Break
    Grapheme_Extend
    Grapheme_Link
    Hangul_Syllable_Type
    Hex
    Hex_Digit
    hst
    Hyphen
    ID_Continue
    ID_Start
    IDC
    Ideo
    Ideographic
    IDS
    IDS_Binary_Operator
    IDS_Trinary_Operator
    IDSB
    IDST
    Indic_Positional_Category
    Indic_Syllabic_Category
    InPC
    InSC
    isc
    ISO_Comment
    Jamo_Short_Name
    jg
    Join_C
    Join_Control
    Joining_Group
    Joining_Type
    JSN
    jt
    kAccountingNumeric
    kCompatibilityVariant
    kIICore
    kIRG_GSource
    kIRG_HSource
    kIRG_JSource
    kIRG_KPSource
    kIRG_KSource
    kIRG_MSource
    kIRG_TSource
    kIRG_USource
    kIRG_VSource
    kOtherNumeric
    kPrimaryNumeric
    kRSUnicode
    lb
    lc
    Line_Break
    LOE
    Logical_Order_Exception
    Lower
    Lowercase
    Lowercase_Mapping
    Math
    na
    na1
    Name
    Name_Alias
    NChar
    NFC_QC
    NFC_Quick_Check
    NFD_QC
    NFD_Quick_Check
    NFKC_Casefold
    NFKC_CF
    NFKC_QC
    NFKC_Quick_Check
    NFKD_QC
    NFKD_Quick_Check
    Noncharacter_Code_Point
    nt
    Numeric_Type
    Numeric_Value
    nv
    OAlpha
    ODI
    OGr_Ext
    OIDC
    OIDS
    OLower
    OMath
    Other_Alphabetic
    Other_Default_Ignorable_Code_Point
    Other_Grapheme_Extend
    Other_ID_Continue
    Other_ID_Start
    Other_Lowercase
    Other_Math
    Other_Uppercase
    OUpper
    Pat_Syn
    Pat_WS
    Pattern_Syntax
    Pattern_White_Space
    PCM
    Prepended_Concatenation_Mark
    QMark
    Quotation_Mark
    Radical
    Regional_Indicator
    RI
    SB
    sc
    scf
    Script
    Script_Extensions
    scx
    SD
    Sentence_Break
    Sentence_Terminal
    Simple_Case_Folding
    Simple_Lowercase_Mapping
    Simple_Titlecase_Mapping
    Simple_Uppercase_Mapping
    slc
    Soft_Dotted
    stc
    STerm
    suc
    tc
    Term
    Terminal_Punctuation
    Titlecase_Mapping
    uc
    UIdeo
    Unicode_1_Name
    Unified_Ideograph
    Upper
    Uppercase
    Uppercase_Mapping
    Variation_Selector
    Vertical_Orientation
    vo
    VS
    WB
    White_Space
    Word_Break
    WSpace
    XID_Continue
    XID_Start
    XIDC
    XIDS
    XO_NFC
    XO_NFD
    XO_NFKC
    XO_NFKD
    valuespecifies the value of a named Unicode property.
    StatusRequired
    Datatypeteidata.text
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    A definitive list of current Unicode property names is provided in The Unicode Standard.

    Example
    <char xml:id="U4EBA_circled">
   <unicodeProp name="Decomposition_Mapping" value="circle" version="12.1"/>
   <localProp name="Name" value="CIRCLED IDEOGRAPH 4EBA"/>
   <localProp name="daikanwa" value="36"/>
@@ -4272,7 +4565,7 @@
    },
    attribute value { text },
    empty
-}

    11.1.96. <unihanProp>

    <unihanProp> (unihan property) holds the name and value of a normative or informative Unihan character (or glyph) property as part of its attributes. [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
    namespecifies the normalized name of a unicode han database (Unihan) property
    StatusRequired
    Datatypeteidata.xmlName
    Legal values are:
    kZVariant
    kAccountingNumeric
    kBigFive
    kCCCII
    kCNS1986
    kCNS1992
    kCangjie
    kCantonese
    kCheungBauer
    kCheungBauerIndex
    kCihaiT
    kCompatibilityVariant
    kCowles
    kDaeJaweon
    kDefinition
    kEACC
    kFenn
    kFennIndex
    kFourCornerCode
    kFrequency
    kGB0
    kGB1
    kGB3
    kGB5
    kGB7
    kGB8
    kGSR
    kGradeLevel
    kHDZRadBreak
    kHKGlyph
    kHKSCS
    kHanYu
    kHangul
    kHanyuPinlu
    kHanyuPinyin
    kIBMJapan
    kIICore
    kIRGDaeJaweon
    kIRGDaiKanwaZiten
    kIRGHanyuDaZidian
    kIRGKangXi
    kIRG_GSource
    kIRG_HSource
    kIRG_JSource
    kIRG_KPSource
    kIRG_KSource
    kIRG_MSource
    kIRG_TSource
    kIRG_USource
    kIRG_VSource
    kJIS0213
    kJa
    kJapaneseKun
    kJapaneseOn
    kJinmeiyoKanji
    kJis0
    kJis1
    kJoyoKanji
    kKPS0
    kKPS1
    kKSC0
    kKSC1
    kKangXi
    kKarlgren
    kKorean
    kKoreanEducationHanja
    kKoreanName
    kLau
    kMainlandTelegraph
    kMandarin
    kMatthews
    kMeyerWempe
    kMorohashi
    kNelson
    kOtherNumeric
    kPhonetic
    kPrimaryNumeric
    kPseudoGB1
    kRSAdobe_Japan1_6
    kRSJapanese
    kRSKanWa
    kRSKangXi
    kRSKorean
    kRSUnicode
    kSBGY
    kSemanticVariant
    kSimplifiedVariant
    kSpecializedSemanticVariant
    kTGH
    kTaiwanTelegraph
    kTang
    kTotalStrokes
    kTraditionalVariant
    kVietnamese
    kXHC1983
    kXerox
    valuespecifies the value of a named Unihan property
    StatusRequired
    Datatypeteidata.word
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    A definitive list of current Unihan property names is provided in the Unicode Han Database.

    Example
    <unihanProp name="kRSKangXi" value="120.5" version="12.1"/>
    Content model
    
+}

    12.1.101. <unihanProp>

    <unihanProp> (unihan property) holds the name and value of a normative or informative Unihan character (or glyph) property as part of its attributes. [5.2.1. Character Properties]

    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
    namespecifies the normalized name of a unicode han database (Unihan) property
    StatusRequired
    Datatypeteidata.xmlName
    Legal values are:
    kZVariant
    kAccountingNumeric
    kBigFive
    kCCCII
    kCNS1986
    kCNS1992
    kCangjie
    kCantonese
    kCheungBauer
    kCheungBauerIndex
    kCihaiT
    kCompatibilityVariant
    kCowles
    kDaeJaweon
    kDefinition
    kEACC
    kFenn
    kFennIndex
    kFourCornerCode
    kFrequency
    kGB0
    kGB1
    kGB3
    kGB5
    kGB7
    kGB8
    kGSR
    kGradeLevel
    kHDZRadBreak
    kHKGlyph
    kHKSCS
    kHanYu
    kHangul
    kHanyuPinlu
    kHanyuPinyin
    kIBMJapan
    kIICore
    kIRGDaeJaweon
    kIRGDaiKanwaZiten
    kIRGHanyuDaZidian
    kIRGKangXi
    kIRG_GSource
    kIRG_HSource
    kIRG_JSource
    kIRG_KPSource
    kIRG_KSource
    kIRG_MSource
    kIRG_TSource
    kIRG_USource
    kIRG_VSource
    kJIS0213
    kJa
    kJapaneseKun
    kJapaneseOn
    kJinmeiyoKanji
    kJis0
    kJis1
    kJoyoKanji
    kKPS0
    kKPS1
    kKSC0
    kKSC1
    kKangXi
    kKarlgren
    kKorean
    kKoreanEducationHanja
    kKoreanName
    kLau
    kMainlandTelegraph
    kMandarin
    kMatthews
    kMeyerWempe
    kMorohashi
    kNelson
    kOtherNumeric
    kPhonetic
    kPrimaryNumeric
    kPseudoGB1
    kRSAdobe_Japan1_6
    kRSJapanese
    kRSKanWa
    kRSKangXi
    kRSKorean
    kRSUnicode
    kSBGY
    kSemanticVariant
    kSimplifiedVariant
    kSpecializedSemanticVariant
    kTGH
    kTaiwanTelegraph
    kTang
    kTotalStrokes
    kTraditionalVariant
    kVietnamese
    kXHC1983
    kXerox
    valuespecifies the value of a named Unihan property
    StatusRequired
    Datatypeteidata.word
    Contained by
    gaiji: char glyph
    May containEmpty element
    Note

    A definitive list of current Unihan property names is provided in the Unicode Han Database.

    Example
    <unihanProp name="kRSKangXi" value="120.5" version="12.1"/>
    Content model
    
 <content>
  <empty/>
 </content>
@@ -4382,7 +4675,7 @@
    },
    attribute value { text },
    empty
-}

    11.1.97. <usg>

    <usg> (usage) contains usage information in a dictionary entry. [9.3.5.2. Usage Information and Other Labels]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRequired
    Legal values are:
    time
    marker which identifies the use of a given lexical unit on a scale from old to new
    geographic
    marker which identifies the place or region where a lexical unit is mainly used
    socioCultural
    marker which identifies the use of a given lexical unit by particular social groups and/or in certain types of communicative situations depending on their level of formality
    domain
    marker which identifies the specialized field of knowledge in which a lexical unit is mainly used
    frequency
    marker which identifies the relative rate of occurrence of a lexical unit in a given textual context
    attitude
    marker which identifies the speaker’s subjective point of view, positive or negative, regarding the object referred to by a given lexical unit
    normativity
    marker which identifies the use of a given lexical unit which is in some aspect considered to be non-standard or incorrect
    meaningType
    marker which identifies a semantic extension of the sense of a given lexical unit
    textType
    marker which identifies the typical use of a lexical unit in a particular discourse type or genre
    hint
    marker which cannot be classified otherwise
    Member of
    model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym form gramGrp sense xr
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    character data
    Example
    <form>
+}

    12.1.102. <usg>

    <usg> (usage) contains usage information in a dictionary entry. [9.3.5.2. Usage Information and Other Labels]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
    type
    StatusRequired
    Legal values are:
    time
    marker which identifies the use of a given lexical unit on a scale from old to new
    geographic
    marker which identifies the place or region where a lexical unit is mainly used
    socioCultural
    marker which identifies the use of a given lexical unit by particular social groups and/or in certain types of communicative situations depending on their level of formality
    domain
    marker which identifies the specialized field of knowledge in which a lexical unit is mainly used
    frequency
    marker which identifies the relative rate of occurrence of a lexical unit in a given textual context
    attitude
    marker which identifies the speaker’s subjective point of view, positive or negative, regarding the object referred to by a given lexical unit
    normativity
    marker which identifies the use of a given lexical unit which is in some aspect considered to be non-standard or incorrect
    meaningType
    marker which identifies a semantic extension of the sense of a given lexical unit
    textType
    marker which identifies the typical use of a lexical unit in a particular discourse type or genre
    hint
    marker which cannot be classified otherwise
    Member of
    model.entryPart model.entryPart.top model.lexicalRefinement model.sensePart
    Contained by
    core: cit
    dictionaries: dictScrap entry etym form gramGrp sense xr
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    character data
    Example
    <form>
   <form>
      <usg type="geographic">U.S.</usg>
      <orth>color</orth>
@@ -4411,19 +4704,232 @@
     | "hint"
    },
    macro.paraContent
-}

    11.1.98. <value>

    <value> contains a single value for some property, attribute, or other analysis. [5.2.1. Character Properties]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charProp
    May contain
    gaiji: g
    character data
    Example
    <value>unknown</value>
    Content model
    
+}

    12.1.103. <value>

    <value> (value) contains a single value for some property, attribute, or other analysis. [5.2.1. Character Properties]

    Deprecatedwill be removed on 2022-02-15
    Modulegaiji — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
    Contained by
    gaiji: charProp
    May contain
    gaiji: g
    character data
    Example
    <value>unknown</value>
    Content model
    
 <content>
  <macroRef key="macro.xtext"/>
 </content>
    Schema Declaration
    
-element value { att.global.attributes, macro.xtext }

    11.1.99. <xr>

    <xr> (cross-reference phrase) contains a phrase, sentence, or icon referring the reader to some other location in this or another text. [9.3.5.3. Cross-References to Other Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    type
    StatusRequired
    Legal values are:
    synonymy
    Relation between two lexical units X and Y which are syntactically identical and have the property that any declarative sentence S containing X has equivalent truth conditions to another sentence S’ which is identical to S, except that X is replaced by Y. (Adapted from Cruse (1986).)
    hyponymy
    Relation between lexical units X and Y characterised by the property that the sentence This is a(n) X entails, but is not entailed by the sentence This is a(n) Y. (Adapted from Cruse (1986))
    hypernymy
    Relation between lexical heads X and Y characterised by the property that the sentence This is a(n) Y entails, but is not entailed by the sentence This is a(n) X. (Adapted from Cruse (1986))
    meronymy
    An inclusion relation between lexical heads X and Y which reflect a potential part-whole relation between their referents in discourse. (Adapted from Cruse (2011, p. 140))
    antonymy
    related
    The default reference to another lexical unit when no addtional information is available.[Default]
    subtype
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    macro.paraContent model.entryPart model.entryPart.top model.quoteLike model.sensePart
    Contained by
    core: author biblScope cit citedRange editor gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: orgName persName placeName
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: orgName persName placeName
    transcr: metamark
    Note

    May contain character data and phrase-level elements; usually contains a <ref> or a <ptr> element.

    This element encloses both the actual indication of the location referred to, which may be tagged using the <ref> or <ptr> elements, and any accompanying material which gives more information about why the reader is being referred there.

    Example
    <entry>
+element value { att.global.attributes, macro.xtext }

    12.1.104. <xenoData>

    <xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]

    Moduleheader — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype)
    Contained by
    header: teiHeader
    May containANY
    ExampleThis example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second <xenoData> block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the <xenoData> block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [[undefined SG-id]]). Do note, however, that if the contents of the <xenoData> block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.
    <xenoData
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+  <rdf:RDF>
+     <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
+        <dc:title>The description of a new world, called the blazing-world</dc:title>
+        <dc:creator>The Duchess of Newcastle</dc:creator>
+        <dc:date>1667</dc:date>
+        <dc:identifier>British Library, 8407.h.10</dc:identifier>
+        <dc:subject>utopian fiction</dc:subject>
+     </rdf:Description>
+  </rdf:RDF>
+</xenoData>
+<xenoData>
+  <rdf:RDF>
+     <rdf:Description rdf:about="">
+        <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
+        <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
+        <dc:publisher>Women Writers Project</dc:publisher>
+        <dc:date>2002-02-12</dc:date>
+        <dc:subject>utopian fiction</dc:subject>
+     </rdf:Description>
+  </rdf:RDF>
+</xenoData>
    ExampleIn this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.
    <xenoData
+   xmlns:cc="http://web.resource.org/cc/"
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+  <rdf:RDF>
+     <cc:Work rdf:about="">
+        <dc:title>Applied Software Project Management - review</dc:title>
+        <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
+        <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>
+     </cc:Work>
+     <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
+        <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
+        <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
+        <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
+        <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
+        <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
+        <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>
+     </cc:License>
+  </rdf:RDF>
+</xenoData>
    ExampleIn this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.
    <xenoData
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/">
+  <oai_dc:dc>
+     <dc:title>The colonial despatches of Vancouver Island and British
+           Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.
+           Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>
+     <dc:date>1858-11-12</dc:date>
+     <dc:creator>Trevelyan</dc:creator>
+     <dc:publisher>University of Victoria Humanities Computing and Media
+           Centre, and UVic Libraries</dc:publisher>
+     <dc:type>InteractiveResource</dc:type>
+     <dc:format>application/xhtml+xml</dc:format>
+     <dc:type>text</dc:type>
+     <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
+     <dc:rights>This document is licensed under a Creative Commons …</dc:rights>
+     <dc:language>(SCHEME=ISO639) en</dc:language>
+     <dc:source>Transcribed from microfilm and/or original documents, and
+           marked up in TEI P5 XML. The interactive XHTML resource is generated
+           from the XHTML using XQuery and XSLT.</dc:source>
+     <dc:source>repository: CO</dc:source>
+     <dc:source>coNumber: 60</dc:source>
+     <dc:source>coVol: 2</dc:source>
+     <dc:source>page: 291</dc:source>
+     <dc:source>coRegistration: 11566</dc:source>
+     <dc:source>received: received 13 November</dc:source>
+     <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
+     <dc:subject>Merivale, Herman</dc:subject>
+     <dc:subject>Elliot, T. Frederick</dc:subject>
+     <dc:subject>Moody, Colonel Richard Clement</dc:subject>
+     <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
+     <dc:subject>Jadis, Vane</dc:subject>
+     <dc:subject>Carnarvon, Earl</dc:subject>
+     <dc:subject>British Columbia</dc:subject>
+     <dc:description>British Columbia correspondence: Public Offices
+           document (normally correspondence between government
+           departments)</dc:description>
+  </oai_dc:dc>
+</xenoData>
    ExampleIn this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.
    <xenoData
+   xmlns:mods="http://www.loc.gov/mods/v3">
+  <mods:mods>
+     <mods:titleInfo>
+        <mods:title>Academic adaptation and cross-cultural
+                 learning experiences of Chinese students at American
+                 universities</mods:title>
+        <mods:subTitle>a narrative inquiry</mods:subTitle>
+     </mods:titleInfo>
+     <mods:name type="personal" authority="local">
+        <mods:namePart/>
+        <mods:role>
+           <mods:roleTerm authority="marcrelator" type="text">Author</mods:roleTerm>
+        </mods:role>
+        <mods:affiliation>Northeastern University</mods:affiliation>
+        <mods:namePart type="given">Hong</mods:namePart>
+        <mods:namePart type="family">Zhang</mods:namePart>
+     </mods:name>
+     <mods:name type="personal" authority="local">
+        <mods:namePart/>
+        <mods:role>
+           <mods:roleTerm authority="local" type="text">Advisor</mods:roleTerm>
+        </mods:role>
+        <mods:namePart type="given">Liliana</mods:namePart>
+        <mods:namePart type="family">Meneses</mods:namePart>
+     </mods:name>
+     
+     <!-- ... -->
+     <mods:typeOfResource>text</mods:typeOfResource>
+     <mods:genre>doctoral theses</mods:genre>
+     <mods:originInfo>
+        <mods:place>
+           <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>
+        </mods:place>
+        <mods:publisher>Northeastern University</mods:publisher>
+        <mods:copyrightDate encoding="w3cdtf" keyDate="yes">2013</mods:copyrightDate>
+     </mods:originInfo>
+     <mods:language>
+        <mods:languageTerm authority="iso639-2b" type="code">eng</mods:languageTerm>
+     </mods:language>
+     <mods:physicalDescription>
+        <mods:form authority="marcform">electronic</mods:form>
+        <mods:digitalOrigin>born digital</mods:digitalOrigin>
+     </mods:physicalDescription>
+     <!-- ... -->
+  </mods:mods>
+</xenoData>
    ExampleThis example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.
    <xenoData xml:space="preserve">
+<![CDATA[
+{
+    "features": [
+        {
+            "geometry": {
+                "type": "Point",
+                "coordinates": [
+                    68.388483,
+                    33.498616
+                ]
+            },
+            "type": "Feature",
+            "id": "darmc-location-19727",
+            "properties": {
+                "snippet": "Unknown; 330 BC - AD 300",
+                "link": "https://pleiades.stoa.org/places/59694/darmc-location-19727",
+                "description": "5M scale point location",
+                "location_precision": "precise",
+                "title": "DARMC location 19727"
+            }
+        }
+    ],
+    "id": "59694",
+    "subject": [
+        "dare:ancient=1",
+        "dare:feature=settlement",
+        "dare:major=0"
+    ],
+    "title": "Arachosiorum Oppidum/Alexandria",
+    "provenance": "Barrington Atlas: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",
+    "placeTypeURIs": [
+        "https://pleiades.stoa.org/vocabularies/place-types/settlement"
+    ],
+    "details": "<p>The Barrington Atlas Directory notes: Kalat-e-Ghilzai? AFG</p>",
+    "@context": {
+        "snippet": "dcterms:abstract",
+        "rights": "dcterms:rights",
+        "description": "dcterms:description",
+        "title": "dcterms:title",
+        "dcterms": "http://purl.org/dc/terms/",
+        "subject": "dcterms:subject",
+        "uri": "@id",
+        "created": "dcterms:created"
+    },
+    "review_state": "published",
+    "type": "FeatureCollection",
+    "description": "An ancient place, cited: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",
+    "reprPoint": [
+        68.388483,
+        33.498616
+    ],
+    "placeTypes": [
+        "settlement"
+    ],
+    "bbox": [
+        68.388483,
+        33.498616,
+        68.388483,
+        33.498616
+    ],
+    "rights": "Copyright © The Contributors. Sharing and remixing permitted under CC-BY.",
+    "created": "2010-09-23T04:31:55Z",
+    "uri": "https://pleiades.stoa.org/places/59694",
+    "creators": [
+        {
+            "username": null,
+            "name": "M.U. Erdosy"
+        }
+    ],
+    "@type": "Place"
+}
+]]>
+</xenoData>
    Note: the example above has been trimmed for legibility. The original may be found linked from Arachosiorum Oppidum/Alexandria. The contributors, listed per the license terms, are R. Talbert, Jeffrey Becker, W. Röllig, Tom Elliott, H. Kopp, DARMC, Sean Gillies, B. Siewert-Mayer, Francis Deblauwe, and Eric Kansa.
    Content model
    
+<content>
+ <alternate>
+  <textNode/>
+  <anyElement/>
+ </alternate>
+</content>
+
    Schema Declaration
    
+element xenoData
+{
+   att.global.attributes,
+   att.declarable.attributes,
+   att.typed.attributes,
+   ( text | anyElement-xenoData )
+}

    12.1.105. <xr>

    <xr> (cross-reference phrase) contains a phrase, sentence, or icon referring the reader to some other location in this or another text. [9.3.5.3. Cross-References to Other Entries]

    Moduledictionaries — Specification
    AttributesAttributes att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat)) (att.lexicographic.normalized (@norm, @orig))
    type
    StatusRequired
    Legal values are:
    synonymy
    Relation between two lexical units X and Y which are syntactically identical and have the property that any declarative sentence S containing X has equivalent truth conditions to another sentence S’ which is identical to S, except that X is replaced by Y. (Adapted from Cruse (1986).)
    hyponymy
    Relation between lexical units X and Y characterised by the property that the sentence This is a(n) X entails, but is not entailed by the sentence This is a(n) Y. (Adapted from Cruse (1986))
    hypernymy
    Relation between lexical heads X and Y characterised by the property that the sentence This is a(n) Y entails, but is not entailed by the sentence This is a(n) X. (Adapted from Cruse (1986))
    meronymy
    An inclusion relation between lexical heads X and Y which reflect a potential part-whole relation between their referents in discourse. (Adapted from Cruse (2011, p. 140))
    antonymy
    related
    The default reference to another lexical unit when no addtional information is available.[Default]
    subtype
    StatusOptional
    Datatypeteidata.enumerated
    Member of
    macro.paraContent model.entryPart model.entryPart.top model.quoteLike model.sensePart
    Contained by
    core: author biblScope cit citedRange editor email gloss head hi name note p pubPlace publisher quote ref term title
    dictionaries: def dictScrap entry etym form gram gramGrp hyph lang lbl orth pron sense stress syll usg xr
    figures: figDesc figure
    header: distributor edition extent licence rendition tagUsage
    linking: seg
    namesdates: forename orgName persName placeName surname
    textstructure: body div
    transcr: metamark
    May contain
    analysis: c pc
    core: bibl biblStruct cit date email gloss graphic hi listBibl name note quote ref term title
    dictionaries: lang lbl usg xr
    figures: figure
    gaiji: g
    header: idno
    linking: seg
    namesdates: forename orgName persName placeName surname
    transcr: metamark
    Note

    May contain character data and phrase-level elements; usually contains a <ref> or a <ptr> element.

    This element encloses both the actual indication of the location referred to, which may be tagged using the <ref> or <ptr> elements, and any accompanying material which gives more information about why the reader is being referred there.

    Example
    <entry>
   <form>
      <orth>lavage</orth>
   </form>
   <etym>[Fr. < <mentioned>laver</mentioned>; L. <mentioned>lavare</mentioned>, to wash;
   <xr>see <ref>lather</ref>
      </xr>]. </etym>
-</entry>
    Example
    <entry>
+</entry>
    Example
    <entry>
   <form>
      <orth>lawful</orth>
   </form>
@@ -4457,21 +4963,33 @@
    },
    attribute subtype { text }?,
    ( model.gLike | model.phrase | model.inter | usg | lbl | model.global )*
-}

    11.2. Model classes

    11.2.1. model.attributable

    model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]

    Moduletei — Specification
    Used by
    macro.phraseSeq model.inter
    Membersmodel.quoteLike[cit quote xr]

    11.2.2. model.availabilityPart

    model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    availability
    Memberslicence

    11.2.3. model.biblLike

    model.biblLike groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    cit listBibl model.entryPart.top model.inter sourceDesc
    Membersbibl biblStruct listBibl

    11.2.4. model.biblPart

    model.biblPart groups elements which represent components of a bibliographic description. [3.11. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    bibl
    Membersmodel.imprintPart[biblScope distributor pubPlace publisher] model.respLike[author editor funder respStmt] availability bibl citedRange edition extent

    11.2.5. model.common

    model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    body div figure
    Membersmodel.divPart[model.lLike model.pLike[p]] model.entryLike[entry] model.inter[model.attributable[model.quoteLike[cit quote xr]] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike model.listLike model.oddDecl model.stageLike]
    Note

    This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

    11.2.6. model.dateLike

    model.dateLike groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.7. Dates and Times]

    Moduletei — Specification
    Used by
    imprint model.pPart.data
    Membersdate

    11.2.7. model.divBottom

    model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]

    Moduletei — Specification
    Used by
    body div figure front
    Membersmodel.divBottomPart model.divWrapper

    11.2.8. model.divLike

    model.divLike groups elements used to represent un-numbered generic structural divisions.

    Moduletei — Specification
    Used by
    back body div front
    Membersdiv

    11.2.9. model.divPart

    model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    macro.specialPara model.common
    Membersmodel.lLike model.pLike[p]
    Note

    Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

    11.2.10. model.divTop

    model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]

    Moduletei — Specification
    Used by
    body div
    Membersmodel.divTopPart[model.headLike[head]] model.divWrapper

    11.2.11. model.divTopPart

    model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]

    Moduletei — Specification
    Used by
    model.divTop
    Membersmodel.headLike[head]

    11.2.12. model.emphLike

    model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    model.highlighted model.limitedPhrase
    Membersgloss lbl term title

    11.2.13. model.encodingDescPart

    model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.

    Moduletei — Specification
    Used by
    encodingDesc
    MembersappInfo charDecl classDecl projectDesc tagsDecl

    11.2.14. model.entryLike

    model.entryLike groups elements structurally analogous to paragraphs within dictionaries. [9.1. Dictionary Body and Overall Structure 1.3. The TEI Class System]

    Moduledictionaries — Specification
    Used by
    model.common
    Membersentry

    11.2.15. model.entryPart

    model.entryPart groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure]

    Moduletei — Specification
    Used by
    cit dictScrap
    Membersetym form gramGrp hyph lbl orth pron sense syll usg xr

    11.2.16. model.entryPart.top

    model.entryPart.top groups high level elements within a structured dictionary entry [9.2. The Structure of Dictionary Entries]

    Moduletei — Specification
    Used by
    entry
    Membersmodel.biblLike[bibl biblStruct listBibl] cit dictScrap entry etym form gramGrp lbl num usg xr
    Note

    Members of this class typically contain related parts of a dictionary entry which form a coherent subdivision, for example a particular sense, homonym, etc.

    11.2.17. model.formPart

    model.formPart groups elements allowed within a <form> element in a dictionary. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    Used by
    form
    Membersmodel.gramPart[model.lexicalRefinement[gramGrp lbl usg] model.morphLike[gram]] form hyph orth pron stress syll

    11.2.18. model.frontPart

    model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]

    Moduletei — Specification
    Used by
    back front
    Membersmodel.frontPart.drama listBibl

    11.2.19. model.gLike

    model.gLike groups elements used to represent individual non-Unicode characters or glyphs.

    Moduletei — Specification
    Used by
    bibl date dictScrap etym form gramGrp head idno macro.paraContent macro.phraseSeq macro.specialPara macro.xtext pc sense xr
    Membersg

    11.2.20. model.global

    model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    back bibl body cit date dictScrap div entry etym figure form front gramGrp head imprint macro.paraContent macro.phraseSeq macro.phraseSeq.limited macro.specialPara sense text xr
    Membersmodel.global.edit model.global.meta model.milestoneLike model.noteLike[note] figure metamark

    11.2.21. model.gramPart

    model.gramPart groups elements allowed within a <gramGrp> element in a dictionary. [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    Used by
    gramGrp model.formPart
    Membersmodel.lexicalRefinement[gramGrp lbl usg] model.morphLike[gram]

    11.2.22. model.graphicLike

    model.graphicLike groups elements containing images, formulae, and similar objects. [3.9. Graphics and Other Non-textual Components]

    Moduletei — Specification
    Used by
    char figure glyph model.phrase
    Membersgraphic

    11.2.23. model.headLike

    model.headLike groups elements used to provide a title or heading at the start of a text division.

    Moduletei — Specification
    Used by
    figure listBibl model.divTopPart
    Membershead

    11.2.24. model.hiLike

    model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    model.highlighted model.limitedPhrase
    Membershi

    11.2.25. model.highlighted

    model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    bibl model.phrase
    Membersmodel.emphLike[gloss lbl term title] model.hiLike[hi]

    11.2.26. model.imprintPart

    model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    imprint model.biblPart
    MembersbiblScope distributor pubPlace publisher

    11.2.27. model.inter

    model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    dictScrap etym form gramGrp head macro.limitedContent macro.paraContent macro.specialPara model.common xr
    Membersmodel.attributable[model.quoteLike[cit quote xr]] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike model.listLike model.oddDecl model.stageLike

    11.2.28. model.lexicalRefinement

    model.lexicalRefinement elements adding further precision to the lexico-grammatical information provided for a dictionary entry.

    Moduledictionaries — Specification
    Used by
    model.gramPart
    MembersgramGrp lbl usg

    11.2.29. model.limitedPhrase

    model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    macro.limitedContent macro.phraseSeq.limited
    Membersmodel.emphLike[gloss lbl term title] model.hiLike[hi] model.pPart.data[model.addressLike model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno lang]] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike[ref]

    11.2.30. model.morphLike

    model.morphLike groups elements which provide morphological information within a dictionary entry. [9.3. Top-level Constituents of Entries]

    Moduledictionaries — Specification
    Used by
    dictScrap model.gramPart
    Membersgram

    11.2.31. model.nameLike

    model.nameLike groups elements which name or refer to a person, place, or organization.

    Moduletei — Specification
    Used by
    model.pPart.data
    Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno lang
    Note

    A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

    11.2.32. model.nameLike.agent

    model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]

    Moduletei — Specification
    Used by
    model.nameLike respStmt
    Membersname orgName persName
    Note

    This class is used in the content model of elements which reference names of people or organizations.

    11.2.33. model.noteLike

    model.noteLike groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing]

    Moduletei — Specification
    Used by
    biblStruct char glyph model.global notesStmt
    Membersnote

    11.2.34. model.pLike

    model.pLike groups paragraph-like elements.

    Moduletei — Specification
    Used by
    availability back editionStmt encodingDesc front langUsage model.divPart projectDesc publicationStmt seriesStmt sourceDesc
    Membersp

    11.2.35. model.pLike.front

    model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]

    Moduletei — Specification
    Used by
    back front
    Membershead

    11.2.36. model.pPart.data

    model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]

    Moduletei — Specification
    Used by
    bibl model.limitedPhrase model.phrase
    Membersmodel.addressLike model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno lang]

    11.2.37. model.pPart.edit

    model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]

    Moduletei — Specification
    Used by
    bibl model.phrase pc
    Membersmodel.pPart.editorial model.pPart.transcriptional

    11.2.38. model.phrase

    model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    date dictScrap etym form gramGrp head macro.paraContent macro.phraseSeq macro.specialPara sense xr
    Membersmodel.graphicLike[graphic] model.highlighted[model.emphLike[gloss lbl term title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno lang]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ref] model.ptrLike.form model.segLike[c pc seg] model.specDescLike
    Note

    This class of elements can occur within paragraphs, list items, lines of verse, etc.

    11.2.39. model.placeNamePart

    model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]

    Moduletei — Specification
    Used by
    model.placeStateLike
    MembersplaceName

    11.2.40. model.placeStateLike

    model.placeStateLike groups elements which describe changing states of a place.

    Moduletei — Specification
    Used by
    model.nameLike
    Membersmodel.placeNamePart[placeName]

    11.2.41. model.profileDescPart

    model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.

    Moduletei — Specification
    Used by
    profileDesc
    MemberslangUsage

    11.2.42. model.ptrLike

    model.ptrLike groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]

    Moduletei — Specification
    Used by
    analytic bibl biblStruct cit entry model.limitedPhrase model.phrase model.publicationStmtPart.detail
    Membersref

    11.2.43. model.publicationStmtPart.agency

    model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    publicationStmt
    Membersauthority distributor publisher
    Note

    The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

    See also model.publicationStmtPart.detail.

    11.2.44. model.publicationStmtPart.detail

    model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    publicationStmt
    Membersmodel.ptrLike[ref] availability date idno pubPlace
    Note

    A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

    See also model.publicationStmtPart.agency.

    11.2.45. model.quoteLike

    model.quoteLike groups elements used to directly contain quotations.

    Moduletei — Specification
    Used by
    cit model.attributable
    Memberscit quote xr

    11.2.46. model.resource

    model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    TEI
    Memberstext

    11.2.47. model.respLike

    model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.

    Moduletei — Specification
    Used by
    editionStmt model.biblPart titleStmt
    Membersauthor editor funder respStmt

    11.2.48. model.segLike

    model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

    Moduletei — Specification
    Used by
    bibl cit model.phrase
    Membersc pc seg
    Note

    The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

    11.2.49. model.sensePart

    model.sensePart groups together all the elements from the dictionary modules that can appear as child of <sense>

    Modulederived-module-TEILex0
    Used by
    sense
    Memberscit def entry etym form gramGrp lbl num sense usg xr

    11.2.50. model.teiHeaderPart

    model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.

    Moduletei — Specification
    Used by
    teiHeader
    MembersencodingDesc profileDesc

    11.3. Attribute classes

    11.3.1. att.cReferencing

    att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.

    Moduletei — Specification
    Membersgloss ref term
    AttributesAttributes
    cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
    StatusOptional
    Datatypeteidata.text
    Note

    The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

    The <refsDecl> to use may be indicated with the decls attribute.

    Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

    11.3.2. att.canonical

    att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]

    Moduletei — Specification
    Membersatt.naming[att.personal[name orgName persName placeName] author editor pubPlace] authority date distributor funder publisher resp respStmt term title
    AttributesAttributes
    keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
    StatusOptional
    Datatypeteidata.text
    <author>
+}

    12.2. Model classes

    12.2.1. model.addressLike

    model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]

    Moduletei — Specification
    Used by
    model.pPart.data
    Membersemail

    12.2.2. model.attributable

    model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]

    Moduletei — Specification
    Used by
    macro.phraseSeq model.inter
    Membersmodel.quoteLike[cit quote xr]

    12.2.3. model.availabilityPart

    model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    availability
    Memberslicence

    12.2.4. model.biblLike

    model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    cit listBibl model.entryPart.top model.inter
    Membersbibl biblStruct listBibl

    12.2.5. model.biblPart

    model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    bibl
    Membersmodel.imprintPart[biblScope distributor pubPlace publisher] model.respLike[author editor respStmt] availability bibl citedRange edition extent

    12.2.6. model.common

    model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    body div figure
    Membersmodel.divPart[model.lLike model.pLike[p]] model.entryLike[entry] model.inter[model.attributable[model.quoteLike[cit quote xr]] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike model.listLike model.oddDecl model.stageLike]
    Note

    This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

    12.2.7. model.dateLike

    model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]

    Moduletei — Specification
    Used by
    imprint model.pPart.data
    Membersdate

    12.2.8. model.divBottom

    model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]

    Moduletei — Specification
    Used by
    body div figure front
    Membersmodel.divBottomPart model.divWrapper

    12.2.9. model.divLike

    model.divLike groups elements used to represent un-numbered generic structural divisions.

    Moduletei — Specification
    Used by
    back body div front
    Membersdiv

    12.2.10. model.divPart

    model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    macro.specialPara model.common
    Membersmodel.lLike model.pLike[p]
    Note

    Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

    12.2.11. model.divTop

    model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]

    Moduletei — Specification
    Used by
    body div
    Membersmodel.divTopPart[model.headLike[head]] model.divWrapper

    12.2.12. model.divTopPart

    model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]

    Moduletei — Specification
    Used by
    model.divTop
    Membersmodel.headLike[head]

    12.2.13. model.emphLike

    model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    model.highlighted model.limitedPhrase
    Membersgloss lbl term title

    12.2.14. model.encodingDescPart

    model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.

    Moduletei — Specification
    Used by
    encodingDesc
    MembersappInfo charDecl classDecl editorialDecl projectDesc tagsDecl

    12.2.15. model.entryLike

    model.entryLike groups elements structurally analogous to paragraphs within dictionaries. [9.1. Dictionary Body and Overall Structure 1.3. The TEI Class System]

    Moduledictionaries — Specification
    Used by
    model.common
    Membersentry

    12.2.16. model.entryPart

    model.entryPart groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure]

    Moduletei — Specification
    Used by
    cit dictScrap
    Membersetym form gramGrp hyph lbl orth pron sense syll usg xr

    12.2.17. model.entryPart.top

    model.entryPart.top groups high level elements within a structured dictionary entry [9.2. The Structure of Dictionary Entries]

    Moduletei — Specification
    Used by
    entry
    Membersmodel.biblLike[bibl biblStruct listBibl] cit dictScrap entry etym form gramGrp lbl num usg xr
    Note

    Members of this class typically contain related parts of a dictionary entry which form a coherent subdivision, for example a particular sense, homonym, etc.

    12.2.18. model.formPart

    model.formPart groups elements allowed within a <form> element in a dictionary. [9.3.1. Information on Written and Spoken Forms]

    Moduledictionaries — Specification
    Used by
    form
    Membersmodel.gramPart[model.lexicalRefinement[gramGrp lbl usg] model.morphLike[gram]] form hyph orth pron stress syll

    12.2.19. model.frontPart

    model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]

    Moduletei — Specification
    Used by
    back front
    Membersmodel.frontPart.drama listBibl

    12.2.20. model.gLike

    model.gLike groups elements used to represent individual non-Unicode characters or glyphs.

    Moduletei — Specification
    Used by
    bibl date dictScrap etym form gramGrp head idno macro.paraContent macro.phraseSeq macro.specialPara macro.xtext pc sense xr
    Membersg

    12.2.21. model.global

    model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    back bibl body cit date dictScrap div entry etym figure form front gramGrp head imprint macro.paraContent macro.phraseSeq macro.phraseSeq.limited macro.specialPara sense text xr
    Membersmodel.global.edit model.global.meta model.milestoneLike model.noteLike[note] figure metamark

    12.2.22. model.gramPart

    model.gramPart groups elements allowed within a <gramGrp> element in a dictionary. [9.3.2. Grammatical Information]

    Moduledictionaries — Specification
    Used by
    gramGrp model.formPart
    Membersmodel.lexicalRefinement[gramGrp lbl usg] model.morphLike[gram]

    12.2.23. model.graphicLike

    model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]

    Moduletei — Specification
    Used by
    char figure glyph model.phrase
    Membersgraphic

    12.2.24. model.headLike

    model.headLike groups elements used to provide a title or heading at the start of a text division.

    Moduletei — Specification
    Used by
    figure listBibl model.divTopPart
    Membershead

    12.2.25. model.hiLike

    model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    model.highlighted model.limitedPhrase
    Membershi

    12.2.26. model.highlighted

    model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]

    Moduletei — Specification
    Used by
    bibl model.phrase
    Membersmodel.emphLike[gloss lbl term title] model.hiLike[hi]

    12.2.27. model.imprintPart

    model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]

    Moduletei — Specification
    Used by
    imprint model.biblPart
    MembersbiblScope distributor pubPlace publisher

    12.2.28. model.inter

    model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    dictScrap etym form gramGrp head macro.limitedContent macro.paraContent macro.specialPara model.common xr
    Membersmodel.attributable[model.quoteLike[cit quote xr]] model.biblLike[bibl biblStruct listBibl] model.egLike model.labelLike model.listLike model.oddDecl model.stageLike

    12.2.29. model.lexicalRefinement

    model.lexicalRefinement elements adding further precision to the lexico-grammatical information provided for a dictionary entry.

    Moduledictionaries — Specification
    Used by
    model.gramPart
    MembersgramGrp lbl usg

    12.2.30. model.limitedPhrase

    model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    macro.limitedContent macro.phraseSeq.limited
    Membersmodel.emphLike[gloss lbl term title] model.hiLike[hi] model.pPart.data[model.addressLike[email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[forename surname] model.placeStateLike[model.placeNamePart[placeName]] idno lang]] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike[ref]

    12.2.31. model.morphLike

    model.morphLike groups elements which provide morphological information within a dictionary entry. [9.3. Top-level Constituents of Entries]

    Moduledictionaries — Specification
    Used by
    dictScrap model.gramPart
    Membersgram

    12.2.32. model.nameLike

    model.nameLike groups elements which name or refer to a person, place, or organization.

    Moduletei — Specification
    Used by
    model.pPart.data
    Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[forename surname] model.placeStateLike[model.placeNamePart[placeName]] idno lang
    Note

    A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

    12.2.33. model.nameLike.agent

    model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

    Moduletei — Specification
    Used by
    model.nameLike respStmt
    Membersname orgName persName
    Note

    This class is used in the content model of elements which reference names of people or organizations.

    12.2.34. model.noteLike

    model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]

    Moduletei — Specification
    Used by
    biblStruct char glyph model.global monogr notesStmt
    Membersnote

    12.2.35. model.pLike

    model.pLike groups paragraph-like elements.

    Moduletei — Specification
    Used by
    availability back editionStmt editorialDecl encodingDesc front langUsage model.divPart projectDesc seriesStmt
    Membersp

    12.2.36. model.pLike.front

    model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]

    Moduletei — Specification
    Used by
    back front
    Membershead

    12.2.37. model.pPart.data

    model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

    Moduletei — Specification
    Used by
    bibl model.limitedPhrase model.phrase
    Membersmodel.addressLike[email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[forename surname] model.placeStateLike[model.placeNamePart[placeName]] idno lang]

    12.2.38. model.pPart.edit

    model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]

    Moduletei — Specification
    Used by
    bibl model.phrase pc
    Membersmodel.pPart.editorial model.pPart.transcriptional

    12.2.39. model.persNamePart

    model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]

    Modulenamesdates — Specification
    Used by
    model.nameLike
    Membersforename surname

    12.2.40. model.phrase

    model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    date dictScrap etym form gramGrp head macro.paraContent macro.phraseSeq macro.specialPara sense xr
    Membersmodel.graphicLike[graphic] model.highlighted[model.emphLike[gloss lbl term title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike[email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart[forename surname] model.placeStateLike[model.placeNamePart[placeName]] idno lang]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ref] model.ptrLike.form model.segLike[c pc seg] model.specDescLike
    Note

    This class of elements can occur within paragraphs, list items, lines of verse, etc.

    12.2.41. model.placeNamePart

    model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]

    Moduletei — Specification
    Used by
    model.placeStateLike
    MembersplaceName

    12.2.42. model.placeStateLike

    model.placeStateLike groups elements which describe changing states of a place.

    Moduletei — Specification
    Used by
    model.nameLike
    Membersmodel.placeNamePart[placeName]

    12.2.43. model.profileDescPart

    model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.

    Moduletei — Specification
    Used by
    profileDesc
    MemberslangUsage

    12.2.44. model.ptrLike

    model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]

    Moduletei — Specification
    Used by
    analytic bibl biblStruct cit entry model.limitedPhrase model.phrase model.publicationStmtPart.detail monogr
    Membersref

    12.2.45. model.publicationStmtPart.agency

    model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    publicationStmt
    Membersauthority distributor publisher
    Note

    The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

    See also model.publicationStmtPart.detail.

    12.2.46. model.publicationStmtPart.detail

    model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]

    Moduletei — Specification
    Used by
    publicationStmt
    Membersmodel.ptrLike[ref] availability date idno pubPlace
    Note

    A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

    See also model.publicationStmtPart.agency.

    12.2.47. model.quoteLike

    model.quoteLike groups elements used to directly contain quotations.

    Moduletei — Specification
    Used by
    cit model.attributable
    Memberscit quote xr

    12.2.48. model.resource

    model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    TEI
    Memberstext

    12.2.49. model.respLike

    model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.

    Moduletei — Specification
    Used by
    editionStmt model.biblPart titleStmt
    Membersauthor editor respStmt

    12.2.50. model.segLike

    model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

    Moduletei — Specification
    Used by
    bibl cit model.phrase
    Membersc pc seg
    Note

    The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

    12.2.51. model.sensePart

    model.sensePart groups together all the elements from the dictionary modules that can appear as child of <sense>

    Modulederived-module-TEILex0
    Used by
    sense
    Memberscit def entry etym form gramGrp lbl num sense usg xr

    12.3. Attribute classes

    12.3.1. att.anchoring

    att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.

    Moduletei — Specification
    Membersnote
    AttributesAttributes
    anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
    StatusOptional
    Datatypeteidata.truthValue
    Defaulttrue
    Note

    In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

    targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().

    Example
    <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
+ necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
+<!-- elsewhere in the document -->
+<noteGrp targetEnd="#A55234">
+  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.
+  </note>
+  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
+  </note>
+</noteGrp>

    12.3.2. att.cReferencing

    att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.

    Moduletei — Specification
    Membersgloss ref term
    AttributesAttributes
    cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
    StatusOptional
    Datatypeteidata.text
    Note

    The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

    The <refsDecl> to use may be indicated with the decls attribute.

    Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

    12.3.3. att.canonical

    att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]

    Moduletei — Specification
    Membersatt.naming[att.personal[forename name orgName persName placeName surname] author editor pubPlace] authority date distributor publisher resp respStmt term title
    AttributesAttributes
    keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
    StatusOptional
    Datatypeteidata.text
    <author>
   <name key="name 427308"
    type="organisation">[New Zealand Parliament, Legislative Council]</name>
-</author>
    <author>
+</author>
    <author>
   <name key="Hugo, Victor (1802-1885)"
    ref="http://www.idref.fr/026927608">Victor Hugo</name>
-</author>
    Note

    The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

    No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.

    ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <name ref="http://viaf.org/viaf/109557338"
- type="person">Seamus Heaney</name>
    Note

    The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

    11.3.3. att.citing

    att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]

    Moduletei — Specification
    MembersbiblScope citedRange
    AttributesAttributes
    unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    volume
    the element contains a volume number.
    issue
    the element contains an issue number, or volume and issue numbers.
    page
    the element contains a page number or page range.
    line
    the element contains a line number or line range.
    chapter
    the element contains a chapter indication (number and/or title)
    part
    the element identifies a part of a book or collection.
    column
    the element identifies a column.
    entry
    the element identifies an entry number or label in a list of entries.
    fromspecifies the starting point of the range of units indicated by the unit attribute.
    StatusOptional
    Datatypeteidata.word
    tospecifies the end-point of the range of units indicated by the unit attribute.
    StatusOptional
    Datatypeteidata.word

    11.3.4. att.datable

    att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.7. Dates and Times]

    Moduletei — Specification
    Membersdate idno licence name orgName persName placeName resp title
    AttributesAttributes 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)
    calendarindicates the system or calendar to which the date represented by the content of this element belongs.
    StatusOptional
    Datatypeteidata.pointer
    Schematron
    
+</author>
    Note

    The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

    No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.

    ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <name ref="http://viaf.org/viaf/109557338"
+ type="person">Seamus Heaney</name>
    Note

    The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

    12.3.4. att.citing

    att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]

    Moduletei — Specification
    MembersbiblScope citedRange
    AttributesAttributes
    unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    volume
    (volume) the element contains a volume number.
    issue
    the element contains an issue number, or volume and issue numbers.
    page
    (page) the element contains a page number or page range.
    line
    the element contains a line number or line range.
    chapter
    (chapter) the element contains a chapter indication (number and/or title)
    part
    the element identifies a part of a book or collection.
    column
    the element identifies a column.
    entry
    the element identifies an entry number or label in a list of entries.
    fromspecifies the starting point of the range of units indicated by the unit attribute.
    StatusOptional
    Datatypeteidata.word
    tospecifies the end-point of the range of units indicated by the unit attribute.
    StatusOptional
    Datatypeteidata.word

    12.3.5. att.datable

    att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]

    Moduletei — Specification
    Membersauthor date editor idno licence name orgName persName placeName resp title
    AttributesAttributes 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)
    calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Schematron
    
 <sch:rule context="tei:*[@calendar]">
-<sch:assert test="string-length(.) gt 0"> @calendar indicates the system or calendar to
+<sch:assert test="string-length(.) gt 0"> @calendar indicates one or more systems or calendars to
  which the date represented by the content of this element belongs, but this
 <sch:name/> element has no textual content.</sch:assert>
-</sch:rule>
    He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"
- when="1732-02-22"> Feb. 11, 1731/32,
- O.S.</date>).
    Note

    Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.

    periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
    StatusOptional
    Datatypeteidata.pointer
    Note

    This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

    11.3.5. att.datable.custom

    att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.7. Dates and Times]

    Modulenamesdates — Specification
    Membersatt.datable[date idno licence name orgName persName placeName resp title]
    AttributesAttributes
    when-customsupplies the value of a date or time in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
    <p>Alhazen died in Cairo on the
+</sch:rule>
    He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"
+ when="1732-02-22">Feb. 11, 1731/32,
+ O.S.</date>).
+
     He was born on <date calendar="#gregorian #julian"
+ when="1732-02-22">Feb. 22, 1732
+ (Feb. 11, 1731/32, O.S.)</date>.
+
    Note

    Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.

    periodsupplies pointers to one or more definitions of named periods of time (typically <category>s or <calendar>s) within which the datable item is understood to have occurred.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

    12.3.6. att.datable.custom

    att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]

    Modulenamesdates — Specification
    Membersatt.datable[author date editor idno licence name orgName persName placeName resp title]
    AttributesAttributes
    when-customsupplies the value of a date or time in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
    <p>Alhazen died in Cairo on the
 <date when="1040-03-06"
    when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH
   </date>.</p>
@@ -4482,31 +5000,31 @@
  (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
 <p>Esidorus bixit in pace annos LXX plus minus sub
 <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
-</p>
    Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
    notBefore-customspecifies the earliest possible date for the event in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    notAfter-customspecifies the latest possible date for the event in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    from-customindicates the starting point of the period in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    <event xml:id="FIRE1"
+</p>
    Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
    notBefore-customspecifies the earliest possible date for the event in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    notAfter-customspecifies the latest possible date for the event in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    from-customindicates the starting point of the period in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    <event xml:id="FIRE1"
  datingMethod="#julian"
  from-custom="1666-09-02"
  to-custom="1666-09-05">
   <head>The Great Fire of London</head>
   <p>The Great Fire of London burned through a large part
      of the city of London.</p>
-</event>
    to-customindicates the ending point of the period in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
    StatusOptional
    Datatypeteidata.pointer
    datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
    StatusOptional
    Datatypeteidata.pointer
    Contayning the Originall, Antiquity, Increaſe, Moderne
+</event>
    to-customindicates the ending point of the period in some custom standard form.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
    StatusOptional
    Datatypeteidata.pointer
    datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
    StatusOptional
    Datatypeteidata.pointer
    Contayning the Originall, Antiquity, Increaſe, Moderne
  eſtate, and deſcription of that Citie, written in the yeare
 <date when-custom="1598"
  calendar="#julian"
  datingMethod="#julian">1598</date>. by Iohn Stow
- Citizen of London.
    In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
    <date when="1382-06-28"
+ Citizen of London.
    In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
    <date when="1382-06-28"
  when-custom="6890-06-20"
  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
-</date>
    In this example, a date is given in a Mediaeval text measured "from the creation of the world", which is normalised (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
    Note

    Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

    11.3.6. att.datable.iso

    att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601 standard. [3.5.4. Dates and Times 13.3.7. Dates and Times]

    Modulenamesdates — Specification
    Membersatt.datable[date idno licence name orgName persName placeName resp title]
    AttributesAttributes
    when-isosupplies the value of a date or time in a standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
    <date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
+</date>
    In this example, a date is given in a Mediaeval text measured "from the creation of the world", which is normalised (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
    Note

    Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

    12.3.7. att.datable.iso

    att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601 standard. [3.6.4. Dates and Times 13.4. Dates]

    Modulenamesdates — Specification
    Membersatt.datable[author date editor idno licence name orgName persName placeName resp title]
    AttributesAttributes
    when-isosupplies the value of a date or time in a standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
    <date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
 <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
 <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
 <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
 <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
 <time when-iso="03:00">3 A.M.</time>
 <time when-iso="14">around two</time>
-<time when-iso="15,5">half past three</time>
    All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
    He likes to be punctual. I said <q>
+<time when-iso="15,5">half past three</time>
    All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
    He likes to be punctual. I said <q>
   <time when-iso="12">around noon</time>
-</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
    The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
    notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.iso
    notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.iso
    from-isoindicates the starting point of the period in standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    to-isoindicates the ending point of the period in standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    Note

    The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601, using the Gregorian calendar.

    If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is, 
    <date when-iso="2007-06-01" dur-iso="P8D"/>
    indicates the same time period as 
    <date when-iso="2007-06-01/P8D"/>

    In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

    11.3.7. att.datable.w3c

    att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.7. Dates and Times]

    Moduletei — Specification
    Membersatt.datable[date idno licence name orgName persName placeName resp title] orth pron
    AttributesAttributes
    whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.w3c
    Examples of W3C date, time, and date & time formats.
    <p>
+</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
    The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
    notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.iso
    notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.iso
    from-isoindicates the starting point of the period in standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    to-isoindicates the ending point of the period in standard form.
    StatusOptional
    Datatypeteidata.temporal.iso
    Note

    The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601, using the Gregorian calendar.

    If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is, 
    <date when-iso="2007-06-01" dur-iso="P8D"/>
    indicates the same time period as 
    <date when-iso="2007-06-01/P8D"/>

    In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

    12.3.8. att.datable.w3c

    att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]

    Moduletei — Specification
    Membersatt.datable[author date editor idno licence name orgName persName placeName resp title] orth pron
    AttributesAttributes
    whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
    StatusOptional
    Datatypeteidata.temporal.w3c
    Examples of W3C date, time, and date & time formats.
    <p>
   <date when="1945-10-24">24 Oct 45</date>
   <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
   <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
@@ -4518,11 +5036,11 @@
   <date when="2006">MMVI</date>
   <date when="0056">AD 56</date>
   <date when="-0056">56 BC</date>
-</p>
    This list begins in
+</p>
    This list begins in
  the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
  Pentecost, in that year the
 <date calendar="#julian"
- when="1632-06-06">27th of May (old style)</date>.
    <opener>
+ when="1632-06-06">27th of May (old style)</date>.
    <opener>
   <dateline>
      <placeName>Dorchester, Village,</placeName>
      <date when="1828-03-02">March 2d. 1828.</date>
@@ -4541,17 +5059,17 @@
 <sch:rule context="tei:*[@to]">
 <sch:report test="@notAfter"
  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report>
-</sch:rule>
    Example
    <date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
    Note

    The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

    The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

    Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

    11.3.8. att.datcat

    att.datcat provides the dcr:datacat and dcr:ValueDatacat attributes which are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]

    Moduletei — Specification
    Membersatt.lexicographic[def etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr] att.segLike[c pc seg]
    AttributesAttributes
    datcatcontains a PID (persistent identifier) that aligns the given element with the appropriate Data Category (or categories) in ISOcat.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    valueDatcatcontains a PID (persistent identifier) that aligns the content of the given element or the value of the given attribute with the appropriate simple Data Category (or categories) in ISOcat.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    ExampleIn this example dcr:datcat relates the feature name to the data category "partOfSpeech" and dcr:valueDatcat the feature value to the data category "commonNoun". Both these data categories reside in the ISOcat DCR at www.isocat.org, which is the DCR used by ISO TC37 and hosted by its registration authority, the MPI for Psycholinguistics in Nijmegen.
    <fs
+</sch:rule>
    Example
    <date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
    Note

    The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

    The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

    Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

    12.3.9. att.datcat

    att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]

    Moduletei — Specification
    Membersatt.lexicographic[def etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr] att.segLike[c pc seg]
    AttributesAttributes
    datcatcontains a PID (persistent identifier) that aligns the given element with the appropriate Data Category (or categories) in ISOcat.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    valueDatcatcontains a PID (persistent identifier) that aligns the content of the given element or the value of the given attribute with the appropriate simple Data Category (or categories) in ISOcat.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    ExampleIn this example dcr:datcat relates the feature name to the data category "partOfSpeech" and dcr:valueDatcat the feature value to the data category "commonNoun". Both these data categories reside in the ISOcat DCR at www.isocat.org, which is the DCR used by ISO TC37 and hosted by its registration authority, the MPI for Psycholinguistics in Nijmegen.
    <fs
    xmlns:dcr="http://www.isocat.org/ns/dcr">
   <f name="POS" dcr:datcat="http://www.isocat.org/datcat/DC-1345" fVal="#commonNoun"
    dcr:valueDatcat="http://www.isocat.org/datcat/DC-1256"/>
-</fs>
    Note

    ISO 12620:2009 is a standard describing the data model and procedures for a Data Category Registry (DCR). Data categories are defined as elementary descriptors in a linguistic structure. In the DCR data model each data category gets assigned a unique Peristent IDentifier (PID), i.e., an URI. Linguistic resources or preferably their schemas that make use of data categories from a DCR should refer to them using this PID. For XML-based resources, like TEI documents, ISO 12620:2009 normative Annex A gives a small Data Category Reference XML vocabulary (also available online at http://www.isocat.org/12620/), which provides two attributes, dcr:datcat and dcr:valueDatcat.

    11.3.9. att.declarable

    att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]

    Moduletei — Specification
    Membersavailability bibl biblStruct listBibl projectDesc seriesStmt sourceDesc
    AttributesAttributes
    defaultindicates whether or not this element is selected by default when its parent is selected.
    StatusOptional
    Datatypeteidata.truthValue
    Legal values are:
    true
    This element is selected if its parent is selected
    false
    This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
    Note

    The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

    11.3.10. att.dimensions

    att.dimensions provides attributes for describing the size of physical objects.

    Moduletei — Specification
    Membersdate
    AttributesAttributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
    unitnames the unit used for the measurement
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    cm
    (centimetres)
    mm
    (millimetres)
    in
    (inches)
    line
    lines of text
    char
    (characters) characters of text
    quantityspecifies the length in the units specified
    StatusOptional
    Datatypeteidata.numeric
    extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
    StatusOptional
    Datatypeteidata.text
    <gap extent="5 words"/>
    <height extent="half the page"/>
    precisioncharacterizes the precision of the values specified by the other attributes.
    StatusOptional
    Datatypeteidata.certainty
    scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    all
    measurement applies to all instances.
    most
    measurement applies to most of the instances inspected.
    range
    measurement applies to only the specified range of instances.

    11.3.11. att.docStatus

    att.docStatus provides attributes for use on metadata elements describing the status of a document.

    Moduletei — Specification
    Membersbibl biblStruct
    AttributesAttributes
    statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    approved
    candidate
    cleared
    deprecated
    draft
    [Default]
    embargoed
    expired
    frozen
    galley
    proposed
    published
    recommendation
    submitted
    unfinished
    withdrawn
    Example
    <revisionDesc status="published">
+</fs>
    Note

    ISO 12620:2009 is a standard describing the data model and procedures for a Data Category Registry (DCR). Data categories are defined as elementary descriptors in a linguistic structure. In the DCR data model each data category gets assigned a unique Peristent IDentifier (PID), i.e., an URI. Linguistic resources or preferably their schemas that make use of data categories from a DCR should refer to them using this PID. For XML-based resources, like TEI documents, ISO 12620:2009 normative Annex A gives a small Data Category Reference XML vocabulary (also available online at http://www.isocat.org/12620/), which provides two attributes, dcr:datcat and dcr:valueDatcat.

    12.3.10. att.declarable

    att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]

    Moduletei — Specification
    Membersavailability bibl biblStruct editorialDecl listBibl projectDesc seriesStmt sourceDesc xenoData
    AttributesAttributes
    defaultindicates whether or not this element is selected by default when its parent is selected.
    StatusOptional
    Datatypeteidata.truthValue
    Legal values are:
    true
    This element is selected if its parent is selected
    false
    This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
    Note

    The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

    12.3.11. att.dimensions

    att.dimensions provides attributes for describing the size of physical objects.

    Moduletei — Specification
    Membersdate
    AttributesAttributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
    unitnames the unit used for the measurement
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    cm
    (centimetres)
    mm
    (millimetres)
    in
    (inches)
    line
    lines of text
    char
    (characters) characters of text
    quantityspecifies the length in the units specified
    StatusOptional
    Datatypeteidata.numeric
    extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
    StatusOptional
    Datatypeteidata.text
    <gap extent="5 words"/>
    <height extent="half the page"/>
    precisioncharacterizes the precision of the values specified by the other attributes.
    StatusOptional
    Datatypeteidata.certainty
    scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    all
    measurement applies to all instances.
    most
    measurement applies to most of the instances inspected.
    range
    measurement applies to only the specified range of instances.

    12.3.12. att.docStatus

    att.docStatus provides attributes for use on metadata elements describing the status of a document.

    Moduletei — Specification
    Membersbibl biblStruct revisionDesc
    AttributesAttributes
    statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
    StatusOptional
    Datatypeteidata.enumerated
    Sample values include:
    approved
    candidate
    cleared
    deprecated
    draft
    [Default]
    embargoed
    expired
    frozen
    galley
    proposed
    published
    recommendation
    submitted
    unfinished
    withdrawn
    Example
    <revisionDesc status="published">
   <change when="2010-10-21" status="published"/>
   <change when="2010-10-02" status="cleared"/>
   <change when="2010-08-02" status="embargoed"/>
   <change when="2010-05-01" status="frozen" who="#MSM"/>
   <change when="2010-03-01" status="draft" who="#LB"/>
-</revisionDesc>

    11.3.12. att.editLike

    att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.4. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]

    Moduletei — Specification
    Membersdate name orgName persName placeName
    AttributesAttributes
    evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
    StatusOptional
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    Suggested values include:
    internal
    there is internal evidence to support the intervention.
    external
    there is external evidence to support the intervention.
    conjecture
    the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
    instantindicates whether this is an instant revision or not.
    StatusOptional
    Datatypeteidata.xTruthValue
    Defaultfalse
    Note

    The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

    Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

    11.3.13. att.fragmentable

    att.fragmentable provides an attribute for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.

    Moduletei — Specification
    Membersatt.segLike[c pc seg] p
    AttributesAttributes
    partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    Y
    (yes) the element is fragmented in some (unspecified) respect
    N
    (no) the element is not fragmented, or no claim is made as to its completeness[Default]
    I
    (initial) this is the initial part of a fragmented element
    M
    (medial) this is a medial part of a fragmented element
    F
    (final) this is the final part of a fragmented element
    Note

    The values I, M, or F should be used only where it is clear how the element may be reconstituted.

    Example
    <etym>
+</revisionDesc>

    12.3.13. att.editLike

    att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]

    Moduletei — Specification
    Membersdate name orgName persName placeName
    AttributesAttributes
    evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
    StatusOptional
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    Suggested values include:
    internal
    there is internal evidence to support the intervention.
    external
    there is external evidence to support the intervention.
    conjecture
    the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
    instantindicates whether this is an instant revision or not.
    StatusOptional
    Datatypeteidata.xTruthValue
    Defaultfalse
    Note

    The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

    Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

    12.3.14. att.fragmentable

    att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.

    Moduletei — Specification
    Membersatt.segLike[c pc seg] p
    AttributesAttributes
    partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    Y
    (yes) the element is fragmented in some (unspecified) respect
    N
    (no) the element is not fragmented, or no claim is made as to its completeness[Default]
    I
    (initial) this is the initial part of a fragmented element
    M
    (medial) this is a medial part of a fragmented element
    F
    (final) this is the final part of a fragmented element
    Note

    The values I, M, or F should be used only where it is clear how the element may be reconstituted.

    Example
    <etym>
   <seg type="desc" part="I">seit dem</seg>
   <usg type="date">
      <date>18. Jh.</date>
@@ -4578,11 +5096,11 @@
   </cit>
   <seg type="desc" part="F">zurückführbar</seg>
   <bibl>(vgl. Pfeifer 2014: 329)</bibl>
-</etym>

    11.3.14. att.gaijiProp

    att.gaijiProp provides attributes for defining the properties of non-standard characters or glyphs. [5. Characters, Glyphs, and Writing Modes]

    Modulegaiji — Specification
    MemberslocalProp unicodeProp unihanProp
    AttributesAttributes
    nameprovides the name of the character or glyph property being defined.
    StatusRequired
    Datatypeteidata.xmlName
    valueprovides the value of the character or glyph property being defined.
    StatusRequired
    Datatypeteidata.text
    versionspecifies the version number of the Unicode Standard in which this property name is defined.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    1.0.1
    1.1
    2.0
    2.1
    3.0
    3.1
    3.2
    4.0
    4.1
    5.0
    5.1
    5.2
    6.0
    6.1
    6.2
    6.3
    7.0
    8.0
    9.0
    10.0
    11.0
    12.0
    12.1
    unassigned
    ExampleIn this example a definition for the Unicode property Decomposition Mapping is provided.
    <unicodeProp name="Decomposition_Mapping" value="circle"/>
    Note

    All name-only attributes need an xs:boolean attribute value inside value.

    11.3.15. att.global

    att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]

    Moduletei — Specification
    MembersTEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr
    AttributesAttributes att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    StatusOptional
    DatatypeID
    Note

    The xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. Reference Systems.

    n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
    StatusOptional
    Datatypeteidata.text
    Note

    The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

    xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
    StatusOptional
    Datatypeteidata.language
    <p> … The consequences of
+</etym>

    12.3.15. att.gaijiProp

    att.gaijiProp provides attributes for defining the properties of non-standard characters or glyphs. [5. Characters, Glyphs, and Writing Modes]

    Modulegaiji — Specification
    MemberslocalProp unicodeProp unihanProp
    AttributesAttributes
    nameprovides the name of the character or glyph property being defined.
    StatusRequired
    Datatypeteidata.xmlName
    valueprovides the value of the character or glyph property being defined.
    StatusRequired
    Datatypeteidata.text
    versionspecifies the version number of the Unicode Standard in which this property name is defined.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    1.0.1
    1.1
    2.0
    2.1
    3.0
    3.1
    3.2
    4.0
    4.1
    5.0
    5.1
    5.2
    6.0
    6.1
    6.2
    6.3
    7.0
    8.0
    9.0
    10.0
    11.0
    12.0
    12.1
    unassigned
    ExampleIn this example a definition for the Unicode property Decomposition Mapping is provided.
    <unicodeProp name="Decomposition_Mapping" value="circle"/>
    Note

    All name-only attributes need an xs:boolean attribute value inside value.

    12.3.16. att.global

    att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]

    Moduletei — Specification
    MembersTEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr
    AttributesAttributes att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
    xml:id(identifier) provides a unique identifier for the element bearing the attribute.
    StatusOptional
    DatatypeID
    Note

    The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

    n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
    StatusOptional
    Datatypeteidata.text
    Note

    The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

    xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
    StatusOptional
    Datatypeteidata.language
    <p> … The consequences of
  this rapid depopulation were the loss of the last
 <foreign xml:lang="rap">ariki</foreign> or chief
  (Routledge 1920:205,210) and their connections to
- ancestral territorial organization.</p>
    Note

    The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

    The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

    The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

    11.3.16. att.global.analytic

    att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]

    Moduleanalysis — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

    11.3.17. att.global.change

    att.global.change supplies the change attribute, allowing its member elements to specify one or more states or revision campaigns with which they are associated.

    Moduletranscr — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    changepoints to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace

    11.3.18. att.global.facs

    att.global.facs provides an attribute used to express correspondence between an element containing transcribed text and all or part of an image representing that text. [11.1. Digital Facsimiles]

    Moduletranscr — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    facs(facsimile) points to all or part of an image which corresponds with the content of the element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace

    11.3.19. att.global.linking

    att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]

    Modulelinking — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    corresp(corresponds) points to elements that correspond to the current element in some way.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <group>
+ ancestral territorial organization.</p>
    Note

    The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

    Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

    The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

    The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

    12.3.17. att.global.analytic

    att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]

    Moduleanalysis — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

    12.3.18. att.global.change

    att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.

    Moduletranscr — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    changepoints to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace

    12.3.19. att.global.facs

    att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]

    Moduletranscr — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace

    12.3.20. att.global.linking

    att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]

    Modulelinking — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    corresp(corresponds) points to elements that correspond to the current element in some way.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <group>
   <text xml:id="t1-g1-t1"
    xml:lang="mi">
      <body xml:id="t1-g1-t1-body1">
@@ -4602,7 +5120,7 @@
         </div>
      </body>
   </text>
-</group>
    In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
    
+</group>
    In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
    
 <!-- In a placeography called "places.xml" --><place xml:id="LOND1"
  corresp="people.xml#LOND2 people.xml#GENI1">
   <placeName>London</placeName>
@@ -4624,15 +5142,15 @@
            allegorical character in mayoral shows.
      </p>
   </note>
-</person>
    In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
    synch(synchronous) points to elements that are synchronous with the current element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    sameAspoints to an element that is the same as the current element.
    StatusOptional
    Datatypeteidata.pointer
    copyOfpoints to an element of which the current element is a copy.
    StatusOptional
    Datatypeteidata.pointer
    Note

    Any content of the current element should be ignored. Its true content is that of the element being pointed at.

    nextpoints to the next element of a virtual aggregate of which the current element is part.
    StatusOptional
    Datatypeteidata.pointer
    Note

    It is recommended that the element indicated be of the same type as the element bearing this attribute.

    prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
    StatusOptional
    Datatypeteidata.pointer
    Note

    It is recommended that the element indicated be of the same type as the element bearing this attribute.

    excludepoints to elements that are in exclusive alternation with the current element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

    11.3.20. att.global.rendition

    att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    rend(rendition) indicates how the element in question was rendered or presented in the source text.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    <head rend="align(center) case(allcaps)">
+</person>
    In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
    synch(synchronous) points to elements that are synchronous with the current element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    sameAspoints to an element that is the same as the current element.
    StatusOptional
    Datatypeteidata.pointer
    copyOfpoints to an element of which the current element is a copy.
    StatusOptional
    Datatypeteidata.pointer
    Note

    Any content of the current element should be ignored. Its true content is that of the element being pointed at.

    nextpoints to the next element of a virtual aggregate of which the current element is part.
    StatusOptional
    Datatypeteidata.pointer
    Note

    It is recommended that the element indicated be of the same type as the element bearing this attribute.

    prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
    StatusOptional
    Datatypeteidata.pointer
    Note

    It is recommended that the element indicated be of the same type as the element bearing this attribute.

    excludepoints to elements that are in exclusive alternation with the current element.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

    12.3.21. att.global.rendition

    att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    rend(rendition) indicates how the element in question was rendered or presented in the source text.
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    <head rend="align(center) case(allcaps)">
   <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
 <lb/>On Her <lb/>
   <hi rend="case(mixed)">New Blazing-World</hi>. 
-</head>
    Note

    These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

    stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
    StatusOptional
    Datatypeteidata.text
    <head style="text-align: center; font-variant: small-caps">
+</head>
    Note

    These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

    stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
    StatusOptional
    Datatypeteidata.text
    <head style="text-align: center; font-variant: small-caps">
   <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
 <lb/>
   <hi style="font-variant: normal">New Blazing-World</hi>. 
-</head>
    Note

    Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

    The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

    If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

    renditionpoints to a description of the rendering or presentation used for this element in the source text.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <head rendition="#ac #sc">
+</head>
    Note

    Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

    The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

    If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

    renditionpoints to a description of the rendering or presentation used for this element in the source text.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    <head rendition="#ac #sc">
   <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
 <lb/>
   <hi rendition="#normal">New Blazing-World</hi>. 
@@ -4643,11 +5161,11 @@
 <rendition xml:id="normal"
  scheme="css">font-variant: normal</rendition>
 <rendition xml:id="ac"
- scheme="css">text-align: center</rendition>
    Note

    The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

    If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

    Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

    11.3.21. att.global.responsibility

    att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
    StatusOptional
    Datatypeteidata.probCert
    resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

    Example
    Blessed are the
+ scheme="css">text-align: center</rendition>
    Note

    The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

    If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

    Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

    12.3.22. att.global.responsibility

    att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
    StatusOptional
    Datatypeteidata.probCert
    resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

    Example
    Blessed are the
 <choice>
   <sic>cheesemakers</sic>
   <corr resp="#editor" cert="high">peacemakers</corr>
-</choice>: for they shall be called the children of God.
    Example
    
+</choice>: for they shall be called the children of God.
    Example
    
 <!-- in the <text> ... --><lg>
   <!-- ... -->
   <l>Punkes, Panders, baſe extortionizing
@@ -4662,11 +5180,11 @@
 <respStmt xml:id="JENS1_transcriber">
   <resp when="2014">Transcriber</resp>
   <name>Janelle Jenstad</name>
-</respStmt>

    11.3.22. att.global.source

    att.global.source provides an attribute used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor encodingDesc entry etym extent figDesc figure fileDesc form front funder g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt seg sense seriesStmt sourceDesc stress syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xr]
    AttributesAttributes
    sourcespecifies the source from which some aspect of this element is drawn.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    The source attribute points to an external source. When used on elements describing schema components such as <schemaSpec> or <moduleRef> it identifies the source from which declarations for the components of the object being defined may be obtained.

    On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

    In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, or private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

    If more than one location is specified, the default assumption is that the required source should be obtained by combining the resources indicated.

    Example
    <p>
+</respStmt>

    12.3.23. att.global.source

    att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]

    Moduletei — Specification
    Membersatt.global[TEI analytic appInfo author authority availability back bibl biblScope biblStruct body c char charDecl charName charProp cit citedRange classDecl date def dictScrap distributor div edition editionStmt editor editorialDecl email encodingDesc entry etym extent figDesc figure fileDesc forename form front g gloss glyph glyphName gram gramGrp graphic head hi hyph idno imprint lang lbl licence listBibl localProp mapping metamark monogr name namespace note notesStmt orgName orth p pc persName placeName profileDesc projectDesc pron pubPlace publicationStmt publisher quote ref rendition resp respStmt revisionDesc seg sense seriesStmt sourceDesc stress surname syll tagUsage tagsDecl teiHeader term text title titleStmt unicodeName unicodeProp unihanProp usg value xenoData xr]
    AttributesAttributes
    sourcespecifies the source from which some aspect of this element is drawn.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    The source attribute points to an external source. When used on elements describing schema components such as <schemaSpec> or <moduleRef> it identifies the source from which declarations for the components of the object being defined may be obtained.

    On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

    In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, or private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

    If more than one location is specified, the default assumption is that the required source should be obtained by combining the resources indicated.

    Example
    <p>
   <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
      term.</quote>
   <!-- ... -->
-</p>
    Example
    <p>
+</p>
    Example
    <p>
   <!-- ... -->
   <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
      less we seem to know.</quote>
@@ -4678,29 +5196,29 @@
 <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
      Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.
 
-</bibl>
    Example
    <elementRef key="p" source="tei:2.0.1"/>
    Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
    Example
    <schemaSpec ident="myODD" source="mycompiledODD.xml">
+</bibl>
    Example
    <elementRef key="p" source="tei:2.0.1"/>
    Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
    Example
    <schemaSpec ident="myODD" source="mycompiledODD.xml">
   <!-- further declarations specifying the components required -->
-</schemaSpec>
    Create a schema using components taken from the file mycompiledODD.xml.

    11.3.23. att.internetMedia

    att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.

    Moduletei — Specification
    Membersatt.media[graphic] ref
    AttributesAttributes
    mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
    <ref mimeType="application/tei+xml; charset=UTF-8"
- target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/>
    Note

    This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

    11.3.24. att.lexicographic

    att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    Membersdef etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr
    AttributesAttributes att.datcat (@datcat, @valueDatcat) att.lexicographic.normalized (@norm, @orig)
    expandgives an expanded form of information presented more concisely in the dictionary
    StatusOptional
    Datatypeteidata.text
    <gramGrp>
+</schemaSpec>
    Create a schema using components taken from the file mycompiledODD.xml.

    12.3.24. att.internetMedia

    att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.

    Moduletei — Specification
    Membersatt.media[graphic] ref
    AttributesAttributes
    mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
    StatusOptional
    Datatype1–∞ occurrences of teidata.word separated by whitespace
    ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
    <ref mimeType="application/tei+xml; charset=UTF-8"
+ target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/>
    Note

    This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

    12.3.25. att.lexicographic

    att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [9.2. The Structure of Dictionary Entries]

    Moduledictionaries — Specification
    Membersdef etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr
    AttributesAttributes att.datcat (@datcat, @valueDatcat) att.lexicographic.normalized (@norm, @orig)
    expand(expand) gives an expanded form of information presented more concisely in the dictionary
    StatusOptional
    Datatypeteidata.text
    <gramGrp>
   <pos expand="noun">n</pos>
-</gramGrp>
    splitgives the list of split values for a merged form
    StatusOptional
    Datatypeteidata.text
    valuegives a value which lacks any realization in the printed source text.
    StatusOptional
    Datatypeteidata.text
    locationindicates an <anchor> element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
    StatusOptional
    Datatypeteidata.pointer
    mergedIngives a reference to another element, where the original appears as a merged form.
    StatusOptional
    Datatypeteidata.pointer
    opt(optional) indicates whether the element is optional or not
    StatusOptional
    Datatypeteidata.truthValue
    Defaultfalse

    11.3.25. att.lexicographic.normalized

    att.lexicographic.normalized provides the norm and orig attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.

    Moduleanalysis — Specification
    Membersatt.lexicographic[def etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr] att.linguistic[pc]
    AttributesAttributes
    norm(normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form
    StatusOptional
    Datatypeteidata.text
    Normalization of part-of-speech information within a dictionary entry.
    <gramGrp>
+</gramGrp>
    split(split) gives the list of split values for a merged form
    StatusOptional
    Datatypeteidata.text
    value(value) gives a value which lacks any realization in the printed source text.
    StatusOptional
    Datatypeteidata.text
    location(location) indicates an <anchor> element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
    StatusOptional
    Datatypeteidata.pointer
    mergedIn(merged into) gives a reference to another element, where the original appears as a merged form.
    StatusOptional
    Datatypeteidata.pointer
    opt(optional) indicates whether the element is optional or not
    StatusOptional
    Datatypeteidata.truthValue
    Defaultfalse

    12.3.26. att.lexicographic.normalized

    att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.

    Moduleanalysis — Specification
    Membersatt.lexicographic[def etym form gram gramGrp hyph lang lbl orth pron ref sense syll usg xr] att.linguistic[pc]
    AttributesAttributes
    norm(normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form
    StatusOptional
    Datatypeteidata.text
    Normalization of part-of-speech information within a dictionary entry.
    <gramGrp>
   <pos norm="noun">n</pos>
-</gramGrp>
    Normalization of a source form in a tokenized historical corpus.
    <s>
+</gramGrp>
    Normalization of a source form in a tokenized historical corpus.
    <s>
   <w>for</w>
   <w norm="virtue's">vertues</w>
   <w>sake</w>
-</s>
    <s>
+</s>
    <s>
   <w norm="persuasion">perswasion</w>
   <w>of</w>
   <w norm="Unity">Vnitie</w>
-</s>
    Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.
    <s>
+</s>
    Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.
    <s>
   <w norm="freiwillig">freywillig</w>
   <pc norm=","
    join="left">/</pc>
   <w norm="unbedrängt">vnbedraͤngt</w>
   <w norm="und">vnd</w>
   <w norm="unverhindert">vnuerhindert</w>
-</s>
    <w norm="Teil">Theyll</w>
    <w norm="Freude">Frewde</w>
    orig(original) gives the original string or is the empty string when the element does not appear in the source text.
    StatusOptional
    Datatypeteidata.text
    Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:
    <w orig="ntsa sia'i">ntsasia'i</w>
    Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:
    <w lemma="he"
+</s>
    <w norm="Teil">Theyll</w>
    <w norm="Freude">Frewde</w>
    orig(original) gives the original string or is the empty string when the element does not appear in the source text.
    StatusOptional
    Datatypeteidata.text
    Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:
    <w orig="ntsa sia'i">ntsasia'i</w>
    Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:
    <w lemma="he"
  pos="pns"
  xml:id="b1afj-003-a-0950">he</w>
 <w lemma="have"
@@ -4712,22 +5230,22 @@
 <w lemma="forth"
  pos="av"
  xml:id="b1afj-003-a-0980"
- orig="sorth">forth</w>
    An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:
    <w lemma="commandment"
+ orig="sorth">forth</w>
    An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:
    <w lemma="commandment"
  pos="n1"
  norm="commandment"
  xml:id="b9avr-018-a-7720"
- orig="commandemēt">commandement</w>
    Note

    It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, <orig>, and <reg> needs to be employed.

    11.3.26. att.linguistic

    att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically <w> and <pc> in the analysis module. [17.4.2. Lightweight Linguistic Annotation]

    Moduleanalysis — Specification
    Memberspc
    AttributesAttributes att.lexicographic.normalized (@norm, @orig)
    lemmaprovides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
    StatusOptional
    Datatypeteidata.text
    <w lemma="wife">wives</w>
    <w lemma="Arznei">Artzeneyen</w>
    lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
    StatusOptional
    Datatypeteidata.pointer
    <w type="verb"
+ orig="commandemēt">commandement</w>
    Note

    It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on <choice>, <orig>, and <reg> needs to be employed.

    12.3.27. att.linguistic

    att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically <w> and <pc> in the analysis module. [17.4.2. Lightweight Linguistic Annotation]

    Moduleanalysis — Specification
    Memberspc
    AttributesAttributes att.lexicographic.normalized (@norm, @orig)
    lemmaprovides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
    StatusOptional
    Datatypeteidata.text
    <w lemma="wife">wives</w>
    <w lemma="Arznei">Artzeneyen</w>
    lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
    StatusOptional
    Datatypeteidata.pointer
    <w type="verb"
  lemma="hit"
  lemmaRef="http://www.example.com/lexicon/hitvb.xml">hitt<m type="suffix">ing</m>
-</w>
    pos(part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.).
    StatusOptional
    Datatypeteidata.text
    The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).
    <s>
+</w>
    pos(part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.).
    StatusOptional
    Datatypeteidata.text
    The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).
    <s>
   <w pos="PPER">Wir</w>
   <w pos="VVFIN">fahren</w>
   <w pos="APPR">in</w>
   <w pos="ART">den</w>
   <w pos="NN">Urlaub</w>
   <w pos="$.">.</w>
-</s>
    The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).
    <p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p>
-        
    The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.
    <p>
+</s>
    The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).
    <p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p>
+        
    The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.
    <p>
   <w pos="PPIS2">We</w>
   <w pos="VBR">'re</w>
   <w pos="VVG">going</w>
@@ -4739,7 +5257,7 @@
   <w pos="AT1">a</w>
   <w pos="NNT1">month</w>
   <pc pos="!">!</pc>
-</p>
    msd(morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features).
    StatusOptional
    Datatypeteidata.text
    <ab>
+</p>
    msd(morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features).
    StatusOptional
    Datatypeteidata.text
    <ab>
   <w pos="PPER"
    msd="1.Pl.*.Nom">Wir</w>
   <w pos="VVFIN"
@@ -4752,7 +5270,7 @@
    msd="Masc.Akk.Sg">Urlaub</w>
   <pc pos="$."
    msd="--">.</pc>
-</ab>
    joinwhen present, it provides information on whether the token in question is adjacent to another, and if so, on which side. The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.
    StatusOptional
    Datatypeteidata.text
    Legal values are:
    no
    (the token is not adjacent to another)
    left
    (there is no whitespace on the left side of the token)
    right
    (there is no whitespace on the right side of the token)
    both
    (there is no whitespace on either side of the token)
    overlap
    (the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream)
    The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.
    <s>
+</ab>
    joinwhen present, it provides information on whether the token in question is adjacent to another, and if so, on which side. The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.
    StatusOptional
    Datatypeteidata.text
    Legal values are:
    no
    (the token is not adjacent to another)
    left
    (there is no whitespace on the left side of the token)
    right
    (there is no whitespace on the right side of the token)
    both
    (there is no whitespace on either side of the token)
    overlap
    (the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream)
    The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.
    <s>
   <pc join="right">"</pc>
   <w join="left">Friends</w>
   <w>will</w>
@@ -4760,7 +5278,7 @@
   <w join="right">friends</w>
   <pc join="both">.</pc>
   <pc join="left">"</pc>
-</s>
    Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.
    The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.
    <p>
+</s>
    Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.
    The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.
    <p>
   <w pos="PNP">We</w>
   <w pos="VBB"
    join="left">'re</w>
@@ -4769,12 +5287,12 @@
   <w pos="NN1">vacation</w>
   <pc pos="PUN"
    join="left">.</pc>
-</p>
    Note

    These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion.

    11.3.27. att.media

    att.media provides attributes for specifying display and related properties of external media.

    Moduletei — Specification
    Membersgraphic
    AttributesAttributes att.internetMedia (@mimeType)
    widthWhere the media are displayed, indicates the display width
    StatusOptional
    Datatypeteidata.outputMeasurement
    heightWhere the media are displayed, indicates the display height
    StatusOptional
    Datatypeteidata.outputMeasurement
    scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
    StatusOptional
    Datatypeteidata.numeric

    11.3.28. att.naming

    att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. Referring Strings 13.3.6. Names and Nyms]

    Moduletei — Specification
    Membersatt.personal[name orgName persName placeName] author editor pubPlace
    AttributesAttributes att.canonical (@key, @ref)
    rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
    StatusOptional
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

    11.3.29. att.notated

    att.notated provides an attribute to indicate any specialised notation used for element content.

    Moduletei — Specification
    Membersc hyph orth pron quote ref seg stress syll
    AttributesAttributes
    notationnames the notation used for the content of the element.
    StatusOptional
    Datatypeteidata.enumerated

    11.3.30. att.partials

    att.partials provides attributes for describing the extent of lexical references for a dictionary term.

    Moduletei — Specification
    Membersorth pron
    AttributesAttributes
    extentindicates whether the pronunciation or orthography applies to all or part of a word.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    full
    (full form)
    pref
    (prefix)
    suff
    (suffix)
    inf
    (infix)
    part
    (partial)
    Note

    This attribute is optional, and no default value is specified, so it can be omitted if this information is not necessary.

    11.3.31. att.personal

    att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]

    Moduletei — Specification
    Membersname orgName persName placeName
    AttributesAttributes att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    yes
    the name component is spelled out in full.[Default]
    abb
    (abbreviated) the name component is given in an abbreviated form.
    init
    (initial letter) the name component is indicated only by one initial.
    sortspecifies the sort order of the name component in relation to others within the name.
    StatusOptional
    Datatypeteidata.count

    11.3.32. att.placement

    att.placement provides attributes for describing where on the source page or object a textual element appears. [3.4.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]

    Moduletei — Specification
    Membersfigure head metamark note
    AttributesAttributes
    placespecifies where this item is placed.
    StatusRecommended
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    Suggested values include:
    below
    below the line
    bottom
    at the foot of the page
    margin
    in the margin (left, right, or both)
    top
    at the top of the page
    opposite
    on the opposite, i.e. facing, page
    overleaf
    on the other side of the leaf
    above
    above the line
    end
    at the end of e.g. chapter or volume.
    inline
    within the body of the text.
    inspace
    in a predefined space, for example left by an earlier scribe.
    <add place="margin">[An addition written in the margin]</add>
+</p>
    Note

    These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion.

    12.3.28. att.media

    att.media provides attributes for specifying display and related properties of external media.

    Moduletei — Specification
    Membersgraphic
    AttributesAttributes att.internetMedia (@mimeType)
    widthWhere the media are displayed, indicates the display width
    StatusOptional
    Datatypeteidata.outputMeasurement
    heightWhere the media are displayed, indicates the display height
    StatusOptional
    Datatypeteidata.outputMeasurement
    scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
    StatusOptional
    Datatypeteidata.numeric

    12.3.29. att.naming

    att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]

    Moduletei — Specification
    Membersatt.personal[forename name orgName persName placeName surname] author editor pubPlace
    AttributesAttributes att.canonical (@key, @ref)
    rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
    StatusOptional
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

    12.3.30. att.notated

    att.notated provides attributes to indicate any specialised notation used for element content.

    Moduletei — Specification
    Membersc hyph orth pron quote ref seg stress syll
    AttributesAttributes
    notationnames the notation used for the content of the element.
    StatusOptional
    Datatypeteidata.enumerated

    12.3.31. att.partials

    att.partials provides attributes for describing the extent of lexical references for a dictionary term.

    Moduletei — Specification
    Membersorth pron
    AttributesAttributes
    extentindicates whether the pronunciation or orthography applies to all or part of a word.
    StatusOptional
    Datatypeteidata.enumerated
    Suggested values include:
    full
    (full form)
    pref
    (prefix)
    suff
    (suffix)
    inf
    (infix)
    part
    (partial)
    Note

    This attribute is optional, and no default value is specified, so it can be omitted if this information is not necessary.

    12.3.32. att.personal

    att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]

    Moduletei — Specification
    Membersforename name orgName persName placeName surname
    AttributesAttributes att.naming (@role, @nymRef) (att.canonical (@key, @ref))
    fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    yes
    (yes) the name component is spelled out in full.[Default]
    abb
    (abbreviated) the name component is given in an abbreviated form.
    init
    (initial letter) the name component is indicated only by one initial.
    sort(sort) specifies the sort order of the name component in relation to others within the name.
    StatusOptional
    Datatypeteidata.count

    12.3.33. att.placement

    att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]

    Moduletei — Specification
    Membersfigure head metamark note
    AttributesAttributes
    placespecifies where this item is placed.
    StatusRecommended
    Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
    Suggested values include:
    top
    at the top of the page
    bottom
    at the foot of the page
    margin
    in the margin (left, right, or both)
    opposite
    on the opposite, i.e. facing, page
    overleaf
    on the other side of the leaf
    above
    above the line
    right
    to the right, e.g. to the right of a vertical line of text, or to the right of a figure
    below
    below the line
    left
    to the left, e.g. to the left of a vertical line of text, or to the left of a figure
    end
    at the end of e.g. chapter or volume.
    inline
    within the body of the text.
    inspace
    in a predefined space, for example left by an earlier scribe.
    <add place="margin">[An addition written in the margin]</add>
 <add place="bottom opposite">[An addition written at the
- foot of the current page and also on the facing page]</add>
    <note place="bottom">Ibid, p.7</note>

    11.3.33. att.pointing

    att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.6. Simple Links and Cross-References]

    Moduletei — Specification
    MemberscitedRange gloss licence note ref term
    AttributesAttributes
    targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
    StatusOptional
    Datatypeteidata.language
    Schematron
    
+ foot of the current page and also on the facing page]</add>
    <note place="bottom">Ibid, p.7</note>

    12.3.34. att.pointing

    att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]

    Moduletei — Specification
    MemberscitedRange gloss licence note ref term
    AttributesAttributes
    targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
    StatusOptional
    Datatypeteidata.language
    Schematron
    
 <sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
 <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
-</sch:rule>
    <linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
+</sch:rule>
    <linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
   <ptr xml:id="pol-swh_aln_2.1.1-ptr"
    target="pol/UDHR/text.xml#pol_txt_1-head"
    type="tuv"
@@ -4783,23 +5301,23 @@
    target="swh/UDHR/text.xml#swh_txt_1-head"
    type="tuv"
    targetLang="sw"/>
-</linkGrp>
    In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
    Note

    The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

    targetspecifies the destination of the reference by supplying one or more URI References
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

    evaluatespecifies the intended meaning when the target of a pointer is itself a pointer.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    all
    if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
    one
    if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
    none
    no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
    Note

    If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

    11.3.34. att.ranging

    att.ranging provides attributes for describing numerical ranges.

    Moduletei — Specification
    Membersatt.dimensions[date]
    AttributesAttributes
    atLeastgives a minimum estimated value for the approximate measurement.
    StatusOptional
    Datatypeteidata.numeric
    atMostgives a maximum estimated value for the approximate measurement.
    StatusOptional
    Datatypeteidata.numeric
    minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
    StatusOptional
    Datatypeteidata.numeric
    maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
    StatusOptional
    Datatypeteidata.numeric
    confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
    StatusOptional
    Datatypeteidata.probability
    Example
    The MS. was lost in transmission by mail from <del rend="overstrike">
+</linkGrp>
    In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
    Note

    The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

    targetspecifies the destination of the reference by supplying one or more URI References
    StatusOptional
    Datatype1–∞ occurrences of teidata.pointer separated by whitespace
    Note

    One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

    evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    all
    if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
    one
    if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
    none
    no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
    Note

    If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

    12.3.35. att.ranging

    att.ranging provides attributes for describing numerical ranges.

    Moduletei — Specification
    Membersatt.dimensions[date]
    AttributesAttributes
    atLeastgives a minimum estimated value for the approximate measurement.
    StatusOptional
    Datatypeteidata.numeric
    atMostgives a maximum estimated value for the approximate measurement.
    StatusOptional
    Datatypeteidata.numeric
    minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
    StatusOptional
    Datatypeteidata.numeric
    maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
    StatusOptional
    Datatypeteidata.numeric
    confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
    StatusOptional
    Datatypeteidata.probability
    Example
    The MS. was lost in transmission by mail from <del rend="overstrike">
   <gap reason="illegible" extent="one or two letters" atLeast="1" atMost="2"
    unit="chars"/>
 </del> Philadelphia to the Graphic office, New York.
-

    11.3.35. att.resourced

    att.resourced provides attributes by which a resource (such as an externally held media file) may be located.

    Moduletei — Specification
    Membersgraphic
    AttributesAttributes
    url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
    StatusRequired
    Datatypeteidata.pointer

    11.3.36. att.scoped

    att.scoped 

    Modulederived-module-TEILex0
    Membersref
    AttributesAttributes
    scopeTEI Lex-0 specific class for providing elements with an attribute describing their extent.
    StatusOptional
    Sample values include
    currentEntry
    externalEntry

    11.3.37. att.segLike

    att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

    Moduletei — Specification
    Membersc pc seg
    AttributesAttributes att.datcat (@datcat, @valueDatcat) att.fragmentable (@part)
    functioncharacterizes the function of the segment.
    StatusOptional
    Datatypeteidata.enumerated
    Note

    Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

    11.3.38. att.sortable

    att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]

    Moduletei — Specification
    Membersbibl biblStruct entry idno listBibl term
    AttributesAttributes
    sortKeysupplies the sort key for this element in an index, list or group which contains it.
    StatusOptional
    Datatypeteidata.word
    David's other principal backer, Josiah
+

    12.3.36. att.resourced

    att.resourced provides attributes by which a resource (such as an externally held media file) may be located.

    Moduletei — Specification
    Membersgraphic
    AttributesAttributes
    url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
    StatusRequired
    Datatypeteidata.pointer

    12.3.37. att.scoped

    att.scoped 

    Modulederived-module-TEILex0
    Membersref
    AttributesAttributes
    scopeTEI Lex-0 specific class for providing elements with an attribute describing their extent.
    StatusOptional
    Sample values include
    currentEntry
    externalEntry

    12.3.38. att.segLike

    att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

    Moduletei — Specification
    Membersc pc seg
    AttributesAttributes att.datcat (@datcat, @valueDatcat) att.fragmentable (@part)
    function(function) characterizes the function of the segment.
    StatusOptional
    Datatypeteidata.enumerated
    Note

    Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

    12.3.39. att.sortable

    att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]

    Moduletei — Specification
    Membersbibl biblStruct entry idno listBibl term
    AttributesAttributes
    sortKeysupplies the sort key for this element in an index, list or group which contains it.
    StatusOptional
    Datatypeteidata.word
    David's other principal backer, Josiah
  ha-Kohen <index indexName="NAMES">
   <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
 </index> b. Azarya, son of one of the last gaons of Sura was David's own first
- cousin.
    Note

    The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

    Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

    11.3.39. att.spanning

    att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]

    Moduletei — Specification
    Membersmetamark
    AttributesAttributes
    spanToindicates the end of a span initiated by the element bearing this attribute.
    StatusOptional
    Datatypeteidata.pointer
    SchematronThe @spanTo attribute must point to an element following the current element
    
+ cousin.
    Note

    The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

    Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

    12.3.40. att.spanning

    att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]

    Moduletei — Specification
    Membersmetamark
    AttributesAttributes
    spanToindicates the end of a span initiated by the element bearing this attribute.
    StatusOptional
    Datatypeteidata.pointer
    SchematronThe @spanTo attribute must point to an element following the current element
    
 <sch:rule context="tei:*[@spanTo]">
 <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
 </sch:assert>
-</sch:rule>
    Note

    The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

    11.3.40. att.styleDef

    att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.

    Moduletei — Specification
    Membersrendition
    AttributesAttributes
    schemeidentifies the language used to describe the rendition.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    css
    Cascading Stylesheet Language
    xslfo
    Extensible Stylesheet Language Formatting Objects
    free
    Informal free text description
    other
    A user-defined rendition description language
    Note

    If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

    schemeVersionsupplies a version number for the style language provided in scheme.
    StatusOptional
    Datatypeteidata.versionNumber
    Schematron
    
+</sch:rule>
    Note

    The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

    12.3.41. att.styleDef

    att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.

    Moduletei — Specification
    Membersrendition
    AttributesAttributes
    schemeidentifies the language used to describe the rendition.
    StatusOptional
    Datatypeteidata.enumerated
    Legal values are:
    css
    Cascading Stylesheet Language
    xslfo
    Extensible Stylesheet Language Formatting Objects
    free
    Informal free text description
    other
    A user-defined rendition description language
    Note

    If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

    schemeVersionsupplies a version number for the style language provided in scheme.
    StatusOptional
    Datatypeteidata.versionNumber
    Schematron
    
 <sch:rule context="tei:*[@schemeVersion]">
 <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified.
 </sch:assert>
-</sch:rule>
    Note

    If schemeVersion is used, then scheme should also appear, with a value other than free.

    11.3.41. att.translatable

    att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.

    Moduletei — Specification
    Membersgloss
    AttributesAttributes
    versionDatespecifies the date on which the source text was extracted and sent to the translator
    StatusOptional
    Datatypeteidata.temporal.w3c
    Note

    The versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

    12.3.42. att.typed

    att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]

    Moduletei — Specification
    MembersTEI bibl biblStruct c charProp cit date div etym figure forename form g gloss gram gramGrp head idno lbl listBibl mapping name note orgName orth pc persName placeName pron quote ref seg surname term text title usg xenoData xr
    AttributesAttributes
    typecharacterizes the element in some sense, using any convenient classification scheme or typology.
    StatusOptional
    Datatypeteidata.enumerated
    <div type="verse">
   <head>Night in Tarras</head>
   <lg type="stanza">
      <l>At evening tramping on the hot white road</l>
@@ -4809,10 +5327,10 @@
      <l>A wind sprang up from nowhere as the sky</l>
      <l>…</l>
   </lg>
-</div>
    Note

    The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

    subtypeprovides a sub-categorization of the element, if needed
    StatusOptional
    Datatypeteidata.enumerated
    Note

    The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

    Schematron
    
+</div>
    Note

    The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

    subtype(subtype) provides a sub-categorization of the element, if needed
    StatusOptional
    Datatypeteidata.enumerated
    Note

    The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

    Schematron
    
 <sch:rule context="tei:*[@subtype]">
 <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
-</sch:rule>
    Note

    When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

    11.3.43. att.written

    att.written provides an attribute to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]

    Moduletei — Specification
    Membersdiv figure head hi note p seg text
    AttributesAttributes
    handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
    StatusOptional
    Datatypeteidata.pointer

    11.4. Macros

    11.4.1. macro.limitedContent

    macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    figDesc rendition tagUsage
    Content model
    
+</sch:rule>
    Note

    When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

    12.3.43. att.written

    att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]

    Moduletei — Specification
    Membersdiv figure head hi note p seg text
    AttributesAttributes
    handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
    StatusOptional
    Datatypeteidata.pointer

    12.4. Macros

    12.4.1. macro.limitedContent

    macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    figDesc rendition tagUsage
    Content model
    
 <content>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4822,7 +5340,7 @@
  </alternate>
 </content>
    Declaration
    
-macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

    11.4.2. macro.paraContent

    macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    def gram hi hyph lang lbl orth p pron ref seg stress syll title usg
    Content model
    
+macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

    12.4.2. macro.paraContent

    macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    def gram hi hyph lang lbl orth p pron ref seg stress syll title usg
    Content model
    
 <content rend="replace">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4847,7 +5365,7 @@
     | lg
     | model.lLike
     | xr
-   )*

    11.4.3. macro.phraseSeq

    macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]

    Moduletei — Specification
    Used by
    author biblScope citedRange distributor edition editor extent gloss name orgName persName placeName pubPlace publisher term
    Content model
    
+   )*

    12.4.3. macro.phraseSeq

    macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]

    Moduletei — Specification
    Used by
    author biblScope citedRange distributor edition editor email extent forename gloss name orgName persName placeName pubPlace publisher surname term
    Content model
    
 <content>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4860,7 +5378,7 @@
 </content>
    Declaration
    
 macro.phraseSeq =
-   ( text | model.gLike | model.attributable | model.phrase | model.global )*

    11.4.4. macro.phraseSeq.limited

    macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]

    Moduletei — Specification
    Used by
    authority funder resp
    Content model
    
+   ( text | model.gLike | model.attributable | model.phrase | model.global )*

    12.4.4. macro.phraseSeq.limited

    macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]

    Moduletei — Specification
    Used by
    authority resp
    Content model
    
 <content>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4870,7 +5388,7 @@
  </alternate>
 </content>
    Declaration
    
-macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

    11.4.5. macro.specialPara

    macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    licence metamark note quote
    Content model
    
+macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

    12.4.5. macro.specialPara

    macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]

    Moduletei — Specification
    Used by
    licence metamark note quote
    Content model
    
 <content>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4891,7 +5409,7 @@
     | model.inter
     | model.divPart
     | model.global
-   )*

    11.4.6. macro.xtext

    macro.xtext (extended text) defines a sequence of character data and gaiji elements.

    Moduletei — Specification
    Used by
    c mapping value
    Content model
    
+   )*

    12.4.6. macro.xtext

    macro.xtext (extended text) defines a sequence of character data and gaiji elements.

    Moduletei — Specification
    Used by
    c mapping value
    Content model
    
 <content>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
@@ -4900,7 +5418,7 @@
  </alternate>
 </content>
    Declaration
    
-macro.xtext = ( text | model.gLike )*

    11.5. Datatypes

    11.5.1. teidata.certainty

    teidata.certainty defines the range of attribute values expressing a degree of certainty.

    Moduletei — Specification
    Used by
    teidata.probCert
    Content model
    
+macro.xtext = ( text | model.gLike )*

    12.5. Datatypes

    12.5.1. teidata.certainty

    teidata.certainty defines the range of attribute values expressing a degree of certainty.

    Moduletei — Specification
    Used by
    teidata.probCert
    Content model
    
 <content>
  <valList type="closed">
   <valItem ident="high"/>
@@ -4910,28 +5428,28 @@
  </valList>
 </content>
    Declaration
    
-teidata.certainty = "high" | "medium" | "low" | "unknown"
    Note

    Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

    11.5.2. teidata.count

    teidata.count defines the range of attribute values used for a non-negative integer value used as a count.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.certainty = "high" | "medium" | "low" | "unknown"
    Note

    Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

    12.5.2. teidata.count

    teidata.count defines the range of attribute values used for a non-negative integer value used as a count.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="nonNegativeInteger"/>
 </content>
    Declaration
    
-teidata.count = xsd:nonNegativeInteger
    Note

    Any positive integer value or zero is permitted

    11.5.3. teidata.duration.iso

    teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats

    Moduletei — Specification
    Used by
    Content model
    
+teidata.count = xsd:nonNegativeInteger
    Note

    Any positive integer value or zero is permitted

    12.5.3. teidata.duration.iso

    teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </content>
    Declaration
    
-teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
    Example
    <time dur-iso="PT0,75H">three-quarters of an hour</time>
    Example
    <date dur-iso="P1,5D">a day and a half</date>
    Example
    <date dur-iso="P14D">a fortnight</date>
    Example
    <time dur-iso="PT0.02S">20 ms</time>
    Note

    A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

    For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

    11.5.4. teidata.duration.w3c

    teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
    Example
    <time dur-iso="PT0,75H">three-quarters of an hour</time>
    Example
    <date dur-iso="P1,5D">a day and a half</date>
    Example
    <date dur-iso="P14D">a fortnight</date>
    Example
    <time dur-iso="PT0.02S">20 ms</time>
    Note

    A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

    For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

    12.5.4. teidata.duration.w3c

    teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="duration"/>
 </content>
    Declaration
    
-teidata.duration.w3c = xsd:duration
    Example
    <time dur="PT45M">forty-five minutes</time>
    Example
    <date dur="P1DT12H">a day and a half</date>
    Example
    <date dur="P7D">a week</date>
    Example
    <time dur="PT0.02S">20 ms</time>
    Note

    A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

    For complete details, see the W3C specification.

    11.5.5. teidata.enumerated

    teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.duration.w3c = xsd:duration
    Example
    <time dur="PT45M">forty-five minutes</time>
    Example
    <date dur="P1DT12H">a day and a half</date>
    Example
    <date dur="P7D">a week</date>
    Example
    <time dur="PT0.02S">20 ms</time>
    Note

    A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

    For complete details, see the W3C specification.

    12.5.5. teidata.enumerated

    teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef key="teidata.word"/>
 </content>
    Declaration
    
-teidata.enumerated = teidata.word
    Note

    Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

    Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

    11.5.6. teidata.language

    teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.enumerated = teidata.word
    Note

    Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

    Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

    12.5.6. teidata.language

    teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <alternate>
   <dataRef name="language"/>
@@ -4941,17 +5459,17 @@
  </alternate>
 </content>
    Declaration
    
-teidata.language = xsd:language | ( "" )
    Note

    The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

    A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

    language
    The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
    script
    The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
    region
    Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
    variant
    An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
    extension
    An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
    private use
    An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

    There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

    Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

    Examples include

    sn
    Shona
    zh-TW
    Taiwanese
    zh-Hant-HK
    Chinese written in traditional script as used in Hong Kong
    en-SL
    English as spoken in Sierra Leone
    pl
    Polish
    es-MX
    Spanish as spoken in Mexico
    es-419
    Spanish as spoken in Latin America

    The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

    11.5.7. teidata.name

    teidata.name defines the range of attribute values expressed as an XML Name.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.language = xsd:language | ( "" )
    Note

    The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

    A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

    language
    The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
    script
    The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
    region
    Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
    variant
    An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
    extension
    An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
    private use
    An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

    There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

    Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

    Examples include

    sn
    Shona
    zh-TW
    Taiwanese
    zh-Hant-HK
    Chinese written in traditional script as used in Hong Kong
    en-SL
    English as spoken in Sierra Leone
    pl
    Polish
    es-MX
    Spanish as spoken in Mexico
    es-419
    Spanish as spoken in Latin America

    The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

    12.5.7. teidata.name

    teidata.name defines the range of attribute values expressed as an XML Name.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="Name"/>
 </content>
    Declaration
    
-teidata.name = xsd:Name
    Note

    Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

    11.5.8. teidata.namespace

    teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.name = xsd:Name
    Note

    Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

    12.5.8. teidata.namespace

    teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="anyURI"/>
 </content>
    Declaration
    
-teidata.namespace = xsd:anyURI
    Note

    The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

    11.5.9. teidata.numeric

    teidata.numeric defines the range of attribute values used for numeric values.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.namespace = xsd:anyURI
    Note

    The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

    12.5.9. teidata.numeric

    teidata.numeric defines the range of attribute values used for numeric values.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <alternate>
   <dataRef name="double"/>
@@ -4962,7 +5480,7 @@
 </content>
    Declaration
    
 teidata.numeric =
-   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
    Note

    Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

    To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

    A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

    11.5.10. teidata.outputMeasurement

    teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.

    Moduletei — Specification
    Used by
    Content model
    
+   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
    Note

    Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

    To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

    A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

    12.5.10. teidata.outputMeasurement

    teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="token"
   restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"/>
@@ -4972,35 +5490,35 @@
    token
    {
       pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
-   }
    Example
    <figure>
+   }
    Example
    <figure>
   <head>The TEI Logo</head>
   <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
      between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
      background.</figDesc>
   <graphic height="600px" width="600px" url="http://www.tei-c.org/logos/TEI-600.jpg"/>
-</figure>
    Note

    These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

    11.5.11. teidata.pattern

    teidata.pattern defines attribute values which are expressed as a regular expression.

    Moduletei — Specification
    Used by
    Content model
    
+</figure>
    Note

    These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

    12.5.11. teidata.pattern

    teidata.pattern defines attribute values which are expressed as a regular expression.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="token"/>
 </content>
    Declaration
    
-teidata.pattern = token
    Note
    A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
    Wikipedia

    This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

    11.5.12. teidata.point

    teidata.point defines the data type used to express a point in cartesian space.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.pattern = token
    Note
    A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
    Wikipedia

    This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

    12.5.12. teidata.point

    teidata.point defines the data type used to express a point in cartesian space.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="token"
   restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
 </content>
    Declaration
    
-teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
    Example
    <facsimile>
+teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
    Example
    <facsimile>
   <surface ulx="0" uly="0" lrx="400" lry="280">
      <zone points="220,100 300,210 170,250 123,234">
         <graphic url="handwriting.png "/>
      </zone>
   </surface>
-</facsimile>
    Note

    A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

    11.5.13. teidata.pointer

    teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+</facsimile>
    Note

    A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

    12.5.13. teidata.pointer

    teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="anyURI"/>
 </content>
    Declaration
    
-teidata.pointer = xsd:anyURI
    Note

    The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

    11.5.14. teidata.probCert

    teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.pointer = xsd:anyURI
    Note

    The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

    12.5.14. teidata.probCert

    teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <alternate>
   <dataRef key="teidata.probability"/>
@@ -5008,17 +5526,17 @@
  </alternate>
 </content>
    Declaration
    
-teidata.probCert = teidata.probability | teidata.certainty

    11.5.15. teidata.probability

    teidata.probability defines the range of attribute values expressing a probability.

    Moduletei — Specification
    Used by
    teidata.probCert
    Content model
    
+teidata.probCert = teidata.probability | teidata.certainty

    12.5.15. teidata.probability

    teidata.probability defines the range of attribute values expressing a probability.

    Moduletei — Specification
    Used by
    teidata.probCert
    Content model
    
 <content>
  <dataRef name="double"/>
 </content>
    Declaration
    
-teidata.probability = xsd:double
    Note

    Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

    11.5.16. teidata.replacement

    teidata.replacement defines attribute values which contain a replacement template.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.probability = xsd:double
    Note

    Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

    12.5.16. teidata.replacement

    teidata.replacement defines attribute values which contain a replacement template.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <textNode/>
 </content>
    Declaration
    
-teidata.replacement = text

    11.5.17. teidata.temporal.iso

    teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.replacement = text

    12.5.17. teidata.temporal.iso

    teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <alternate>
   <dataRef name="date"/>
@@ -5043,7 +5561,7 @@
  | xsd:gMonthDay
  | xsd:time
  | xsd:dateTime
- | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
    Note

    If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

    For all representations for which ISO 8601 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

    While ISO 8601 permits the use of both 00:00 and 24:00 to represent midnight, these Guidelines strongly recommend against the use of 24:00.

    11.5.18. teidata.temporal.w3c

    teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.

    Moduletei — Specification
    Used by
    Content model
    
+ | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
    Note

    If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

    For all representations for which ISO 8601 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

    While ISO 8601 permits the use of both 00:00 and 24:00 to represent midnight, these Guidelines strongly recommend against the use of 24:00.

    12.5.18. teidata.temporal.w3c

    teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <alternate>
   <dataRef name="date"/>
@@ -5065,36 +5583,36 @@
  | xsd:gYearMonth
  | xsd:gMonthDay
  | xsd:time
- | xsd:dateTime
    Note

    If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

    11.5.19. teidata.text

    teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+ | xsd:dateTime
    Note

    If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

    12.5.19. teidata.text

    teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="string"/>
 </content>
    Declaration
    
-teidata.text = string
    Note

    Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

    11.5.20. teidata.truthValue

    teidata.truthValue defines the range of attribute values used to express a truth value.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.text = string
    Note

    Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

    12.5.20. teidata.truthValue

    teidata.truthValue defines the range of attribute values used to express a truth value.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="boolean"/>
 </content>
    Declaration
    
-teidata.truthValue = xsd:boolean
    Note

    The possible values of this datatype are 1 or true, or 0 or false.

    This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

    11.5.21. teidata.version

    teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.truthValue = xsd:boolean
    Note

    The possible values of this datatype are 1 or true, or 0 or false.

    This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

    12.5.21. teidata.version

    teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="token"
   restriction="[\d]+(\.[\d]+){0,2}"/>
 </content>
    Declaration
    
-teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
    Note

    The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

    11.5.22. teidata.versionNumber

    teidata.versionNumber defines the range of attribute values used for version numbers.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
    Note

    The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

    12.5.22. teidata.versionNumber

    teidata.versionNumber defines the range of attribute values used for version numbers.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <dataRef name="token"
   restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
 </content>
    Declaration
    
 teidata.versionNumber =
-   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

    11.5.23. teidata.word

    teidata.word defines the range of attribute values expressed as a single word or token.

    Moduletei — Specification
    Used by
    teidata.enumeratedElement:
    Content model
    
+   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

    12.5.23. teidata.word

    teidata.word defines the range of attribute values expressed as a single word or token.

    Moduletei — Specification
    Used by
    teidata.enumeratedElement:
    Content model
    
 <content>
  <dataRef name="token"
   restriction="[^\p{C}\p{Z}]+"/>
 </content>
    Declaration
    
-teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
    Note

    Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

    11.5.24. teidata.xTruthValue

    teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
    Note

    Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

    12.5.24. teidata.xTruthValue

    teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <alternate>
   <dataRef name="boolean"/>
@@ -5105,17 +5623,17 @@
  </alternate>
 </content>
    Declaration
    
-teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
    Note

    In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

    11.5.25. teidata.xmlName

    teidata.xmlName defines attribute values which contain an XML name.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
+teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
    Note

    In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

    12.5.25. teidata.xmlName

    teidata.xmlName defines attribute values which contain an XML name.

    Moduletei — Specification
    Used by
    Element:
    Content model
    
 <content>
  <dataRef name="NCName"/>
 </content>
    Declaration
    
-teidata.xmlName = xsd:NCName
    Note

    The rules defining an XML name form a part of the XML Specification.

    11.5.26. teidata.xpath

    teidata.xpath defines attribute values which contain an XPath expression.

    Moduletei — Specification
    Used by
    Content model
    
+teidata.xmlName = xsd:NCName
    Note

    The rules defining an XML name form a part of the XML Specification.

    12.5.26. teidata.xpath

    teidata.xpath defines attribute values which contain an XPath expression.

    Moduletei — Specification
    Used by
    Content model
    
 <content>
  <textNode/>
 </content>
    Declaration
    
-teidata.xpath = text
    Note

    Any XPath expression using the syntax defined in [[undefined XSLT2]].

    When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

    12. Frequently Asked Questions

    12.1. How do I start using TEI Lex-0 in my project?

    To start using TEI Lex-0 in your own dictionary project, you need to set up your favorite XML editor to validate your dictionary against the TEI Lex-0 schema. This, you can do:

    • in oXygen XML Editor, by associating an existing TEI document with the TEI Lex-0 schema's url: https://raw.githubusercontent.com/DARIAH-ERIC/lexicalresources/master/Schemas/TEILex0/out/TEILex0.rng using either menubar actions (Document > Schema > Associate Schema) or the red-pin icon in the oXygen menu bar. Both of these methods will display the Associate Schema dialog box:
      Figure 2: Associating schema in oXygen XML Editor
    • manually by including the following xml processing instructions at the top of your TEI file: 
        
+teidata.xpath = text
    Note

    Any XPath expression using the syntax defined in 6.2..

    When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

    13. Frequently Asked Questions

    13.1. How do I start using TEI Lex-0 in my project?

    To start using TEI Lex-0 in your own dictionary project, you need to set up your favorite XML editor to validate your dictionary against the TEI Lex-0 schema. This, you can do:

    • in oXygen XML Editor, by associating an existing TEI document with the TEI Lex-0 schema's url: https://raw.githubusercontent.com/DARIAH-ERIC/lexicalresources/master/Schemas/TEILex0/out/TEILex0.rng using either menubar actions (Document > Schema > Associate Schema) or the red-pin icon in the oXygen menu bar. Both of these methods will display the Associate Schema dialog box:
      Figure 2: Associating schema in oXygen XML Editor
    • manually by including the following xml processing instructions at the top of your TEI file: 
        
 <?xml version="1.0" encoding="UTF-8"?> 
 <?xml-model href="https://raw.githubusercontent.com/DARIAH-ERIC/lexicalresources/master/Schemas/TEILex0/out/TEILex0.rng" 
     type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
@@ -5124,17 +5642,17 @@
 <TEI xmlns="http://www.tei-c.org/ns/1.0">
 <!--etc.--> 
 </TEI>
-
    • by downloading the schema file from https://raw.githubusercontent.com/DARIAH-ERIC/lexicalresources/master/Schemas/TEILex0/out/TEILex0.rng and associating your xml file with it, using either of the above mentioned methods (see 1).

    Once you associate your dictionary file with the TEI Lex-0 schema, you can use your XML editor to validate it.

    12.2. What should I do if I don't know how to encode something in TEI Lex-0?

    TEI Lex-0 is a community-based project. If you have a question or need help encoding lexicographic data using TEI Lex-0, get in touch using our issue tracker here on GitHub.

    12.3. How can I contribute to the development of TEI Lex-0?

    More advanced users can propose solutions by submitting pull requests. Make sure you understand the internal nitty-gritty as well as our GitHub workflow.

    12.3.1. The internal nitty-gritty

    • TEILex0.odd is an index file: it uses a bunch of <xi:include> pointers to individual "chapters" which live in TEILex0.parts
    • examples of dictionary entries encoded in TEI Lex-0 live in a file called examples.xml inside the folder TEILex0.examples
    • examples.xml validates against the TEI Lex-0 schema compiled in out/TEILex0.rng
    • stylesheets/tei-stripper.xsl is used to strip the TEI examples file of the TEI namespace, replacing it with "http://www.tei-c.org/ns/Examples" so that they can be used directly inside <egXML> in our ODD file. For more info about why this is necessary, see https://github.com/BCDH/tei-strip-and-include.
    • to include validated examples, you can either point to the id of the element you want to include using the xpointer() scheme like this: 
         
+
    • by downloading the schema file from https://raw.githubusercontent.com/DARIAH-ERIC/lexicalresources/master/Schemas/TEILex0/out/TEILex0.rng and associating your xml file with it, using either of the above mentioned methods (see 1).

    Once you associate your dictionary file with the TEI Lex-0 schema, you can use your XML editor to validate it.

    13.2. What should I do if I don't know how to encode something in TEI Lex-0?

    TEI Lex-0 is a community-based project. If you have a question or need help encoding lexicographic data using TEI Lex-0, get in touch using our issue tracker here on GitHub.

    13.3. How can I contribute to the development of TEI Lex-0?

    More advanced users can propose solutions by submitting pull requests. Make sure you understand the internal nitty-gritty as well as our GitHub workflow.

    13.3.1. The internal nitty-gritty

    • TEILex0.odd is an index file: it uses a bunch of <xi:include> pointers to individual "chapters" which live in TEILex0.parts
    • examples of dictionary entries encoded in TEI Lex-0 live in a file called examples.xml inside the folder TEILex0.examples
    • examples.xml validates against the TEI Lex-0 schema compiled in out/TEILex0.rng
    • stylesheets/tei-stripper.xsl is used to strip the TEI examples file of the TEI namespace, replacing it with "http://www.tei-c.org/ns/Examples" so that they can be used directly inside <egXML> in our ODD file. For more info about why this is necessary, see https://github.com/BCDH/tei-strip-and-include.
    • to include validated examples, you can either point to the id of the element you want to include using the xpointer() scheme like this: 
         
 <egXML xmlns="http://www.tei-c.org/ns/Examples"> 
   <xi:include href="../TEILex0.examples/examples.stripped.xml" 
       corresp="../TEILex0.examples/examples.xml" xpointer="pflaume"/>
 </egXML> 
-                
      or, using the element() scheme, you can also include segments: 
         
+                
      or, using the element() scheme, you can also include segments: 
         
 <egXML xmlns="http://www.tei-c.org/ns/Examples"> 
   <xi:include href="../TEILex0.examples/examples.stripped.xml"
       corresp="../TEILex0.examples/examples.xml"
       xpointer="element(MZ.RGJS.сејче/4/1)"/> 
-</egXML> 
    • If you are using oXygen XML, clicking on the link in Author Mode will take you directly to the element or fragment in the examples.xml for editing XML.
      Figure 3: testing captions
    • After making any changes to examples.xml, use the tei-stripper.xsl (or the include TEI Stripper transformation scenario in oXygen) to produce examples.stripped.xml. Without this step, the examples in your ODD file will not validate.

    12.3.2. GitHub Workflow

    Before submitting your proposal to change something in the TEI Lex-0 specification or the narrative guidelines, make sure:

    • you have received some feedback from the community using our GitHub issues
    • you understand the internal nitty-gritty of how the TEI Lex-0 source files are organized and how the guidelines and the RNG schema is generated from ODD

    To implement changes, make sure to follow our GitHub forklow:

    • if you're starting for the first time, fork the lexical-resources repository; then clone your fork on your machine; the cloned fork is your so-called working copy; the original repository from which you made your clone is called "upstream"
    • if you've forked and cloned the lexical-resources repository before, make sure the master branch in your working copy is up-to-date by fetching the latest changes and merging them into your working master branch from the upstream master
    • create a new branch off your master branch; name it appropriately (e.g. fix-attr-values-on-sense)
    • do the work (changing the specification, adding examples, or changing the narrative sections) in the specific branch you created for this particular issue
    • commit and push your changes
    • once you've finished implementing all the changes needed, create a pull-request
    • if editors ask you to make additional changes, keep working in the same branch (i.e. fix-attr-values-on-sense); commit and push; your changes will be automatically added to your pull request
    • once the editors accept your pull request, you can safely delete the branch from which you created your pull request (i.e. fix.attr-values-on-sense)
    • once your pull request has been merged into the upstream master branch by the editors, you can bring the master branch in your working copy up to date by fetching and merging changes from upstream master; then pushing them to your remote repo

    12.4. How can I convert dictionaries from TEI Lex-0 to Ontolex-Lemon?

    Funny you should ask, because we have exactly what you're looking for. Check out the tei2ontolex stylesheet.