<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright TEI Consortium. 
Dual-licensed under CC-by and BSD2 licences 
See the file COPYING.txt for details.
$Date$
$Id$
-->


<?xml-model href="http://tei.oucs.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/P5/release/xml/tei/odd/p5.nvdl" type="application/xml" schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>

<div xmlns="http://www.tei-c.org/ns/1.0" type="div1" xml:id="DI" n="12">
<head>Dictionaries</head>

<p>This chapter defines a module for encoding lexical resources of all
kinds, in particular human-oriented
monolingual and multilingual dictionaries, glossaries, and similar
documents. The elements described here may also be useful in the
encoding of computational lexica and similar resources intended for
use by language-processing software; they may also be used to provide
a rich encoding for wordlists, lexica, glossaries, etc. included
within other documents.  Dictionaries are most familiar in
their printed form; however, increasing numbers of dictionaries exist
also in electronic forms which are independent of any particular
printed form, but from which various displays can be produced. </p>

<p>Both typographically and structurally, print dictionaries are
extremely complex. Such lexical resources are moreover of interest to
many communities with different and sometimes conflicting goals. As a
result, many general problems of text encoding are particularly
pronounced here, and more compromises and alternatives within the
encoding scheme may be required in the future.<note place="bottom">We
refer the reader to previous and current discussions of a common
format for encoding lexical resources. For example, <ptr type="cit"
target="#DI-BIBL-1"/>; <ptr type="cit" target="#DI-BIBL-2"/>;<ptr
type="cit" target="#DI-BIBL-3"/>; <ptr type="cit"
target="#DI-BIBL-4"/>; <ptr type="cit" target="#DI-BIBL-5"/>; <ptr
type="cit" target="#DI-BIBL-6"/>; <ptr type="cit"
target="#DI-BIBL-7"/>; and <ptr type="cit" target="#DI-BIBL-8"/>; <ptr
type="cit" target="#DI-BIBL-9"/>.</note> Two problems are particularly
prominent.</p>

<p>First, because the structure of dictionary entries varies widely
both among and within dictionaries, the simplest way for an encoding
scheme to accommodate the entire range of structures actually
encountered is to allow virtually any element to appear virtually
anywhere in a dictionary entry. It is clear, however, that strong and
consistent structural principles do govern the vast majority of
conventional dictionaries, as well as many or most entries even in
more <soCalled>exotic</soCalled> dictionaries; 
encoding guidelines should include these structural principles. We
therefore define two distinct elements for dictionary entries, one
(<gi>entry</gi>) which captures the regularities of many conventional
dictionary entries, and a second (<gi>entryFree</gi>) which uses the
same elements, but allows them to combine much more freely. It is
however recommended that <gi>entry</gi> be used in preference to
<gi>entryFree</gi> wherever possible.
These elements and their contents are described in sections <ptr target="#DIEN"/>, <ptr target="#DIFR"/>, and <ptr target="#DIHW"/>.</p>

<p>Second, since so much of the information in printed dictionaries is
implicit or highly compressed, their encoding requires clear thought
about whether it is to capture the precise typographic form of the
source text or the underlying structure of the information it
presents. Since both of these views of the dictionary may be of
interest, it proves necessary to develop methods of recording both,
and of recording the interrelationship between them as well. Users
interested mainly in the printed format of the dictionary will require
an encoding to be faithful to an original printed version. However,
other users will be interested primarily in capturing the lexical
information in a dictionary in a form suitable for further processing,
which may demand the expansion or rearrangement of the information
contained in the printed form. Further, some users wish to encode
<emph>both</emph> of these views of the data, and retain the links
between related elements of the two encodings. Problems of recording
these two different views of dictionary data are discussed in section
<ptr target="#DIMV"/>, together with mechanisms for retaining both
views when this is desired.</p>

<p>To deal with this complexity, and in particular to account for the
wide variety of linguistic contexts within which a dictionary may be
designed, it can be necessary to customize or change the schema by
providing more restriction or possibly alternate content models for
the elements defined in this chapter.  Section <ptr target="#DITPGR"/>
illustrates this with the provision of a closed set of values for
grammatical descriptors.</p>

<p>This chapter contains a large number of examples taken from
existing print dictionaries; in each case, the original source is
identified. In presenting such examples, we have tried to retain the
original typographic appearance of the example as well as presenting a
suggested encoding for it. Where this has not been possible (for
example in the display of pronunciation) we have adopted the
transliteration found in the electronic edition of the <title>Oxford
Advanced Learner's Dictionary</title>. Also, the middle dot in quoted
entries is rendered with a full stop, while within the sample
transcriptions hyphenation and syllabification points are indicated by
a vertical bar |, regardless of their appearance in the source
text.</p>

<div type="div2" xml:id="DIBO">
<head>Dictionary Body and Overall Structure</head>

<p>Overall, dictionaries have the same structure of front matter,
body, and back matter familiar from other texts. In addition,
this module defines <gi>entry</gi>, <gi>entryFree</gi>,
and <gi>superEntry</gi> as component-level elements which can occur
directly within a text division or the text body. </p>

<p>The following tags can therefore be used to mark the gross structure of a
printed dictionary; the dictionary-specific tags are discussed further
in the following section.<specList>
<specDesc key="text"/>
<specDesc key="front"/>
<specDesc key="body"/>
<specDesc key="back"/>
<specDesc key="div"/>
<specDesc key="entry"/>
<specDesc key="entryFree"/>
<specDesc key="superEntry"/>
</specList></p>

<p>As members of the classes <ident type="class">att.entryLike</ident> and 
 <ident type="class">att.sortable</ident>,
<gi>entry</gi> and <gi>entryFree</gi> share the following
attributes:<specList>
<specDesc key="att.entryLike" atts="type"/>  
 <specDesc key="att.sortable" atts="sortKey"/> 
</specList>
</p>

<p>The front and back matter of a dictionary may well contain
specialized material such as lists of common and proper nouns,
grammatical tables, gazetteers, a <soCalled>guide to the use of the
dictionary</soCalled>, etc. These should be tagged using elements
defined elsewhere in these Guidelines, chiefly in the core module
(chapter <ptr target="#CO"/>) together with the specialized dictionary
elements defined in this chapter.</p>

<p>The <gi>body</gi> element consists of a set of
<term>entries</term>, optionally grouped into one or several
<gi>div</gi> elements. These text divisions might, for example, correspond to
sections for different letters of the alphabet, or to sections for
different languages in a bilingual dictionary, as in the following
example:

<egXML xmlns="http://www.tei-c.org/ns/Examples">
<body>
<div><head>English-French</head>
<entry><form><orth>cat</orth></form><!-- ... --></entry>
<entry><form><orth>dog</orth></form><!-- ... --></entry>
<entry><form><orth>horse</orth></form><!-- ... --></entry>
</div>
<div>
<head>French-English</head>
<entry><form><orth>chat</orth></form><!-- ... --></entry>
<entry><form><orth>chien</orth></form><!-- ... --></entry>
<entry><form><orth>cheval</orth></form><!-- ... --></entry>
</div>
</body>
</egXML>
</p><!-- why both same type? -->

<p>In a
print dictionary, the entries are typically typographically distinct
entities, each headed by some morphological form of the lexical item
described (the <term>headword</term>), and sorted in alphabetical
order or (especially for non-alphabetic scripts) in some other
conventional sequence. Dictionary entries should be encoded as
distinct successive items, each marked as an <gi>entry</gi> or
<gi>entryFree</gi> element. The <att>type</att> attribute may be used
to distinguish different types of entries, for example main entries,
related entries, run-on entries, or entries for cross-references,
etc. </p>

<p>Some dictionaries provide distinct entries for homographs, on the
basis of etymology, part-of-speech, or both, and typically provide a
numeric superscript on the headword identifying the homograph
number. In these cases each homograph should be encoded as a separate
entry; the <gi>superEntry</gi> element may optionally be used to group
such successive homograph entries. In addition to a series of
<gi>entry</gi> elements, the <gi>superEntry</gi> may contain a
preliminary <gi>form</gi> group (see section <ptr target="#DITPFO"/>)
when information about hyphenation, pronunciation, etc., is given only
once for two or more homograph entries. If the homograph number is to
be recorded, the global attribute <att>n</att> may be used for this
purpose. In some dictionaries, homographs are treated in distinct
parts of the same entry; in these cases, they may be separated by use
of the <gi>hom</gi> element, for which see section <ptr target="#DIENHI"/>. </p>

<p>A sort key, given in the <att>sortKey</att> attribute, is often
required for superentries and entries, especially in cases where the
order of entries does not follow the local character-set collating
sequence (as, for example, when an entry for <q>3D</q> appears at the
place where <q>three-D</q> would appear). </p>



<p>A dictionary with no internal divisions might thus have a structure like
the following; a <gi>superEntry</gi> is shown grouping two homograph
entries.<egXML xml:lang="und" xmlns="http://www.tei-c.org/ns/Examples">
<body>
<entry>
<form>
	<orth>manifestation</orth> <!-- demonstration -->
</form>
</entry>
<entry>
<form>
	<orth>émeute</orth> <!-- riot -->
</form></entry>
<superEntry>
 <entry type="hom" n="1">
<form>
	<orth>grève</orth> <!-- strike -->
</form>
</entry>
 <entry type="hom" n="2">
<form>
	<orth>grève</orth> <!-- shore -->
</form>
</entry>
</superEntry>
</body>
</egXML>
</p>


<specGrpRef target="#DEDIMV"/> 




<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/model.entryLike.xml"/>










<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/att.entryLike.xml"/>





 
<specGrpRef target="#DEDITPFO"/>
<specGrpRef target="#DEDIHW"/>
<specGrpRef target="#DDIEN"/>
<specGrpRef target="#DDITPFO"/>
<specGrpRef target="#DDITPGR"/>
<specGrpRef target="#DDITPDE"/>
<specGrpRef target="#DDITPET"/>
<specGrpRef target="#DDITPUS"/>
<specGrpRef target="#DDITPXR"/>
<specGrpRef target="#DDITPRE"/>
<specGrpRef target="#DDIHW"/>

<specGrp xml:id="DEDIMV" n="Attributes for dictionary work">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/att.lexicographic.xml"/>





 </specGrp>

</div>
<div type="div2" xml:id="DIEN">
<head>The Structure of Dictionary Entries</head>

<p>A simple dictionary entry may contain information about the form of
the word treated, its grammatical characterization, its definition,
synonyms, or translation equivalents, its etymology, cross-references
to other entries, usage information, and examples. These we refer to
as the <term>constituent parts</term> or <term>constituents</term> of
the entry; some dictionary constituents possess no internal structure,
while others are most naturally viewed as groups of smaller elements,
which may be marked in their own right.  In some styles of markup,
tags will be applied only to the low-level items, leaving the
constituent groups which contain them untagged. We distinguish the
class of <term>top-level constituents</term> of dictionary entries,
which can occur directly within the <gi>entry</gi> element, from the class of
<term>phrase-level</term> constituents, which can normally occur only
within top-level constituents. The top-level constituents of
dictionary entries are described in section <ptr target="#DIENGP"/>,
and documented more fully, together with their phrase-level
sub-constituents, in section <ptr target="#DITP"/>. </p>

<p>In addition, however, dictionary entries often have a complex
hierarchical structure. For example, an entry may consist of two or
more sub-parts, each corresponding to information for a different
part-of-speech homograph of the headword. The entry (or part-of-speech
homographs, if the entry is split this way) may also consist of
senses, each of which may in turn be composed of two or more
sub-senses, etc. Each sub-part, homograph entry, sense, or sub-sense
we call a <term>level</term>; at any level in an entry, any or all of
the constituent parts of dictionary entries may appear. The
hierarchical levels of dictionary entries are documented in section
<ptr target="#DIENHI"/>. </p>

<div type="div3" xml:id="DIENHI">
<head>Hierarchical Levels</head>

<p>The outermost structural level of an entry is marked with the
elements <gi>entry</gi> or <gi>entryFree</gi>. The <gi>hom</gi>
element marks the subdivision of entries into homographs differing in
their part-of-speech. The <gi>sense</gi> element marks the subdivision
of entries and part-of-speech homographs into senses; this element
nests recursively in order to provide for a hierarchy of sub-senses of
any depth.  It is recommended to use the <gi>sense</gi> 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. 
All of these levels may each contain any of the
constituent parts of an entry. A special case of hierarchical
structure is represented by the <gi>re</gi> (related entry) element,
which is discussed in section <ptr target="#DITPRE"/>. Finally, the
element <gi>dictScrap</gi> may be used at any point in the hierarchy
to delimit parts of the dictionary entry which are structurally
anomalous, as further discussed in section <ptr target="#DIFR"/>.<specList>
<specDesc key="entry"/>
<specDesc key="entryFree"/>
<specDesc key="hom"/>
<specDesc key="sense" atts="level"/>
<specDesc key="dictScrap"/>
</specList>
</p>
 <p>For example, an entry with two senses will have the following structure:<egXML xml:lang="und" xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<sense n="1"/>
<sense n="2"/>
</entry>
</egXML>
</p>
<p>An entry with two homographs, the first with two senses and the second with three
 (one of which has two sub-senses), may have a structure like this:<egXML xml:lang="und" xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<hom n="1">
<sense n="1"> <!-- ... --> </sense>
<sense n="2"> <!-- ... --> </sense>
</hom>
<hom n="2">
<sense n="1">
<sense n="a"> <!-- ... --> </sense>
<sense n="b"> <!-- ... --> </sense>
</sense>
<sense n="2"> <!-- ... --> </sense>
<sense n="3"> <!-- ... --> </sense>
</hom>
</entry>
</egXML> In some dictionaries, homographs have separate entries; in
such a case, as noted in section <ptr target="#DIBO"/>, the two homographs may be
 treated as entries, optionally grouped in a <gi>superEntry</gi>:<egXML xml:lang="und" xmlns="http://www.tei-c.org/ns/Examples">
