<!--* $Id: p2di.odd,v 1.9 1998/01/31 19:50:52 tei Exp $
    * -->
<!--*
    * $Log: p2di.odd,v $
    * Revision 1.9  1998/01/31 19:50:52  tei
    * Change system 'tei2.dtd' to public identifier
    * fix log keyword (if not already fixed)
    * normalize the sgml
    *
    * Revision 1.8  94/04/01  16:21:35  msmcq
    * correct typo in bibl ref for Ide et al.
    *
    * Revision 1.7  1994/03/27  16:29:18  lou
    * semi-hemi-demi final check
    *
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    *
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    *
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    *
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    * -->
<!-- Revisions:                                               -->
<!-- 94-03-29 : MSM : correct typo in bibl entry for ide et al. -->
<!-- Revisions:                                               -->
<!-- 27 mar: LB checked all egs and terms -->
<!-- 94-01-12 : MSM : stylistic fixes                         -->
<!-- 94-01-12 : MSM : minor stylistic cleanups                -->
<!-- 94-01-09 : MSM : minor stylistic changes for P3          -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-03-08 : MSM : eliminate null character                -->
<!-- 93-03-08 : MSM : add entity refs for subsections         -->
<div1 id="di" n="12"><head>Print Dictionaries</head>

<p>This chapter defines a base tag set for encoding human-oriented
monolingual and polyglot dictionaries (as opposed to computational
lexica, which are intended for use by language-processing software).
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 --- e.g. CD-ROM dictionaries.

<!-- <note place=foot>The primary responsibility for thischapter -->
<!-- was borne by TEI work group AI5 (print dictionaries); a list -->
<!-- of members is given in the front matter.  The text was -->
<!-- originally drafted by Nancy Ide and Jean Veronis; examples -->
<!-- and revisions were provided by other members of the work -->
<!-- group, including Nicoletta Calzolari, John Fought, and Carol -->
<!-- Van Ess-Dykema.</note> --></p>

<p>Both typographically and structurally, dictionaries are extremely
complex.  In addition, dictionaries interest 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.
<note place="foot">We refer the reader to previous and current discussions
of a common format for encoding dictionaries.  For example,

Robert A. Amsler and Frank W. Tompa, <title>An SGML-Based Standard for
English Monolingual Dictionaries,</title> in <title>Information in
Text:  Fourth Annual Conference of the U[niversity of] W[aterloo] Centre
for the New Oxford English Dictionary</title> October 26-28, 1988,
Waterloo, Canada, pp. 61-79;

Nicoletta Calzolari et al., <title>Computational Model of the
Dictionary Entry:  Preliminary Report,</title> Acquilex:  Esprit Basic
Research Action No. 3030, Six-Month Deliverable, Pisa, April 1990;

John Fought and Carol Van Ess-Dykema, <title>Toward an SGML Document
Type Definition for Bilingual Dictionaries,</title> TEI working paper
TEI AIW20 (available from the TEI);

Nancy Ide and Jean Veronis, <title>Encoding Print
Dictionaries</title>, <title>Computers and the Humanities</title>
(special TEI issue --- to appear);

Nancy Ide, Jacques Le Maitre, and Jean Veronis, <title>Outline of a
Model for Lexical Databases,</title> (Information Processing and
Management, 29, 2, 159-186, 1993);

Nancy Ide, Jean Veronis, Susan Warwick- Armstrong, Nicoletta Calzolari,
<title>Principles for Encoding machine readable
dictionaries</title>, <title>Proceedings of the Fifth EURALEX
International Congress, EURALEX'92</title> (to appear), University of
Tempere, Finland;

and

The DANLEX Group, <title>Descriptive tools for electronic processing
of dictionary data,</title> in <title>Lexicographica, Series
Maior</title> (T&uuml;bingen:  Niemeyer, 1987).</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; ideally, a set of encoding
guidelines should capture these structural principles.  We therefore
define two distinct elements for dictionary entries, one
(<gi>entry</gi>) which captures the regularities of most conventional
dictionary entries, and a second (<gi>entryFree</gi>) which uses the
same elements, but allows them to combine much more freely.  It is
recommended that <gi>entry</gi> be used in preference to
<gi>entryFree</gi> wherever the structure of the entry allows it.

<!-- omitted sentence as redundant. -msm                      -->
<!-- The flexible but unconstrained encoding allowed by       -->
<!-- <gi>entryFree</gi> should be used parsimoniously.        -->

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>Whichever view is adopted, a parameter entity
<ident type="pe">TEI.dictionaries</ident> must be declared within the
document type subset of any document using this base tag set. This
should have the value <code>INCLUDE</code>, as
further described in section <ptr target="STin">. A document using this
base tag set and no other additional tag sets will thus begin as
follows:

<eg>
<![ CDATA [
 <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!ENTITY % TEI.dictionaries 'INCLUDE' >
 ]>
]]>
</eg>

<!-- $Id: p2dibo.odd,v 1.9 1998/01/31 17:17:18 tei Exp $ -->
<!--*
    * $Log: p2dibo.odd,v $
    * Revision 1.9  1998/01/31 17:17:18  tei
    * Fix log keyword
    *
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.7  1994/04/01  16:21:35  msmcq
    * protect teistr reference in marked section, define dimix
    *
    * Revision 1.6  1994/03/27  16:29:31  lou
    * *** empty log message ***
    *
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    *
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    *
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    *
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    *-->
<!-- Revisions:                                               -->
<!-- 4 Jan 98 : LB : add "especially" per 1996-05-13 CMSMCQ -->
<!-- 94-03-31 : MSM : protect teistr invocation               -->
<!-- 94-03-31 : MSM : define dimix                            -->
<!-- 94-01-15 : MSM : change comment in dtd frag              -->
<!-- 94-01-13 : MSM : correct example:  body not GI body      -->
<!-- 94-01-12 : MSM : suppress duplicated inclusion of tpde   -->
<!-- 94-01-12 : MSM : minor stylistic fixes                   -->
<!-- 94-01-12 : MSM : suppress call to dummy dtdfrag for notes -->
<!-- 94-01-12 : MSM : clean reference to tei.structure.dtd    -->
<!-- 94-01-12 : MSM : correct dtdFrag id dDIhw                -->
<!-- 94-01-09 : MSM : work at cleaning up dtd fragments       -->
<!-- 94-01-08 : MSM : add commentary to examples              -->
<!-- 93-10-19 : MSM : preliminary rough cleanup               -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-06-04 : MSM : call class compdict not dicomp          -->
<!-- 93-03-11 : MSM : make taglists, dtdfrags                 -->
<!-- 93-03-08 : MSM : correct mkd sectn openings l 81 108     -->

<div2 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; the base tag set for
dictionaries uses the same front-matter and back-matter elements as
other TEI base tag sets; these are documented in chapter <ptr
target=DS>.  In addition, dictionaries define the elements
<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>The following tags should be used to mark the gross structure of a
printed dictionary; the dictionary-specific tags are discussed further
in the following section.

<list type=gloss>
<label><gi>text</gi></label>
<item>contains a single text of any kind, whether unitary or

composite, for example a poem or drama, a collection of 
essays, a novel,
a dictionary, or a corpus sample.</item>
<label><gi>front</gi></label>
<item>contains any prefatory matter (headers,
title page, 
prefaces, dedications, etc.)
found before the start of a 
text proper.</item>
<label><gi>body</gi></label>
<item>contains the whole body of a single unitary
text, 
excluding any front or back
matter.</item>
<label><gi>back</gi></label>
<item>contains any appendixes, etc. following the main part of a

text.</item>
<label><gi>div</gi></label>
<item>contains a subdivision of the front, body, or back of a 
text.</item>
<label><gi>div0</gi></label>
<item>contains the largest possible subdivision of the body
of a 
text.</item>
<label><gi>div1</gi></label>
<item>contains a first-level subdivision of the front, body, or 
back
of a text (the largest, if
<gi>div0</gi> is not 
used, the second largest if it is).</item>
<label><gi>entry</gi></label>
<item>contains a reasonably well-structured dictionary entry.</item>
<label><gi>entryFree</gi></label>
<item>contains a dictionary entry which does not necessarily 
conform
to the constraints imposed by the <gi>entry</gi> 
element.</item>
<label><gi>superentry</gi></label>
<item>groups successive entries for a set of homographs.</item>
</list>


The text-division elements <gi>div2</gi> through <gi>div7</gi> may also
be used, as described in chapter <ptr target=DS>.

<p>As members of the class <ident type=class>entries</ident>,
<gi>entry</gi> and <gi>entryFree</gi> share the following attributes:

<list type=gloss>
<label><att>type</att></label>
<item>indicates type of entry, in dictionaries with multiple 
types.
Suggested values include:
<list type=gloss>
<label><term>foreign</term></label>
<item>an entry for a <socalled>foreign</socalled> word in a 
monolingual dictionary.</item>
<label><term>abbr</term></label>
<item>an entry for an abbreviation.</item>
<label><term>supplemental</term></label>
<item>a supplemental entry (for use in dictionaries which issue 
supplements to their main work in which they include 
updated information about entries).</item>
<label><term>affix</term></label>
<item>an entry for a prefix, infix, or suffix.</item>
<label><term>xref</term></label>
<item>a reduced entry whose only function is to point to another 
main entry (e.g. for forms of an irregular verb or for 
variant spellings: <mentioned>was</mentioned> pointing to 
<mentioned>be</mentioned>, or <mentioned>esthete</mentioned> to 
<mentioned>aesthete</mentioned>).</item>
<label><term>main</term></label>
<item>a main entry (default).</item>
<label><term>hom</term></label>
<item>a homograph with a separate entry.</item>
</list></item>
<label><att>key</att></label>
<item>contains a (sortable) character sequence reflecting the 
entry's alphabetical position in the printed dictionary.</item>
</list>

<p>The front and back matter of a dictionary may well contain
specialized material like lists of common and proper nouns, grammatical
tables, gazetteers, a <soCalled>guide to the use of the
dictionary</soCalled>, etc.  These may be tagged as elements defined in
the core tag set (chapter <ptr target=CO>) or as specialized dictionary
elements as defined in this chapter.

<p>The <gi>body</gi> element consists of a set of <term>entries</term>,
optionally grouped into one or several <gi>div</gi>, <gi>div0</gi>, or
<gi>div1</gi> elements.  These text divisions might correspond, for
example, to sections for different languages in bilingual
dictionaries, sections for different letters of the alphabet, etc.<note
place=foot>It is unlikely that many conventional dictionaries will
require smaller divisions, but all the usual division elements
<gi>div2</gi> through <gi>div7</gi> may be used.</note> In print
dictionaries, 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> 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>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> should 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>A sort key, given in the <att>key</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>The body of a bilingual dictionary with two parts will thus have an
overall structure resembling the following:

<eg>
<![ CDATA [
<body>
  <div0 type='dictionary'>
    <!-- English-French -->
    <entry>...</entry>
    <entry>...</entry>
    <entry>...</entry>
  <!-- ... -->
  </div0>
  <div0>
    <!-- French-English -->
    <entry>...</entry>
    <entry>...</entry>
    <entry>...</entry>
  <!-- ... -->
  </div0>
</body>
]]>
</eg>

<p>A dictionary with no internal divisions might have a structure like
the following; a <gi>superEntry</gi> is shown grouping two homograph
entries.

<eg>
<![ CDATA [
<body>
  <entry>...</entry>
  <entry>...</entry>
  <!-- ... -->
  <superEntry>
    <entry type=hom n='1'>...</entry>
    <entry type=hom n='2'>...</entry>
  </superEntry>
  <!-- ... -->
</body>
]]>
</eg>

<p>The base tag set for dictionaries is contained in the files <ident
type=file>teidict2.ent</ident> and <ident
type=file>teidict2.dtd</ident>.  The first of these defines the class
<ident type=class>comp.dictionaries</ident>, so that the generic
text-division elements <gi>div</gi>, <gi>div0</gi>, <gi>div1</gi>,
etc. can contain <gi>entry</gi> elements:

<eg id=ddients>
<![ CDATA [
<!-- 12.1:  Element classes for dictionary base               -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->


<!-- First we define attributes available on all the          -->
<!-- elements in this tag set.                                -->

<!-- ... declarations from section 12.5.4                     -->
<!--     (Attributes for dictionary work)                     -->
<!--     go here ...                                          -->

<!-- Next we define comp.dictionaries, which will be used in  -->
<!-- the declaration of component, within file TEI2.DTD.      -->

<!ENTITY % x.comp.dictionaries ''                               >
<!ENTITY % m.comp.dictionaries '%x.comp.dictionaries entry | 
           entryFree | superentry'                              >
<!ENTITY % mix.dictionaries '| %m.comp.dictionaries'            >

<!-- Next, we declare some specialized element classes, used  -->
<!-- in various content models in the dictionary tag set.     -->

<!ENTITY % a.entries '
          key                CDATA               #IMPLIED
          type               CDATA               "main"'        >

<!-- ... declarations from section 12.2.2                     -->
<!--  (Class for top-level structure of dictionary entries)   -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.1                     -->
<!--     (Classes for morphological and form information)     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.2                     -->
<!--     (Elements for grammatical information)               -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.4                       -->
<!--     (Classes for headword references)                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.6                       -->
<!--     (Model class for unstructured dictionary entries)    -->
<!--     go here ...                                          -->
]]>
</eg>


The dictionary-specific elements are all declared in the file
<ident type=file>teidict2.dtd</ident>, which has the following
overall structure.

