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

1.2.4. The Rahtz Prize

In recognition of their work on TEI Lex-0, the DARIAH WG Lexical Resources was awarded the 2020 Rahtz Prize for TEI Ingenuity.

Members of the DARIAH Working Group Lexical Resources have made a valuable contribution to the Dictionaries Chapter of the TEI Guidelines. Their efforts and their expertise have been formidable and highly appreciated by the TEI Community for many years. — Martina Scholger, Chair of the TEI Technical Council

1.2.5. 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.6. 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:

• Lexical Data Masterclass 2017. 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), CLARIN and DARIAH-DE. For an overview, check out this blog post.
• 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 Ministry for Higher Education, Research and Innovation (MESRI), ELEXIS, CLARIN and DARIAH-DE. For an overview, check out From Àbèsàbèsì to XPath on DigiLex.
• From Print to Screen: The Theory and Practice of Digitizing Dictionaries. Lisbon Summer School in Linguistics (2-6 July 2018).
• Encoding Dictionaries with TEI: A Masterclass. Lisbon Summer School in Linguistics (1-5 July 2019).
• DH Training Workshop: Digital Methods for Linguistic Investigation (13-15 November 2019). Organized by the Seminar für Semitistik und Arabistik, Freie Universität Berlin, with the support of the Alexander von Humboldt Foundation and Syncro Soft.

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

A picture is worth a thousand words

Figure 1: TEI Lex-0 would not be possible without joint community effort

1.4.1. How to cite these guidelines

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.3. DARIAH Working Group on Lexical Resources. https://dariah-eric.github.io/lexicalresources/pages/TEILex0/TEILex0.html.

Toma Tasovac, Laurent Romary et al. 2018. TEI Lex-0: A baseline encoding for lexicographic data. Version 0.9.3. 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.