<superEntry>
<entry n="1" type="hom">
<sense n="1"> <!-- ... --> </sense>
<sense n="2"> <!-- ... --> </sense>
</entry>
<entry n="2" type="hom">
<sense n="1">
<sense n="a"> <!-- ... --> </sense>
<sense n="b"> <!-- ... --> </sense>
</sense>
<sense n="2"> <!-- ... --> </sense>
<sense n="3"> <!-- ... --> </sense>
</entry>
</superEntry>
</egXML>
</p>
<p>The hierarchic structure of a dictionary entry is enforced by the
structures defined in this module. The content model for
<gi>entry</gi> specifies that entries do not nest, that homographs
nest within entries, and that senses nest within entries, homographs,
or senses, and may be nested to any depth to reflect the embedding of
sub-senses. Any of the top-level constituents (<gi>def</gi>,
<gi>usg</gi>, <gi>form</gi>, etc.) can appear at any level (i.e.,
within entries, homographs, or senses).<specGrp xml:id="DDIEN" n="Dictionary entries and their structure">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/superEntry.xml"/>















<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/entry.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/entryFree.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/hom.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/sense.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/dictScrap.xml"/>





 </specGrp>
</p>
</div>
<div type="div3" xml:id="DIENGP">
<head>Groups and Constituents</head>