<eg id=ddibo>
<![ CDATA [
<!-- 12.1:  Base tag set for printed dictionaries             -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->

<!-- First we embed the default text structure.               -->

<![ %TEI.singleBase [
<!ENTITY % TEI.structure.dtd system 'teistr2.dtd'               >
%TEI.structure.dtd;
]]&nil;>


<!-- Now we define the dictionary-specific material.          -->

<!-- ... declarations from section 12.2.1                     -->
<!--     (Dictionary entries and their structure)             -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.1                     -->
<!--     (The form group)                                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.2                     -->
<!--     (The gram group)                                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.3.1                   -->
<!--     (Definition text)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.3.2                   -->
<!--     (Translation information)                            -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.4                     -->
<!--     (Etymologies)                                        -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.5.1                   -->
<!--     (Examples and citations)                             -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.5.2                   -->
<!--     (Usage information)                                  -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.5.3                   -->
<!--     (Cross References)                                   -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.3.6                     -->
<!--     (Related entries)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 12.4                       -->
<!--     (Headword references)                                -->
<!--     go here ...                                          -->
]]>
</eg>



<!-- $Id: p2dien.odd,v 1.7 1998/01/28 11:09:58 cmsmcq Exp $ -->
<!-- $Log: p2dien.odd,v $
# Revision 1.7  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.6  1994/03/27  16:29:37  lou
# *** empty log message ***
#
# Revision 1.5  1994/03/07  15:19:03  lou
# fix ^Z
#
# Revision 1.4  1994/03/07  14:44:05  lou
# apply typos etc. noted by DTB et al.
#
# Revision 1.3  1994/01/15  20:45:31  msmcq
# cmsmcq revision for P3
# see comments for details
#
# Revision 1.2  1994/01/04  19:38:25  msmcq
# first cut at DI revisions
# -->
<!-- Revisions:                                               -->
<!-- 7 jan 98 : LB : fix typos from msm -->
<!-- 94-01-15 : MSM : add biblio info for WNC                 -->
<!-- 94-01-14 : MSM : explicit end-tag in a SENSE             -->
<!-- 94-01-13 : MSM : in EGs, replace & in PRONs with &amp    -->
<!-- 94-01-13 : MSM : add supentry to dtd frag                -->
<!-- 94-01-12 : MSM : minor stylistic fixes                   -->
<!-- 94-01-12 : MSM : trans not transl, dieg not eg, diengp   -->
<!-- 94-01-08 : MSM : attempt to clarify structure,           -->
<!--                  define classes clearly,                 -->
<!--                  clean up dtd fragments,                 -->
<!--                  weed out expendible examples,           -->
<!--                  explain significance of examples        -->
<!-- 94-01-05 : MSM : in pronunciation, replace & by amp      -->
<!-- 93-10-19 : MSM : quick rough cleanup                     -->
<!-- 93-10-19 : MSM : change hn attribute to n                -->
<!-- 93-10-19 : MSM : change sn attribute to n                -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-04-12 : MSM : rename gram as digram                   -->
<!-- 93-03-11 : MSM : make taglists and dtdfrags              -->
<!-- 93-03-08 : MSM : change C&R to C/R (no entity)           -->

<div2 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 entries, 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>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>.

<div3 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 part-of-speech homographs.  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.  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>.

<list type=gloss>
<label><gi>entry</gi></label>
<item>contains a reasonably well-structured dictionary entry.</item>
<label><gi>entryFree</gi></label>
<item>contains a dictionary entry which does not necessarily 
conform
to the constraints imposed by the <gi>entry</gi> 
element.</item>
<label><gi>hom</gi></label>
<item>groups information relating to one homograph within an

<gi>entry</gi>.</item>
<label><gi>sense</gi></label>
<item>groups together all information relating to one word sense 
in a
dictionary <gi>entry</gi> (definitions, examples, 
translation
equivalents, etc.)
Attributes include:
<list type=gloss>
<label><att>level</att></label>
<item>gives the nesting depth of this sense.</item>
</list>
</item>
</list>


<p>For example, an entry with two senses will have the following
structure:

<eg>
<![ CDATA [
<entry>
  <!-- ... information common to both senses -->
  <sense n='1'>
     <!-- ... sense number 1 -->
  </sense>
  <sense n='2'>
     <!-- ... sense number 2 -->
  </sense>
</entry>
]]>
</eg>

<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:

<eg>
<![ CDATA [
<entry>
  <!-- ... information common to both homographs, if any ... -->
  <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>
]]>
</eg>

In some dictionaries, homographs typically receive separate entries; in
such a case, as noted in section <ptr target=DIbo>, the two homographs
may be treated as entries, optionally grouped by a superentry:

<eg>
<![ CDATA [
<superEntry>
<!-- ... form information common to both
     homographs, if any ... -->
<entry n='1'>
  <sense n='1'>...</sense>
  <sense n='2'>...</sense>
</entry>
<entry n='2'>
  <sense n='1'>
    <sense n='a'>...</sense>
    <sense n='b'>...</sense>
  </sense>
  <sense n='2'>...</sense>
  <sense n='3'>...</sense>
</entry>
</superEntry>
]]>
</eg>

<p>The hierarchical levels of dictionary entries are declared as shown
in the following DTD fragment.  As may be seen, 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).