• spec<catDesc> must contain a <term>
• specswitch to using the external TEI add-on in oXygen when generating schema and documentation
• specfix the mismatch in <usg> types between the specification and documentation (use temporal instead of time
• specrequire <listBibl> in <sourceDesc> with three suggested type values: dictionaries, corpora and literature

• xprocswitch to using oXygen's TEI framework when generating schema and documentation
• specallow <list> and <item> because lists feature prominently in dictionary front matter
• specintroduce model.lexicalInter (based on model.inter), model.lexicalPhrase (based on model.phrase) and macro.lexicalParaContent (based on macro.paraContent) to make it easier to simplify the content model of various dictionary elements
• specremove model.listLike from model.lexicalInter
• htmllink version number in the menu to revision history
• specallow <abbr> and <expan> so that they can be used in lists of abbreviations in dictionary front matter
• specintroduced valency as a suggested value in gram[@type="valency"]
• specintroduced gram[@type="government"] and clarified the difference from gram[@type="colloc"]. See sections on Typology of gram and Collocates
• specmade @type mandatory on <TEI>
• specadd <principal> and <affiliation> for more robust metadata in the <teiHeader>

• htmlfix namespace issues in html output
• docsadd new examples to the Header section
• docsadd section on hierarchichal usage labels
• specallow <taxonomy>, <category> and <catDesc> in <classDecl>
• docsmove the specification to a different webpage for quicker loading

• docsadd section on TEI Header
• docscorrection of various misspellings
• specadd <monogr> (needed for <biblStruct>)
• specadd <forename> and <surname> for more fine-grained bibliographic information
• specadd <editorialDecl>
• specadd <email> to make possible contact information in the header
• specrequire <availability> in <publicationStmt> to provide <licence>
• specmake <sourceDesc> optional
• specallow only <biblStruct> in <sourceDesc>
• specmake model.publicationStmtPart.agency unbound to allow both <publisher> and <authority> in <publicationStmt>
• specadd role to <authority> with suggested values: funder, sponsor, rightsHolder
• specrequire <language>, <langUsage> and <profileDesc>
• specadd role to <language> with a closed list of values: objectLanguage, workingLanguage, sourceLanguage, targetLanguage

2.2.1. Source description

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 that the sources be grouped in <listBibl> elements:

• <listBibl type="dictionaries"></listBibl> lists all the dictionaries that were used as a source for the given dictionary; if you are retrodigitizing a print dictionary, your <listBibl> may include only one <biblStruct> with the bibliographic information about your print source;
• <listBibl type="literature"></listBibl> groups all the literature: for instance, all the sources used by the dictionary author to illustrate examples;
• <listBibl type="corpora"></listBibl> groups the information on all the corpora that were used in the production of the given lexicographic resource.

TEI Lex-0 requires the use of <biblStruct> for structuring bibliographic information about each individual source. This, too, is a departure from vanilla TEI which is more permissive in this respect.

<sourceDesc xml:base="../TEILex0.examples/headers/VOLP.stripped.xml">
  <listBibl type="dictionaries">
     <biblStruct>
        <monogr>
           <title>Vocabulário Ortográfico da Língua Portuguesa</title>
           <author>
              <orgName>Academia das Ciências</orgName>
           </author>
           <imprint>
              <publisher>Imprensa Nacional de Lisboa</publisher>
              <date>1940</date>
           </imprint>
           <extent>1 volume</extent>
           <extent>821 pp.</extent>
        </monogr>
     </biblStruct>
  </listBibl>
</sourceDesc>VOLP (1940) 



<sourceDesc xml:base="../TEILex0.examples/headers/EtymWB-XML.stripped.xml">
  <listBibl type="dictionaries">
     <biblStruct>
        <monogr>
           <author>
              <persName>
                 <forename>Wolfgang</forename>
                 <surname>Pfeifer</surname>
              </persName>
           </author>
           <title>Etymologisches Wörterbuch des Deutschen</title>
           <edition>2</edition>
           <imprint>
              <publisher>Akademie Verlag</publisher>
              <pubPlace>Berlin</pubPlace>
              <date>1993</date>
              <note>with additional notes by the author</note>
           </imprint>
        </monogr>
     </biblStruct>
  </listBibl>
</sourceDesc>EtymWB-XML (2009) 



<sourceDesc xml:base="../TEILex0.examples/headers/St%C4%8DS.stripped.xml">
  <listBibl type="dictionaries">
     <biblStruct>
        <monogr>
           <title level="m" type="main">Staročeský slovník</title>
           <title level="m" type="sub">[Seš.] 1–26: na – při</title>
           <editor>
              <persName>
                 <forename>Bohuslav</forename>
                 <surname>Havránek</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Vladimír</forename>
                 <surname>Šmilauer</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Václav</forename>
                 <surname>Křístek</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Jan</forename>
                 <surname>Petr</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Igor</forename>
                 <surname>Němec</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Emanuel</forename>
                 <surname>Michálek</surname>
              </persName>
           </editor>
           <editor>
              <persName>
                 <forename>Jaroslava</forename>
                 <surname>Pečírková</surname>
              </persName>
           </editor>
           <imprint>
              <date>1968–2008</date>
              <publisher>Academia</publisher>
              <pubPlace>Praha</pubPlace>
           </imprint>
        </monogr>
     </biblStruct>
     <biblStruct>
        <monogr>
           <title level="m" type="main">Slovník staročeský</title>
           <title level="m" type="sub">A – J</title>
           <author>
              <persName>
                 <forename>Jan</forename>
                 <surname>Gebauer</surname>
              </persName>
           </author>
           <edition>druhé, nezměněné vydání</edition>
           <imprint>
              <date>1970</date>
              <publisher>Academia</publisher>
              <pubPlace>Praha</pubPlace>
           </imprint>
        </monogr>
     </biblStruct>
     <biblStruct>
        <monogr>
           <title level="m" type="main">Slovník staročeský</title>
           <title level="m" type="sub">K – N</title>
           <author>
              <persName>
                 <forename>Jan</forename>
                 <surname>Gebauer</surname>
              </persName>
           </author>
           <edition>druhé, nezměněné vydání</edition>
           <imprint>
              <date>1970</date>
              <publisher>Academia</publisher>
              <pubPlace>Praha</pubPlace>
           </imprint>
        </monogr>
     </biblStruct>
  </listBibl>
</sourceDesc>StčS (1999-2011) 



<sourceDesc xml:base="../TEILex0.examples/headers/Morais.stripped.xml">
  <listBibl type="dictionaries">
     <biblStruct>
        <monogr>
           <title level="m" type="main">Diccionario da lingua portugueza composto pelo padre D. Rafael Bluteau, reformado, e accrescentado por Antonio de Moraes Silva, natural do Rio de Janeiro</title>
           <title level="m" type="sub">A – K</title>
           <author>
              <persName>
                 <forename>António de</forename>
                 <surname>Morais Silva</surname>
              </persName>
           </author>
           <imprint>
              <pubPlace>Lisboa</pubPlace>
              <publisher>Officina de Simão Thaddeo Ferreira</publisher>
              <pubPlace>Lisboa</pubPlace>
              <date when="1789">1789</date>
              <note>Com Licença da Real Meza da Comissão Geral, sobre o Exame, e Censura dos Livros.</note>
              <note>Vende-ſe na loja de Borel Borel, e Companhia, quaſi defronte da Igreja nova de Noſſa Senhora dos Martyres, na eſquina.</note>
           </imprint>
           <extent>Tomo primeiro</extent>
           <extent>752 pp.</extent>
        </monogr>
     </biblStruct>
     <biblStruct>
        <monogr>
           <title level="m" type="main">Diccionario da lingua portugueza composto pelo padre D. Rafael Bluteau, reformado, e accrescentado por Antonio de Moraes Silva, natural do Rio de Janeiro</title>
           <title level="m" type="sub">L – Z</title>
           <author corresp="https://isni.org/isni/0000000083438040">
              <persName>
                 <forename>António de</forename>
                 <surname>Morais Silva</surname>
              </persName>
           </author>
           <imprint>
              <publisher>Officina de Simão Thaddeo Ferreira</publisher>
              <pubPlace>Lisboa</pubPlace>
              <date>1789</date>
           </imprint>
           <extent>Tomo segundo</extent>
           <extent>541 pp.</extent>
        </monogr>
     </biblStruct>
  </listBibl>
  <listBibl type="literature">
     <biblStruct>
        <monogr corresp="https://purl.pt/29333">
           <title>Abecedario Real e Regia Instrucçam dos Principes Lusitanos, composto de 63. discursos Politicos, &amp; Moraes : offerecido ao Serenissimo Principe Dom Joam N.S. / pelo M.R.P. Fr. Joam dos Prazeres, Prègador Gèral, &amp; Chronista mòr da Religiaõ do Principe dos Patriarcas Sam Bento</title>
           <author>
              <persName>
                 <surname>Prazeres</surname>
                 <forename>João dos</forename>
              </persName>
           </author>
           <imprint>
              <date>1692</date>
              <pubPlace>Lisboa</pubPlace>
              <publisher>na Officina de Miguel Deslandes, Impressor de S. Magestade</publisher>
              <note>More information found in BND ; 191 p.</note>
           </imprint>
        </monogr>
     </biblStruct>
     <biblStruct xml:id="Academ.sing">
        <monogr corresp="https://purl.pt/21936">
           <title>Academia dos ſingulares de Lisboa dedicadas a Apollo</title>
           <author>
              <persName>
                 <surname>Faria</surname>
                 <forename>André Leitão de</forename>
              </persName>
           </author>
           <imprint>
              <date>1665</date>
              <pubPlace>Lisboa</pubPlace>
              <publisher>na Officina de Henrique Valente de Oliveira</publisher>
              <biblScope unit="volume">2 t. em 2 vol.</biblScope>
              <note>More information found in BND; 2 vol.</note>
           </imprint>
        </monogr>
     </biblStruct>
     <!-- [...] -->
  </listBibl>
</sourceDesc>Silva (1789) 

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>
  <gramGrp>
     <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.

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:

Note: See also next section on Collocates.

TEI5 is missing a specific element for encoding the grammatical aspect of verbs (for values such as perfective, imperfective) and valency (for values such as transitive, intransitive, reflexive, and impersonal). TEI Lex-0 is therefore introducing two suggested grammatical types: gram[@type="aspect"] and gram[@type="valency"]for encoding such values in dictionaries.

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

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 replaced by the nested <entry> construct.

For instance, the following example from the TEI Guidelines:

<entry>
  <form>
     <orth>bray</orth>
     <pron>breI</pron>
  </form>
  <hom>
     <gramGrp>
        <gram type="pos">n</gram>
     </gramGrp>
     <sense>
        <def>cry of an ass; sound of a trumpet.</def>
     </sense>
  </hom>
  <hom>
     <gramGrp>
        <gram type="pos">vt</gram>
        <subc>VP2A</subc>
     </gramGrp>
     <sense>
        <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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>bray</orth>
     <pron>brel</pron>
  </form>
  <entry xml:id="bray_n" xml:lang="en" type="homonymicEntry">
     <gramGrp>
        <gram type="pos">n</gram>
     </gramGrp>
     <sense xml:id="bray_n.1">
        <def>cry of an ass</def>
     </sense>
     <pc>;</pc>
     <sense xml:id="bray_n.2">
        <def>sound of a trumpet</def>
     </sense>
     <pc>.</pc>
  </entry>
  <entry xml:id="bray_vt" xml:lang="en" type="homonymicEntry">
     <gramGrp>
        <gram type="pos">vt</gram>
        <gram type="inflectionType">VP2A</gram>
     </gramGrp>
     <sense xml:id="bray_vt.1">
        <def>make a cry or sound of this kind</def>
     </sense>
     <pc>.</pc>
  </entry>
</entry>

In a similar fashion, consider this entry from the Dictionary of the Portuguese Language by Morais:

<entry xml:id="MORAIS.1.DLP.JANTAR" type="mainEntry" xml:lang="pt"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <entry xml:id="MORAIS.1.DLP.JANTAR-vt" type="homonymicEntry" xml:lang="pt">
     <form type="lemma">
        <orth>JANTAR</orth>
     </form>
     <metamark function="lemmaDelimiter">,</metamark>
     <gramGrp>
        <gram type="pos" norm="VERB">v.</gram>
        <gram type="voice">at.</gram>
     </gramGrp>
     <sense xml:id="MORAIS.1.DLP.JANTAR.s.1">
        <def>comer ao meio dia , ou comer depois de almoçar.</def>
     </sense>
  </entry>
  <entry xml:id="MORAIS.1.DLP.JANTAR-n" type="homonymicEntry" xml:lang="pt">
     <form type="lemma">
        <orth>JANTAR</orth>
     </form>
     <metamark function="lemmaDelimiter">,</metamark>
     <gramGrp>
        <gram type="pos" norm="NOUN">ſ.</gram>
        <gram type="gen">m.</gram>
     </gramGrp>
     <sense xml:id="MORAIS.1.DLP.JANTAR.s.2">
        <def>a ſegunda das tres comidas regulares do dia, entre o almoço , e aceia , ou antes da merenda.</def>
     </sense>
     <pc>.</pc>
     <metamark function="senseDelimiter">§</metamark>
     <sense xml:id="MORAIS.1.DLP.JANTAR.s.3">
        <def>Porção de dinheiro , que as Villas , e Cidades davão aos Reis , quando hião de correição para ſuſtento de ſua comitiva</def>
     </sense>
     <pc>.</pc>
     <bibl type="attestation" source="#M._L._Monarchia_Luſitana">
        <title>M. Luſ.</title>
        <citedRange unit="volume">t. 5</citedRange>
        <citedRange unit="folium">f. 53</citedRange>
        <citedRange unit="chapter">cap. 27</citedRange>
     </bibl>
  </entry>
</entry>Silva (1789) 

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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="root">
     <orth>سيج</orth>
  </form>
  <pc>:</pc>
  <!-- To fence (verb) -->
  <entry type="mainEntry" xml:lang="ar" xml:id="syj1">
     <form type="lemma">
        <orth>سيّج</orth>
     </form>
     <sense xml:id="syj1_sense1">
        <cit type="example">
           <quote>الكرم</quote>
        </cit>
        <pc>:</pc>
        <def>جعل له سياجا</def>
     </sense>
     <pc>٠</pc>
  </entry>
  <!-- A fence (noun) -->
  <entry type="mainEntry" xml:lang="ar" xml:id="syj2">
     <form type="lemma">
        <orth>السياج</orth>
     </form>
     <form type="inflected">
        <gramGrp>
           <gram type="number" value="plural">ج</gram>
        </gramGrp>
        <form type="variant">
           <orth>سيَاجات</orth>
        </form>
        <lbl>و</lbl>
        <form type="variant">
           <orth>أسْوِجة</orth>
        </form>
        <lbl>و</lbl>
        <form type="variant">
           <orth>أَسْوِجة</orth>
        </form>
        <lbl>و</lbl>
        <form type="variant">
           <orth>سُوج</orth>
        </form>
     </form>
     <pc>:</pc>
     <sense xml:id="syj2_sense1">
        <def>الحائط</def>
     </sense>
     <pc>||</pc>
     <sense xml:id="syj2_sense2">
        <def>ما أُحيط بهِ على شيءٍ كالكرم و النخل</def>
     </sense>
  </entry>
  <pc>٠</pc>
  <!-- A kind of fish -->
  <entry type="mainEntry" xml:lang="ar" xml:id="syj3">
     <form type="lemma">
        <orth>السيْجان</orth>
     </form>
     <pc>(</pc>
     <usg type="domain" value="animal">ح</usg>
     <pc>)</pc>
     <pc>:</pc>
     <sense xml:id="syj3_sense1">
        <def>نوع من السمك</def>
     </sense>
  </entry>
</entry>Almonjid (2014) 



<entry type="wordFamily" xml:lang="ar" xml:id="shahama"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="root">
     <orth>شهم</orth>
  </form>
  <pc>:</pc>
  <entry type="wordfamily" xml:lang="ar" xml:id="shahama1">
     <num>١ــ</num>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama1_1">
        <form type="lemma">
           <orth>شَهَمَ</orth>
        </form>
        <form type="scheme">
           <orth>ـَ</orth>
        </form>
        <form type="inflected">
           <form type="variant">
              <orth>شَهْمًا</orth>
           </form>
           <lbl>و</lbl>
           <form type="variant">
              <orth>شُهُمًا</orth>
           </form>
        </form>
        <sense xml:id="shahama1_1_sense1">
           <cit type="example">
              <quote>الفرسَ</quote>
           </cit>
           <pc>:</pc>
           <def>زجره</def>
        </sense>
        <pc>||</pc>
        <lbl>و</lbl>
        <sense xml:id="shahama1_1_sense2">
           <cit type="example">
              <quote>ــ الرجُل</quote>
           </cit>
           <pc>:</pc>
           <def>افزعه</def>
        </sense>
     </entry>
     <pc>٠</pc>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama1_2">
        <form type="lemma">
           <orth>اَلمشْهوم</orth>
        </form>
        <pc>٠:</pc>
        <sense xml:id="shahama1_2_sense1">
           <def>المذعور</def>
        </sense>
     </entry>
  </entry>
  <entry type="wordFamily" xml:lang="ar" xml:id="shahama2">
     <num>٢٠ ــ</num>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama2_1">
        <form type="lemma">
           <orth>شَهُم</orth>
        </form>
        <form type="scheme">
           <orth>ـُـ</orth>
        </form>
        <form type="inflected">
           <form type="variant">
              <orth>شَهَامةً</orth>
           </form>
           <lbl>و</lbl>
           <form type="variant">
              <orth>شُهُومَةُُ</orth>
           </form>
        </form>
        <lbl>:</lbl>
        <sense xml:id="shahama2_1_sense1">
           <def> كان شهْمًا</def>
        </sense>
     </entry>
     <pc>٠</pc>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama2_2">
        <form type="lemma">
           <orth>الشَهْم</orth>
        </form>
        <form type="inflected">
           <gramGrp>
              <gram type="number" value="plural">ج</gram>
           </gramGrp>
           <orth>شِهام</orth>
        </form>
        <pc>:</pc>
        <sense xml:id="shahama2_2_sense1">
           <def>الذكيّ الفؤاد</def>
        </sense>
        <pc>||</pc>
        <sense xml:id="shahama2_2_sense2">
           <def>السيِّد النافذ الحكم</def>
        </sense>
        <pc>||</pc>
        <sense xml:id="shahama2_2_sense3">
           <lbl>وــ</lbl>
           <form type="inflected">
              <gramGrp>
                 <gram type="number" value="plural">ج</gram>
              </gramGrp>
              <orth>شُهُم</orth>
           </form>
           <pc>:</pc>
           <def>الفرس النشيط السريع القويّ</def>
        </sense>
     </entry>
     <pc>٠</pc>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama2_3">
        <form type="lemma">
           <orth>اَلمَشْهُوم</orth>
        </form>
        <pc>*:</pc>
        <sense xml:id="shahama2_3_sense1">
           <def>الذكيّ الفؤاد</def>
        </sense>
     </entry>
  </entry>
  <entry type="wordFamily" xml:lang="ar" xml:id="shahama3">
     <num>٠٣ ــ</num>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama3_1">
        <form type="lemma">
           <orth>الشَيْهَم</orth>
        </form>
        <form type="inflected">
           <gramGrp>
              <gram type="number" value="plural">ج</gram>
           </gramGrp>
           <orth>شَيَهِم</orth>
        </form>
        <pc>(</pc>
        <usg type="domain" value="animal">ح</usg>
        <pc>)</pc>
        <sense xml:id="shahama3_1_sense1">
           <def>ذَكَر القنافذ</def>
        </sense>
     </entry>
     <pc>٠</pc>
     <entry type="mainEntry" xml:lang="ar" xml:id="shahama3_2">
        <form type="lemma">
           <orth>الشَيْهَمَة</orth>
        </form>
        <pc>:</pc>
        <sense xml:id="shahama3_2_sense1">
           <def>العجوز</def>
        </sense>
     </entry>
  </entry>
</entry>Almonjid (2014) 

See also Section on grammatical properties in senses.

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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth type="segmented">
        <seg>Fluss</seg>
        <seg>schifffahrt</seg>
     </orth>
     <form type="variant">
        <orth>
           <seg>Fluss</seg>
           <pc>-</pc>
           <seg>Schifffahrt</seg>
        </orth>
     </form>
     <form type="variant">
        <orth notAfter="1996">
           <seg>Fluß</seg>
           <seg>schiffahrt</seg>
        </orth>
        <usg type="temporal">Vor 1996 Rechtschreibung Reform</usg>
     </form>
     <gramGrp>
        <gram type="pos">noun</gram>
     </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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <pron notation="ipa">
        <seg xml:id="ousma" corresp="#usma #osma">ow."sa.ma</seg>
        <seg>bɪn</seg>
        <seg>ˈlaːdn̹</seg>
     </pron>
     <form type="variant">
        <orth type="transliterated">
           <seg xml:id="osma" corresp="#usma #ousma">Osama</seg>
           <seg>Bin</seg>
           <seg>Laden</seg>
        </orth>
     </form>
     <form type="variant">
        <orth type="transliterated">
           <seg xml:id="usma" corresp="#osma #ousma">Usama</seg>
           <seg>Bin</seg>
           <seg>Laden</seg>
        </orth>
     </form>
  </form>
  <!--...-->
</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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>caramel</orth>
     <form type="variant">
        <pron notation="ipa">'keɹə"mɛl</pron>
     </form>
     <form type="variant">
        <pron notation="ipa">'kaɹmɫ̩</pron>
     </form>
  </form>
  <gramGrp>
     <gram type="pos">noun</gram>
  </gramGrp>
  <!-- ... -->
</entry>

In focus: multiple variants

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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>
        <seg>Ñuu</seg>
        <seg>Ntua</seg>
     </orth>
     <pron notation="ipa">
        <seg>ɲùù</seg>
        <seg>nd̪ùá</seg>
     </pron>
     <form type="variant" xml:lang="mix-x-YCNY">
        <orth>Ntua</orth>
        <pron notation="ipa">nd̪ùá</pron>
        <usg type="geographic"> Yucanany
        </usg>
     </form>
  </form>
  <gramGrp>
     <gram type="pos">locationNoun</gram>
  </gramGrp>
  <!--...-->
</entry>

4.6.1. Collocations

TODO: explain "lexicographically transparent"

<entry xml:id="DLPC.descalçar" xml:lang="pt"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <!--etc.-->
  <sense xml:id="DLPC.descalçar.1">
     <!--etc.-->
     <form type="collocations">
        <form type="collocation">
           <orth>
              <ref type="form" scope="currentEntry" value="descalçar">
                 <lbl>+</lbl>
              </ref>
              <seg>as botas</seg>
           </orth>
           <gramGrp>
              <gram type="mwe" value="co-ocorrente_privilegiado"/>
           </gramGrp>
        </form>
        <pc>,</pc>
        <form type="collocation">
           <orth>
              <ref type="form" scope="currentEntry" value="descalçar"/>
              <seg>as luvas</seg>
           </orth>
           <gramGrp>
              <gram type="mwe" value="co-ocorrente_privilegiado"/>
           </gramGrp>
        </form>
        <pc>,</pc>
        <form type="collocation">
           <orth>
              <ref type="form" scope="currentEntry" value="descalçar"/>
              <seg>as meias</seg>
           </orth>
           <gramGrp>
              <gram type="mwe" value="co-ocorrente_privilegiado"/>
           </gramGrp>
        </form>
     </form>
     <pc>;</pc>
     <form type="collocations">
        <form type="collocation">
           <orth>
              <ref type="form" scope="currentEntry" value="descalçar">
                 <lbl>+</lbl>
              </ref>
              <seg>os sapatos</seg>
           </orth>
           <gramGrp>
              <gram type="mwe" value="co-ocorrente_privilegiado"/>
           </gramGrp>
        </form>
     </form>
     <pc>.</pc>
  </sense>
</entry>DLPC (2001) 

4.6.2. Idiomatic expressions

TODO text ("lexicographically non-transparent")

<entry xml:lang="pt" xml:id="DLPC.bombeiro" type="mainEntry"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>bombeiro</orth>
  </form>
  <!--etc. -->
  <sense xml:id="bombeiro.1">
     <!--etc. -->
     <entry xml:id="DLPC.bombeiro_voluntario" xml:lang="pt" type="relatedEntry">
        <form type="lemma">
           <orth>bombeiro voluntário</orth>
        </form>
        <gramGrp>
           <gram type="mwe" value="combinatória_fixa"/>
        </gramGrp>
        <pc>,</pc>
        <sense xml:id="DLPC.bombeiro_voluntario.1">
           <def>o que pertence a uma corporação com a obrigatoriedade de acudir a
                       incêndios, acidentes, unicamente por filantropia</def>
           <pc>.</pc>
        </sense>
     </entry>
     <entry xml:id="DLPC.corpo_de_bombeiros" xml:lang="pt" type="relatedEntry">
        <form type="lemma">
           <orth>
              <ref type="entry" scope="currentEntry">
                 <seg>corpo</seg>
                 <lbl rend="sup">+</lbl>
              </ref>
              <seg>de bombeiros</seg>
           </orth>
        </form>
        <pc>.</pc>
     </entry>
  </sense>
  <!--etc.-->
</entry>DLPC (2001) 

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.

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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>living</orth>
  </form>
  <gramGrp>
     <gram type="pos">adj</gram>
  </gramGrp>
  <sense n="1" xml:id="LDOCE.living.1">
     <num>1</num>
     <def>alive now 
        <!--[...] -->
     </def>
     <metamark>|</metamark>
     <cit type="example">
        <quote>The sun affects all <ref type="entry" scope="currentEntry">living</ref>
                 things <gloss>(=people, animals, and plants)</gloss>.</quote>
     </cit>
     <metamark>|</metamark>
     <cit type="example">
        <quote>A <ref type="entry" scope="currentEntry">living</ref> language <gloss>(=one
                       that people still use)</gloss>
           <!--[….] -->
        </quote>
     </cit>
  </sense>
</entry>Gadsby (ed.) (2003) 

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>
</sense>
<sense n="1" xml:id="LD.peto.2">
  <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.

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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <!--this, as we'll explain later, is valid but not the preferred encoding-->
  <form type="lemma">
     <orth>gash</orth>
     <pron>gash</pron>
  </form>
  <lbl type="homNum" rend="sup">2</lbl>
  <sense xml:id="CHDOEL.gash2.1">
     <pc>(</pc>
     <usg type="socioCultural" expand="slang">sl</usg>
     <pc>)</pc>
     <gramGrp>
        <gram type="pos">adj</gram>
     </gramGrp>
     <def>spare, extra</def>
     <pc>.</pc>
  </sense>
  <metamark function="senseSeparator">◆</metamark>
  <sense xml:id="CDHDOEL.gash2.2">
     <gramGrp>
        <gram type="pos">n</gram>
     </gramGrp>
     <pc>(</pc>
     <usg type="temporal" expand="originally">orig</usg>
     <lbl>and esp</lbl>
     <usg type="domain" expand="nautical">naut</usg>
     <pc>)</pc>
     <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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>gash</orth>
     <pron>gash</pron>
  </form>
  <lbl type="homNum" rend="sup">2</lbl>
  <entry xml:id="CH.gash2.1" xml:lang="en" type="homonymicEntry">
     <sense xml:id="CH.gash2.1.1">
        <pc>(</pc>
        <usg type="socioCultural" expand="slang">sl</usg>
        <pc>)</pc>
        <gramGrp>
           <gram type="pos">adj</gram>
        </gramGrp>
        <def>spare, extra</def>
        <pc>.</pc>
     </sense>
  </entry>
  <metamark function="entrySeparator">◆</metamark>
  <entry xml:id="CH.gash2.2" xml:lang="en" type="homonymicEntry">
     <gramGrp>
        <gram type="pos">n</gram>
     </gramGrp>
     <sense xml:id="CH.gahs2.2.1">
        <pc>(</pc>
        <usg type="temporal" expand="originally">orig</usg>
        <lbl>and esp</lbl>
        <usg type="domain" expand="nautical">naut</usg>
        <pc>)</pc>
        <def>rubbish, waste</def>
        <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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>aid</orth>
     <pron>/ed/</pron>
  </form>
  <entry xml:id="ED.aid_n" xml:lang="en" type="homonymicEntry">
     <gramGrp>
        <gram type="pos">noun</gram>
     </gramGrp>
     <sense xml:id="ED.aid_n.1" n="1">
        <num>1.</num>
        <gramGrp>
           <gram type="number" value="singularia tantum"/>
        </gramGrp>
        <def>help, especially money, food or other gifts given to people living in
                 difficult conditions</def>
        <metamark function="exampleMarker">○</metamark>
        <cit type="example">
           <quote>aid to the earth-quake zone</quote>
        </cit>
        <cit type="example">
           <quote>an aid worker</quote>
        </cit>
        <note>(NOTE: This meaning of aid has no plural.)</note>
        <metamark function="relatedEntryMarker">○</metamark>
        <entry type="relatedEntry" xml:id="ED.aid_n.1.in_aid_of" xml:lang="en">
           <form type="lemma">
              <orth>in aid of</orth>
           </form>
           <sense xml:id="ED.aid_n.1.in_aid_of.1">
              <def>in order to help</def>
              <metamark function="exampleMarker">○</metamark>
              <cit type="example">
                 <quote>We give money in aid of the Red Cross.</quote>
              </cit>
              <metamark function="exampleMarker">○</metamark>
              <cit type="example">
                 <quote>They are collecting money in aid of refugees.</quote>
              </cit>
           </sense>
        </entry>
     </sense>
     <sense xml:id="ED.aid_n.2" n="2">
        <num>2.</num>
        <def>thing which helps you to do something</def>
        <metamark function="exampleMarker">○</metamark>
        <cit type="example">
           <quote>kitchen aids</quote>
        </cit>
     </sense>
  </entry>
  <metamark function="subentryMarker">■</metamark>
  <entry xml:id="ED.aid_v" xml:lang="en" type="homonymicEntry">
     <gramGrp>
        <gram type="pos">verb</gram>
     </gramGrp>
     <sense xml:id="ED.aid.v.1" n="1">
        <num>1.</num>
        <def>to help something to happen</def>
     </sense>
     <sense xml:id="ED.aid.v.2" n="2">
        <num>2.</num>
        <def>to help someone</def>
     </sense>
  </entry>
</entry>

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.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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>borcht</orth>
  </form>
  <xr type="related">
     <lbl>Cf.</lbl>
     <ref target="#M012340" type="entry">burcht</ref>
  </xr>
</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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>arbeitsunfähig</orth>
  </form>
  <sense xml:id="arbeitsunfähig.1">
     <xr type="synonymy">
        <ref type="entry">bettlägerig</ref>
     </xr>
     <pc>,</pc>
     <xr type="synonymy">
        <ref type="entry">krank</ref>
     </xr>
     <pc>,</pc>
     <xr type="synonymy">
        <ref type="entry">unpässlich</ref>
     </xr>
     <pc>;</pc>
  </sense>
  <sense xml:id="arbeitsunfähig.2">
     <pc>(</pc>
     <usg type="domain">bildungsspr.</usg>
     <pc>):</pc>
     <xr type="synonymy">
        <ref type="entry">indisponiert</ref>
     </xr>
  </sense>
  <sense xml:id="arbeitsunfähig.3">
     <xr type="synonymy">
        <pc>(</pc>
        <lbl>oft</lbl>
        <usg type="attitude">emotional</usg>
        <pc>):</pc>
        <ref type="entry">malade</ref>
     </xr>
     <pc>.</pc>
  </sense>
</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"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>dog</orth>
  </form>
  <gramGrp>
     <gram type="pos">n</gram>
  </gramGrp>
  <xr type="hypernymy">
     <ref type="entry">mammal</ref>
  </xr>
</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:base="../TEILex0.examples/examples.stripped.xml" xml:lang="pt">
  <def>Que pertence ou viveu numa época anterior.</def>
  <xr type="synonymy">
     <ref type="sense">antecessor</ref>
  </xr>
  <xr type="synonymy">
     <ref type="sense">sucessor</ref>
  </xr>
  <xr type="antonymy">
     <ref type="sense">descendente</ref>
  </xr>
  <xr type="antonymy">
     <ref type="sense">sucessor</ref>
  </xr>
</sense>

7.5.1. More complex example including quotations

<entry xml:id="dog" xml:lang="en"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>dog</orth>
  </form>
  <sense xml:id="dog.1">
     <gramGrp>
        <gram type="gen" value="m">Male or unknown gender</gram>
     </gramGrp>
     <cit type="translationEquivalent" xml:lang="fr">
        <form>
           <orth>chien</orth>
        </form>
     </cit>
     <cit type="example" xml:lang="fr">
        <quote> Le matin j'ouvre au <ref type="oRef">chien</ref> et je lui fais manger sa
                 soupe. Le soir je lui siffle de venir se coucher</quote>
        <bibl>RENARD, Poil de Carotte, 1894, p. 102.</bibl>
        <cit type="translation" xml:lang="en">
           <!-- included in the french cit, otherwise relation is lost -->
           <quote>In the morning, I open the door for the dog, and I 
              <!--...-->
           </quote>
        </cit>
     </cit>
  </sense>
  <sense xml:id="dog.2">
     <gramGrp>
        <gram type="gen" value="f">Female</gram>
     </gramGrp>
     <cit type="translationEquivalent" xml:lang="fr">
        <form type="lemma">
           <orth>chienne</orth>
        </form>
     </cit>
     <cit type="example" xml:lang="fr">
        <quote>6. Les fleuristes, murmura Lorilleux, toutes des Marie-couche-toi-là. Eh
                 bien! Et moi? reprit la grande veuve, les lèvres pincées. Vous êtes galant.
                 Vous savez, je ne suis pas une <ref type="oRef">chienne</ref>, je ne me mets
                 pas les pattes en l'air, quand on siffle! </quote>
        <bibl>ZOLA, L'Assommoir, 1877, p. 681.</bibl>
        <cit type="translation" xml:lang="en">
           <quote>
              <!--...-->
           </quote>
        </cit>
     </cit>
  </sense>
</entry>

7.5.2. Antepassado

<entry xml:lang="pt" xml:id="DLPC.antepassado_a"
 xml:base="../TEILex0.examples/examples.stripped.xml">
  <form type="lemma">
     <orth>antepassado</orth>
     <pron>ɐ̃tɨpɐsˈadu</pron>
  </form>
  <form type="inflected">
     <orth>antepassado</orth>
     <gramGrp>
        <gram type="gen">m.</gram>
     </gramGrp>
  </form>
  <form type="inflected">
     <orth>antepassada</orth>
     <gramGrp>
        <gram type="gen">f.</gram>
     </gramGrp>
     <pron>ɐ̃tɨpɐsˈadɐ</pron>
     <lbl>:1</lbl>
  </form>
  <gramGrp>
     <gram type="pos" norm="ADJ">adj.</gram>
  </gramGrp>
  <etym type="grammaticalization">
     <seg type="desc">De</seg>
     <cit type="etymon">
        <form>
           <orth extent="pref">ante-</orth>
        </form>
     </cit>
     <lbl>+</lbl>
     <cit type="etymon">
        <form>
           <orth>passado</orth>
        </form>
     </cit>
  </etym>
  <sense xml:id="DLPC.antepassado_a_1">
     <def>Que pertence ou viveu numa época anterior.</def>
     <xr type="synonymy">
        <ref type="sense">antecessor</ref>
     </xr>
     <xr type="synonymy">
        <ref type="sense">sucessor</ref>
     </xr>
     <xr type="antonymy">
        <ref type="sense">descendente</ref>
     </xr>
     <xr type="antonymy">
        <ref type="sense">sucessor</ref>
     </xr>
  </sense>
</entry>

7.5.3. Cross-references inside definitions

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