<p>As noted above, dictionary entries, and subordinate levels within dictionary entries,
may comprise several constituent parts, each providing a different type of
information about the word treated. The <term>top-level constituents</term> of
dictionary entries are:<list rend="bulleted">
<item>information about the form of the word treated (orthography,
pronunciation, hyphenation, etc.)</item>
<item>grammatical information (part of speech, grammatical sub-categorization,
etc.)</item>
<item>definitions or translations into another language</item>
<item>etymology</item>
<item>examples</item>
<item>usage information</item>
<item>cross-references to other entries</item>
<item>notes</item>
<item>entries (often of reduced form) for related words, typically called
<term>related entries</term>
</item>
</list> Any of the hierarchical levels (<gi>entry</gi>, <gi>entryFree</gi>,
<gi>hom</gi>, and <gi>sense</gi>) may contain any of these top-level constituents, since
information about word form, particular grammatical information, special
pronunciation, usage information, etc., may apply to an entire entry, or to only one
homograph, or only to a particular sense. The examples below illustrate this point. </p>
<p>The following elements are used to encode these top-level constituents:<specList>
<specDesc key="form"/>
<specDesc key="gramGrp"/>
<specDesc key="def"/>
<specDesc key="cit"/>
<specDesc key="usg"/>
<specDesc key="xr"/>
<specDesc key="etym"/>
<specDesc key="re"/>
<specDesc key="note"/>
</specList>
</p>
<p>In a simple entry with no internal hierarchy, all top-level constituents can appear 
as children of <gi>entry</gi>.<!--
<note place="bottom"> Each example taken from a real
dictionary indicates its source using the following abbreviations for dictionary
names:<list type="gloss">
<label>C/R </label>
<item>Beryl T. Atkins et al., <title>Collins Robert French-English
English-French Dictionary</title> (London: Collins, 1978, rpt. 1983) </item>
<label>CED</label>
<item>Collins English Dictionary </item>
<label>CP</label>
<item>Collins Pocket </item>
<label>DNT</label>
<item>
<title>Le Dictionnaire de Notre Temps</title>, ed. Françoise Guerard
(Paris: Hachette, 1990). </item>
<label>LDOCE</label>
<item>Longman Dictionary of Contemporary English </item>
<label>NPEG</label>
<item>
<title>The New Penguin English Dictionary</title> (London: Penguin,
1986, rpt. 1987). </item>
<label>OALD</label>
<item>
<title>Oxford Advanced Learner's Dictionary of Current English</title>,
ed. A. S. Hornby with A. P. Cowie and A. C. Gimson (Oxford University
Press, 1974). </item>
<label>PLC</label>
<item>
<title>Petit Larousse en Couleurs</title> (Paris: Larousse, 1990). </item>
<label>PLI</label>
<item>
<title>Pequeño Larousse Illustrado</title> por Ramón García-Pelayo y
Gross (Buenos Aires, Mexico, Paris: Ediciones Larousse, 1964). </item>
<label>PR</label>
<item>
<title>Le Petit Robert</title>
</item>
<label>SSSE</label>
<item>
<title>Simon and Schuster's International Dictionary English/Spanish
Spanish/English</title> ed. Tana de Gómez (New York: Simon and
Schuster, 1973). </item>
<label>W7</label>
<item>Webster's 7th Collegiate </item>
<label>WNC</label>
<item>
<title>Webster's New Collegiate Dictionary</title> (Springfield, Mass.:
G. &amp; C. Merriam Co., 1975). </item>
</list> </note>-->
<q rend="display">
<hi rend="bold">com.peti.tor</hi>
<code lang="ipa">/k@m"petit@(r)/</code> n person who competes. <ref target="#DIC-OALD">OALD</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>competitor</orth>
<hyph>com|peti|tor</hyph>
<pron>k@m"petit@(r)</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<def>person who competes.</def>
</entry>
</egXML> 
For the elements which appear within the <gi>form</gi> and <gi>gramGrp</gi>
elements of this and other  examples, see below, section <ptr target="#DITPFO"/>, and section <ptr target="#DITPGR"/>. </p>
<p>Any top-level constituent can appear at any level when the
hierarchical structure of the entry is more complex. The most obvious examples are
<gi>def</gi> and <gi>cit</gi>, which appear at the <gi>sense</gi> level when
several senses or translations exist:<q rend="display">
<hi rend="bold">disproof</hi>
<code lang="ipa">(dIs"pru:f)</code> n. 1. facts that disprove something. 2. the
act of disproving. <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>disproof</orth>
<pron>dIs"pru:f</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>facts that disprove something.</def>
</sense>
<sense n="2">
<def>the act of disproving.</def>
</sense>
</entry>
</egXML>
</p>
<p>For ease of processing of such entries containing multiple senses along with those containing 
only a single sense, it is recommended to use <gi>sense</gi> in all entries to wrap those elements 
relating to a particular word sense.</p>
<p>In the following example, <gi>gramGrp</gi> is used to distinguish two homographs:<q rend="display">
<hi rend="bold">bray</hi>
<code lang="ipa">/breI/</code> n cry of an ass; sound of a trumpet. ∙ vt [VP2A]
make a cry or sound of this kind. <ref target="#DIC-OALD">OALD</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>bray</orth>
<pron>breI</pron>
</form>
<hom>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense>
<def>cry of an ass; sound of a trumpet.</def>
</sense>
</hom>
<hom>
<gramGrp>
<pos>vt</pos>
<subc>VP2A</subc>
</gramGrp>
<sense>
<def>make a cry or sound of this kind.</def>
</sense>
</hom>
</entry>
</egXML>

</p>
<p>Information of the same kind can appear at different levels within the same entry;
here, grammatical information occurs both at entry and homograph level.<q rend="display">
<hi rend="bold">ca.reen</hi>
<code lang="ipa">/k@"ri:n/</code> vt,vi 1 [VP6A] turn (a ship) on one side for
cleaning, repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side.
<ref target="#DIC-OALD">OALD</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>careen</orth>
<hyph>ca|reen</hyph>
<pron>k@"ri:n</pron>
</form>
<gramGrp>
<pos>vt</pos>
<pos>vi</pos>
</gramGrp>
<sense n="1">
<gramGrp>
<subc>VP6A</subc>
</gramGrp>
<def>turn (a ship) on one side for cleaning, repairing, etc.</def>
</sense>
<sense n="2">
<gramGrp>
<subc>VP6A</subc>
<subc>VP2A</subc>
</gramGrp>
<def>(cause to) tilt, lean over to one side.</def>
</sense>
</entry>
</egXML>
<!-- suppress:  supererogatory
<q rend='display'>
conjure <code>("kVndZ@) </code> vb 1. to practice conjuring. 2. to
summon (a spirit or demon) by magic. 3. <code>(k@n"dGU@) </code> to
appeal earnestly to ... [CP] </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples"><entry>
  <form>
<orth>conjure</orth>
<pron>"kVndZ@</pron>
  </form>
  <gramGrp>
<pos>vb</pos>
  </gramGrp>
  <sense n='1'>
<def>to practice conjuring.</def>
  </sense>
  <sense n='2'>
<def>to summon (a spirit or demon) by magic.</def>
  </sense>
  <sense n='3'>
<form>
<pron>k@n"dGU@</pron>
</form>
<def>to appeal earnestly to</def>
  <! - - ...  - - >
</entry>
]]>
</egXML>
-->
</p>
<p>Alone among the constituent groups, <gi>form</gi> can appear at the
<gi>superEntry</gi> level as well as at the <gi>entry</gi>, <gi>hom</gi>, and
<gi>sense</gi> levels:<q rend="display">
<hi rend="bold">a.ban.don</hi> 1<code lang="ipa">/@"band@n/ </code>
v [T1] 1 to leave completely and for ever; desert: The sailors abandoned the
burning ship. 2 …<hi rend="bold">abandon</hi> 2 n [U] the state when one's
feelings and actions are uncontrolled; freedom from control...<ref target="#DIC-LDOCE">LDOCE</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<superEntry>
<form>
<orth>abandon</orth>
<hyph>a|ban|don</hyph>
<pron>@"band@n</pron>
</form>
<entry n="1">
<gramGrp>
<pos>v</pos>
<subc>T1</subc>
</gramGrp>
<sense n="1">
<def>to leave completely and for ever … </def>
</sense>
<sense n="2"/>
</entry>
<entry n="2">
<gramGrp>
<pos>n</pos>
<subc>U</subc>
</gramGrp>
<sense>
<def>the state when one's feelings and actions are uncontrolled; freedom
from control…</def>
</sense>
</entry>
</superEntry>
</egXML>
</p>
</div>
</div>
<div type="div2" xml:id="DITP">
<head>Top-level Constituents of Entries</head>
<p>This section describes the top-level constituents of dictionary entries, together with
the phrase-level constituents peculiar to each.<list rend="bulleted">
<item>the <gi>form</gi> element, which groups orthographic information and
pronunciations, is described in section <ptr target="#DITPFO"/>
</item>
<item>the <gi>gramGrp</gi> element, which groups elements for the grammatical
characterization of the headword, is described in section <ptr target="#DITPGR"/>
</item>
<item>the <gi>def</gi> element, which describes the meaning of the headword, is
described in section <ptr target="#DITPSE"/>
</item>
<item>the <gi>etym</gi> element and its special phrase-level elements are documented
in section <ptr target="#DITPET"/>
</item>
<item>the <gi>cit</gi> element and its specific applications are described in
section <ptr target="#DITPSE"/> and section <ptr target="#DITPMI"/>
</item>
<item>the <gi>usg</gi>, <gi>lbl</gi>, <gi>xr</gi>, and <gi>note</gi> elements are
described in section <ptr target="#DITPMI"/>
</item>
<item>the <gi>re</gi> element, which marks nested entries for related words, is
described in section <ptr target="#DITPRE"/>
</item>
</list>
</p>
<div type="div3" xml:id="DITPFO">
<head>Information on Written and Spoken Forms</head>
<p>Dictionary entries most often begin with information about the form of the word to
which the entry applies. Typically, the orthographic form of the word, sometimes
marked for syllabification or hyphenation, is the first item in an entry. Other
information about the word, including variant or alternate forms, inflected forms,
pronunciation, etc., is also often given. </p>
<p>The following elements should be used to encode this information: the <gi>form</gi>
element groups one or more occurrences of any of them; it can also be
recursively nested to reflect more complex sub-grouping of information about word
form(s), as shown in the examples.<specList>
<specDesc key="form" atts="type"/>
<specDesc key="orth" atts="type extent"/>
<specDesc key="pron" atts="extent"/>
<specDesc key="hyph"/>
<specDesc key="syll"/>
<specDesc key="stress"/>
<specDesc key="lbl"/>
</specList>
</p>
<p>In addition to those listed above, the following elements, which encode morphological
details of the form, may also occur within <gi>form</gi> elements:<specList>
<specDesc key="gram" atts="type"/>
<specDesc key="gen"/>
<specDesc key="number"/>
<specDesc key="case"/>
<specDesc key="per"/>
<specDesc key="tns"/>
<specDesc key="mood"/>
<specDesc key="iType" atts="type"/>
<specDesc key="pos"/>
<specDesc key="subc"/>
<specDesc key="colloc"/>
</specList> Of these, the <gi>gram</gi> element is most general, and all of the
others are synonymous with a <gi>gram</gi> element with appropriate values (<val>gen,
number, case</val>, etc.) for the <att>type</att> attribute.</p>
<p>The use of these elements as children of <gi>form</gi> is deprecated; instead, they
should always be children of a <gi>gramGrp</gi> within <gi>form</gi> when describing 
that particular form of the word.</p>
<p>Different dictionaries use different means to mark hyphenation,
syllabification, and stress, and they often use some unusual glyphs
(e.g., the <soCalled>middle dot</soCalled> for hyphenation). All of
these glyphs are in the Unicode character set, as discussed in <ptr target="#SG-er"/>. When transcribing representations of pronunciation
the International Phonetic Alphabet should be used. It may be
convenient (as has been done in the text of this chapter) to use a
simple transliteration scheme for this; such a scheme should however be
properly documented in the header. </p>
<p>In the simplest case, nothing is given but the orthography:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>doom-laden</orth>
</form>
</egXML>
</p>
<p>Often, however, pronunciation is given.<q rend="display">
<hi rend="bold">soucoupe</hi> [sukup] … <ref target="#DIC-DNT">DNT</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="fr">
<form>
<orth>soucoupe</orth>
<pron>sukup</pron>
</form>
</egXML>
</p>
<p>For a variety of reasons including ease of processing, it may be desired to split
into separate elements information which is collapsed into a single element in the
source text; orthography and hyphenation may for example be transcribed as separate
elements, although given together in the source text. For a discussion of the issues
involved, and of methods for retaining both the presentation form and the
interpreted form, see section <ptr target="#DIMV"/>. </p>
<p>This example splits orthography and hyphenation, and adds syllabification because it
differs from hyphenation:<q rend="display">
<hi rend="bold">ar.ea</hi> … <ref target="#DIC-W7">W7</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>area</orth>
<hyph>ar|ea</hyph>
<syll>ar|e|a</syll>
</form>
</egXML>
<!--
<q rend='display'>
<hilited rend='bold'>alternating current</hilited>  <code>/,....'../
</code> ...  <ref target="#DIC-LDOCE">LDOCE</ref>
</q>
<egXML xmlns="http://www.tei-c.org/ns/Examples"><![CDATA[<form>
   <orth>alternating current</orth>
   <stress>,....'..</stress>
</form>
]]>
</egXML>
-->
</p>
<p>Multiple orthographic forms may be given, e.g. to illustrate a word's inflectional
pattern:<q rend="display">
<hi rend="bold">brag</hi> … vb. brags, bragging, bragged … <ref target="#DIC-CED">CED</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>brag</orth>
</form>
<gramGrp>
<pos>vb</pos>
</gramGrp>
<form type="inflected">
<orth>brags</orth>
<orth>bragging</orth>
<orth>bragged</orth>
</form>
</egXML> Or the inflectional pattern may be indicated by reference to a table of
paradigms, as here:<q rend="display">
<hi rend="bold">horrifier</hi>
<code lang="ipa">[ORifje]</code> (7) vt … [C/R] </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="fr">
<form>
<orth>horrifier</orth>
<pron>ORifje</pron>
<gramGrp>
<iType type="vbtable">7</iType>
<!-- ... -->
</gramGrp>
</form>
<!-- ... -->
</egXML>
</p>
<!-- 
<p>As noted, <gi>iType</gi> etc. are synonymous with appropriately typed instances of
the general <gi>gram</gi> element; the last example might equally be tagged
thus:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>horrifier</orth>
<pron>ORifje</pron>
<gram type="iType / vbtable">7</gram>
</form>
</egXML>
</p>
-->
<p>Explanatory labels may be attached to alternate forms:<q rend="display">
<hi rend="bold">MTBF</hi>
<hi rend="it"> abbrev. for</hi> mean time between failures. <ref target="#DIC-CED">CED</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form type="abbrev">
<orth>MTBF</orth>
</form>
<form type="full">
<lbl>abbrev. for</lbl>
<orth>mean time between failures</orth>
</form>
</entry>
</egXML>
</p>
<p>When multiple orthographic forms are given, a pronunciation may be associated with
all of them, as here:<q rend="display">
<hi rend="bold">biryani</hi> or <hi rend="bold">biriani</hi>
<code lang="ipa">(%bIrI"A:nI) </code> … <ref target="#DIC-CED">CED</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>biryani</orth>
<orth>biriani</orth>
<pron>%bIrI"A:nI</pron>
</form>
</egXML>
</p>
<p>In other cases, different pronunciations are provided for different orthographic
forms; here, the <gi>form</gi> element is repeated to associate the first
orthographic form explicitly with the first pronunciation, and the second
orthographic form with the second pronunciation:<q rend="display">
<hi rend="bold">mackle</hi>
<code lang="ipa">("mak^@l) </code> or macule <code lang="ipa">("makju:l) </code> … <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>mackle</orth>
<pron>"makəl</pron>
</form>
<form>
<orth>macule</orth>
<pron>"makju:l</pron>
</form>
</egXML>
</p>
<p>Recursive nesting of the <gi>form</gi> element can preserve relations among elements
that are implicit in the text. For example, in the CED entry for <q>hospitaller</q>,
it is clear that <q>U.S.</q> is associated only with <q>hospitaler</q>, but that the
pronunciation applies to both forms. The following encoding preserves these
relations:<q rend="display">
<hi rend="bold">hospitaller</hi> or U.S. hospitaler <code lang="ipa">("hQspIt@l@) </code> … <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>hospitaller</orth>
<form>
<usg type="geo">U.S.</usg>
<orth>hospitaler</orth>
</form>
<pron>"hQspIt@l@</pron>
</form>
</egXML>

</p>
<specGrp xml:id="DDITPFO" n="The form group">



<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/form.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/orth.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/pron.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/hyph.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/syll.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/stress.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/gram.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/gen.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/number.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/case.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/per.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/tns.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/mood.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/iType.xml"/>



 </specGrp>
<specGrp xml:id="DEDITPFO" n="Classes for morphological, grammatical, and form information">



<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/model.morphLike.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/model.gramPart.xml"/>






<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/model.formPart.xml"/>



 </specGrp>

</div>
<div type="div3" xml:id="DITPGR">
<head>Grammatical Information</head>
<p>The <gi>gramGrp</gi> element groups grammatical information, such as part of speech,
subcategorization information (e.g., syntactic patterns for verbs, count/mass
distinctions for nouns), etc. It can contain any of the morphological elements defined
in section <ptr target="#DITPFO"/> for <gi>form</gi> and can appear as a child of <gi>entry</gi>, 
<gi>form</gi>, <gi>sense</gi>, <gi>cit</gi>, or any other element containing content about which 
there is grammatical information. For example, in the entry <q>
<hi rend="bold">pinna</hi> ('pIn@) n., pl. -nae (-ni:) or -nas</q> <ref target="#DIC-CED">CED</ref>, the
word defined can be either singular or plural; the <q>pl.</q> specification applies
only to the inflected forms provided. Compare this with <q>pants (paents) pl.
n.</q>, where <q>pl.</q> applies to the headword itself. </p>
<p>As noted above in section <ptr target="#DITPFO"/>, the elements for morphological
information are simply shorthand for the general purpose <gi>gram</gi> element.
Consider this entry for the French word <mentioned>médire</mentioned>: <!-- no such word, unless you add the accent! (LB -->
<q rend="display">
<hi rend="bold">médire</hi> v.t. ind. (de) … <ref target="#DIC-PLC">PLC</ref></q> This entry can be
tagged using specialized grammatical elements:<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>médire</orth>
</form>
<gramGrp>
<pos>v</pos>
<subc>t ind</subc>
<colloc>de</colloc>
</gramGrp>
</egXML> Or using the <gi>gram</gi> element:<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>médire</orth>
</form>
<gramGrp>
<gram type="pos">v</gram>
<gram type="subc">t ind</gram>
<gram type="collocPrep">de</gram>
</gramGrp>
</egXML>
</p>
<p>Like <gi>form</gi>, <gi>gramGrp</gi> can be repeated, recursively nested, or used at
the <gi>sense</gi> level to show relations among elements.<q rend="display">
<hi rend="bold">isotope</hi> adj. et n. m. … <ref target="#DIC-DNT">DNT</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos>adj</pos>
</gramGrp>
<gramGrp>
<pos>n</pos>
<gen>m</gen>
</gramGrp>
</egXML>
<!-- <q rend='display'> -->
<!-- ablaze (@"bleIz) adj.  (postpositive), adv. 1. on fire;  -->
<!-- burning. 2. brightly illuminated. 3. emotionnally-->
<!-- aroused.  <ref target="#DIC-CED">CED</ref>  -->
<!-- </q> -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- <entry>  -->
<!--   <form> -->
<!-- <orth>ablaze</orth>  -->
<!-- 
<pron>@"bleIz</pron> -->
<!--   </form>-->
<!--   <gramGrp>  -->
<!-- 
<pos>adj</pos>   -->
<!-- <subc>postpositive</subc>-->
<!--   </gramGrp> -->
<!--   <gramGrp>  -->
<!-- 
<pos>adv</pos>   -->
<!--   </gramGrp> -->
<!--   <sense n='1'>  -->
<!-- <def>on fire; burning.</def> -->
<!--   </sense>   -->
<!--   <sense n='2'>  -->
<!-- <def>brightly illuminated.</def> -->
<!--   </sense>   -->
<!--   <sense n='3'>  -->
<!-- <def>emotionnally aroused.</def> -->
<!--   </sense>   -->
<!-- </entry> -->
<!--  -->
<!-- ]]>  -->
<!-- </egXML>-->
<q rend="display">
<hi rend="bold">wits</hi> (wIts) pl. n. 1. (sometimes sing.) the ability to
reason and act, esp. quickly … <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>wits</orth>
<pron>wIts</pron>
</form>
<gramGrp>
<number>pl</number>
<pos>n</pos>
</gramGrp>
<sense n="1">
<gramGrp>
<number>sometimes sing.</number>
</gramGrp>
<def>the ability to reason and act, esp. quickly …</def>
</sense>
</entry>
</egXML>
</p>
<specGrp xml:id="DDITPGR" n="The gram group">









<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/gramGrp.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/pos.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/subc.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/colloc.xml"/>





 </specGrp>
</div>
<div type="div3" xml:id="DITPSE">
<head>Sense Information</head>
<p>Dictionaries may describe the meanings of words in a wide variety of different 
 ways—by means of synonyms, paraphrases, translations into other languages, formal
definitions in various highly stylized forms, etc. No attempt is made here to
distinguish all the different forms which sense information may take;
all of them may
be tagged using the <gi>def</gi> element described in section <ptr target="#DITPDE"/>. </p>
<p>As a special case it is frequently desirable to distinguish
the provision of translation equivalents in other languages from other
forms of sense information; the use of <tag>cit
type="translation"</tag> (which groups a translation equivalent with
related information such as its grammatical description) 
for this purpose is described
in section <ptr target="#DITPTR"/>. </p>
<!--<p>Whether sense information in multilingual dictionaries is consistently tagged using
<gi>tr</gi> or <gi>def</gi> is a matter of the encoder's choice; no blanket
recommendation is made here. </p>-->
<div type="div4" xml:id="DITPDE">
<head>Definitions</head>
<p>Dictionary definitions are those pieces of prose in a dictionary entry that
describe the meaning of some lexical item. Most often, definitions describe the
headword of the entry; in some cases, they describe translated texts, examples,
etc.; see <tag>cit type="translation"</tag>, section <ptr target="#DITPTR"/>, and
<tag>cit type="example"</tag>, section <ptr target="#DITPEG"/>. The
<gi>def</gi> element directly contains the text of the definition; unlike
<gi>form</gi> and <gi>gramGrp</gi>, it does not serve solely to
group a set of smaller elements. The close analysis of definition text, such as
the tagging of hypernyms, typical objects, etc., is not covered by these
Guidelines. </p>
<p>Definitions may occur directly within an entry; when multiple
definitions are given, they are typically identified as belonging to
distinct senses, as here:<q rend="display"> <hi rend="bold">demigod</hi> (…) n. 1.a. a being who is part mortal, part
god. b. a lesser deity. 2. a godlike person. <ref target="#DIC-CP">CP</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>demigod</orth>
<pron> … </pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<sense n="a">
<def>a being who is part mortal, part god.</def>
</sense>
<sense n="b">
<def>a lesser deity.</def>
</sense>
</sense>
<sense n="2">
<def>a godlike person.</def>
</sense>
</entry>
</egXML>
</p>
<p>In multilingual dictionaries, it is sometimes possible to distinguish translation
equivalents from definitions proper; here a <gi>def</gi> element is
distinguished from the translation information within which it appears.<q rend="display">
<hi rend="bold">rémoulade</hi>
<code lang="ipa">[Remulad] </code> nf remoulade, rémoulade (<hi rend="it">dressing containing mustard and herbs</hi>). <ref target="#DIC-CR">CR</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="mul">
<entry>
<form>
<orth>rémoulade</orth>
<pron>Remulad</pron>
</form>
<gramGrp>
<pos>n</pos>
<gen>f</gen>
</gramGrp>
<cit type="translation" xml:lang="en">
<quote>remoulade</quote>
<quote>rémoulade</quote>
<def>dressing containing mustard and herbs</def>
</cit>
</entry>
</egXML>
</p>
<specGrp xml:id="DDITPDE" n="Definition text">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/def.xml"/>





 </specGrp>

</div>
<div type="div4" xml:id="DITPTR">
<head>Translation Equivalents</head>
<p>Multilingual dictionaries contain information about translations of a given word
in some source language for one or more target languages. Minimally, the
dictionary provides the corresponding translation in the target language; other
material, such as morphological information (gender, case), various kinds of
usage restrictions, etc., may also be given. If translation equivalents are to
be distinguished from other kinds of sense information, they may be encoded
using <tag>cit type="translation"</tag>. The global <att>xml:lang</att> attribute
should be used to specify the target language. </p>
<p>As in monolingual dictionaries, the <gi>sense</gi> element is used in
multilingual dictionaries to group information (forms, grammatical information,
usage, translation(s), etc.) about a given sense of a word where necessary.
Information about the individual translation equivalents within a sense is
grouped using <tag>cit type="translation"</tag>. This information may include the
translation text (tagged <gi>q</gi> or <gi>quote</gi>), morphological
information (<gi>gen</gi>, <gi>case</gi>, etc.), usage notes (<gi>usg</gi>),
translation labels (<gi>lbl</gi>), and definitions (<gi>def</gi>).When
bibliographic data is provided, the <gi>quote</gi> element should be used.<specList>
<specDesc key="cit"/>
<specDesc key="lbl"/>
</specList>
</p>
<p>Note how in the following example, different translation
equivalents are grouped into the same or different senses, following
the punctuation of the source and the usage labels:<q rend="display">
<hi rend="bold">dresser</hi> … (a) (Theat) habilleur m, -euse f;
(Comm: window ~) étalagiste mf. she's a stylish ~ elle s'habille avec
chic; V hair.  (b) (tool) (for wood) raboteuse f; (for stone) rabotin
m. <ref target="#DIC-CR">CR</ref> </q>
<!-- < note place='inline' > [homograph numbers superscripted   -->
<!-- in original text; pronunciations have to be fixed -JV,   -->
<!-- NI] < /note >-->
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="mul">
<entry n="1">
<form>
<orth>dresser</orth>
</form>
<sense n="a">
<sense>
<usg type="dom">Theat</usg>
<cit type="translation" xml:lang="fr">
<quote>habilleur</quote>
<gramGrp>
<gen>m</gen>
</gramGrp>
</cit>
<cit type="translation" xml:lang="fr">
<quote>-euse</quote>
<gramGrp>
<gen>f</gen>
</gramGrp>
</cit>
</sense>
<sense>
<usg type="dom">Comm</usg>
<form type="compound">
<orth>window <oRef/>
</orth>
</form>
<cit type="translation" xml:lang="fr">
<quote>étalagiste</quote>
<gramGrp>
<gen>mf</gen>
</gramGrp>
</cit>
</sense>
<cit type="example">
<quote>she's a stylish <oRef/>
</quote>
<cit type="translation" xml:lang="fr">
<quote>elle s'habille avec chic</quote>
</cit>
</cit>
<xr type="see">V. <ref target="#hair">hair</ref>
</xr>
</sense>
<sense n="b">
<usg type="category">tool</usg>
<sense>
<usg type="hint">for wood</usg>
<cit type="translation" xml:lang="fr">
<quote>raboteuse</quote>
<gramGrp>
<gen>f</gen>
</gramGrp>
</cit>
</sense>
<sense>
<usg type="hint">for stone</usg>
<cit type="translation" xml:lang="fr">
<quote>rabotin</quote>
<gramGrp>
<gen>m</gen>
</gramGrp>
</cit>
</sense>
</sense>
</entry>
 <!-- ... -->
<entry xml:id="hair">
<sense><!-- ... --></sense>
</entry>
</egXML>
</p>
<p>In the following example, a distinction is made between the
translation equivalent (<q>OAS</q>) and a descriptive phrase providing
further information for the user of the dictionary.<q rend="display">
<hi rend="bold">O.A.S.</hi> ... nf (abrév de <hi rend="bold">Organisation de l'Armée secrète</hi>) OAS (<hi rend="it">illegal military organization supporting French rule of
Algeria</hi>). <ref target="#DIC-CR">CR</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<!-- ... -->
<cit type="translation" xml:lang="en">
<quote>OAS</quote>
<def>illegal military organization supporting French rule of
Algeria</def>
</cit>
</entry>
</egXML>
</p>
<p>Note that <tag>cit type="translation"</tag> may also be used in monolingual
dictionaries when a translation is given for a foreign word: 
<q rend="display">
<hi rend="bold">havdalah</hi> or <hi rend="bold">havdoloh</hi> Hebrew.
(Hebrew <code lang="ipa">hAvdA"lA; </code> Yiddish <code lang="ipa">hAv"dOl@) </code> n. Judaism. the ceremony marking the end of the
sabbath or of a festival, including the blessings over wine, candles and
spices. [literally: separation] <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry type="foreign">
<form>
<orth>havdalah</orth>
<orth>havdoloh</orth>
<gramGrp>
<gram type="pos">n.</gram>
</gramGrp>
</form>
<sense>
<usg type="dom">Judaism</usg>
<def>the ceremony marking the end of the sabbath or of a festival,
including the blessings over wine, candles and spices.</def>
</sense>
<cit type="translation" xml:lang="en">
<usg type="style">literally</usg>
<quote>separation</quote>
</cit>
</entry>
</egXML>
</p>
</div>
</div>
<div type="div3" xml:id="DITPET">
<head>Etymological Information</head>
<p>The element <gi>etym</gi> marks a block of etymological information. Etymologies may
contain highly structured lists of words in an order indicating their descent from
each other, but often also include related words and forms outside the direct line
of descent, for comparison. Not infrequently, etymologies include commentary of
various sorts, and can grow into short (or long!) essays with prose-like structure.
This variation in structure makes it impracticable to define tags which capture the
entire intellectual structure of the etymology or record the precise interrelation
of all the words mentioned. It is, however, feasible to mark some of the more
obvious phrase-level elements frequently found in etymologies, using tags defined in
the core module or elsewhere in this chapter. Of particular relevance for the
markup of etymologies are:<specList>
<specDesc key="etym"/>
<specDesc key="lang"/>
<specDesc key="date"/>
<specDesc key="mentioned"/>
<specDesc key="gloss"/>
<specDesc key="pron"/>
<specDesc key="usg"/>
<specDesc key="lbl"/>
</specList>
</p>
<p>As in other prose, individual word forms mentioned in an etymological description are
tagged with <gi>mentioned</gi> elements. Pronunciations, usage labels, and glosses
can be tagged using the <gi>pron</gi>, <gi>usg</gi>, and <gi>gloss</gi> elements
defined elsewhere in these Guidelines. In addition, the <gi>lang</gi> element may be
used to identify a particular language name where it appears, in addition to using
the <att>xml:lang</att> attribute of the <gi>mentioned</gi> element. </p>
<p>Examples:<q rend="display">
<hi rend="bold">abismo</hi> m. (del gr. a priv. y byssos, fondo). Sima, gran
profundidad. … </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="es">
<entry>
<form>
<orth>abismo</orth>
</form>
<etym>del <lang>gr.</lang>
<mentioned>a</mentioned> priv. y <mentioned>byssos</mentioned>,
<gloss>fondo</gloss>
</etym>
<!-- ... -->
</entry>
</egXML>
<q rend="display">
<hi rend="bold">neume</hi>
<code lang="ipa">\'n(y)üm\</code> n [F, fr. ML pneuma, neuma, fr. Gk pneuma
breath — more at <hi rend="bold">pneumatic</hi>]: any of various symbols used in
the notation of Gregorian chant … [WNC]</q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<!-- ... -->
<etym>
<lang>F</lang> fr. <lang>ML</lang>
<mentioned>pneuma</mentioned>
<mentioned>neuma</mentioned> fr. <lang>Gk</lang>
<mentioned>pneuma</mentioned>
<gloss>breath</gloss>
<xr type="etym">more at <ptr target="#pneumatic"/>
</xr>
</etym>
<sense>
<def>any of various symbols used in the notation of Gregorian chant <!-- ... --> </def>
</sense>
</entry>
<!-- ... -->
<entry xml:id="pneumatic">
<etym><!-- ... --></etym>
</entry>
</egXML>
</p>
<specGrp xml:id="DDITPET" n="Etymologies">
<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/etym.xml"/>
<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/lang.xml"/>
 </specGrp>

</div>
<div type="div3" xml:id="DITPMI">
<head>Other Information</head>
<div type="div4" xml:id="DITPEG">
<head>Examples</head>
<p>Dictionaries typically include examples of word use, usually accompanying
definitions or translations. In some cases, the examples are quotations from
another source, and are occasionally followed by a citation to the author. </p>
<p>The <tag>cit type="example"</tag> element contains usage examples and associated
information; the example text itself should be enclosed in a <gi>q</gi> or
<gi>quote</gi> element. The <gi>cit</gi> element associates a quotation with
a bibliographic reference to its source.<specList>
<specDesc key="q"/>
<specDesc key="quote"/>
<specDesc key="cit"/>
</specList>
</p>
<p>Examples frequently abbreviate the headword, and so their transcription will
frequently make use of the <gi>oRef</gi> or <gi>oVar</gi> elements described
below in section <ptr target="#DIHW"/>. </p>
<p>Examples:<q rend="display">
<hi rend="bold">multiplex</hi>
<code lang="ipa">/…/</code> adj tech having many parts: the multiplex eye
of the fly. <ref target="#DIC-LDOCE">LDOCE</ref></q>
<!-- [Check pron -JV, NI] -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<quote>the multiplex eye of the fly.</quote>
</egXML> Or when one wants a more comprehensive representation of
examples:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<cit type="example">
<quote>the multiplex eye of the fly.</quote>
</cit>
</egXML> As the following example shows, <gi>cit</gi> can also contain elements
such as <gi>pron</gi>, <gi>def</gi>, etc.<q rend="display">
<hi rend="bold">some</hi> … 4. (<hi rend="it">S~</hi> and <hi rend="it">any</hi> are used with <hi rend="it">more</hi>): Give me ~ more<code lang="ipa">/s@'mO:(r)/</code> <ref target="#DIC-OALD">OALD</ref> </q>
<!-- 
<pron> in an example -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<sense n="4">
<usg type="colloc">
<oRef type="cap"/> and <mentioned>any</mentioned> are used with
<mentioned>more</mentioned>
</usg>
<cit type="example">
<quote>Give me <oRef/> more</quote>
<pron extent="part">s@'mO:(r)</pron>
</cit>
</sense>
</egXML> In multilingual dictionaries, examples may also be accompanied by
translations:<q rend="display">
<hi rend="bold">horrifier</hi> … vt to horrify. <hi rend="bold">elle était
horrifiée par la dépense</hi> she was horrified at the expense. <ref target="#DIC-CR">CR</ref> </q>
<!-- <trans> in an example -->
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="mul">
<entry>
<!-- ... -->
<cit type="translation" xml:lang="en">
<quote>to horrify</quote>
</cit>
<cit type="example">
<quote>elle était horrifiée par la dépense</quote>
<cit type="translation" xml:lang="en">
<quote>she was horrified at the expense.</quote>
</cit>
</cit>
</entry>
</egXML>
<!-- <q rend='display'> -->
<!-- 1. cent ...  III.  POUR CENT.  B&eacute;n&eacute;fice-->
<!-- de trois pour cent (3 %):  B&eacute;n&eacute;fice de 3F  -->
<!-- sur 100F.  <ref target="#DIC-DNT">DNT</ref> -->
<!-- </q> -->
<!-- <def> in an example -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!--   <q>B&eacute;n&eacute;fice de trois pour cent (3 %)</q> -->
<!--   <def>B&eacute;n&eacute;fice de 3F sur 100F</def>   -->
<!-- </egXML>-->
<!-- ]]>  -->
<!-- </egXML>-->
<!-- <q rend='display'> break1 ... 5 ...  <hilited  -->
<!-- rend='ital'>When the bank broke</hilited> (= was unable-->
<!-- to carry on business because of lack of funds) <hilited  -->
<!-- rend='ital'>, many people were ruined.</hilited> ...   -->
<!-- [OALD] </q>  -->
<!-- example interrupted by a partial definition -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!--   <q next='e2' xml:id='E1'>When the bank broke</q>   -->
<!--   <def>was unable to carry on business because   -->
<!--of lack of funds</def> -->
<!--   <q prev='e1' xml:id='E2'>, many people were ruined.</q>-->
<!-- </egXML>-->
<!-- ]]>  -->
<!-- </egXML>--> When a source is indicated, the example should be marked
with a <gi>bibl</gi> element:<q rend="display">
<hi rend="bold">valeur</hi> … n. f. … 2. Vx. Vaillance, bravoure
(spécial., au combat). <q>La valeur n'attend pas le nombre des années</q>
(Corneille). … <ref target="#DIC-DNT">DNT</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="fr">
<sense n="2">
<usg type="time">Vx.</usg>
<def>Vaillance, bravoure (spécial., au combat)</def>
<cit type="example">
<quote>La valeur n'attend pas le nombre des années</quote>
<bibl>
<author>Corneille</author>
</bibl>
</cit>
</sense>
</egXML>
</p>
</div>
<div type="div4" xml:id="DITPUS">
<head>Usage Information and Other Labels</head>