<!-- Note that elements of class <term>formptrs</term> can    -->
<!-- appear anywhere (see section <ptr target=DIhw>.         -->


<eg id=ddien>
<![ CDATA [
<!-- 12.2.1:  Dictionary entries and their structure          -->
<!ELEMENT superentry    - O  (form?, entry+)                    >
<!ATTLIST superentry         %a.global;
                             %a.entries;                        >
<!ELEMENT entry         - O  (hom | sense | 
                             %m.dictionaryTopLevel)+ 
                                                  +(anchor)     >
<!ATTLIST entry              %a.global;
                             %a.entries;                        >
<!ELEMENT entryFree     - O  (#PCDATA)           
                                                 
                                                 +(%m.dictionaryParts
                                                 | %m.phrase | 
                                                 %m.inter)      >
<!ATTLIST entryFree          %a.global;
                             %a.dictionaries;
                             %a.entries;                        >
<!ELEMENT hom           - O  (sense | %m.dictionaryTopLevel)* 
                                                    -(entry)    >
<!ATTLIST hom                %a.global;
                             %a.dictionaries;                   >
<!ELEMENT sense         - -  (#PCDATA | sense | 
                             %m.dictionaryTopLevel; | 
                             %m.phrase;)*                       >
<!ATTLIST sense              %a.global;
                             %a.dictionaries;
          level              NUMBER              #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div3 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 type=bullets>
<item>information about the form of the word treated (orthography,
pronunciation, hyphenation, etc.)
<item>grammatical information (part of speech, grammatical
sub-categorization, etc.)
<item>definitions or translations into another language
<item>etymology
<item>examples
<item>usage information
<item>cross-references to other entries
<item>notes
<item>entries (often of reduced form) for related words,
typically called <term>related entries</term>
</list>

Any of the hierarchical levels (<gi>entry</gi>, <gi>entryFree</gi>,
<gi>hom</gi>, <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>The following elements are used to encode these top-level
constituents:
<list type=gloss>
<label><gi>form</gi></label>
<item>groups all the information on the written and spoken forms 
of one
headword.</item>
<label><gi>gramGrp</gi></label>
<item>groups morpho-syntactic information about a lexical item, 
e.g.
<gi>pos</gi>, <gi>gen</gi>, <gi>number</gi>, 
<gi>case</gi>, or
<gi>itype</gi> (inflectional class).</item>
<label><gi>def</gi></label>
<item>contains definition text in a dictionary entry.</item>
<label><gi>trans</gi></label>
<item>contains translation text and related information (within 
an
entry in a multilingual dictionary).</item>
<label><gi>eg</gi></label>
<item>(in a dictionary) contains an example text containing at 
least one
occurrence of the word form, used in the sense 
being described; examples
may be quoted from (named) 
authors or contrived.</item>
<label><gi>usg</gi></label>
<item>contains usage information in a dictionary entry.</item>
<label><gi>xr</gi></label>
<item>contains a phrase, sentence, or icon referring the reader 
to
some other location in this or another text.</item>
<label><gi>etym</gi></label>
<item>encloses the etymological information in a dictionary 
entry.</item>
<label><gi>re</gi></label>
<item>contains a dictionary entry for a lexical item related to 
the
headword, such as a compound phrase or derived form, 
embedded inside a
larger entry.</item>
<label><gi>note</gi></label>
<item>contains a note or annotation.</item>
</list>


<p>In a simple entry with no internal hierarchy, all top-level
constituents appear at the <gi>entry</gi> level.

<note place=foot>

Each example taken from a real dictionary indicates its source using
the following abbreviations for dictionary names:

<list type=gloss>

<label>C/R <item>Beryl T. Atkins et al., <title>Collins Robert
French-English English-French Dictionary</title> (London:
Collins, 1978, rpt. 1983)

<label>CED   <item>Collins English Dictionary

<label>CP    <item>Collins Pocket

<label>DNT   <item><title>Le Dictionnaire de Notre Temps 1990</title>,
ed. Franc,,oise Guerard (Paris:  Hachette, 1990).

<label>LDOCE <item>Longman Dictionary of Contemporary English

<label>NPEG  <item><title>The New Penguin English Dictionary</title>
(London:  Penguin, 1986, rpt. 1987).

<label>OALD  <item><title>Oxford Advanced Learner's Dictionary of
Current English</title>, ed. A. S. Hornby with A. P. Cowie and A. C.
Gimson ([Oxford]:  Oxford University Press, 1974).

<label>PLC   <item><title>Petit Larousse en Couleurs</title> (Paris:
Larousse, 1990).

<label>PLI   <item><title>Peque&ntilde;o Larousse Illustrado</title> por
Ramo''n Garci''a-Pelayo y Gross (Buenos Aires, Me''xico, Paris:
Ediciones Larousse, 1964).

<label>PR    <item>Le Petit Robert

<label>SSSE <item><title>Simon and Schuster's International Dictionary
English/Spanish Spanish/English</title> ed. Tana de G&aacute;mez (New
York:  Simon and Schuster, 1973).

<label>W7    <item>Webster's 7th Collegiate

<label>WNC   <item><title>Webster's New Collegiate Dictionary</title>
(Springfield, Mass.:  G. & C. Merriam Co., 1975).

</list>

To simplify the electronic presentation of this document on systems with
limited character sets, many of the pronunciations are presented using
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 with
<code>|</code>, regardless of their rendition in the source text.
</note>

<q rend=display> <hi rend=bold>com.peti.tor</hi>
<code>/k@m"petit@(r)/</code> n person who competes. [OALD] </q>

<eg>
<![ CDATA [
<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>
]]>
</eg>

For the elements which appear within the <gi>form</gi> and <gi>gramGrp</gi>
elements of this example, see below, section <ptr target=DItpfo>, and
section <ptr target=DItpgr>.

<p>As mentioned above, 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>trans</gi>, which appear at the
<gi>sense</gi> level when several senses or translations exist:

<q rend=display> <hi rend=bold>disproof</hi> <code>
(dIs"pru:f)</code> n. 1. facts that disprove something. 2. the act of
disproving. [CED] </q>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>disproof</orth>
    <pron>dIs"pru:f</pron>
  </form>
  <gramGrp><pos>n</></gramGrp>
  <sense n='1'><def>facts that disprove something.</def></sense>
  <sense n='2'><def>the act of disproving.</def></sense>
</entry>
]]>
</eg>

<p>In the following example, <gi>gramGrp</gi> is used to distinguish two
homographs:

<q rend=display> <hi rend=bold>bray</hi> <code>/breI/
</code> n cry of an ass; sound of a trumpet. &squf; vt [VP2A] make a
cry or sound of this kind.  [OALD] </q>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>bray</orth>
    <pron>breI</pron>
  </form>
  <hom>
    <gramGrp><pos>n</pos></gramGrp>
    <def>cry of an ass; sound of a trumpet.</def>
  </hom>
  <hom>
    <gramGrp>
      <pos>vt</pos>
      <subc>VP2A</subc>
    </gramGrp>
    <def>make a cry or sound of this kind.</def>
  </hom>
</entry>
]]>
</eg>

<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>/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.
[OALD] </q>

<eg>
<![ CDATA [
<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>
]]>
</eg>

<!-- 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>

<eg>
<![ CDATA [
<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>

]]>
</eg>
-->

<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>/@"b&amp;nd@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: The
people were so excited that they jumped and shouted with abandon / in
gay abandon.  [LDOCE] </q>

<eg>
<![ CDATA [
<superEntry>
  <form>
    <orth>abandon</orth>
    <hyph>a|ban|don</hyph>
    <pron>@"b&amp;nd@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'>
      <!-- ... -->
    </sense>
  </entry>
  <entry n='2'>
    <gramGrp> <pos>n/pos> <subc>U</subc> </gramGrp>
    <def>the state when one's feelings and actions are
            uncontrolled; freedom from control</def>
    <!-- ... -->
  </entry>
</superEntry>
]]>
</eg>

<p>The class of top-level constituents for dictionary entries is defined
by the following DTD fragment:

<eg id=dedien>
<![ CDATA [
<!-- 12.2.2: Class for top-level structure of dictionary      -->
<!-- entries                                                  -->
<!ENTITY % x.dictionaryTopLevel ''                              >
<!ENTITY % m.dictionaryTopLevel '%x.dictionaryTopLevel def | eg 
           | etym | form | gramGrp | note | re | trans | usg | 
           xr'                                                  >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<p>The individual constituents are declared below, each in the section
which documents it in more detail.


<!-- $Id: p2ditp.odd,v 1.11 1999/05/18 13:36:15 tei Exp $ -->
<!--*
    * $Log: p2ditp.odd,v $
    * Revision 1.11  1999/05/18 13:36:15  tei
    * version control headers screwed up
    *
    *  1.10  1999/05/18 10:37:51  tei
    *  <p> from within quoted example
    *  1.9  1998/01/28 11:09:58  cmsmcq
    *  changes of January 1998
    *  1.8  1994/04/07  23:55:41  msmcq
    * some Script-motivated line breaks
    *
    * Revision 1.7  1994/03/27  16:29:49  lou
    * *** empty log message ***
    *
    * Revision 1.6  1994/03/07  15:19:03  lou
    * fix ^Z
    *
    * Revision 1.5  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    *
    * Revision 1.4  1994/02/07  20:39:03  msmcq
    * msmcq cumulation end January 1994
    *
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    *
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    * -->
<!-- Revisions:                                               -->
<!-- 12 jan 98 : LB : add missing </sense> in Corneille eg -->
<!-- 7 jan 98 : LB : fix typos from MSM -->
<!-- 94-04-07 : MSM : rebreak some lines (Script problem)     -->
<!-- 94-02-01 : MSM : suppress triangle entity                -->
<!-- 94-01-15 : MSM : miscellaneous minor typos               -->
<!-- 94-01-15 : MSM : change dtdfrag title                    -->
<!-- 94-01-14 : MSM : correct typo in xref to madrigal.1      -->
<!-- 94-01-13 : MSM : supply explicit /sense in EGs           -->
<!-- 94-01-13 : MSM : replace ampersands in PRONs with &amp   -->
<!-- 94-01-12 : MSM : suppress duplicated declaration of gram -->
<!-- 94-01-12 : MSM : stylistic fixes                         -->
<!-- 94-01-12 : MSM : DIeg not EG, add entity dtdfrag for graminfo -->
<!-- 94-01-12 : MSM : number not num                          -->
<!-- 94-01-11 : MSM : resume work with gram section, complete -->
<!-- 94-01-09 : MSM : reorder and attempt to clarify          -->
<!-- 94-01-05 : MSM : fix entity typos, bad comment           -->
<!-- 94-01-05 : MSM : replace hi with hilited, & with &amp    -->
<!-- 94-01-05 : MSM : replace ital, bold with hi              -->
<!-- 93-10-19 : MSM : rename tgt as te                        -->
<!-- 93-10-19 : MSM : change sn attribute to n                -->
<!-- 93-10-19 : MSM : change hn attribute to n                -->
<!-- 93-10-19 : MSM : clean examples                          -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-04-12 : MSM : rename gram as digram                   -->
<!-- 93-04-12 : MSM : delete N att on divs                    -->
<!-- 93-03-08 : MSM : eliminate funny character (check for lost data!) -->

<div2 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 type=bullets>

<item>the <gi>form</gi> element, which groups orthographic information
and pronunciations, is described in section <ptr target=DItpfo>

<item>the <gi>gramGrp</gi> element, which groups elements for the
grammatical characterization of the headword, is described in section
<ptr target=DItpgr>

<item>the <gi>def</gi> and <gi>trans</gi> elements, which describe the
meaning of the headword, are described in section <ptr target=DItpse>

<item>the <gi>etym</gi> element and its special phrase-level elements
are documented in section <ptr target=DItpet>

<item>the <gi>eg</gi>, <gi>usg</gi>, <gi>lbl</gi>, <gi>xr</gi>, and
<gi>note</gi> elements are described in section <ptr target=DItpmi>

<item>the <gi>re</gi> element, which marks nested entries for related
words, is described in section <ptr target=DItpfo>

</list>

<div3 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, 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>The following elements should be used to encode this information:
the <gi>form</gi> element groups one or more occurrences of any of the
others; it can also be recursively nested to reflect more complex
sub-grouping of information about word form(s), as shown in the
examples.

<list type=gloss>
<label><gi>form</gi></label>
<item>groups all the information on the written and spoken forms 
of one
headword.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies form as simple, compound, etc.
Suggested values include:
<list type=gloss>
<label><term>inflected</term></label>
<item>word in other than usual dictionary form</item>
<label><term>lemma</term></label>
<item>the headword itself</item>
<label><term>phrase</term></label>
<item>multiple-word lexical item</item>
<label><term>simple</term></label>
<item>single free lexical item</item>
<label><term>variant</term></label>
<item>a variant form</item>
<label><term>derivative</term></label>
<item>word derived from headword</item>
<label><term>compound</term></label>
<item>word formed from simple lexical items</item>
</list></item>
</list>
</item>
<label><gi>orth</gi></label>
<item>gives the orthographic form of a dictionary headword.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>gives the type of spelling.</item>
<label><att>extent</att></label>
<item>gives the extent of the orthographic information provided.
Sample values include:
<list type=gloss>
<label><term>suff</term></label>
<item>suffix</item>
<label><term>pref</term></label>
<item>prefix</item>
<label><term>part</term></label>
<item>partial</item>
<label><term>full</term></label>
<item>full form</item>
</list></item>
</list>
</item>
<label><gi>pron</gi></label>
<item>contains the pronunciation(s) of the word.
Attributes include:
<list type=gloss>
<label><att>extent</att></label>
<item>indicates whether the pronunciation is for whole word or 
part.
Sample values include:
<list type=gloss>
<label><term>suff</term></label>
<item>suffix</item>
<label><term>pref</term></label>
<item>prefix</item>
<label><term>part</term></label>
<item>partial</item>
<label><term>full</term></label>
<item>full form</item>
</list></item>
</list>
</item>
<label><gi>hyph</gi></label>
<item>contains a hyphenated form of a dictionary headword, or

hyphenation information in some other form.</item>
<label><gi>syll</gi></label>
<item>contains the syllabification of the headword.</item>
<label><gi>stress</gi></label>
<item>contains the stress pattern for a dictionary headword, if 
given
separately.</item>
<label><gi>lbl</gi></label>
<item>in dictionaries, contains a label for a form, example,

translation, or other piece of information, e.g. 
<q>abbreviation
for</q>, <q>contraction of</q>, 
<q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, 
etc.</item>
</list>


<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:

<list type=gloss>
<label><gi>gram</gi></label>
<item>within an entry in a dictionary or a terminological data 
file,
contains grammatical information relating to a term, 
word, or form.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the grammatical information given according to 
some convenient typology --- in the case of terminological 
information, preferably the dictionary of data element 
types specified in ISO WD 12 620.
Sample values include:
<list type=gloss>
<label><term>pos</term></label>
<item>part of speech (any of the word classes to which a word may 
be assigned in a given language, based on form, meaning, or 
a combination of features, e.g. noun, verb, adjective, 
etc.)</item>
<label><term>num</term></label>
<item>number (e.g. singular, plural, dual, ...)</item>
<label><term>proper</term></label>
<item>proper noun or common noun</item>
<label><term>gen</term></label>
<item>gender (formal classification by which nouns and pronouns, 
and often accompanying modifiers, are grouped and 
inflected, or changed in form, so as to control certain 
syntactic relationships)</item>
<label><term>animate</term></label>
<item>animate or inanimate</item>
</list></item>
</list>
</item>
<label><gi>gen</gi></label>
<item>identifies the morphological gender of a lexical item, as 
given in
the dictionary.</item>
<label><gi>number</gi></label>
<item>indicates grammatical number associated with a form, as 
given
in a dictionary.</item>
<label><gi>case</gi></label>
<item>contains grammatical case information given by a dictionary 
for
a given form.</item>
<label><gi>per</gi></label>
<item>contains an indication of the grammatical person (1st, 2d, 
3d,
etc.) associated with a given inflected form in a 
dictionary.</item>
<label><gi>tns</gi></label>
<item>indicates the grammatical tense associated with a given 
inflected
form in a dictionary.</item>
<label><gi>mood</gi></label>
<item>contains information about the grammatical mood of verbs 
(e.g.
<q>indicative</q>, <q>subjunctive</q>, 
<q>imperative</q>)</item>
<label><gi>itype</gi></label>
<item>indicates the inflectional class associated with a lexical 
item.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the type of indicator used to specify the 
inflection class, when it is necessary to distinguish 
between the usual abbreviated indications (e.g. <q>inv</q>) 
and other kinds of indicators, such as special codes 
referring to conjugation patterns, etc.
Sample values include:
<list type=gloss>
<label><term>abbrev</term></label>
<item>abbreviated indicator</item>
<label><term>verb table</term></label>
<item>coded reference to a table of verbs</item>
</list></item>
</list>
</item>
</list>


Of these, the <gi>gram</gi> element is most general, and all of the
others are synonymous with <gi>gram</gi> elements with appropriate
values (<code>gen, number, case</code>, etc.) for the
<att>type</att> attribute.

<p>Different dictionaries use different means to mark hyphenation,
syllabification, and stress, and they often use special symbols (e.g.,
the <soCalled>middle dot</soCalled> for hyphenation).  Many of these
symbols are defined as entities within standard ISO entity sets (see
chapter <ptr target=XW>; others may require the definition of new
entities.  For pronunciation transcriptions, the user is referred to the
discussion of TEI definitions for the symbols of the International
Phonetic Alphabet, in chapter <ptr target=XW>.  When alternative or
additional symbols are used in the encoding, the conventions used should
be fully documented in the header.  (This may occur, for instance, in
cases where pronunciations are not given at all in the original, but are
added in the encoded text, when a simplified pronunciation transcription
is used, when pronunciations in several dictionaries are normalized to a
single scheme, or when pronunciation symbols are transliterated into a
standard character set like ISO 646, as in the scheme used by the OALD
and by some examples here.)

<p>Among the ISO entity sets most likely to be useful in the
transcription of form information are:
<list type=bullets>
<item>ISOlat1 (Latin characters and diacritics for Western European
languages)
<item>ISOlat2 (Eastern European languages)
<item>ISOpub (miscellaneous publishing and special symbols)
<item>ISOnum (numeric and related symbols)
</list>
<!-- list useful ISO entity sets here:  ISOpub, ISOnum,       -->
<!-- ISOlat1, ISOlat2                                         -->

<p>In the simplest case, nothing is given but the orthography:

<eg>
<![ CDATA [
<form>
  <orth>doom-laden</orth>
</form>
<!-- [CED] -->
]]>
</eg>

<p>Often, however, pronunciation is given.

<q rend=display>
<hi rend=bold>soucoupe</hi> [sukup] ...     [DNT]
</q>

<eg>
<![ CDATA [
<form>
  <orth>soucoupe</orth>
  <pron>sukup</pron>
</form>
]]>
</eg>

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

<!-- supererogatory (msm)
<q rend=display>
gov.ern.ment <code>/"gVv@nm@nt/ </code> ...  [OALD]
</q>

<eg>
<![ CDATA [
<form>
   <orth>government</orth>
   <hyph>gov|ern|ment</hyph>
   <pron>"gVv@nm@nt</pron>
</form>
]]>
</eg>
-->

<p>This example splits orthography and hyphenation, and adds
syllabification because it differs from hyphenation:

<q rend=display>
<hi rend=bold>ar.ea</hi>  ...  [W7]
</q>

<eg>
<![ CDATA [
<form>
   <orth>area</orth>
   <hyph>ar|ea</hyph>
   <syll>ar|e|a</syll>
</form>
]]>
</eg>

<!--
<q rend=display>
<hi rend=bold>alternating current</hi>  <code>/,....'../
</code>  ... [LDOCE]
</q>

<eg>
<![ CDATA [
<form>
   <orth>alternating current</orth>
   <stress>,....'..</stress>
</form>
]]>
</eg>
-->

<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 ...   [CED]
</q>

<eg>
<![ CDATA [
<form>
  <orth>brag</orth>
  <pron>br&amp;g</pron>
</form>
<gramGrp>
  <pos>vb</pos>
</gramGrp>
<form type=infl>
  <orth>brags</orth>
  <orth>bragging</orth>
  <orth>bragged</orth>
</form>
<!-- ... -->
]]>
</eg>

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>[ORifje]</code> (7) vt ...  [C/R] </q>

<eg>
<![ CDATA [
<form>
  <orth>horrifier</orth>
  <pron>ORifje</pron>
  <itype type=vbtable>7</itype>
</form>
]]>
</eg>

<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:
<eg>
<![ CDATA [
<form>
  <orth>horrifier</orth>
  <pron>ORifje</pron>
  <gram type='itype / vbtable'>7</gram>
</form>
]]>
</eg>

<p>Explanatory labels may be attached to alternate forms:

<q rend=display> <hi rend=bold>MTBF</hi> <hi
rend=ital>abbrev. for</hi> mean time between failures.  [CED]
</q>

<eg>
<![ CDATA [
<entry>
  <form type=abbrev>
    <orth>MTBF</orth>
  </form>
  <form type=full>
    <lbl>abbrev. for</lbl>
    <orth>mean time between failures</orth>
  </form>
</entry>
]]>
</eg>

<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>(%bIrI"A:nI) </code>... [CED]
</q>

<eg>
<![ CDATA [
<!-- The pronunciation is associated with both forms. -->
<form>
  <orth>biryani</orth>
  <orth>biriani</orth>
  <pron>%bIrI"A:nI</pron>
</form>
]]>
</eg>

<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>("m&amp;k^@l) </code> or macule <code>("m&amp;kju:l) </code>
... [CED] </q>

<eg>
<![ CDATA [
<!-- &supschwa is a small superscript schwa -->
<form>
  <orth>mackle</orth>
  <pron>"m&amp;k&supschwa;l</pron>
</form>
<form>
  <orth>macule</orth>
  <pron>"m&amp;kju:l</pron>
</form>
]]>
</eg>

<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>("hQspIt@l@) </code> ... [CED] </q>

<eg>
<![ CDATA [
<form>
  <orth>hospitaller</orth>
  <form>
    <usg type=geo>U.S.</usg>
    <orth>hospitaler</orth>
  </form>
  <pron>"hQspIt@l@</pron>
</form>
]]>
</eg>

<!-- suppressed; supererogatory (msm) -->

<!-- <p>In this example, the "pl." specification applies to   -->
<!-- two orthographic forms, but a pronunciation is           -->
<!-- associated with only one of them:                        -->

<!-- <q rend=display>                                         -->
<!-- pinna ("pIn@) n., pl. -nae (-ni:) or -nas.   ... [CED]   -->
<!-- </q>                                                     -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <form>                                                   -->
<!--   <orth>pinna</orth>                                     -->
<!--   <pron>"pIn@</pron>                                     -->
<!-- </form>                                                  -->
<!-- <gramGrp>                                                -->
<!--   <pos>n</pos>                                           -->
<!-- </gramGrp>                                               -->
<!-- <form type=infl>                                         -->
<!--   <num>pl</num>                                          -->
<!--   <form>                                                 -->
<!--     <orth type=lat extent=part>-nae</orth>               -->
<!--     <pron extent=part>-ni:</pron>                        -->
<!--   </form>                                                -->
<!--   <orth type=std extent=part>-nas</orth>                 -->
<!-- </form>                                                  -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->
<!-- ... end suppression (msm)                                -->

<p>The formal declarations for the elements of the <gi>form</gi>
group are these:

<eg id=dditpfo>
<![ CDATA [
<!-- 12.3.1:  The form group                                  -->
<!ELEMENT form          - -  (%m.formInfo | %paraContent)+      >
<!ATTLIST form               %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!ELEMENT orth          - O  (%paraContent)                     >
<!ATTLIST orth               %a.global;
                             %a.dictionaries;
          extent             CDATA               full
          type               CDATA               #IMPLIED       >
<!ELEMENT pron          - O  (%paraContent)                     >
<!ATTLIST pron               %a.global;
                             %a.dictionaries;
          notation           CDATA               #IMPLIED
          extent             CDATA               full           >
<!ELEMENT hyph          - O  (%paraContent;)                    >
<!ATTLIST hyph               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT syll          - O  (%paraContent;)                    >
<!ATTLIST syll               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT stress        - O  (%paraContent;)                    >
<!ATTLIST stress             %a.global;                         >
<!-- (LBL is declared with USG, elsewhere.)                   -->


<!-- Elements for morphological information:                  -->

<!ELEMENT gram          - O  (%paraContent;)                    >
<!ATTLIST gram               %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!ELEMENT gen           - -  (%paraContent)                     >
<!ATTLIST gen                %a.global;
                             %a.dictionaries;                   >
<!ELEMENT number        - -  (%paraContent;)                    >
<!ATTLIST number             %a.global;
                             %a.dictionaries;                   >
<!ELEMENT case          - -  (%paraContent;)                    >
<!ATTLIST case               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT per           - O  (%paraContent;)                    >
<!ATTLIST per                %a.global;
                             %a.dictionaries;                   >
<!ELEMENT tns           - O  (%paraContent;)                    >
<!ATTLIST tns                %a.global;
                             %a.dictionaries;                   >
<!ELEMENT mood          - O  (%paraContent;)                    >
<!ATTLIST mood               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT itype         - -  (%paraContent)                     >
<!ATTLIST itype              %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<p>The classes of morphological elements, and of elements allowed within
the <gi>form</gi> group, are declared thus:

<eg id=deditpfo>
<![ CDATA [
<!-- 12.3.1:  Classes for morphological and form information  -->
<!ENTITY % x.morphInfo ''                                       >
<!ENTITY % m.morphInfo '%x.morphInfo case | gen | gram | itype 
           | mood | number | per | tns'                         >
<!ENTITY % x.formInfo ''                                        >
<!ENTITY % m.formInfo '%x.formInfo %m.morphInfo; | form | hyph 
           | lbl | orth | pron | syll | usg'                    >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div3 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 following elements:

<list type=gloss>
<label><gi>pos</gi></label>
<item>indicates the part of speech assigned to a dictionary 
headword
(noun, verb, adjective, etc.)</item>
<label><gi>subc</gi></label>
<item>contains subcategorization information 
(transitive/intransitive,
countable/non-count, etc.)</item>
<label><gi>colloc</gi></label>
<item>contains a collocate of the headword.</item>
</list>


<p>In addition, <gi>gramGrp</gi> can contain any of the morphological
elements defined in section <ptr target=DItpfo> for <gi>form</gi>:

<list type=gloss>
<label><gi>gram</gi></label>
<item>within an entry in a dictionary or a terminological data 
file,
contains grammatical information relating to a term, 
word, or form.</item>
<label><gi>itype</gi></label>
<item>indicates the inflectional class associated with a lexical 
item.</item>
<label><gi>gen</gi></label>
<item>identifies the morphological gender of a lexical item, as 
given in
the dictionary.</item>
<label><gi>number</gi></label>
<item>indicates grammatical number associated with a form, as 
given
in a dictionary.</item>
<label><gi>case</gi></label>
<item>contains grammatical case information given by a dictionary 
for
a given form.</item>
<label><gi>per</gi></label>
<item>contains an indication of the grammatical person (1st, 2d, 
3d,
etc.) associated with a given inflected form in a 
dictionary.</item>
<label><gi>tns</gi></label>
<item>indicates the grammatical tense associated with a given 
inflected
form in a dictionary.</item>
<label><gi>mood</gi></label>
<item>contains information about the grammatical mood of verbs 
(e.g.
<q>indicative</q>, <q>subjunctive</q>, 
<q>imperative</q>)</item>
</list>


Elements conveying morphological information bear different
interpretations within <gi>gramGrp</gi> and <gi>form</gi> groups, the
difference being that in the <gi>form</gi> group, the morphological
information specified pertains to the specific alternate form in
question, while within <gi>gramGrp</gi> it applies to the headword form.
For example, in the entry <q><hi rend=bold>pinna</hi> ('pIn@) n., pl. -nae (-ni:) or
-nas</q> [CED], 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.

<!-- suppress as more than enough (msm)                       -->
<!--                                                          -->
<!-- <p>Examples:                                             -->
<!--                                                          -->
<!-- <q rend=display>                                         -->
<!-- amass /@"m&amp;s/ vt [VP6A] pile or heap up, collect.   [OALD] -->
<!-- </q>                                                     -->
<!--                                                          -->
<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <entry>                                                  -->
<!--    <form>                                                -->
<!--       <orth>amass</orth>                                 -->
<!--       <pron>@"m&amp;s</pron>                                 -->
<!--    </form>                                               -->
<!--    <gramGrp>                                             -->
<!--       <pos>vt</pos>                                      -->
<!--       <subc>VT6A</subc>                                  -->
<!--    </gramGrp>                                            -->
<!--    <def>pile or heap up, collect.</def>                  -->
<!-- </entry>                                                 -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->
<!--                                                          -->
<!-- ... end suppression (msm)                                -->

<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&eacute;dire</mentioned>:
<!-- no such word, unless you add the accent! (LB -->
<q rend=display>
<hi rend=bold>m&eacute;dire</hi> v.t. ind. (de) ...   [PLC]
</q>

This entry can be tagged using specialized grammatical elements:

<eg>
<![ CDATA [
<form><orth>m&eacute;dire</orth></form>
<gramGrp>
   <pos>v</pos>
   <subc>t ind</subc>
   <colloc type=prep>de</colloc>
</gramGrp>
]]>
</eg>

Or using the <gi>gram</gi> element:
<eg>
<![ CDATA [
<form><orth>m&eacute;dire</orth></form>
<gramGrp>
   <gram type=pos>v</>
   <gram type=subc>t ind</>
   <gram type='colloc / prep'>de</>
</gramGrp>
]]>
</eg>

<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.  ... [DNT]
</q>

<eg>
<![ CDATA [
<form><orth>isotope</orth></form>
<gramGrp>
   <pos>adj</pos>
</gramGrp>
<gramGrp>
   <pos>n</pos>
   <gen>m</gen>
</gramGrp>
]]>
</eg>

<!-- <q rend=display>                                         -->
<!-- ablaze (@"bleIz) adj.  (postpositive), adv. 1. on fire;  -->
<!-- burning. 2. brightly illuminated. 3. emotionnally        -->
<!-- aroused.  [CED]                                          -->
<!-- </q>                                                     -->

<!-- <eg>                                                     -->
<!-- <![ 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>                                                 -->
<!--                                                          -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<q rend=display> <hi rend=bold>wits</hi> (wIts)
pl. n. 1. (sometimes sing.) the ability to reason and act,
esp. quickly...  [CED] </q>

<eg>
<![ CDATA [
<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>
]]>
</eg>

<!-- <q rend=display>                                         -->
<!-- carry ("k&amp;rI) vb.  ...(mainly tr.) 1. (also intr.)   -->
<!-- to take or bear...  [CED]                                -->
<!-- </q>                                                     -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <entry>                                                  -->
<!--   <form>                                                 -->
<!--     <orth>carry</orth>                                   -->
<!--     <pron>"k&amp;rI</pron>                                   -->
<!--   </form>                                                -->
<!--   <gramGrp>                                              -->
<!--     <pos>vb</pos>                                        -->
<!--     <subc>mainly tr</subc>                               -->
<!--   </gramGrp>                                             -->
<!--   <sense n='1'>                                          -->
<!--     <gramGrp>                                            -->
<!--       <subc>also intr</subc>                             -->
<!--     </gramGrp>                                           -->
<!--     <def>to take or bear...</def>                        -->
<!-- ...                                                      -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->


<p>The following gives the formal declarations for elements in the
grammatical-information group.

<eg id=dditpgr>
<![ CDATA [
<!-- 12.3.2:  The gram group                                  -->
<!ELEMENT gramGrp       - -  (%m.gramInfo | %paraContent)*      >
<!ATTLIST gramGrp            %a.global;
                             %a.dictionaries;                   >
<!ELEMENT pos           - O  (%paraContent;)                    >
<!ATTLIST pos                %a.global;
                             %a.dictionaries;                   >
<!ELEMENT subc          - O  (%paraContent;)                    >
<!ATTLIST subc               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT colloc        - O  (%paraContent;)                    >
<!ATTLIST colloc             %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<p>The class of elements allowed within
the <gi>gramGrp</gi> element is declared thus.
The class <term>morphInfo</term> is
defined above in section <ptr target=DItpfo>.

<eg id=deditpgr>
<![ CDATA [
<!-- 12.3.2:  Elements for grammatical information            -->
<!ENTITY % x.gramInfo ''                                        >
<!ENTITY % m.gramInfo '%x.gramInfo %m.morphInfo; | colloc | 
           gramGrp | lbl | pos | subc | usg'                    >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div3 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 alike may be tagged using the
<gi>def</gi> element described in section <ptr target=DItpde>.

<p>Because as a special case it is frequently desired to distinguish the
provision of translation equivalents in other languages from other forms
of sense information, however, the specialized elements <gi>tr</gi>
(translation equivalent) and <gi>trans</gi> (which groups a translation
equivalent with related information such as its grammatical description)
are defined for this purpose in section <ptr target=DItptr>.

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

<div4 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 <gi>tr</gi>, section
<ptr target=DItptr>, and <gi>eg</gi>, section <ptr target=DItpeg>.
The <gi>def</gi> element directly contains the text of the definition;
unlike <gi>form</gi> and <gi>gramGrp</gi>, that is, 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>Definitions may occur directly within an entry; when multiple
definitions are given, they typically are 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.  [CP] </q>

<eg>
<![ CDATA [
<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>
]]>
</eg>

<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&eacute;moulade</hi>
<code>[Remulad] </code> nf remoulade, r&eacute;moulade (<hi
rend=ital>dressing containing mustard and herbs</hi>).  [C/R]
</q>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>r&eacute;moulade</orth>
    <pron>Remulad</pron>
  </form>
  <gramGrp>
    <pos>n</pos>
    <gen>f</gen>
  </gramGrp>
  <trans>
    <tr>remoulade</tr>
    <tr>r&eacute;moulade</tr>
    <def>dressing containing mustard and herbs</def>
  </trans>
</entry>
]]>
</eg>

<p>The following gives the formal definition of <gi>def</gi>:

<eg id=dditpde>
<![ CDATA [
<!-- 12.3.3.1:  Definition text                               -->
<!ELEMENT def           - O  (%paraContent;)                    >
<!ATTLIST def                %a.global;
                             %a.dictionaries;                   >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div4 id=DItptr><head>Translation Equivalents</head>

<p>Multi-lingual 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 information, 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 the <gi>tr</gi>
element.

<p>As in monolingual dictionaries, the <gi>sense</gi> element is used in
multi-lingual dictionaries to group information (forms, grammatical
information, usage, translation(s), etc.) about a given sense of a word
where necessary, as in monolingual dictionaries.  Information about the
individual translation equivalents within a sense is grouped using
<gi>trans</gi> element.  This information may include the translation
text (tagged <gi>tr</gi> or <gi>def</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>).

<!-- [do we need other things in the trans group?  NEEDS      -->
<!-- WORK.  -JV, NI] <                                        -->

<list type=gloss>
<label><gi>trans</gi></label>
<item>contains translation text and related information (within 
an
entry in a multilingual dictionary).</item>
<label><gi>tr</gi></label>
<item>contains a translation of the headword or an example.</item>
<label><gi>lbl</gi></label>
<item>in dictionaries, contains a label for a form, example,

translation, or other piece of information, e.g. 
<q>abbreviation
for</q>, <q>contraction of</q>, 
<q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, 
etc.</item>
</list>


<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 ~) &eacute;talagiste
mf. she's a stylish ~ elle s'habille avec chic; V hair.  (b)
(tool) (for wood) raboteuse f; (for stone) rabotin m. [C/R] </q>

<!-- < note place=inline > [homograph numbers superscripted   -->
<!-- in original text; pronunciations have to be fixed -JV,   -->
<!-- NI] < /note >                                            -->

<eg>
<![ CDATA [
<entry n='1'>
  <form><orth>dresser</orth><!-- ... --></form>
  <gramGrp> <pos>n</pos> </gramGrp>
  <sense n='a'>
    <sense>
      <usg type=dom>Theat</usg>
      <trans>
        <tr>habilleur</tr>
        <gen>m</gen>
      </trans>
      <trans>
        <tr>-euse</tr>
        <gen>f</gen>
      </trans>
    </sense>
    <sense>
      <usg type=dom>Comm</usg>
      <form type=compound>
        <orth>window <oRef></orth>
      </form>
      <trans>
        <tr>etalagiste</tr>
        <gen>mf</gen>
      </trans>
     </sense>
     <eg>
       <q>she's a stylish <oRef></q>
       <trans><tr>elle s'habille avec chic</tr></trans>
     </eg>
     <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>
      <trans>
        <tr>raboteuse</tr>
        <gen>f</gen>
      </trans>
    </sense>
    <sense>
      <usg type=hint>for stone</usg>
      <trans>
        <tr>rabotin</tr>
        <gen>m</gen>
     </trans>
    </sense>
  </sense>
</entry>
]]>
</eg>

<p>In this encoding, 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&eacute;v de <hi rend=bold>Organisation de l'Arm&eacute;e
secr&egrave;te</hi>) OAS (<hi rend=ital>illegal military
organization supporting French rule of Algeria</hi>).  [C/R] </q>

<eg>
<![ CDATA [
<entry>
  <!-- ... -->
  <trans>
    <tr>OAS</tr>
    <def>illegal military organization supporting French
         rule of Algeria</def>
  </trans>
</entry>
]]>
</eg>


<!-- <q rend=display>                                         -->

<!-- canary [k@"nE@rI] 1 n (a) (bird) canari m, serin m.      -->
<!--   (b) (wine) vin m des Canaries.                         -->
<!-- 2 cpd (also canary yellow) (de couleur) jaune serin      -->
<!-- inv, jaune canari inv.  (Bot) canary grass alpiste m;    -->
<!-- (Geog) Canary Isles, Canaries (&icirc;les fpl) Canaries  -->
<!-- fpl; (Bot) canary seed millet m. [C/R]                   -->

<!-- </q>                                                     -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <entry>                                                  -->
<!--   <form>                                                 -->
<!--     <orth>canary</orth>                                  -->
<!--     <pron>k@"nE@rI</pron>                                -->
<!--   </form>                                                -->
<!--   <sense n='1'>                                          -->
<!--     <gramGrp>                                            -->
<!--        <pos>n</pos>                                      -->
<!--     </gramGrp>                                           -->
<!--     <sense n='a'>                                        -->
<!--       <usg type=hyper>bird</usg>                         -->
<!--       <trans>                                            -->
<!--         <tr>canari</tr>                                  -->
<!--         <gen>m</gen>                                     -->
<!--       </trans>                                           -->
<!--       <trans>                                            -->
<!--         <tr>serin</tr>                                   -->
<!--         <gen>m</gen>                                     -->
<!--       </trans>                                           -->
<!--     </sense>                                             -->
<!--     <sense n='b'>                                        -->
<!--       <usg type=hyper>wine</usg>                         -->
      <!--note use of NEXT and PREV TEI attributes-->
      <!--for discontinous elements               -->
<!--       <trans id=t1 next=t2>                              -->
<!--         <tr>vin</tr>                                     -->
<!--         <gen>m</gen>                                     -->
<!--       </trans>                                           -->
<!--       <trans id=t2 prev=t1>                              -->
<!--         <tr>des canaries</tr>                            -->
<!--       </trans>                                           -->
<!--      </sense>                                            -->
<!--    </sense>                                              -->
<!--    <sense n='2'>                                         -->
<!--      <gramGrp>                                           -->
<!--        <pos>cpd</pos>                                    -->
<!--      </gramGrp>                                          -->
<!--      <re type=cmpd>                                      -->
<!--        <form>                                            -->
<!--           <orth>canary yellow</orth>                     -->
<!--        </form>                                           -->
<!--        <usg type=hint>de couleur</usg>                   -->
<!--        <trans>                                           -->
<!--          <tr>jaune serin</tr>                            -->
<!--          <itype>inv</itype>                              -->
<!--        </trans>                                          -->
<!--        <trans>                                           -->
<!--          <tr>jaune canari</tr>                           -->
<!--          <itype>inv</itype>                              -->
<!--        </trans>                                          -->
<!--      </re>                                               -->
<!--      <re type=cmpd>                                      -->
<!--        <usg type=dom>Bot</usg>                           -->
<!--        <form>                                            -->
<!--          <orth>canary grass</orth>                       -->
<!--        </form>                                           -->
<!--        <trans>                                           -->
<!--          <tr>alpiste</tr>                                -->
<!--          <gen>m</gen>                                    -->
<!--        </trans>                                          -->
<!--      </re>                                               -->
<!--      <re type=cmpd>                                      -->
<!--        <usg type=dom>Geog</usg>                          -->
<!--        <form>                                            -->
<!--          <orth>Canary Isles</orth>                       -->
<!--          <orth>Canaries</orth>                           -->
<!--        </form>                                           -->
<!--        <trans id=t1 opt=y next=t2>                       -->
<!--          <tr>&icirc;les</tr>                             -->
<!--          <gen>f</gen>                                    -->
<!--          <num>pl</num>                                   -->
<!--        </trans>                                          -->
<!--        <trans id=t2 prev=t1>                             -->
<!--          <tr>Canaries</tr>                               -->
<!--          <gen>f</gen>                                    -->
<!--          <num>pl</num>                                   -->
<!--        </trans>                                          -->
<!--      </re>                                               -->
<!--      <re type=cmpd>                                      -->
<!--        <usg type=dom>Bot</usg>                           -->
<!--        <form>                                            -->
<!--          <orth>canary seed</orth>                        -->
<!--        </form>                                           -->
<!--        <trans>                                           -->
<!--          <tr>millet</tr>                                 -->
<!--          <gen>m</gen>                                    -->
<!--        </trans>                                          -->
<!--      </re>                                               -->
<!--    </sense>                                              -->
<!--  </entry>                                                -->
<!--                                                          -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<p>Note that <gi>tr</gi> may also be used in monolingual dictionaries
when a translation is given for a foreign word:

<!-- < note place=inline > [headwords are in bold italics     -->
<!-- intead of just bold; pronunciations to be completed      -->
<!-- -JV, NI] < /note >                                       -->

<q rend=display> <hi rend=bold>havdalah</hi> or <hi
rend=bold>havdoloh</hi> Hebrew. (Hebrew <code>hAvdA"lA; </code>
Yiddish <code>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] [CED] </q>

<eg>
<![ CDATA [
<entry type=foreign>
  <form>
    <orth>havdalah</orth>
    <orth>havdoloh</orth>
  </form>
  <!-- ... -->
  <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>
  <trans>
    <lbl>literally</lbl>
    <tr>separation</tr>
  </trans>
</entry>
]]>
</eg>

<p>The formal definition of these elements is as follows:

<eg id=dditptr>
<![ CDATA [
<!-- 12.3.3.2:  Translation information                       -->
<!ELEMENT trans         - O  (%paraContent | 
                             %m.dictionaryParts)*               >
<!ATTLIST trans              %a.global;
                             %a.dictionaries;                   >
<!ELEMENT tr            - O  (%paraContent;)                    >
<!ATTLIST tr                 %a.global;
                             %a.dictionaries;                   >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div3 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 tag set
or elsewhere in this chapter.  Of particular relevance for the markup of
etymologies are:

<list type=gloss>
<label><gi>etym</gi></label>
<item>encloses the etymological information in a dictionary 
entry.</item>
<label><gi>lang</gi></label>
<item>name of a language mentioned in etymological or other 
linguistic
discussion.</item>
<label><gi>date</gi></label>
<item>contains a date in any format.</item>
<label><gi>mentioned</gi></label>
<item>marks words or phrases mentioned, not used.</item>
<label><gi>gloss</gi></label>
<item>identifies a phrase or word used to provide a gloss or

definition for some other word or phrase. </item>
<label><gi>pron</gi></label>
<item>contains the pronunciation(s) of the word.</item>
<label><gi>usg</gi></label>
<item>contains usage information in a dictionary entry.</item>
<label><gi>lbl</gi></label>
<item>in dictionaries, contains a label for a form, example,

translation, or other piece of information, e.g. 
<q>abbreviation
for</q>, <q>contraction of</q>, 
<q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, 
etc.</item>
</list>


<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>lang</att> attribute of the
<gi>mentioned</gi> element.

<p>Examples:

<q rend='display'> <hi rend=bold>abismo</hi> m. (del gr. a
priv. y byssos, fondo). Sima, gran profundidad. ...  </q>


<eg>
<![ CDATA [
<entry>
  <form><orth>abismo</orth></form>
  <!-- ... -->
  <etym>del <lang>gr.</> <mentioned>a</> priv. y
       <mentioned>byssos</>, <gloss>fondo</>
  </etym>
  <!-- ... -->
</entry>
]]>
</eg>

<q rend='display'> <hi rend=bold>neume</hi>
<code>\'n(y)&uuml;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>


<eg>
<![ CDATA [
<entry>
  <!-- ... -->
  <etym><lang>F</> fr. <lang>ML</> <mentioned>pneuma</>
        <mentioned>neuma</> fr. <lang>Gk</>
        <mentioned>pneuma</><gloss>breath</>
        <xr type=etym>more at <ptr target='pneumatic'></xr>
  </etym>
  <def>any of various symbols ...
  <!-- ... -->
</entry>
]]>
</eg>


<p>The formal definition for the elements described in this section and
not declared elsewhere is:

<eg id=dditpet>
<![ CDATA [
<!-- 12.3.4:  Etymologies                                     -->
<!ELEMENT etym          - O  (%paraContent | usg | lbl | def | 
                             trans | tr | (%m.morphInfo) | eg | 
                             xr)*                               >
<!ATTLIST etym               %a.global;
                             %a.dictionaries;                   >
<!ELEMENT lang          - -  (%paraContent)                     >
<!ATTLIST lang               %a.global;
                             %a.dictionaries;                   >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div3 id=DItpmi><head>Other Information</head>
<div4 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>The <gi>eg</gi> element contains usage examples and associated
information; the example text itself should be enclosed in a
<gi>cit</gi> element, if attributed, or a <gi>q</gi> or <gi>quote</gi>
element otherwise.  The <gi>cit</gi> element associates a quotation with
a bibliographic reference to its source.

<list type=gloss>
<label><gi>eg</gi></label>
<item>(in a dictionary) contains an example text containing at 
least one
occurrence of the word form, used in the sense 
being described; examples
may be quoted from (named) 
authors or contrived.</item>
<label><gi>q</gi></label>
<item>contains a quotation or apparent quotation --- a 
representation of
speech or thought marked as being quoted 
from someone else (whether in
fact quoted or not); in 
narrative, the words are usually those of of a
character 
or speaker; in dictionaries, <gi>q</gi> may be used to mark
real or contrived examples of usage.</item>
<label><gi>quote</gi></label>
<item>contains a phrase or passage attributed by the narrator or

author to some agency external to the text. </item>
<label><gi>cit</gi></label>
<item>A quotation from some other document, together with a 
bibliographic
reference to its source.</item>
</list>


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

<!-- [NEEDS WORK: what can go in EG?  anything?  -JV, NI]     -->

<p>Examples:

<q rend='display'> <hi rend=bold>multiplex</hi>
<code>/.../</code>
adj tech having many parts: the multiplex eye of the fly.
[LDOCE]
</q>

<!-- [Check pron -JV, NI]                                     -->


<eg>
<![ CDATA [
   <eg>
     <q>the multiplex eye of the fly.</q>
   </eg>
]]>
</eg>

As the following example shows, <gi>eg</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=ital>S~</hi> and <hi rend=ital>any</hi> are
used with <hi rend=ital>more</hi>): Give me ~ more
<code>/s@'mO:(r)/</code> [OALD] </q>

<!-- <pron> in an example -->
<eg>
<![ CDATA [
<sense n='4'>
  <usg type=colloc><oRef type=cap> and <mentioned>any</>
       are used with <mentioned>more</></usg>
  <eg>
    <q>Give me <oRef> more</q>
    <pron extent=part>s@'mO:(r)</pron>
  </eg>
</sense>
]]>
</eg>

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 &eacute;tait horrifi&eacute;e par la
d&eacute;pense</hi> she was horrified at the expense.  [C/R] </q>

<!-- <trans> in an example -->
<eg>
<![ CDATA [
<entry>
  <!-- ... -->
  <trans><tr>to horrify</tr></trans>
  <eg><q>elle &eacute;tait horrifi&eacute;e par la
         d&eacute;pense</q>
      <trans>
        <tr>she was horrified at the expense.</tr>
      </trans>
  </eg>
</entry>
]]>
</eg>


<!-- <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.  [DNT]                                         -->
<!-- </q>                                                     -->

<!-- <def> in an example -->
<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <eg>                                                     -->
<!--   <q>B&eacute;n&eacute;fice de trois pour cent (3 %)</q> -->
<!--   <def>B&eacute;n&eacute;fice de 3F sur 100F</def>       -->
<!-- </eg>                                                    -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->


<!-- <q rend=display> break1 ... 5 ...  <hi              -->
<!-- rend=ital>When the bank broke</hi> (= was unable    -->
<!-- to carry on business because of lack of funds) <hi  -->
<!-- rend=ital>, many people were ruined.</hi> ...       -->
<!-- [OALD] </q>                                              -->

<!-- example interrupted by a partial definition -->
<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <eg>                                                     -->
<!--   <q next=e2 id=e1>When the bank broke</q>               -->
<!--   <def>was unable to carry on business because           -->
<!--        of lack of funds</def> -->
<!--   <q prev=e1 id=e2>, many people were ruined.</q>        -->
<!-- </eg>                                                    -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

When a source is indicated, the example should be marked with a
<gi>cit</gi> element:

<q rend=display> <hi rend=bold>valeur</hi> ... n. f. ...
2. Vx.  Vaillance, bravoure (sp&eacute;cial., au combat).  <q>La
valeur n'attend pas le nombre des ann&eacute;es</q> (Corneille).  ...  [DNT]
</q>

<eg>
<![ CDATA [
  <sense n='2'>
    <usg type=time>Vx.</usg>
    <def>Vaillance, bravoure (sp&eacute;cial., au combat)</def>
      <eg><cit>
            <q>La valeur n'attend pas le nombre des annees</q>
            <bibl><author>Corneille</author></bibl>
          </cit>
      </eg>
  </sense>
]]>
</eg>

<p>The formal definition of <gi>eg</gi> is:

<eg id=dditpeg>
<![ CDATA [
<!-- 12.3.5.1:  Examples and citations                        -->
<!ELEMENT eg            - O  (q | quote | cit)+   
                                                 +(%m.dictionaryParts
                                                 | 
                                                 %m.formPointers)
                                                                >
<!ATTLIST eg                 %a.global;
                             %a.dictionaries;                   >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div4 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 labels, not
necessarily related to usage, may be attached to forms, translations,
cross references, and examples.  Usage and other labels should be marked
with the following elements:

<list type=gloss>
<label><gi>usg</gi></label>
<item>contains usage information in a dictionary entry.</item>
<label><gi>lbl</gi></label>
<item>in dictionaries, contains a label for a form, example,

translation, or other piece of information, e.g. 
<q>abbreviation
for</q>, <q>contraction of</q>, 
<q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, 
etc.</item>
</list>


Typical usage labels mark

<list type=bullets>
<item>temporal use (archaic, obsolete, etc.)
<item>register (slang, formal, taboo, ironic, facetious, etc.)
<item>style (literal, figurative, etc.)
<item>connotative effect (e.g. derogatory, offensive)
<item>subject field (Astronomy, Philosophy, etc.)
<item>national or regional use (Australian, U.S., Midland dialect, etc.)
</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><code>geo</code> <item>geographic area
<label><code>time</code> <item>temporal, historical era
(<q>archaic</q>, <q>old</q>, etc.)
<label><code>dom</code> <item>domain
<label><code>reg</code> <item>register
<label><code>style</code> <item>style (figurative, literal, etc.)
<label><code>plev</code> <item>preference level (<q>chiefly</q>,
<q>usually</q>, etc.)
<label><code>acc</code><item>acceptability
<label><code>lang</code> <item>language for foreign words,
spellings pronunciations, etc.
<label><code>gram</code> <item>grammatical usage
</list>

<!-- why is this list given twice? (LB) -->

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 are also marked with the <gi>usg</gi> element; sample values for
the <att>type</att> attribute in these cases include:

<list type=gloss>
<label><code>syn</code> <item>synonym given to show use
<label><code>hyper</code> <item>hypernym given to show usage
<label><code>colloc</code> <item>collocation given to show usage
<label><code>comp</code> <item>typical complement
<label><code>obj</code> <item>typical object
<label><code>subj</code> <item>typical subject
<label><code>verb</code> <item>typical verb
<label><code>hint</code> <item>unclassifiable piece of information to
guide sense choice
</list>

<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> ...  [CED] </q>

<eg>
<![ CDATA [
<form>
   <orth>colour</orth>
</form>
<form>
   <usg type=geo>U.S.<usg>
   <orth>color</orth>
</form>
]]>
</eg>

<p>In this example, usage labels are used to indicate domains, register,
and synonyms associated with different senses:

<q rend=display> <hi rend=bold>palette</hi>
<code>[palEt]</code> nf (a) (Peinture: lit, fig) palette. (b)
(Boucherie) shoulder. (c) (aube de roue) paddle; (battoir &agrave;
linge) beetle; (Manutention, Constr) pallet.  [C/R] </q>

<eg>
<![ CDATA [
<!-- ... -->
  <sense n='a'>
    <usg type=dom>Peinture</usg>
    <usg type=style>lit</usg>
    <usg type=style>fig</usg>
    <trans><tr>palette</tr></trans>
  </sense>
  <sense n='b'>
    <usg type=dom>Boucherie</usg>
    <trans><tr>shoulder</tr></trans>
  </sense>
  <sense n='c'>
    <sense>
      <usg type=syn>aube de roue</usg>
      <trans><tr>paddle</tr></trans>
    </sense>
    <sense>
      <usg type=syn>battoir &agrave; linge</usg>
      <trans><tr>beetle</tr></trans>
    </sense>
    <sense>
      <usg type=dom>Manutention</usg>
      <usg type=dom>Constr</usg>
      <trans><tr>beetle</tr></trans>
    </sense>
  </sense>
<!-- ... -->
]]>
</eg>


<!-- <q rend=display> parabola [p@"r&amp;@l@] n parabole f    -->
<!-- (Math) [C/R] </q>                                        -->

<!-- <eg>                                                     -->
<!-- <![ 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>                                                 -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<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=ital>with straw</hi>).
[C/R] </q>

<!-- [note: tilde on the a in ~a (IPA nasal a) -JV, NI]       -->

<eg>
<![ CDATA [
<entry>
  <!-- ... -->
  <trans>
    <tr>reseating</tr>
    <tr>rebottoming</tr>
    <usg type=hint>with straw</usg>
  </trans>
</entry>
]]>
</eg>

<p>The following gives the formal definition of <gi>usg</gi> and
<gi>lbl</gi>:

<eg id=dditpus>
<![ CDATA [
<!-- 12.3.5.2:  Usage information                             -->
<!ELEMENT usg           - O  (%paraContent;)                    >
<!ATTLIST usg                %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!ELEMENT lbl           - O  (%paraContent;)                    >
<!ATTLIST lbl                %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div4 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>Cross references may be tagged in dictionaries using the simple
<gi>ref</gi> and <gi>ptr</gi> elements defined in the core tag set
(section <ptr target=COxr>), or the <soCalled>extended</soCalled>
pointing elements <gi>xref</gi> and <gi>xptr</gi> defined in the
additional tag set for linking, segmentation, and alignment (section
<ptr target=SAxr>).  In addition, the <gi>xr</gi> element may be used
to group all the information relating to a cross reference.  The
following elements may be used for tagging cross references within
dictionaries:

<list type=gloss>
<label><gi>xr</gi></label>
<item>contains a phrase, sentence, or icon referring the reader 
to
some other location in this or another text.</item>
<label><gi>ref</gi></label>
<item>defines a reference to another location in the current 
document,
in terms of one or more identifiable elements, 
possibly modified by
additional text or comment.</item>
<label><gi>ptr</gi></label>
<item>defines a pointer to another location in the current 
document
in terms of one or more identifiable elements.</item>
<label><gi>xref</gi></label>
<item>defines a reference to another location in the current 
document,
or an external document, using an extended 
pointer notation,
possibly modified by additional text or 
comment.</item>
<label><gi>xptr</gi></label>
<item>defines a pointer to another location in the current 
document
or an external document.</item>
<label><gi>lbl</gi></label>
<item>in dictionaries, contains a label for a form, example,

translation, or other piece of information, e.g. 
<q>abbreviation
for</q>, <q>contraction of</q>, 
<q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, 
etc.</item>
</list>


<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 accompanyied by
a homograph number, a sense number, or other further restriction
specifiying what portion of the target entry is being referred to); as
usual, a <gi>ptr</gi> element may be used when the actual text of the
target description can be reconstructed automatically, and a
<gi>ref</gi> element is typically to be preferred when it cannot be
reconstructed automatically.

<!-- in P4, XR or refPhr should go into core. -msm -->

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) [CED] </q>

<eg>
<![ CDATA [
<entry><form><orth>glee</></>
  <!-- ... -->
  <xr>Compare <ptr target='madrigal.1'></xr>
</entry>
]]>
</eg>

<q rend=display> <hi rend=bold>hostellerie</hi> Syn. de
h&ocirc;tellerie (sens 1).  [DNT] </q>

<eg>
<![ CDATA [
<xr type=syn>
  <lbl>Syn. de</lbl> <ref>h&ocirc;tellerie (sens 1)</ref>.
</xr>
]]>
</eg>

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
SGML identifier <q>madrigal.1</q>, 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&ocirc;tellerie</q> to have an SGML 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>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>.  [CED] </q>

<eg>
<![ CDATA [
<entry type='xr, hom' n=2>
  <form><orth>rose</orth><!-- ... --></form>
  <!-- ... -->
  <xr type=pastof>
    <lbl>the past tense of</lbl>
    <ref target='rise'>rise</ref>
  </xr>
</entry>
]]>
</eg>

from cross-references for synonyms and the like:

<q rend=display> <hi rend=bold>antagonist</hi> ... syn see
<hi rend=bold>adverse</hi> [W7] </q>

<eg>
<![ CDATA [
<xr type=syn>
  <lbl>syn see</lbl>
  <ref target='adverse'>adverse</ref>
</xr>
]]>
</eg>

Strictly speaking, this reference is not to the entry given, but to the
list of synonyms it contains.  Slightly more complicated is this
reference to an illustration accompanying another article:

<q rend=display> <hi rend=bold>ax, axe</hi> ... &rarr; see
the illus at <hi rend=bold>tool</hi> [OALD] </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).

<eg>
<![ CDATA [
<xr type='see illustration'>
  <lbl>see the illus at</lbl>
  <ptr target='tool.illus'>
</xr>
]]>
</eg>

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&egrave;re) [PR] </q>

<eg>
<![ CDATA [
<xr>V. <ref target='armillaire'>armillaire</ref>
       <lbl type='sense-restriction'>sph&egrave;re</lbl>
</xr>
]]>
</eg>


<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=ital>Acte entach&eacute; de nullit&eacute;,</hi> contenant
un vice de forme ou pass&eacute; par un incapable*.  [DNT] </q>

The asterisk signals a reference to the entry for
<mentioned>incapable</mentioned>.

<eg>
<![ CDATA [
<def>contenant un vice de forme ou pass&eacute;
par un <ptr target='incapable'>.</def>
]]>
</eg>
<!-- 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, 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).  [DNT] </q>

<eg>
<![ CDATA [
<sense n='4'>
   <usg type=dom>imprim</usg>
   <def>Donner a (une ligne) une longeur convenable au moyen
        de <ref target='blanc-2.1 blanc-2.3'>blancs (2, sens
        1, 3)</ref>
   </def>
</sense>
]]>
</eg>

<p>The formal definition for <gi>xr</gi> is as follows:

<eg id=dditpxr>
<![ CDATA [
<!-- 12.3.5.3:  Cross References                              -->
<!ELEMENT xr            - O  (%paraContent | usg | lbl)*        >
<!ATTLIST xr                 %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<div4 id=DItpno><head>Notes within Entries</head>

<!-- [Someone needs to look into this deeply, to find out     -->
<!-- what can actually appear within such notes.  We have     -->
<!-- seen domain labels, cross references, examples, and it   -->
<!-- is likely that grammatical information, related          -->
<!-- entries etc. can also appear.  We need an inventory in   -->
<!-- order to know what to do here.  At present we have       -->
<!-- left this largely unspecified.  -JV, NI]                 -->

<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 <gi>note</gi> element
should be used for such material.

<list type=gloss>
<label><gi>note</gi></label>
<item>contains a note or annotation.</item>
</list>


<p>For example:

<q rend=display> <hi rend=bold>ain't</hi>
<code>(eInt)</code> <hi rend=ital>Not standard. contraction
of</hi> am not, is not, are not, have not <hi
rend=ital>or</hi> has not: <hi rend=ital>I ain't seen
it.</hi>
....
&utrif;<hi rend=bold>Usage.</hi>
Although the interrogative form <hi rend=ital>ain't I?</hi>
would be a natural contraction of <hi rend=ital>am I
not?</hi>, it is generally avoided in spoken English and never
used in formal English. [CED] </q>

<!-- note: &triangle; is a small triangle -JV, NI             -->
<!-- note: &triangle; changed to utrif to avoid name conflict (msm)  -->

<eg>
<![ CDATA [
<entry>
  <form type=contr>
    <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>
  <eg>
    <q>I ain't seen it.</q>
  </eg><!-- ... -->
  <note type=usage>
     Although the interrogative form <mentioned>ain't
     I?</> would be a natural contraction of <mentioned>am
     I not?</>, it is generally avoided in spoken English
     and never used in formal English.
  </note>
</entry>
]]>
</eg>

<p>The formal declaration for <gi>note</gi> is given in section <ptr
target=COno>.  It has this form:

<eg id=dditpno>
<![ CDATA [
<!-- 12.3.5.4:  [Note]                                        -->
<!ELEMENT note          - O  (%specialPara;)                    >
<!ATTLIST note               %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          target             IDREFS              #IMPLIED
          place              CDATA               'unspecified'
          targetEnd          IDREFS              #IMPLIED
          resp               CDATA               #IMPLIED
          anchored           (yes | no)          yes
          n                  CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
]]>
</eg>


<div3 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>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>Examples:

<q rend='display'> <hi rend=bold>bevvy</hi> <code>("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 vevee, buvee, drinking] --'bevvied adj.  [CED] </q>

<eg>
<![ CDATA [
<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</def>
      <!-- ... -->
    </sense>
    <!-- ... -->
  </hom>
  <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>buvee</>
       <gloss>drinking</gloss>
  </etym>
  <re type=derived>
    <form>
      <orth>'bevvied</orth>
    </form>
    <gramGrp>
      <pos>adj</pos>
    </gramGrp>
  </re>
</entry>
]]>
</eg>

<p>The formal definition of <gi>re</gi> is

<eg id=dditpre>
<![ CDATA [
<!-- 12.3.6:  Related entries                                 -->
<!ELEMENT re            - O  (#PCDATA | sense | 
                             %m.dictionaryTopLevel | %m.phrase 
                             )*                  
                                                 -(re)          >
<!ATTLIST re                 %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<!-- $Id: p2dihw.odd,v 1.6 1994/03/27 16:29:43 lou Exp $ -->
<!-- $Log: p2dihw.odd,v $
# Revision 1.6  1994/03/27  16:29:43  lou
# *** empty log message ***
#
# Revision 1.5  1994/03/07  15:19:03  lou
# fix ^Z
#
# Revision 1.4  1994/03/07  14:44:05  lou
# apply typos etc. noted by DTB et al.
#
# Revision 1.3  1994/01/15  20:45:31  msmcq
# cmsmcq revision for P3
# see comments for details
#
# Revision 1.2  1994/01/04  19:38:25  msmcq
# first cut at DI revisions
# -->
<!-- Revisions:                                               -->
<!-- 94-01-15 : MSM : typo                                    -->
<!-- 94-01-14 : MSM : fix oRef, pRef examples:  target= not form= -->
<!-- 94-01-12 : MSM : stylistic fixes                         -->
<!-- 94-01-12 : MSM : number not num                          -->
<!-- 94-01-12 : MSM : correct entity:  oelig, not oe          -->
<!-- 94-01-12 : MSM : fix dashes inside commented-out exx     -->
<!-- 94-01-11 : MSM : changes for P3, mostly recasting,       -->
<!--                  pruning examples, commenting            -->
<!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   -->
<!-- 94-01-09 : MSM : move class decls into dtdFrag here      -->
<!-- 93-10-19 : MSM : rename tgt as te                        -->
<!-- 93-10-19 : MSM : change sn attribute to n                -->
<!-- 93-10-19 : MSM : change hn attribute to n                -->
<!-- 93-10-19 : MSM : delete some notes from ni, jv           -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-04-12 : MSM : delete N att on divs                    -->

<div2 id=DIhw><head>Headword and Pronunciation References</head>

<!-- oRef, pRef, oVar and pVar                                -->

<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:

<list type=gloss>
<label><gi>oRef</gi></label>
<item>in a dictionary example, indicates a reference to the

orthographic form(s) of the headword.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the kind of typographic modification made to the 
headword in the reference.
Sample values include:
<list type=gloss>
<label><term>nohyph</term></label>
<item>indicates that the headword, though a prefix or suffix, 
loses its hyphen</item>
<label><term>cap</term></label>
<item>indicates first letter is given as capital</item>
</list></item>
</list>
</item>
<label><gi>pRef</gi></label>
<item>in a dictionary example, indicates a reference to the

pronunciation(s) of the headword.</item>
<label><gi>oVar</gi></label>
<item>in a dictionary example, indicates a reference to variant

orthographic form(s) of the headword.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the kind of variant involved.
Sample values include:
<list type=gloss>
<label><term>pp</term></label>
<item>past participle</item>
<label><term>f</term></label>
<item>feminine</item>
<label><term>pl</term></label>
<item>plural</item>
<label><term>pt</term></label>
<item>past tense</item>
<label><term>prp</term></label>
<item>present participle</item>
</list></item>
</list>
</item>
<label><gi>pVar</gi></label>
<item>in a dictionary example, indicates a reference to variant

pronunciation(s) of the headword.</item>
</list>


<p>As members of the class <ident type=class>formPointers</ident>, all these
elements share a <att>target</att> attribute, which may optionally be
used to resolve any ambiguity about the headword form being referred to.

<list type=gloss>
<label><att>target</att></label>
<item>gives the SGML identifier of the orthographic form referred 
to.</item>
</list>

<p>Headword references come in a variety of formats:

<list type=gloss>
<label>~        <item>indicates a reference to the full form of
                      the headword
<label>pref~    <item>gives a prefix to be affixed to the headword
<label>~suf     <item>gives a suffix to be affixed to the headword
<label>A~       <item>gives the first letter in upper case,
                      indicating that the headword is capitalized
<label>pref~suf <item>gives a prefix and a suffix to be affixed to
                      the headword
<label>a.       <item>gives the initial of the word followed by a
                      full stop, to indicate reference to the full form
                      of the headword
<label>A.       <item>refers to a capitalized form of the headword
<!-- <label>[font-shifted] <item>some font shift (e.g.,       -->
<!-- italics) for (e.g.) a suffix, prefix, inflected form,    -->
<!-- etc.                                                     -->
</list>

<!-- last item commented out because I do not understand      -->
<!-- what it is supposed to mean.  (msm)                      -->

<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> [OALD], the tilde stands for either
headword form (<mentioned>colour</mentioned>, <mentioned>color</mentioned>).

<p>Examples:

<q rend=display> <hi rend=bold>colonel</hi> ... army officer
above a lieutenant-~.  [OALD] </q>

<eg>
<![ CDATA [
<def>army officer above a lieutenant-<oRef></def>
]]>
</eg>

<!-- <q rend=display>                                         -->
<!-- take ...  < I don't &tilde; milk in my tea >                   -->
<!-- [NPEG]                                                   -->
<!-- </q>                                                     -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <eg><q>I don't <oRef> milk in my tea</q></eg>            -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<q rend=display>
<hi rend=bold>academy</hi> ... The Royal A~ of Arts [OALD]
</q>

<eg>
<![ CDATA [
<q>The Royal <oRef type=cap> of Arts</q>
]]>
</eg>

<!-- 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]            -->

<!-- <eg>                                                     -->
<!-- <![ 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>                                                 -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<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 < <hi
rend=bold>vag</hi>al > < <hi rend=bold>vago</hi>tomy >
[W7] </q>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth id=o1>vag-</orth>
    <orth id=o2>vago-</orth>
  </form>
  <!-- ... -->
  <def>vagus nerve</def>
  <eg>
    <q><oRef target=o1 type=nohyph>al</q>
    <q><oRef target=o2 type=nohyph>tomy</q>
  </eg>
</entry>
]]>
</eg>

<!-- <p>In this example the hyphen is retained in the first   -->
<!-- oRef, and not in the second:                             -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- 1 deuter- or deutero- ... <DEUTERO-genesis>              -->
<!-- 2 deuter- or deutero- ... <DEUTERated>    [W7]           -->
<!--                                                          -->
<!-- <entry n=1>                                              -->
<!--   <form>                                                 -->
<!--     <orth id=o11>deuter-</orth>                          -->
<!--     <orth id=o12>deutero-</orth>                         -->
<!--   </form>                                                -->
<!--  ...                                                     -->
<!--   <eg>                                                   -->
<!--     <q><oRef target=o12>genesis</q>                        -->
<!--   </eg>                                                  -->
<!-- </entry>                                                 -->
<!--                                                          -->
<!-- <entry n=2>                                              -->
<!--   <form>                                                 -->
<!--     <orth id=o21>deuter-</orth>                          -->
<!--     <orth id=o22>deutero-</orth>                         -->
<!--   </form>                                                -->
<!--  ...                                                     -->
<!--   <eg>                                                   -->
<!--     <q><oRef target=o21 type=nohyph>ated</q>               -->
<!--   </eg>                                                  -->
<!-- </entry>                                                 -->
<!--                                                          -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->



<!-- 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]                                                    -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <entry>                                                  -->
<!--   <form>                                                 -->
<!--     <orth id=o1>neur-</orth>                             -->
<!--     <orth 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>                                     -->
<!--     <eg>                                                 -->
<!--       <q><oRef target=o1 type=nohyph>al</q>                -->
<!--     </eg>                                                -->
<!--     <eg>                                                 -->
<!--       <q><oRef form=o2 type=nohyph>logy</q>              -->
<!--     </eg>                                                -->
<!--   </sense>                                               -->
<!--   <sense n='2'>                                          -->
<!--     <def>neural</def>                                    -->
<!--     <def>neural and</def>                                -->
<!--     <eg>                                                 -->
<!--       <q><oRef target=o2 type=nohyph>muscular</q>          -->
<!--     </eg>                                                -->
<!--   </sense>                                               -->
<!-- </entry>                                                 -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<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> ... < Mr Burton
<hi rend=bold>took</hi> us for French > [NPEG] </q>

<eg>
<![ CDATA [
<eg>
  <q>Mr Burton <oVar type=pt>took</oVar> us for French</q>
</eg>
]]>
</eg>

<q rend=display> <hi rend=bold>take</hi> ... < was quite
<hi rend=bold>~n</hi> with him > [NPEG] </q>

<eg>
<![ CDATA [
<eg>
  <q>was quite <oVar type=pp><oRef>n</oVar> with him</q>
</eg>
]]>
</eg>

<p>Note that, in the example above, tilde and font shift combine.  The
encoding

<eg>
<![ CDATA [
<q>was quite <oRef>n with him</q>
]]>
</eg>

would correspond to <q>was quite ~n with him</q> (no font shift).

<!-- What? (msm) -->

<p>The next example shows a discontinuous reference, using the attributes
<att>next</att> and <att>prev</att>, which are defined in the additional
tag set for linking, segmentation, and alignment (see chapter <ptr
target=SA>) and therefore require that that tag set be selected in
addition to that for dictionaries.

<q rend=display> <hi rend=bold>mix up</hi>... < it's easy to
<hi rend=bold>mix</hi> her <hi rend=bold>up</hi>
with her sister > [NPEG] </q>

<eg>
<![ CDATA [
<eg><q>it's easy to <oVar next=ov2 id=ov1>mix</oVar>
     her <oVar prev=ov1 id=ov2>up</oVar> with her
     sister</q>
</eg>
]]>
</eg>

<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>/,aw'duhv </code> (Fr O:r d&oelig;vr)/ n, pl hors d'oeuvres also
hors d'oeuvre <code>/'duhv(z) </code> (Fr ~)/ [NPEG] </q>

<eg>
<![ CDATA [
<form>
  <orth>hors d'oeuvre</orth>
  <pron>%aU"dUv</pron>
  <form>
    <usg type=lang>Fr</usg>
    <pron id=p2>OR d0vR</pron>
  </form>
</form>
<!-- ... -->
<form type=infl>
  <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=p2></pron>
  </form>
</form>
]]>
</eg>

<p>Because headword and pronunciaton 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>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>The class of headword references is defined thus:

<eg id=dedihw>
<![ CDATA [
<!-- 12.4:  Classes for headword references                   -->
<!ENTITY % x.formPointers ''                                    >
<!ENTITY % m.formPointers '%x.formPointers oRef | oVar | pRef | 
           pVar'                                                >
<!ENTITY % a.formPointers '
          target             IDREF               #IMPLIED'      >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>


<p>The formal declaration for headword reference elements is:

<eg id=ddihw>
<![ CDATA [
<!-- 12.4:  Headword references                               -->
<!ELEMENT oRef          - O  EMPTY                              >
<!ATTLIST oRef               %a.global;
                             %a.dictionaries;
                             %a.formPointers;
          type               CDATA               #IMPLIED       >
<!ELEMENT oVar          - -  (#PCDATA | oRef)*                  >
<!ATTLIST oVar               %a.global;
                             %a.dictionaries;
                             %a.formPointers;
          type               CDATA               #IMPLIED       >
<!ELEMENT pRef          - O  EMPTY                              >
<!ATTLIST pRef               %a.global;
                             %a.dictionaries;
                             %a.formPointers;                   >
<!ELEMENT pVar          - -  (#PCDATA | pRef)*                  >
<!ATTLIST pVar               %a.global;
                             %a.dictionaries;
                             %a.formPointers;                   >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>




<!-- $Id: p2dimv.odd,v 1.9 1998/01/30 16:45:57 tei Exp $ -->
<!--*
    * $Log: p2dimv.odd,v $
    * Revision 1.9  1998/01/30 16:45:57  tei
    * fix log keyword
    *
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.7  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.6  1994/03/27  16:29:46  lou
    * *** empty log message ***
    *
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    *
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    *
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    *
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    *-->
<!-- Revisions:                                               -->
<!-- 4 jan 98 : LB : minor fixes from 1996-06-13 CMSMCQ -->
<!-- 94-04-08 : MSM : cosmetic changes to line format in some long qs -->
<!-- 94-01-15 : MSM : minor lastminute fixes                  -->
<!-- 94-01-14 : MSM : suppress value in adlist                -->
<!-- 94-01-14 : MSM : expand= and value= merged into norm=    -->
<!-- 94-01-14 : MSM : suppress claims that diglobal class is global -->
<!-- 94-01-14 : MSM : delete ghost endtag for morph           -->
<!-- 94-01-14 : MSM : fix typo in thyrostimuline example      -->
<!-- 94-01-14 : MSM : restore name of orig attribute          -->
<!-- 94-01-14 : MSM : restore opt=y                           -->
<!-- 94-01-14 : MSM : change OPT usage to solve name clash problems -->
<!-- 94-01-14 : MSM : fix xref to auricle                     -->
<!-- 94-01-12 : MSM : stylistic changes                       -->
<!-- 94-01-12 : MSM : number not num                          -->
<!-- 94-01-12 : MSM : correct some typos, SGML errors         -->
<!-- 94-01-11 : MSM : revise for clarity                      -->
<!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   -->
<!-- 94-01-09 : MSM : add dtdFrag                             -->
<!-- 94-01-05 : MSM : replace hi with hilited, & with &amp    -->
<!-- 94-01-05 : MSM : replace ital, bold with hi              -->
<!-- 93-10-19 : MSM : rename tgt as te                        -->
<!-- 93-10-19 : MSM : change sn attribute to n                -->
<!-- 93-10-19 : MSM : delete some notes from ni, jv           -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-04-12 : MSM : delete N att on divs                    -->
<!-- 93-03-08 : MSM : change pronunciation of pastel          -->

<div2 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 type=bullets>

<item>(a) the <term>typographic view</term>, which is concerned with the
two-dimensional printed page, including information about line and
page breaks and other features of layout

<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>(c) the <term>lexical view</term> --- this view includes the
underlying information represented in a dictionary, without concern for
its exact textual form

</list>

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

<div3 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 type=ordered>

<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>Characters appearing in the source text should typically be given
as character data content in the SGML document, rather than as the value
of an attribute; again, rendition text may optionally be excepted from
this rule.

<item>Apart from the characters or graphics in the source text, nothing
else should appear as content in the SGML document, although it may be
given in attribute values.

<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=foot>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>

</list>

<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
SGML tags from such a transcription will leave all and only the
characters of the source text, in their original sequence.<note
place=foot>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>Consider, for example, the following entry:

<q rend=display>
<hi rend=bold>pinna</hi> ('pIn@) n., pl. -nae (-ni:) <hi rend=ital>or</hi> -nas.
1. any leaflet of a pinnate compound leaf. 2. <hi
rend=ital>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]      [CED]
</q>

A conservative encoding of the editorial view of this entry, which
retains all rendition text, might resemble the following:

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>pinna</orth>
    <pron>("pIn@)</pron>
  </form>
  <gramGrp><pos>n.</pos>, </gramGrp>
  <form type=infl>
    <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>
]]>
</eg>

<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=foot>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>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 type=bullets>
<item>parentheses appear around <gi>pron</gi> elements
<item>commas appear before inflected forms
<item>the word <q>or</q> appears before alternate forms
<item>brackets appear around the etymology
<item>full stops appear after <gi>pos</gi>, inflection information,
and sense numbers
<item>senses are numbered in sequence unless otherwise specified using
the global <att>n</att> attribute
</list>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>pinna</orth>
    <pron>"pIn@</pron>
  </form>
  <gramGrp><pos>n</pos></gramGrp>
  <form type=infl>
    <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>
]]>
</eg>

<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>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 <code>no-comma</code>, <code>no-left-paren</code>, etc.
Specific values can be documented using the <gi>rendition</gi> element
in the TEI header.

<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:

<eg>
<![ CDATA [
<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>
]]>
</eg>

<div3 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 recomended 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>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 type=bullets>

<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, clammimg, clammed    [CED]
</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>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
unmmarried, esp as a religious obligation. celi.bate
/"selIb@t/ n [C] unmmarried person (esp a priest who has
taken a vow not to marry).    [OALD]
</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>.

</list>

<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 type=bullets>
<item>abbreviated forms have been silently expanded
<item>some forms have been moved to allow related forms to be grouped
together
<item>the part of speech information has been moved to allow all forms
to be given together
<item>the cross reference to <q>auricle</q> has been simplified
</list>

<eg>
<![ CDATA [
<entry>
  <form>
    <orth>pinna</orth>
    <pron>"pIn@</pron>
    <form type=infl>
      <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</> from
     <lang>Latin</>: <gloss>wing</>, <gloss>feather</>,
     <gloss>fin</>
  </etym>
</entry>
]]>
</eg>

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

<div4><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 SGML tags were to
be removed, the remaining characters would be those of the dominant view
of the text.

<p>The attribute class <ident type=class>dictionaries</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 tag set for dictionaries is selected.

<p>When the editorial view is dominant, the following attributes may be
used to capture the lexical view:

<list type=gloss>
<label><att>norm</att></label>
<item>gives a normalized form of information given by the source 
text in a non-normalized form</item>
<label><att>split</att></label>
<item>gives the list of split values for a merged form</item>
</list>

<!-- <list type=gloss>                                        -->
<!-- <label><att>expand</att> <item>gives expanded form       -->
<!-- <label><att>norm</att> <item>gives normalized form       -->
<!-- <label><att>split</att> <item>gives the list of split    -->
<!-- values for a merged form                                 -->
<!-- <label><att>value</att> <item>gives a value which has    -->
<!-- no print realization                                     -->
<!-- </list>                                                  -->

<p>When the lexical view is dominant, the following attributes may be
used to record the editorial view:

<list type=gloss>
<label><att>orig</att></label>
<item>gives the original string or is the empty string when the 
element does not appear in the source text.</item>
<label><att>mergedin</att></label>
<item>gives a reference to another element, where the original 
appears as a merged form.</item>
</list>

<!-- <list type=gloss>                                        -->
<!-- <label><att>orig</att> <item>gives the original          -->
<!-- string or is the empty string when the element           -->
<!-- does not appear in original                              -->
<!-- <label><att>mergedin</att> <item>gives a                 -->
<!-- reference to another tag with id=xxx where the           -->
<!-- original appears as a merged form                        -->
<!-- </list>                                                  -->

<p>One attribute is useful in either view:

<list type=gloss>
<label><att>opt</att></label>
<item>indicates whether the element is optional or not</item>
</list>

<!-- <list type=gloss>                                        -->
<!-- <label><att>opt</att> <item>identifies an optional element -->
<!-- </list>                                                  -->

<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:

<eg>
<![ CDATA [
  <usg type=dom norm='nautical'>naut.</usg>
]]>
</eg>

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:

<eg>
<![ CDATA [
  <usg type=dom orig='naut.'>nautical</usg>
]]>
</eg>

<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:

<eg>
<![ CDATA [
<form>
  <orth>delay</orth>
  <form type=infl>
    <orth norm='delayed' extent=part>-ed</orth>
    <tns norm='pst,pstp'></tns>
  </form>
  <form type=infl>
    <orth norm='delaying' extent=part>-ing</orth>
    <tns norm='prsp'></tns>
  </form>
</form>
]]>
</eg>

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>The lexical view might be encoded thus:

<eg>
<![ CDATA [
<form>
  <orth>delay</orth>
  <form type=infl>
    <orth orig='-ed'>delayed</orth>
    <tns orig=''>pst</tns>
    <tns orig=''>pstp</tns>
  </form>
  <form type=infl>
    <orth orig='-ing'>delaying</orth>
    <tns orig=''>prsp</tns>
  </form>
</form>
]]>
</eg>

<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&eacute;ostimuline</q>:

<q rend=display>
<hi rend=bold>thyr(&eacute;)ostimuline</hi> [tiR(e)ostimylin] ...
</q>

With the editorial view dominant, this entry might begin thus:

<eg>
<![ CDATA [
<form>
  <orth split='thyrostimuline,
               thyr&eacute;ostimuline'>
        thyr(&eacute;)ostimuline</orth>
  <pron split='tiRostimylin,
               tiReostimylin'>
        tiR(e)ostimylin</pron>
</form>
]]>
</eg>

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.

<eg>
<![ CDATA [
<form>
  <orth orig='thyr(&eacute;)ostimuline' id=o1>
        thyrostimuline</orth>
  <pron orig='tiR(e)ostimylin' id=p1>
        tiRostimylin</pron>
</form>
<form>
  <orth mergedin=o1>thyr&eacute;ostimuline</orth>
  <pron mergedin=p1>tiReostimylin</pron>
</form>
]]>
</eg>

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

<eg>
<![ CDATA [
<form>
  <orth next=o2 id=o1>thyr</orth>
  <orth prev=o1 next=o3 opt=y id=o2>&eacute;</orth>
  <orth prev=o2 id=o3>ostimuline</orth>

  <pron next=p2 id=p1>tiR</pron>
  <pron prev=p1 next=p3 opt=y id=p2>e</pron>
  <pron prev=p2 id=p3>ostimylin</pron>
</form>
]]>
</eg>

<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
recomended, however, when long spans of text are involved, or when the
optional part contains embedded tags.

<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> /"p&amp;stl US: p&amp;"stel/ n 1 (picture drawn with) coloured
chalk made into crayons. 2...   [OALD]
</q>

<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:

<eg>
<![ CDATA [
<sense n='1'>
  <def>coloured chalk made into crayons</def>
  <def>picture drawn with coloured chalk made into crayons</def>
</sense>
]]>
</eg>

<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:

<eg>
<![ CDATA [
<sense n='1'>
  <def id=d1 opt=y next=d2>picture drawn with</def>
  <def id=d2 prev=d1>coloured chalk made into crayons</def>
</sense>
]]>
</eg>

<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 (&icirc;les fpl) Canaries
fpl...  [C/R]
</q>

<eg>
<![ CDATA [
<re type=cmpd>
  <usg type=dom>Geog</usg>
  <form>
    <orth>Canary Isles</orth>
    <orth>Canaries</orth>
  </form>
  <trans id=t1 opt=y next=t2>
    <tr>&icirc;les</tr>
    <gen>f</gen>
    <number>pl</number>
  </trans>
  <trans id=t2 prev=t1>
    <tr>Canaries</tr>
    <gen>f</gen>
    <number>pl</number>
  </trans>
</re>
]]>
</eg>

<div4><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 SGML ID/IDREF mechanism may be used to show the original
location of material transposed in an encoding of the lexical view.

<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>dictionaries</ident>:

<list type=gloss>
<label><att>opt</att></label>
<item>indicates whether the element is optional or not</item>
</list>

<p>For example:

<q rend=display> <hi rend=bold>pinna</hi>
<code>("pIn@)</code> n., pl. -nae (-ni:) or -nas. [CED] </q>

<eg>
<![ CDATA [
<form>
  <orth>pinna</orth>
  <pron>'pIn@</pron>
  <anchor id=p1>
  <form type=infl>
    <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=p1>n</pos>         <!-- moved -->
</gramGrp>
]]>
</eg>

<!-- < 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                                                 -->

<!-- <eg> <![ CDATA [ clem (klEm) or clam vb. clems,          -->
<!-- clemming, clemmed or clams, clammimg, clammed ...        -->
<!-- [CED] ]]> </eg>                                          -->

<!-- <p>Textual view:                                         -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <entry>                                                  -->
<!--                                                          -->
<!-- <var>                                                    -->
<!--                                                          -->
<!-- <rdg view=editorial>                                     -->
<!-- <form>                                                   -->
<!--   <orth>clem</orth>                                      -->
<!--   <pron>klEm</pron>                                      -->
<!-- </form>                                                  -->
<!-- <form>                                                   -->
<!--     <orth id=o1>clam</orth>                              -->
<!-- </form>                                                  -->
<!-- </form>                                                  -->
<!-- <gramGrp>                                                -->
<!--   <pos 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>                                                 -->
<!--                                                          -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<div3><head>Attributes for Dictionary Elements</head>

<p>The attributes provided for all dictionary-specific elements
and documented in
this section are defined thus:

<eg id=dedimv>
<![ CDATA [
<!-- 12.5.4:  Attributes for dictionary work                  -->
<!ENTITY % a.dictionaries '
          mergedin           IDREF               #IMPLIED
          expand             CDATA               #IMPLIED
          location           IDREF               #IMPLIED
          value              CDATA               #IMPLIED
          norm               CDATA               #IMPLIED
          orig               CDATA               #IMPLIED
          split              CDATA               #IMPLIED
          opt                (y | n)             n'             >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>



<!-- $Id: p2difr.odd,v 1.9 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    * $Log: p2difr.odd,v $
    * Revision 1.9  1998/02/05 17:14:35  tei
    * correct EG rend type
    *
    * Revision 1.8  1998/01/31 18:50:07  tei
    * fix eg
    *
    * Revision 1.6  94/03/27  16:29:41  lou
    * *** empty log message ***
    *
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    *
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    *
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    *
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    * -->
<!-- Revisions:                                               -->
<!-- 94-01-15 : MSM : add para introducing dtdfrag., change comment -->
<!-- 94-01-14 : MSM : mentioned, not cited                    -->
<!-- 94-01-14 : MSM : note that the oald example is not TEI   -->
<!-- 94-01-12 : MSM : change examples to use entryFree        -->
<!-- 94-01-12 : MSM : correct typo                            -->
<!-- 94-01-11 : MSM : revise                                  -->
<!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   -->
<!-- 94-01-09 : MSM : add a dtdFrag                           -->
<!-- 93-10-19 : MSM : Added RCS id                            -->
<!-- 93-04-12 : MSM : delete N att on divs                    -->

<div2 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>
element is defined, which allows for much wider variation in entry
structure.  Its content model places no constraints at all upon the
entry:  any element defined in this chapter, as well as all the
phrase-level and inter-level elements defined in the core tag set, can
appear anywhere in an entry.  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>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.

<eg rend=other>
<![ CDATA [
<ent h=demigod><hwd>demi|god</hwd><pr><ph>"demIgQd</ph></pr>
<hps ps=n>
<hsn><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<cf>Hercules</cf><pr><ph>"h3:kjUli:z</ph></pr></def>
</hsn></hps></ent>

[OALD electronic]
]]>
</eg>

<eg>
<![ CDATA [
<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</><pron>"h3:kjUli:z</pron></def>
</entryFree>
]]>
</eg>

<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>(%bIrI"A:nI) </code> any of a
variety of Indian dishes...[from Urdu] [CED] </q>

<eg>
<![ CDATA [
<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>

]]>
</eg>

<p>The declaration of <gi>entryFree</gi> is given above in section
<ptr target=DIen>.  It allows any elements defined for use within
dictionary entries to appear within it, in any order.

<eg id=dedifr>
<![ CDATA [
<!-- 12.6:  Model class for unstructured dictionary entries   -->
<!-- This entity declares the class of elements defined       -->
<!-- specifically for use in dictionary entries, except       -->
<!-- those which are included in the phrase class. This       -->
<!-- class is used in defining the 'free' dictionary entry.   -->

<!ENTITY % x.dictionaryParts ''                                 >
<!ENTITY % m.dictionaryParts '%x.dictionaryParts case | colloc 
           | def | eg | etym | form | gen | gramGrp | hom | 
           hyph | itype | lbl | mood | number | orth | per | 
           pos | pron | re | sense | stress | subc | superentry 
           | syll | tns | tr | trans | usg | xr'                >
<!-- This fragment is used in sec. 12.1                       -->
]]>
</eg>








</div1>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->
             <!-- 12 Printed Dictionaries -->