<p>Most dictionaries provide restrictive labels and phrases indicating
the usage of given words or particular senses. Other phrases, not
necessarily related to usage, may also be attached to forms, translations,
cross-references, and examples.  The following elements are provided
to mark up such  labels:<specList>
<specDesc key="usg"/>
<specDesc key="lbl"/>
</specList> As indicated in the following section (<ptr target="#DITPXR"/>), the
<gi>lbl</gi> element may be used for any kind of significative phrase
or label within the text. The <gi>usg</gi> element is a specialization
of this to mark usage labels in particular. Usage labels typically
indicate <list rend="bulleted">
<item>temporal use (archaic, obsolete, etc.)</item>
<item>register (slang, formal, taboo, ironic, facetious, etc.)</item>
<item>style (literal, figurative, etc.)</item>
<item>connotative effect (e.g. derogatory, offensive)</item>
<item>subject field (Astronomy, Philosophy, etc.)</item>
<item>national or regional use (Australian, U.S., Midland dialect,
etc.)</item>
</list> Many dictionaries provide an explanation and/or a list of such usage
labels in a preface or appendix. The type of the usage information may be
indicated in the <att>type</att> attribute on the <gi>usg</gi> element. Some
typical values are:<list type="gloss">
<label>
<val>geo</val>
</label>
<item>geographic area</item>
<label>
<val>time</val>
</label>
<item>temporal, historical era (<q>archaic</q>, <q>old</q>, etc.)</item>
<label>
<val>dom</val>
</label>
<item>domain</item>
<label>
<val>reg</val>
</label>
<item>register</item>
<label>
<val>style</val>
</label>
<item>style (figurative, literal, etc.)</item>
<label>
<val>plev</val>
</label>
<item>preference level (<q>chiefly</q>, <q>usually</q>, etc.)</item>
<label>
<val>acc</val>
</label>
<item>acceptability</item>
<label>
<val>lang</val>
</label>
<item>language for foreign words, spellings pronunciations, etc.</item>
<label>
<val>gram</val>
</label>
<item>grammatical usage</item>
</list> In addition to this kind of information, multilingual dictionaries often
provide <soCalled>semantic cues</soCalled> to help the user determine the right
sense of a word in the source language (and hence the correct translation).
These include synonyms, concept subdivisions, typical subjects and objects,
typical verb complements, etc. These labels may also be marked with the
<gi>usg</gi> element; sample values for the <att>type</att> attribute in these
cases include:<list type="gloss">
<label>
<val>syn</val>
</label>
<item>synonym given to show use</item>
<label>
<val>hyper</val>
</label>
<item>hypernym given to show usage</item>
<label>
<val>colloc</val>
</label>
<item>collocation given to show usage</item>
<label>
<val>comp</val>
</label>
<item>typical complement</item>
<label>
<val>obj</val>
</label>
<item>typical object</item>
<label>
<val>subj</val>
</label>
<item>typical subject</item>
<label>
<val>verb</val>
</label>
<item>typical verb</item>
<label>
<val>hint</val>
</label>
<item>unclassifiable piece of information to guide sense choice</item>
</list>
</p>
<p>In this entry, one spelling is marked as geographically restricted:<q rend="display">
<hi rend="bold">colour</hi> or U.S. <hi rend="bold">color</hi> … <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>colour</orth>
<form>
<usg type="geo">U.S.</usg>
<orth>color</orth>
</form>
</form>
</egXML>
</p>
<p>In the next example, usage labels are used to indicate domains, register, and
synonyms associated with different senses:<q rend="display">
<hi rend="bold">palette</hi>
<code lang="ipa">[palEt]</code> nf (a) (Peinture: lit, fig) palette. (b)
(Boucherie) shoulder. (c) (aube de roue) paddle; (battoir à linge) beetle;
(Manutention, Constr) pallet. <ref target="#DIC-CR">CR</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="mul">
<sense n="a">
<usg type="dom">Peinture</usg>
<usg type="style">lit</usg>
<usg type="style">fig</usg>
<cit type="translation" xml:lang="en">
<quote>palette</quote>
</cit>
</sense>
<sense n="b">
<usg type="dom">Boucherie</usg>
<cit type="translation" xml:lang="en">
<quote>shoulder</quote>
</cit>
</sense>
<sense n="c">
<sense>
<usg type="syn">aube de roue</usg>
<cit type="translation" xml:lang="en">
<quote>paddle</quote>
</cit>
</sense>
<sense>
<usg type="syn">battoir à linge</usg>
<cit type="translation" xml:lang="en">
<quote>beetle</quote>
</cit>
</sense>
<sense>
<usg type="dom">Manutention</usg>
<usg type="dom">Constr</usg>
<cit type="translation" xml:lang="en">
<quote>pallet</quote>
</cit>
</sense>
</sense>
</egXML>
<!-- <q rend='display'> parabola [p@"r&amp;@l@] n parabole f-->
<!-- (Math) <ref target="#DIC-CR">CR</ref> </q>-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- <entry>  -->
<!--   <form> -->
<!-- <orth>parabola</orth>-->
<!-- 
<pron>p@"r&amp;@l@</pron>-->
<!--   </form>-->
<!--   <gramGrp>  -->
<!-- 
<pos>n</pos> -->
<!--   </gramGrp> -->
<!--   <trans>-->
<!-- <tr>parabole<tr> -->
<!-- <gen>f</gen> -->
<!-- <usg type='dom'>Math</usg> -->
<!--   </trans>   -->
<!-- </entry> -->
<!-- ]]>  -->
<!-- </egXML>-->
</p>
<p>When the usage label is hard to classify, it may be described as a <q>hint</q>:<q rend="display">
<hi rend="bold">rempaillage</hi> […] nm reseating, rebottoming (<hi rend="it">with straw</hi>). <ref target="#DIC-CR">CR</ref> </q>
<!-- [note: tilde on the a in ~a (IPA nasal a) -JV, NI]   -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<cit type="translation" xml:lang="en">
<quote>reseating</quote>
<quote>rebottoming</quote>
<usg type="hint">with straw</usg>
</cit>
</entry>
</egXML>
</p>
<specGrp xml:id="DDITPUS" n="Usage information">
<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/usg.xml"/>
<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/lbl.xml"/>
 </specGrp>

</div>
<div type="div4" xml:id="DITPXR">
<head>Cross-References to Other Entries</head>
<p>Dictionary entries frequently refer to information in other entries, often using
extremely dense notations to convey the headword of the entry to be sought, the
particular part of the entry being referred to, and the nature of the
information to be sought there (synonyms, antonyms, usage notes, etymology, an
illustration, etc.)</p>
<p>Cross-references may be tagged in dictionaries using the <gi>ref</gi> and
<gi>ptr</gi> elements defined in the core module (section <ptr target="#COXR"/>). In addition, the <gi>xr</gi> element may be used to group all the
information relating to a cross-reference. 
<specList>
<specDesc key="xr"/>
<specDesc key="ref"/>
<specDesc key="ptr"/>
<specDesc key="lbl"/>
</specList>
</p>
<p>As in other types of text, the actual pointing element (e.g. <gi>ref</gi> or
<gi>ptr</gi>) is used to tag the cross-reference target proper (in
dictionaries, usually the headword, possibly accompanied by a homograph number,
a sense number, or other further restriction specifying what portion of the
target entry is being referred to).
The <gi>xr</gi> element
is used to group the target with any accompanying phrases or symbols used to
label the cross-reference; the cross-reference label itself may be tagged as a
<gi>lbl</gi> or may remain untagged. Both of the following are thus
legitimate:<q rend="display">
<hi rend="bold">glee</hi> … Compare <hi rend="bold">madrigal</hi> (sense 1)
<ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>glee</orth>
</form>
<xr>Compare <ptr target="#madrigal.1"/>
</xr>
</entry>
<entry xml:id="madrigal.1">
<form><!-- ... --></form>
</entry>
</egXML>
<q rend="display">
<hi rend="bold">hostellerie</hi> Syn. de hôtellerie (sens 1). <ref target="#DIC-DNT">DNT</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="fr">
<xr type="syn">
<lbl>Syn. de</lbl>
<ref>hôtellerie (sens 1)</ref>.</xr>
</egXML> In addition to using, or not using, <gi>lbl</gi> to mark the
cross-reference label, the two examples differ in another way. The former
assumes that the first sense of <mentioned>madrigal</mentioned> has the
identifier <val>madrigal.1</val>, and that the specific form of the reference in the
source volume can be reconstructed, if needed, from that information. The latter
does not require the first sense of <q>hôtellerie</q> to have an identifier, and
retains the print form of the cross-reference; by omitting the <att>target</att>
attribute of the <gi>ref</gi> element, however, the second example does assume
implicitly either that some software could usefully parse the phrase tagged as a
<gi>ref</gi> and find the location referred to, or else that such processing
will not be necessary. </p>
<p>The <att>type</att> attribute on the pointing element or on the <gi>xr</gi>
element may be used to indicate what kind of cross-reference is being made,
using any convenient typology. Since different dictionaries may label the same
kind of cross-reference in different ways, it may be useful to give normalized
indications in the <att>type</att> attribute, enabling the encoder to distinguish
irregular forms of cross-reference more reliably:<q rend="display">
<hi rend="bold">rose</hi>2 … vb. the past tense of <hi rend="bold">rise</hi>. <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry n="2">
<form>
<orth>rose</orth>
</form>
<xr type="inflectedForm">
<lbl>the past tense of</lbl>
<ref target="#rise">rise</ref>
</xr>
</entry>
<!-- ... -->
<entry xml:id="rise">
<form>
<orth>rise</orth>
</form>
<!-- main entry for "rise" as verb -->
</entry>
</egXML> from cross-references for synonyms and the like:<q rend="display">
<hi rend="bold">antagonist</hi> … syn see <hi rend="bold">adverse </hi>
<ref target="#DIC-W7">W7</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<xr type="synonym">
<lbl>syn see</lbl>
<ref target="#adverse">adverse</ref>
</xr>
<!-- ... -->
<entry xml:id="adverse">
<form>
<orth>adverse</orth>
</form>
<!-- list of synonyms  for "adverse"  -->
</entry>
</egXML>Strictly speaking, the reference above is not to the entry for
<mentioned>adverse</mentioned>, but to the list of synonyms found
within that entry. <!-- so why not point to that? --> 
<!--
Similarly,  the
target of the following reference is an illustration
accompanying another entry, not the whole entry:<q rend="display">
<hi rend="bold">ax, axe</hi> … → see the illus at <hi rend="bold">tool
</hi> <ref target="#DIC-OALD">OALD</ref> </q> This entry refers to the illustration at the entry
for <mentioned>tool</mentioned>, not the entry itself. The <att>target</att>
attribute might give the identifier of the illustration itself, or of the
enclosing entry (in which case the <att>type</att> attribute might be used to
infer that the reference is actually to the illustration, not the entry as a
whole).<egXML xmlns="http://www.tei-c.org/ns/Examples">
<xr type="illustration">
<lbl>see the illus at</lbl>
<ptr target="#tool.illus"/>
</xr>

<entry xml:id="tool">
<form><orth>tool</orth></form>
...
<graphic xml:id="tool.illus" ref="tool-figure.png"/>
</entry>
</egXML>
-->
 In some cases, the cross-reference is to a particular subset of the
meanings of the entry in question:<q rend="display">
<hi rend="bold">globe</hi> …V. <hi rend="bold">armillaire</hi> (sphère)
<ref target="#DIC-PR">PR</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="fr">
<xr>V. <ref target="#armillaire">armillaire</ref>
<lbl type="sense-restriction">sphère</lbl>
</xr>
</egXML>
</p>

<p>Cross-references occasionally occur in definition texts, example
texts, etc., or may be free-standing within an entry. These may
typically be encoded using <gi>ref</gi> or <gi>ptr</gi>, without an
enclosing <gi>xr</gi>. For example:
<q rend="display">
<hi rend="bold">entacher</hi> … <hi rend="it">Acte entaché de
nullité</hi>, contenant un vice de forme ou passé par un incapable*. <ref target="#DIC-DNT">DNT</ref>
</q> The asterisk signals a reference to the entry for
<mentioned>incapable</mentioned>.<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<def>contenant un vice de forme ou passé par un <ptr target="#incapable"/>.</def>
</egXML>
<!-- surely this should have been tagged as a <ref> not a 
<ptr> LB ? --> In
some cases, the form in the definition is inflected, and thus <gi>ref</gi> must
be used to indicate more exactly the intended target, as here:<q rend="display">
<hi rend="bold">justifier</hi> …4. IMPRIM Donner a (une ligne) une longeur
convenable au moyen de blancs (2, sens 1, 3). <ref target="#DIC-DNT">DNT</ref> </q>
<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<sense n="4">
<usg type="dom">imprim</usg>
<def>Donner a (une ligne) une longeur convenable au moyen de 
<ref target="#blanc-2.1.3">blancs (2, sens 1, 3)</ref>
</def>
</sense>

<entry xml:id="blanc" n="2">
<!-- ... -->
<sense n="1">
<!-- ... -->
<def xml:id="blanc-2.1.3">...</def>
<!-- ... -->
</sense>
<!-- ... -->
</entry>
</egXML>


</p>
<specGrp xml:id="DDITPXR" n="Cross-References">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/xr.xml"/>





 </specGrp>

</div>
<div type="div4" xml:id="DITPNO">
<head>Notes within Entries</head>
<p>Dictionaries may include extensive explanatory notes about usage, grammar,
context, etc. within entries. Very often, such notes appear as a separate
section at the end of an entry. The standard <gi>note</gi> element should be used for
such material.<specList>
<specDesc key="note"/>
</specList>
</p>
<p>For example:<q rend="display">
<hi rend="bold">ain't</hi>
<code lang="ipa">(eInt)</code>
<hi rend="it">Not standard. contraction of</hi> am not, is not, are not,
have not <hi rend="it">or</hi> has not: <hi rend="it">I ain't seen it.</hi>
….<hi rend="bold">Usage.</hi> Although the interrogative form <hi rend="it">ain't I?</hi> would be a natural contraction of <hi rend="it">am I not?</hi>, it is generally avoided in spoken English and never
used in formal English. <ref target="#DIC-CED">CED</ref> </q>
<!-- note: &triangle; is a small triangle -JV, NI -->
<!-- note: &triangle; changed to utrif to avoid name conflict (msm)  -->
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form type="contraction">
<orth>ain't</orth>
<pron>eInt</pron>
</form>
<usg type="reg">Not standard</usg>
<form type="full">
<lbl>contraction of</lbl>
<orth>am not</orth>
<orth>is not</orth>
<orth>are not</orth>
<orth>have not</orth>
<orth>has not</orth>
</form>
<cit type="example">
<quote>I ain't seen it.</quote>
</cit>
<note type="usage">Although the interrogative form <mentioned>ain't
I?</mentioned> would be a natural contraction of <mentioned>am I
not?</mentioned>, it is generally avoided in spoken English and
never used in formal English.</note>
</entry>
</egXML>
</p>
<p>The formal declaration for <gi>note</gi> is given in section <ptr target="#CONO"/>. </p>
</div>
</div>
<div type="div3" xml:id="DITPRE">
<head>Related Entries</head>
<p>The <gi>re</gi> element encloses a degenerate entry which appears in the body of
another entry for some purpose. Many dictionaries include related entries for direct
derivatives or inflected forms of the entry word, or for compound words, phrases,
collocations, and idioms containing the entry word. </p>
<p>Related entries can be complex, and may in fact include any of the information to be
found in a regular entry. Therefore, the <gi>re</gi> element is defined to contain
the same elements as an <gi>entry</gi> element, with the exception that it may not
contain any nested <gi>re</gi> elements. </p>
<p>Examples:<q rend="display">
<hi rend="bold">bevvy</hi>
<code lang="ipa">("bEvI)</code> Dialect. ~ n., pl. -vies. 1. a drink, esp. an
alcoholic one: we had a few bevvies last night. 2. a night of drinking. ~ vb. -
vies, -vying, -vied (intr.) 3. to drink alcohol [probably from Old French bevee,
buvee, drinking] —'bevvied adj. <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>bevvy</orth>
<pron>"bEvI</pron>
</form>
<usg type="reg">Dialect</usg>
<hom>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>a drink, esp. an alcoholic one: we had a few bevvies last night.</def>
</sense>
</hom>
<!-- ... sense 2 ... -->
<hom>
<gramGrp>
<pos>vb</pos>
</gramGrp>
<sense n="3">
<def>to drink alcohol</def>
</sense>
</hom>
<etym>probably from <lang>Old French</lang>
<mentioned>bevee</mentioned>, <mentioned>buvee</mentioned>
<gloss>drinking</gloss>
</etym>
<re type="derived">
<form>
<orth>bevvied</orth>
</form>
<gramGrp>
<pos>adj</pos>
</gramGrp>
</re>
</entry>
</egXML>
</p>
<specGrp xml:id="DDITPRE" n="Related entries">









<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/re.xml"/>





 </specGrp>

</div>
</div>
<div type="div2" xml:id="DIHW">
<head>Headword and Pronunciation References</head>
<p>Examples, definitions, etymologies, and occasionally other elements such as
cross-references, orthographic forms, etc., often contain a shortened or iconic reference to
the headword, rather than repeating the headword itself. The references may be to the
orthographic form or to the pronunciation, to the form given or to a variant of that
form. The following elements are used to encode such iconic references to a headword:<specList>
<specDesc key="oRef" atts="type"/>
<specDesc key="pRef"/>
<specDesc key="oVar" atts="type"/>
<specDesc key="pVar"/>
</specList>
</p>
<p>These elements all inherit the following attributes from the class <ident type="class">att.pointing</ident>
which may optionally be used to resolve any
ambiguity about the headword form being referred to.<specList>
<specDesc key="att.pointing" atts="target"/>
</specList></p>
<p>Headword references come in a variety of formats:<list type="gloss">
<label>~ </label>
<item>indicates a reference to the full form of the headword</item>
<label>pref~ </label>
<item>gives a prefix to be affixed to the headword</item>
<label>~suf </label>
<item>gives a suffix to be affixed to the headword</item>
<label>A~ </label>
<item>gives the first letter in uppercase, indicating that the headword is
capitalized</item>
<label>pref~suf </label>
<item>gives a prefix and a suffix to be affixed to the headword</item>
<label>a. </label>
<item>gives the initial of the word followed by a full stop, to indicate reference
to the full form of the headword</item>
<label>A. </label>
<item>refers to a capitalized form of the headword </item>
</list>
</p>
<p>The <gi>oRef</gi> element should be used for iconic or shortened references to the
orthographic form(s) of the headword itself. It is an empty element and replaces, rather
than enclosing, the reference. Note that the reference to a headword is not necessarily
a simple string replacement. In the example <q>
<hi rend="bold">colour</hi>1, (US = color) …~ films; ~ TV; Red, blue and yellow
are ~s.</q> <ref target="#DIC-OALD">OALD</ref>, the tilde stands for either headword form
(<mentioned>colour</mentioned>, <mentioned>color</mentioned>). </p>
<p>Examples:<q rend="display">
<hi rend="bold">colonel</hi> … army officer above a lieutenant-~. <ref target="#DIC-OALD">OALD</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<def>army officer above a lieutenant-<oRef/>
</def>
</egXML>
<!-- <q rend='display'> -->
<!-- take ...  < I don't &tilde; milk in my tea >   -->
<!-- [NPEG]   -->
<!-- </q> -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"><q>I don't <oRef> milk in my tea</q></egXML>-->
<!-- ]]>  -->
<!-- </egXML>-->
<q rend="display">
<hi rend="bold">academy</hi> … The Royal A~ of Arts <ref target="#DIC-OALD">OALD</ref></q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<q>The Royal <oRef type="cap"/> of Arts</q>
</egXML>
<!-- abeja, f. 1. (ento.) bee. 2. busy bee, hard worker. 3.   -->
<!-- (astron.)  A., Musca.  &mdash; a. albanila, mason bee; a.-->
<!-- carpintera, carpenter bee; a. reina or maestra, queen-->
<!-- bee; a. neutra or obrera, worker bee.  [SSSE]-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- encoding for sense 3 only-->
<!-- <sense n='3'>-->
<!--   <usg type='sem'>astron</usg> -->
<!--   <form> -->
<!-- <orth><oRef type='cap'></orth> -->
<!--   </form>-->
<!--   <trans>-->
<!-- <tr>Musca</tr>   -->
<!--   </trans>   -->
<!--   <re>   -->
<!-- <sense>  -->
<!--   <form> -->
<!-- <orth><oRef> albanila</orth> -->
<!--   </form>-->
<!--   <trans>-->
<!-- <tr>mason bee</tr>   -->
<!--   </trans>   -->
<!-- </sense> -->
<!-- <sense>  -->
<!--   <form> -->
<!-- <orth><oRef> carpintera</orth>   -->
<!--   </form>-->
<!--   <trans>-->
<!-- <tr>carpenter bee</tr>   -->
<!--   </trans>   -->
<!-- </sense> -->
<!-- <sense>  -->
<!--   <form> -->
<!-- <orth><oRef> reina</orth>-->
<!-- <orth orig='maestra'><oRef> maestra</orth>   -->
<!--   </form>-->
<!--   <trans>-->
<!-- <tr>queen bee</tr>   -->
<!--   </trans>   -->
<!-- </sense> -->
<!-- <sense>  -->
<!--   <form> -->
<!-- <orth><oRef> neutra</orth>   -->
<!-- <orth orig='obrera'><oRef> obrera</orth> -->
<!--   </form>-->
<!--   <trans>-->
<!-- <tr>worker bee</tr>  -->
<!--   </trans>   -->
<!-- </sense> -->
<!--   </re>  -->
<!-- </sense> -->
<!-- ]]>  -->
<!-- </egXML>-->
</p>
<p>The following example demonstrates the use of the <att>target</att> attribute to refer to
a specific form of the headword:<q rend="display">
<hi rend="bold">vag-</hi> or <hi rend="bold">vago-</hi> comb form … : vagus nerve
&lt; <hi rend="bold">vag</hi>al &gt; &lt; <hi rend="bold">vago</hi>tomy
&gt; <ref target="#DIC-W7">W7</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth xml:id="di-o1">vag-</orth>
<orth xml:id="di-o2">vago-</orth>
</form>
<def>vagus nerve</def>
<cit type="example">
<quote>
<oRef target="#di-o1" type="nohyph"/>al</quote>
<quote>
<oRef target="#di-o2" type="nohyph"/>tomy</quote>
</cit>
</entry>
</egXML>
<!-- 
<p>In this example the hyphen is retained in the first   -->
<!-- oRef, and not in the second: -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- 1 deuter- or deutero- ... <DEUTERO-genesis>  -->
<!-- 2 deuter- or deutero- ... <DEUTERated><ref target="#DIC-W7">W7</ref>   -->
<!--  -->
<!-- <entry n='1'>  -->
<!--   <form> -->
<!-- <orth xml:id='O11'>deuter-</orth>  -->
<!-- <orth xml:id='O12'>deutero-</orth> -->
<!--   </form>-->
<!--  ... -->
<!--   
<dicteg xmlns="http://www.tei-c.org/ns/Examples">   -->
<!-- <q><oRef target='O12'>genesis</q>-->
<!--   </dicteg>  -->
<!-- </entry> -->
<!--  -->
<!-- <entry n='2'>  -->
<!--   <form> -->
<!-- <orth xml:id='O21'>deuter-</orth>  -->
<!-- <orth xml:id='O22'>deutero-</orth> -->
<!--   </form>-->
<!--  ... -->
<!--   
<dicteg xmlns="http://www.tei-c.org/ns/Examples">   -->
<!-- <q><oRef target='O21' type='nohyph'>ated</q>   -->
<!--   </dicteg>  -->
<!-- </entry> -->
<!--  -->
<!-- ]]>  -->
<!-- </egXML>-->
<!-- neur- or neuro- comb form [NL, fr.  Gk, nerve, sinew,-->
<!-- fr. neuron &mdash; more at *nerve*] 1 :  nerve <NEURal>  -->
<!-- <NEUROlogy> 2 :  neural :  neural and <NEUROmuscular>.   -->
<!-- [WNC]-->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- <entry>  -->
<!--   <form> -->
<!-- <orth xml:id='O1'>neur-</orth> -->
<!-- <orth xml:id='O2'>neuro-</orth>-->
<!--   </form>-->
<!--   <gramGrp>  -->
<!-- 
<pos>comb form</pos> -->
<!--   </gramGrp> -->
<!--   <etym><lang>NL</lang> fr. <lang>Gk</lang> <cited>nerve</cited> -->
<!-- <gloss>sinew</gloss> fr. <cited>neuron</cited>   -->
<!-- <xr target='ETYM'> -->
<!--<xrl>more at</xrl>-->
<!--<xref path='nerve'> -->
<!-- </xr>-->
<!--   </etym>-->
<!--   <sense n='1'>  -->
<!-- <def>nerve</def> -->
<!-- 
<dicteg xmlns="http://www.tei-c.org/ns/Examples"> -->
<!--   <q><oRef target='O1' type='nohyph'>al</q>-->
<!-- </dicteg>-->
<!-- 
<dicteg xmlns="http://www.tei-c.org/ns/Examples"> -->
<!--   <q><oRef form='o2' type='nohyph'>logy</q>  -->
<!-- </dicteg>-->
<!--   </sense>   -->
<!--   <sense n='2'>  -->
<!-- <def>neural</def>-->
<!-- <def>neural and</def>-->
<!-- 
<dicteg xmlns="http://www.tei-c.org/ns/Examples"> -->
<!--   <q><oRef target='O2' type='nohyph'>muscular</q>  -->
<!-- </dicteg>-->
<!--   </sense>   -->
<!-- </entry> -->
<!-- ]]>  -->
<!-- </egXML>-->
</p>
<p>In many cases the reference is not to the orthographic form of the headword, but rather
to another form of the headword—usually to an inflected form. In these cases, the
element <gi>oVar</gi> should be used; this element takes as its content the string as it
appears in the text.<q rend="display">
<hi rend="bold">take</hi> … &lt; Mr Burton <hi rend="bold">took</hi> us for
French &gt; <ref target="#DIC-NPEG">NPEG</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<cit type="example">
<quote>Mr Burton <oVar type="pt">took</oVar> us for French</quote>
</cit>
</egXML>
<q rend="display">
<hi rend="bold">take</hi> … &lt; was quite <hi rend="bold">~n</hi> with him
&gt; <ref target="#DIC-NPEG">NPEG</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<cit type="example">
<quote>was quite <oVar type="pp">
<oRef/>n</oVar> with him</quote>
</cit>
</egXML>
</p>
<p>The next example shows a discontinuous reference, using the
attributes
<att>next</att> and
<att>prev</att>, which are defined in the additional module for linking,
segmentation, and alignment (see chapter <ptr target="#SA"/>) and therefore require that
that module be selected in addition to that for dictionaries.<q rend="display">
<hi rend="bold">mix up</hi>… &lt; it's easy to <hi rend="bold">mix</hi> her <hi rend="bold">up</hi> with her sister &gt; <ref target="#DIC-NPEG">NPEG</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<cit type="example">
<quote>it's easy to <oVar next="#ov2" xml:id="ov1">mix</oVar> 
her <oVar prev="#ov1" xml:id="ov2">up</oVar> with her sister</quote>
</cit>
</egXML>
</p>
<p>In addition, some dictionaries make reference to the pronunciation of the headword in the
pronunciation of related entries, variants, or examples. The <gi>pRef</gi>
and <gi>pVar</gi> elements should be used for such references.<q rend="display">
<hi rend="bold">hors d'oeuvre</hi>
<code lang="ipa">/,aw'duhv </code> (Fr O:r dœvr)/ n, pl hors d'oeuvres also hors
d'oeuvre <code lang="ipa">/'duhv(z) </code> (Fr ~)/ <ref target="#DIC-NPEG">NPEG</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:lang="mul">
<form>
<orth>hors d'oeuvre</orth>
<pron>%aU"dUv</pron>
<form>
<usg type="lang">Fr</usg>
<pron xml:id="di-p2">OR d0vR</pron>
</form>
</form>
<form type="inflected">
<number>pl</number>
<orth>hors d'oeuvres</orth>
<orth>hors d'oeuvre</orth>
<pron extent="part">"dUv(z)</pron>
<form>
<usg type="lang">Fr</usg>
<pron>
<pRef target="#di-p2"/>
</pron>
</form>
</form>
</egXML>
</p>
<p>Because headword and pronunciation references can occur virtually anywhere in an entry,
the <gi>oRef</gi>, <gi>oVar</gi>, <gi>pRef</gi>, and <gi>pVar</gi> elements can appear
within any other element defined for dictionary entries. </p>
<p>Since existing printed dictionaries use different conventions for headword references
(swung dash, first letter abbreviated form, capitalization, or italicization of the word,
etc.) the exact method used should be documented in the header. </p>

<specGrp xml:id="DEDIHW" n="Classes for headword references">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/model.ptrLike.form.xml"/>
















</specGrp>

<specGrp xml:id="DDIHW" n="Headword references">





<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/oRef.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/oVar.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/pRef.xml"/>











<include xmlns="http://www.w3.org/2001/XInclude" href="../../Specs/pVar.xml"/>





 </specGrp>

</div>
<div type="div2" xml:id="DIMV">
<head>Typographic and Lexical Information in Dictionary Data</head>
<p>Among the many possible views of dictionaries, it is useful to distinguish at least the
following three, which help to clarify some issues raised with particular urgency by
dictionaries, on account of the complexity of both their typography and their
information structure.<list rend="bulleted">
<item>(a) the <term>typographic view</term>—the
two-dimensional printed page, including information about line and page breaks
and other features of layout </item>
<item>(b) the <term>editorial view</term>—the one-dimensional sequence of tokens
which can be seen as the input to the typesetting process; the wording and
punctuation of the text and the sequencing of items are visible in this view,
but specifics of the typographic realization are not </item>
<item>(c) the <term>lexical view</term>—this view includes the underlying
information represented in a dictionary, without concern for its exact textual
form </item>
</list>
</p>
<p>For example, a domain indication in a dictionary entry might be broken over a line and
therefore hyphenated (<q>naut-</q>
<q>ical</q>); the typographic view of the dictionary preserves this information. In a
purely editorial view, the particular form in which the domain name is given in the
particular dictionary (as <q>nautical</q>, rather than <q>naut.</q>, <q>Naut.</q>, etc.)
would be preserved, but the fact of the line break would not. Font shifts might
plausibly be included in either a strictly typographic or an editorial view. In the
lexical view, the only information preserved concerning domain would be some standard
symbol or string representing the nautical domain (e.g. <q>naut.</q>) regardless of the
form in which it appears in the printed dictionary. </p>
<p>In practice, publishers begin with the lexical view—i.e., lexical data as it might
appear in a database—and generate first the editorial view, which reflects editorial
choices for a particular dictionary (such as the use of the abbreviation <q>Naut.</q>
for <q>nautical</q>, the fonts in which different types of information are to be
rendered, etc.), and then the typographic view, which is tied to a specific printed
rendering. Computational linguists and philologists often begin with the typographic
view and analyse it to obtain the editorial and/or lexical views. Some users may
ultimately be concerned with retaining only the lexical view, or they may wish to
preserve the typographic or editorial views as a reference text, perhaps as a guard
against the loss or misinterpretation of information in the translation process. Some
researchers may wish to retain all three views, and study their interrelations, since
research questions may well span all three views. </p>
<p>In general, an electronic encoding of a text will allow the recovery of at least one view
of that text (the one which guided the encoding); if editorial and typographic practices
are consistently applied in the production of a printed dictionary, or if exceptions to
the rules are consistently recorded in the electronic encoding, then it is <emph>in
principle</emph> possible to recover the editorial view from an encoding of the
lexical view, and the typographic view from an encoding of the editorial view. In
practice, of course, the severe compression of information in dictionaries, the variety
of methods by which this compression is achieved, the complexity of formulating
completely explicit rules for editorial and typographic practice, and the relative
rarity of complete consistency in the application of such rules, all make the mechanical
transformation of information from one view into another something of a vexed question. </p>
<p>This section describes some principles which may be useful in capturing one or the other
of these views as consistently and completely as possible, and describes some methods of
attempting to capture more than one view in a single encoding. Only the editorial and
lexical views are explicitly treated here; for methods of recording the physical or
typographic details of a text, see chapter <ptr target="#PH"/>. Other approaches to
these problems, such as the use of repetitive encoding and links to show their
correspondences, or the use of feature structures to capture the information structure,
and of the <att>ana</att> and <att>inst</att> attributes to link feature structures to a
transcription of the editorial view of a dictionary, are not discussed here (for
feature structures, see chapter <ptr target="#FS"/>. For linkage of textual form and
underlying information, see chapter <ptr target="#AI"/>). </p>
<div type="div3" xml:id="DIMVTV">
<head>Editorial View</head>
<p>Common practice in encoding texts of all sorts relies on principles such as the
following, which can be used successfully to capture the editorial view when
encoding a dictionary:<list rend="numbered">
<item>All characters of the source text should be retained, with the possible
exception of <term>rendition text</term> (for which see further below). </item>
<item>Characters appearing in the source text should typically be given as
character data content in the document, rather than as the value of an
attribute; again, rendition text may optionally be excepted from this rule. </item>
<item>Apart from the characters or graphics in the source text, nothing else
should appear as content in the document, although it may be given in
attribute values. </item>
<item>The material in the source text should appear in the encoding in the same
order. Complications of the character sequence by footnotes, marginal notes,
etc., text wrapping around illustrations, etc., may be dealt with by the
usual means (for notes, see section <ptr target="#CONO"/>).<note place="bottom">Complications of sequence caused by marginal or interlinear
insertions and deletions, which are frequent in manuscripts, or by
unconventional page layouts, as in concrete poetry, magazines with
imaginative graphic designers, and texts about the nature of typography
as a medium, typically do not occur in dictionaries, and so are not
discussed here.</note>
</item>
</list>
</p>
<p>In a very conservative transcription of the editorial view of a text, <term>rendition
characters</term> (e.g. the commas, parentheses, etc., used in dictionary
entries to signal boundaries among parts of the entry) and <term>rendition
text</term> (for example, conjunctions joining alternate headwords, etc.) are
typically retained. Removing the tags from such a transcription will leave all and
only the characters of the source text, in their original sequence.<note place="bottom">This is a slight oversimplification. Even in conservative
transcriptions, it is common to omit page numbers, signatures of gatherings,
running titles and the like. The simple description above also elides, for the
sake of simplicity, the difficulties of assigning a meaning to the phrase
<q>original sequence</q> when it is applied to the printed characters of a
source text; the <q>original sequence</q> retained or recovered from a
conservative transcription of the editorial view is, of course, the one
established during the transcription by the encoder.</note>
</p>
<p>Consider, for example, the following entry:<q rend="display">
<hi rend="bold">pinna</hi> ('pIn@) n., pl. -nae (-ni:) <hi rend="it">or</hi>
-nas. 1. any leaflet of a pinnate compound leaf. 2. <hi rend="it">Zoology</hi>.
a feather, wing, fin, or similarly shaped part. 3. another name for <hi rend="bold">auricle</hi> (sense 2). [C18: via New Latin from Latin: wing,
feather, fin] <ref target="#DIC-CED">CED</ref></q> A conservative encoding of the editorial view of this
entry, which retains all rendition text, might resemble the following:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>pinna</orth>
<pron>("pIn@)</pron>
</form>
<gramGrp>
<pos>n.</pos>, </gramGrp>
<form type="inflected">
<number>pl.</number>
<form>
<orth type="lat" extent="part">-nae</orth>
<pron extent="part">(-ni:)</pron>
</form> or <orth type="std" extent="part">-nas</orth>
</form>
<sense n="1">1. <def>any leaflet of a pinnate compound leaf.</def>
</sense>
<sense n="2">2. <usg type="dom">Zoology</usg>
<def>a feather, wing, fin, or similarly shaped part.</def>
</sense>
<sense n="3">3. <xr type="syn">
<lbl>another name for</lbl>
<ref target="#auricle.2">auricle (sense 2).</ref>
</xr>
</sense>
<etym>[<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>,
<gloss>fin</gloss>]</etym>
</entry>
<entry xml:id="auricle.2">
<form><!-- .... --></form>
</entry>
</egXML>
</p>
<p>A somewhat simplified encoding of the editorial view of this entry might exploit the
fact that rendition text is often systematically recoverable. For example,
parentheses consistently appear around pronunciation in this dictionary, and thus
are effectively implied by the start- and end-tags for <gi>pron</gi>.<note place="bottom">The omission of rendition text is particularly common in systems
for document production; it is considered good practice there, since automatic
generation of rendition text is more reliable and more consistent than
attempting to maintain it manually in the electronic text.</note> In such an
encoding, removing the tags should exactly reproduce the sequence of characters in
the source, minus rendition text. The original character sequence can be recovered
fully by replacing tags with any rendition text they imply. </p>
<p>Encoding in this way, the example given above might resemble the following. The
<gi>tagUsage</gi> element in the header would be used to record the following
patterns of rendition text:<list rend="bulleted">
<item>parentheses appear around <gi>pron</gi> elements</item>
<item>commas appear before inflected forms</item>
<item>the word <q>or</q> appears before alternate forms</item>
<item>brackets appear around the etymology</item>
<item>full stops appear after <gi>pos</gi>, inflection information, and sense
numbers</item>
<item>senses are numbered in sequence unless otherwise specified using the
global <att>n</att> attribute</item>
</list>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>pinna</orth>
<pron>"pIn@</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<form type="inflected">
<number>pl</number>
<form>
<orth type="lat" extent="part">-nae</orth>
<pron extent="part">-ni:</pron>
</form>
<orth type="std" extent="part">-nas</orth>
</form>
<sense n="1">
<def>any leaflet of a pinnate compound leaf.</def>
</sense>
<sense n="2">
<usg type="dom">Zoology</usg>
<def>a feather, wing, fin, or similarly shaped part.</def>
</sense>
<sense n="3">
<xr type="syn">
<lbl>another name for</lbl>
<ref>auricle (sense 2).</ref>
</xr>
</sense>
<etym>
<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>, <gloss>fin</gloss>
</etym>
</entry>
</egXML>
</p>
<p>When rendition text is omitted, it is recommended that the means to regenerate it be
fully documented, using the <gi>tagUsage</gi> element of the TEI header. </p>
<p>If rendition text is used systematically in a dictionary, with only a few mistakes or
exceptions, the global attribute <att>rend</att> may be used on any tag to flag
exceptions to the normal treatment. The values of the <att>rend</att> attribute are
not prescribed, but it can be used with values such as <val>no-comma</val>,
<val>no-left-paren</val>, etc. Specific values can be documented using the
<gi>rendition</gi> element in the TEI header. </p>
<p>In the following (imaginary) example, no left parenthesis precedes the
pronunciation:<q rend="display">
<hi rend="bold">biryani</hi> or <hi rend="bold">biriani</hi> %bIrI"A:nI) any of a
variety of Indian dishes … [from Urdu]</q> This irregularity can be recorded
thus:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>biryani</orth>
<orth>biriani</orth>
<pron rend="noleftparen">%bIrI"A:nI</pron>
</form>
<def>any of a variety of Indian dishes … </def>
<etym>from <lang>Urdu</lang>
</etym>
</entry>
</egXML>
</p>
</div>
<div type="div3" xml:id="DIMVLV">
<head>Lexical View</head>
<p>If the text to be interchanged retains only the lexical view of the text, there may
be no concern for the recoverability of the editorial (not to speak of the
typographic) view of the text. However, it is strongly recommended that the TEI
header be used to document fully the nature of all alterations to the original data,
such as normalization of domain names, expansion of inflected forms, etc. </p>
<p>In an encoding of the lexical view of a text, there are degrees of departure from the
original data: normalizing inconsistent forms like <q>nautical</q>, <q>naut</q>.,
<q>Naut.</q>, etc., to <q>nautical</q> is a relatively slight alteration;
expansion of <q>delay -ed -ing</q> to <q>delay, delayed, delaying</q> is a more
substantial departure. Still more severe is the rearranging of the order of
information in entries; for example:<list rend="bulleted">
<item>reorganizing the order of elements in an entry to show their
relationship, as in<q rend="display"> <hi rend="bold">clem</hi> (klEm)
or clam vb. clems, clemming, clemmed or clams, clamming, clammed <ref target="#DIC-CED">CED</ref></q> where in a strictly lexical view one
might wish to group <q>clem</q> and <q>clam</q> with their respective
inflected forms. </item>
<item>splitting an entry into two separate entries, as in <q rend="display">
<hi rend="bold">celi.bacy</hi> /"selIb@sI/ n [U] state of living
unmarried, esp as a religious obligation. celi.bate /"selIb@t/ n [C]
unmarried person (esp a priest who has taken a vow not to marry).
<ref target="#DIC-OALD">OALD</ref></q> For some purposes, this entry might usefully be split into an
entry for <q>celibacy</q> and a separate entry for <q>celibate</q>. </item>
</list>
</p>
<p>An encoding which captures the lexical view of the example given in the previous
section might look something like the following. In this encoding:<list rend="bulleted">
<item>abbreviated forms have been silently expanded</item>
<item>some forms have been moved to allow related forms to be grouped together</item>
<item>the part of speech information has been moved to allow all forms to be
given together</item>
<item>the cross-reference to <q>auricle</q> has been simplified</item>
</list>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<form>
<orth>pinna</orth>
<pron>"pIn@</pron>
<form type="inflected">
<number>pl</number>
<form>
<orth type="lat">pinnae</orth>
<pron>'pIni:</pron>
</form>
<orth type="std">pinnas</orth>
</form>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<sense n="1">
<def>any leaflet of a pinnate compound leaf.</def>
</sense>
<sense n="2">
<usg type="dom">Zoology</usg>
<def>a feather, wing, fin, or similarly shaped part.</def>
</sense>
<sense n="3">
<xr type="syn">
<ptr target="#auricle.2"/>
</xr>
</sense>
<etym>
<date>C18</date>: via <lang>New Latin</lang> from <lang>Latin</lang>:
<gloss>wing</gloss>, <gloss>feather</gloss>, <gloss>fin</gloss>
</etym>
</entry>
</egXML>
</p>
<p>Whether the given dictionary encoding focusses on the lexical view and thus approaches the status of
lexical databases, or uses the typographic/editorial view approach and needs to communicate the
sometimes informally stated values for the particular descriptive features, the issue of <soCalled>interoperability</soCalled> 
of the content and of the container objects becomes relevant, in view of the growing
tendency to interlink pieces of information across Internet resources. In such
cases, it becomes crucial to be able to encode the fact that whether the information on,
for instance, the value of the grammatical category of Number is provided as "sg.", "sing.", "Singular", or
equivalently "poj." in Polish, or "Ez." in German, etc., what is actually referred to is always the same 
grammatical value that can be rendered with a plethora of markers, depending on the publisher, language, or lexicographic tradition.
In order to signal that this variety of surface markers in fact indicate the same
underlying value, it is possible to align them with an external inventory of standardized
values. The TEI provides means to align grammatical categories as well as their content
with the ISOcat reference, which is a Web implementation of <ref
target="#ISO-12620">ISO 12620</ref>.</p>
<p>In the example below, a fragment of the entry for <foreign>isotope</foreign> cited
in section <ptr target="#DITPGR"/> is adorned by references to ISOcat definitions for "part
of speech" (<att>dcr:datcat</att>) and "adjective" (<att>dcr:valueDatcat</att>). Depending
on the status and extent of the dictionary, various strategies may be used to reduce the
redundancy of the repeated ISOcat references.<egXML
xmlns="http://www.tei-c.org/ns/Examples" valid="feasible">
<entry xmlns:dcr="http://www.isocat.org/ns/dcr">
<!--...-->
<form>
<orth>isotope</orth>
</form>
<gramGrp>
<pos dcr:datcat="http://www.isocat.org/datcat/DC-1345" dcr:valueDatcat="http://www.isocat.org/datcat/DC-1230">adj</pos>
</gramGrp>
<!--...-->
</entry>
</egXML></p>

</div>
<div type="div3" xml:id="DIMVBO">
<head>Retaining Both Views</head>
<p>It is sometimes desirable to retain both the lexical and the editorial view, in which
case a potential conflict exists between the two. When there is a conflict between
the encodings for the lexical and editorial views, the principles described in the
following sections may be applied. </p>
<div type="div4" xml:id="DIMVAV">
<head>Using Attribute Values to Capture Alternate Views</head>
<p>If the order of the data is the same in both views, then both views may be
captured by encoding one <soCalled>dominant</soCalled> view in the character
data content of the document, and encoding the other using attribute values on
the appropriate elements. If all tags were to be removed, the remaining
characters would be those of the dominant view of the text. </p>
<p>The attribute class <ident type="class">att.lexicographic</ident> is used to
provide attributes for use in encoding multiple views of the same dictionary
entry. These attributes are available for use on all elements defined in this
chapter when the base module for dictionaries is selected. </p>
<p>When the editorial view is dominant, the following attributes may be used to
capture the lexical view:<specList>
<specDesc key="att.lexicographic" atts="norm split"/>
</specList>
</p>
<p>When the lexical view is dominant, the following attributes may be used to record
the editorial view:<specList>
<specDesc key="att.lexicographic" atts="orig mergedIn"/>

</specList>
</p>
<p>One attribute is useful in either view:<specList>
<specDesc key="att.lexicographic" atts="opt"/>
</specList>
</p>
<p>For example, if the source text had the domain label <q>naut.</q>, it might be
encoded as follows. With the editorial view dominant:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<usg norm="nautical" type="dom">naut.</usg>
</egXML> The lexical view of the same label would transcribe the normalized form
as content of the <gi>usg</gi> element, the typographic form as an attribute
value:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<usg orig="naut." type="dom">nautical</usg>
</egXML>
</p>
<p>If the source text gives inflectional information for the verb
<mentioned>delay</mentioned> as <q>delay, -ed, -ing</q>, it might usefully be
expanded to <q>delayed, delayed, delaying</q>. An encoding of the editorial view
might take this form:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>delay</orth>
<form type="inflected">
<orth norm="delayed" extent="part">-ed</orth>
<tns norm="pst,pstp"/>
</form>
<form type="inflected">
<orth norm="delaying" extent="part">-ing</orth>
<tns norm="prsp"/>
</form>
</form>
</egXML> Note the use of the <gi>tns</gi> tag with null content, to enable the
representation of implicit information even though it has no print realization. </p>
<p>The lexical view might be encoded thus:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>delay</orth>
<form type="inflected">
<orth orig="-ed">delayed</orth>
<tns orig="">pst</tns>
<tns orig="">pstp</tns>
</form>
<form type="inflected">
<orth orig="-ing">delaying</orth>
<tns orig="">prsp</tns>
</form>
</form>
</egXML>
</p>

<!-- following section is problematic -->

<p>A particular problem may be posed by the common practice of presenting two
alternate forms of a word in a single string, by marking some parts of the word
as optional in some forms. The following entry is for a word which can be
spelled either <q>thyrostimuline</q> or <q>thyréostimuline</q>:<q rend="display">
<hi rend="bold">thyr(é)ostimuline</hi> [tiR(e)ostimylin] …</q> With the
editorial view dominant, this entry might begin thus:<egXML xmlns="http://www.tei-c.org/ns/Examples"
 xml:lang="fr">
<form>
<orth split="thyrostimuline, thyréostimuline">thyr(é)ostimuline</orth>
<pron split="tiRostimylin, tiReostimylin">tiR(e)ostimylin</pron>
</form>
</egXML> 

With the lexical view dominant, however, two <gi>orth</gi> and
two <gi>pron</gi> elements would be encoded, in order to disentangle the two
forms; the <att>orig</att> attribute would be used to record the typographic
presentation of the information in the source.<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth xml:id="dic-o1" orig="thyr(é)ostimuline">thyrostimuline</orth>
<pron xml:id="dic-p1" orig="tiR(e)ostimylin">tiRostimylin</pron>
</form>
<form>
<orth mergedIn="#dic-o1">thyréostimuline</orth>
<pron mergedIn="#dic-p1">tiReostimylin</pron>
</form>
</egXML>

</p>

<p>This example might also be encoded using the <att>opt</att> attribute combined
with the attributes <att>next</att> and <att>prev</att> defined in chapter <ptr
 target="#SA"/>.<egXML xml:lang="fr" xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth next="#dict-o2" xml:id="dict-o1">thyr</orth>
<orth next="#dict-o3" prev="#dict-o1" xml:id="dict-o2" opt="true">é</orth>
<orth prev="#dict-o2" xml:id="dict-o3">ostimuline</orth>
<pron next="#dict-p2" xml:id="dict-p1">tiR</pron>
<pron next="#dict-p3" prev="#dict-p1" xml:id="dict-p2" opt="true">e</pron>
<pron prev="#dict-p2" xml:id="dict-p3">ostimylin</pron>
</form>
</egXML>
</p>
<p>Note that this transcription preserves both the lexical and
editorial views in a single encoding. However, it has the disadvantage
that the strings corresponding to entire words do not appear in the
encoding uninterrupted, and therefore complex processing is required
to retrieve them from the encoded text. The use of the <att>opt</att>
attribute is recommended, however, when long spans of text are
involved, or when the optional part contains embedded tags. </p>

<p>For example, the following gives two definitions in one text:
<q>picture drawn with coloured chalk made into crayons</q>, and
<q>coloured chalk made into crayons</q>:
<q rend="display"> <hi rend="bold">pas.tel</hi> /"pastl US: pa"stel/ n
1 (picture drawn with) coloured chalk made into crayons. 2… <ref target="#DIC-OALD">OALD</ref></q> </p> <p>A simple encoding solution
would be to leave the definition text unanalysed, but this might be
felt inadequate since it does not show that there are two
definitions. A possible alternative encoding would be:<egXML xmlns="http://www.tei-c.org/ns/Examples"> <sense n="1"> <def>coloured
chalk made into crayons</def> <def>picture drawn with coloured chalk
made into crayons</def> </sense> </egXML> </p> <p>This transcribes
some characters of the source text twice, however, which deviates from
the usual practice. The following encoding records both the editorial
and lexical views:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<sense n="1"> <def next="#d2" xml:id="d1" opt="true">picture drawn
with</def> <def prev="#d1" xml:id="d2">coloured chalk made into
crayons</def> </sense> </egXML> </p> <!-- example doesnt work because
cit isnt a member of att.lexicographic—and shouldnt be --> <!-- <p>A
more complex example is the following, in which the optional element
contains additional tags:<q rend="display"> <hi
rend="bold">canary</hi> ...(Geog) Canary Isles, Canaries (îles fpl)
Canaries fpl... <ref target="#DIC-CR">CR</ref></q> <egXML
xmlns="http://www.tei-c.org/ns/Examples"> <re type="cmpd"> <usg
type="dom">Geog</usg> <form> <orth>Canary Isles</orth>
<orth>Canaries</orth> </form> <cit type="translation" next="#DICT-t2"
xml:id="DICT-t1" opt="true"> <q>îles</q> <gen>f</gen>
<number>pl</number> </cit> <cit type="translation" prev="#DICT-t1"
xml:id="DICT-t2"> <q>Canaries</q> <gen>f</gen> <number>pl</number>
</cit> </re> </egXML> </p> -->

</div> 
<div type="div4" xml:id="DIMVOL">
<head>Recording Original Locations of Transposed Elements</head>
<p>The attributes described in the previous section are useful only when the order
of material is the same in both the editorial and the lexical view. When the two
views impose different orders on the data, the standard linking mechanisms may be used to
show the original location of material transposed in an encoding of the lexical
view. </p>
<p>If the original is only slightly modified, the <gi>anchor</gi> element may be
used to mark the original location of the material, and the <att>location</att>
attribute may be used on the lexical encoding of that material to indicate its
original location(s). Like those in the preceding section, this attribute is
defined for the attribute class <ident type="class">att.lexicographic</ident>:<specList>
<specDesc key="att.lexicographic" atts="opt"/>
</specList>
</p>
<p>For example:<q rend="display">
<hi rend="bold">pinna</hi>
<code lang="ipa">("pIn@)</code> n., pl. -nae (-ni:) or -nas. <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<form>
<orth>pinna</orth>
<pron>'pIn@</pron>
<anchor xml:id="p01"/>
<form type="inflected">
<number>pl</number>
<form>
<orth extent="part">-nae</orth>
<pron extent="part">-ni:</pron>
</form>
<orth extent="part">-nas</orth>
</form>
</form>
<gramGrp>
<pos location="#p01">n</pos>
</gramGrp>
</egXML>
<!-- < p > If the modifications are more drastic (for -->
<!-- example, involving several elements), use the  < gi >-->
<!-- var < /gi >  and  < gi > rdg < /gi >  tags (see  -->
<!-- section ???  in Guidelines) to span the duplicated   -->
<!-- section in the original: -->
<!--  -->
<!-- < note place='inline' > [ Is this still valid in P2?   -->
<!-- -JV, NI] < /note >   -->
<!-- no. -msm -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> <![CDATA[clem (klEm) or clam vb. clems,  -->
<!-- clemming, clemmed or clams, clammimg, clammed ...-->
<!-- <ref target="#DIC-CED">CED</ref> ]]> </egXML>  -->
<!-- 
<p>Textual view: -->
<!-- 
<egXML xmlns="http://www.tei-c.org/ns/Examples"> -->
<!-- <![CDATA[-->
<!-- <entry>  -->
<!--  -->
<!-- <var>-->
<!--  -->
<!-- <rdg view='editorial'> -->
<!-- <form>   -->
<!--   <orth>clem</orth>  -->
<!--   
<pron>klEm</pron>  -->
<!-- </form>  -->
<!-- <form>   -->
<!-- <orth xml:id='O1'>clam</orth>  -->
<!-- </form>  -->
<!-- </form>  -->
<!-- <gramGrp>-->
<!--   
<pos xml:id='G1'>vb</pos>-->
<!-- </gramGrp>   -->
<!-- <form>   -->
<!--   <form type='infl'>   -->
<!-- 
<pers value='3'></pers>  -->
<!-- <num value='sing'></num> -->
<!-- <tns value='pres'></tns> -->
<!-- <orth>clems</orth>   -->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns value='prsp'></tns> -->
<!-- <orth>clemming</orth>-->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns value='pst,pstp'></tns> -->
<!-- <orth>clemmed</orth> -->
<!--   </form>-->
<!-- </form>  -->
<!-- <form>   -->
<!--   <form type='infl'>   -->
<!-- 
<pers value='3'></pers>  -->
<!-- <num value='sing'></num> -->
<!-- <tns value='pres'></tns> -->
<!-- <orth>clams</orth>   -->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns value='prsp'></tns> -->
<!-- <orth>clamming</orth>-->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns value='pst,pstp'></tns> -->
<!-- <orth>clammed</orth> -->
<!--   </form>-->
<!-- </form>  -->
<!-- </rdg>   -->
<!--  -->
<!-- <rdg view='lexical'>   -->
<!-- <form>   -->
<!--   <form> -->
<!-- <orth>clem</orth>-->
<!-- 
<pron>klEm</pron>-->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- 
<pers>3</pers>   -->
<!-- <num>sing</num>  -->
<!-- <tns>pres</tns>  -->
<!-- <orth>clems</orth>   -->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns>prsp</tns>  -->
<!-- <orth>clemming</orth>-->
<!--   </form>-->
<!--   <form type='infl'>   -->
<!-- <tns>pst</tns>   -->
<!-- <tns>pstp</tns>  -->
<!-- <orth>clemmed</orth> -->
<!--   </form>-->
<!-- </form>  -->
<!-- <form>   -->
<!--   <form> -->
<!-- <orth location='o1'>clam</orth>  <! - moved - >-->
<!-- <form type='infl'> -->
<!--   
<pers>3</pers> -->
<!--   <num>sing</num>-->
<!--   <tns>pres</tns>-->
<!--   <orth>clams</orth> -->
<!-- </form>  -->
<!-- <form type='infl'> -->
<!--   <tns>prsp</tns>-->
<!--   <orth>clamming</orth>  -->
<!-- </form>  -->
<!-- <form type='infl'> -->
<!--   <tns>pst</tns> -->
<!--   <tns>pstp</tns>-->
<!--   <orth>clammed</orth>   -->
<!-- </form>  -->
<!--   </form>-->
<!-- </form>  -->
<!-- <gramGrp>-->
<!--
<pos location='g1'>vb</pos>   <! - moved - >-->
<!-- </gramGrp>   -->
<!-- </rdg>   -->
<!--  -->
<!-- </var>   -->
<!--  -->
<!-- <! - rest of the entry  ->   -->
<!--  -->
<!-- </entry> -->
<!--  -->
<!-- ]]>  -->
<!-- </egXML>-->
</p>
</div>
</div>

</div>
<div type="div2" xml:id="DIFR">
<head>Unstructured Entries</head>

<p>The content model for the <gi>entry</gi> element provides an entry
structure suitable for many average dictionaries, as well as many
regular entries in more exotic dictionaries.  However, the structure
of some dictionaries does not allow the restrictions imposed by the
content model for <gi>entry</gi>. To handle these cases, the
<gi>entryFree</gi> and <gi>dictScrap</gi> elements are provided to
support much wider variation in entry structure. The
<gi>dictScrap</gi> element offers less freedom, in that it can only
contain phrase level elements, but it can itself appear at any point
within a dictionary entry where any of the structural components of a
dictionary entry are permitted. As such, it acts as a container for
otherwise anomalous parts of an entry.</p>

<p>The <gi>entryFree</gi> element places no constraints at all upon
the entry: any element defined in this chapter, as well as all the
normal phrase-level and inter-level elements, can
appear anywhere within it. With the <gi>entryFree</gi> element, the
encoder is free to use any element anywhere, as well as to use or omit
grouping elements such as <gi>form</gi>, <gi>gramGrp</gi>, etc. </p>

<p>The <gi>entryFree</gi> element allows the encoding of entries which
violate the structure specified for the <gi>entry</gi> element. For
example, in the following entry from a dictionary already in
electronic form, it is necessary to include a <gi>pron</gi> element
within a <gi>def</gi>. This is not permitted in the content model for
<gi>entry</gi>, but it poses no problem in the <gi>entryFree</gi>
element. <egXML xmlns="http://www.tei-c.org/ns/Examples">&lt;ent
h="demigod"&gt; &lt;hwd&gt;demi|god&lt;/hwd&gt; &lt;pr&gt; &lt;ph&gt;"demIgQd&lt;/ph&gt; &lt;/pr&gt; &lt;hps
ps="n"&gt; &lt;hsn&gt; &lt;def&gt;one who is partly divine and partly human&lt;/def&gt;
&lt;def&gt;(in Gk myth, etc) the son of a god and a mortal woman,
eg&lt;cf&gt;Hercules&lt;/cf&gt; &lt;pr&gt; &lt;ph&gt;"h3:kjUli:z&lt;/ph&gt; &lt;/pr&gt; &lt;/def&gt; &lt;/hsn&gt;
&lt;/hps&gt; &lt;/ent&gt; </egXML>(<ref target="#DIC-OALD">OALD</ref>)
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entryFree>
<form>
<orth>demigod</orth>
<hyph>demi|god</hyph>
<pron>"demIgQd</pron>
</form>
<gramGrp>
<pos>n</pos>
</gramGrp>
<def>one who is partly divine and partly human</def>
<def>(in Gk myth, etc) the son of a god and a mortal woman, eg
<mentioned>Hercules</mentioned></def>
<pron>"h3:kjUli:z</pron>
</entryFree>
</egXML>
</p>
<p>The <gi>entryFree</gi> element also makes it possible to transcribe a dictionary using
only phrase-level (<soCalled>atomic</soCalled>) elements—that is, using no grouping
elements at all. This can be desirable if the encoder wants a completely
<soCalled>flat</soCalled> view, with no indication of or commitment to the association
of one element with another. The following encoding uses no grouping elements, and keeps
all rendition text:<q rend="display">
<hi rend="bold">biryani</hi> or <hi rend="bold">biriani</hi>
<code lang="ipa">(%bIrI"A:nI) </code> any of a variety of Indian dishes…[from
Urdu] <ref target="#DIC-CED">CED</ref> </q>
<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entryFree>
<orth>biryani</orth> or <orth>biriani</orth>
<pron>(%bIrI"A:nI)</pron>
<def>any of a variety of Indian dishes …</def>
<etym>[from <lang>Urdu</lang>]</etym>
</entryFree>
</egXML>
</p>
<p>Here is an alternative way of representing the same structure, this time using
<gi>dictScrap</gi>:<egXML xmlns="http://www.tei-c.org/ns/Examples">
<entry>
<dictScrap>
<orth>biryani</orth> or <orth>biriani</orth>
<pron>(%bIrI"A:nI)</pron>
<def>any of a variety of Indian dishes …</def>
<etym>[from <lang>Urdu</lang>]</etym>
</dictScrap>
</entry>
</egXML>
</p>
</div>
<div><head>The Dictionary Module</head>

<p>The module defined in this chapter makes available the following
components:


<moduleSpec xml:id="DDIBO" ident="dictionaries">
<altIdent type="FPI">Dictionaries</altIdent>
<desc>Dictionaries</desc>
<desc xml:lang="fr">Dictionnaires</desc>
<desc xml:lang="zh-TW">紙本字典</desc>
<desc xml:lang="it">Dizionari a stampa</desc><desc xml:lang="pt">Dicionários impressos</desc><desc xml:lang="ja">辞書モジュール</desc></moduleSpec>
The selection and combination of modules to form a TEI schema is described in
<ptr target="#STIN"/>.

</p>
</div>

</div>
