<!-- $Id: p2te.odd,v 1.11 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    **
    * $Log: p2te.odd,v $
    * Revision 1.11  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.10  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.9  94/04/06  10:32:44  lou
    * kill initial note; revise some titles; add rendering info
    *
    * Revision 1.8  1994/04/01  16:39:21  msmcq
    * Changes during validation of DTD
    *
    * Revision 1.7  1994/03/28  14:52:47  lou
    * more typos
    *
    * Revision 1.6  1994/03/27  16:31:42  lou
    * semiofinal
    *
    * Revision 1.3  1994/01/04  19:49:17  msmcq
    * make dtd frags produce ent file
    *
    * Revision 1.2  1993/07/29  21:08:26  msmcq
    * add RCS id, log
    * -->
<!-- * start of Chapter III.7 * -->
<!-- TE: TEI P2 chapter for Terminology                       -->
<!-- Revisions:                                               -->
<!-- 6 apr: kill note; change titles; add rend info -->
<!-- 94-03-31 : MSM : protect teistr invocation               -->
<!-- 94-03-31 : MSM : define temix                            -->
<!-- 94-03-30 : MSM : four corrections / policy changes from A Melby -->
<!-- 19 mar: LB:  title change; JL's typos fixed -->
<!-- 93-10-05 : MSM : fix for DTD                             -->
<!-- 93-06-03 : MSM : change IDREFs to class docs             -->
<!-- 20 may 93 : LB : incorporate AM's post-Eynsham comments  -->
<!-- 92-12-23 : MSM : finish revision for publication         -->
<!-- 92-12-23 : MSM : rev for pub                             -->
<!-- 92-12-21 : MSM : eliminate flatterm, I thought I said    -->
<!-- 92-12-21 : MSM : extensive stylistic changes             -->
<!-- 92-12-18 : MSM : changes for publication                 -->
<!-- 92-12-17 : MSM : tag inline tags as tag                  -->
<!-- 92-12-17 : MSM : correct some format problems in SEW's work -->
<!-- 92-12-15 : SEW : edit P2X file per AI7 consensus         -->
<!-- 92-11-23 : MSM : correct typos in xrefs                  -->
<!-- 92-11-23 : MSM : correct NOTE atts, for peDecl read entDecl -->
<!-- 92-11-21 : MSM : reorganize, rework, add tagdocs etc     -->
<!-- 92-11-21 : MSM : change doctype to ODD                   -->
<!-- 92-11-19 : MSM : change system ids                       -->
<!-- 92-11-06:  WP : Made changes after seeing output.        -->
<!-- 92-11-05:  WP : Incorporated MSM's suggestions/cont.d    -->
<!-- 92-11-04 : MSM : Added comments on retagging, tag usage  -->
<!-- 92-11-03 : WP : made P2X file from AI7D18 TEI1 file      -->

<div1 id="TE" n="13" type="chapter"><head>Terminological Databases</head>

<!-- < div2 id=TEna name='section'>                           -->
<!-- < head>The Nature of Terminological Data< /head>         -->

<p>Terminological information generally resides in <term>terminology
databases</term> (<term>TDBs</term>), but for SGML applications, these
collections of data can be viewed as documents.  A document containing
terminological data is made up of <term>terminological entries</term>.
Typically, a terminological entry treats a single concept and contains
information on the assignment of single or multi-word terms to this
concept.  Bilingual and multilingual terminological entries deal with
harmonized or very closely related concepts in two or more languages
that are treated as functional equivalents in the context of a specific
domain or subdomain.  Terminological data can take the form of
terminological databases (TDBs) or can be used to print hardcopy
terminological documents, such as terminological dictionaries,
technical vocabularies, or thesauri.
<!--
<note place=foot>
The primary responsibility for this chapter was borne by TEI work
group AI7 (terminological data).  The text was originally drafted
by Alan K. Melby (chair), Sue Ellen Wright, Gerhard Budin, and
Gregory Shreve; the DTD fragments were drafted by Gregory Shreve.
Further revisions were made by the above and by Richard Strehlow.
</note>
--></p>

<p>The TEI description of terminological data was originally designed
primarily as a <term>terminology interchange format</term>
(<term>TIF</term>) to allow users of terminology databases to exchange
database records.  In this guise it is called the <term>Electronic
Terminology Interchange Format</term> (<term>E-TIF</term>).  The
exchange of database records is especially important in practice
because the structure of terminological records varies considerably
from TDB to TDB, reflecting differences of design and of user needs.
Users of TDBs frequently need to interchange data in order to access
expert information and to prevent the duplication of effort, but
differences in software, hardware, and methodology complicate
interchange.  A universal interchange format is a crucial element in
making interchange easier.</p>

<p>The tag set defined in this chapter may also be used to mark up
documents for the purpose of printing <term>terminological
dictionaries</term> and <term>vocabularies</term>, or exchanging them
in electronic form.  Printed terminological documents differ from
terminological databases in that they are frequently divided into
sections and subsections and include prose text in introductions, etc.
When used for marking up printed documentation, we can speak of the tag
set defined here as a <term>Print Terminology Interchange Format</term>
(<term>P-TIF</term>).</p>

<p>Because printed terminological dictionaries differ from
terminological databases, problems may arise if one attempts to use the
same electronic document both for printing and to exchange records
among databases.  A printed terminological dictionary may contain
material not suitably encoded for introduction into database records.
Domain and subdomain information may be implied by the arrangement of
<gi>termEntry</gi>s rather than by explicit domain specifications
within the individual entries.</p>

<p>Other interchange difficulties include differences
between term entry styles used in prescriptive and descriptive
terminology work and problems arising from differences in the degree of
detail used to classify data elements in different databases.
(The term <term>data element</term> is used by terminologists to
refer to <gloss>the smallest defined individual items of
information</gloss>, regardless of whether they are represented as
SGML elements, SGML attributes, or fields or columns in a database.
That is the usage followed here.) Procedures for addressing these
various problems are treated in more detail in another document, the
<bibl><title>TEI / LISA / ISO - TIF --- Terminology Interchange
Format --- A Tutorial</title> (1993)</bibl>.
<note place="foot"> This document is reprinted in <title>TermNet
News</title>, no 40, 1993, pp 5-64; copies are also available from
Infoterm, z.Hd. Herrn Dr. Gerhard Budin, Heinestra&szlig;e 38, Postfach
No. 130, A-1021 Vienna, Austria.</note></p>

<div2 id="TEen"><head>The Terminological Entry</head>

<p>The basic unit of terminology management is the <term>terminological
entry</term>.  A terminological entry documents information pertaining
to a concept and generally speaking contains at least one
<term>term</term>.  In addition to the term, various kinds of
descriptive and administrative data are recorded concerning the term,
the concept to which it is assigned, and relationships to other terms
and concepts.  Administrative information supports the management of the
terminology database or document.

<!-- LB revised slightly for consistency with other parts of P2 -->
<!-- and to avoid need to define table element for this chap only --></p>

<p>A sample terminological entry consists of a series of entries like
the following:
<list type="gloss">
<label>subject field</label>                <item>appearance of materials</item>
<label>English term</label>                 <item>opacity</item>
<label>grammatical information, part of speech, English term</label> <item>noun</item>
<label>definition, English term</label>
<item>degree of obstruction to the transmission of visible light</item>
<label>bibliographical source, English term information</label>
<item>ASTM Standard E284</item>
<label>responsibility for English term information</label>
<item>ASTM Technical Committee E12</item>
<label>German term</label>
<item>Opazit&auml;t</item>
<label>grammatical information, part of speech, German term</label> <item>noun</item>
<label>grammatical information, gender, German term</label> <item>feminine</item>
<label>definition, German term</label>
<item>Ma&szlig; f&uuml;r die Lichtdurchsichtigkeit</item>
<label>bibliographical source, German term information</label>
<item>HFdn1983-382</item>
<label>responsibility, German term information</label>
<item>DIN Technical Committee for paper products</item>
<label>French term</label>
<item>opacit&eacute;</item>
<label>grammatical information, part of speech, French term</label> <item>noun</item>
<label>grammatical information, gender, French term</label> <item>feminine</item>
<label>definition, French term</label>
<item>rapport du flux lumineux incident au flux lumineux transmis ou
r&eacute;fl&eacute;chi par un noircissement photographique</item>
<label>bibliographical source, French term information</label>
<item>HJdi1986</item>
<label>responsibility, French term information</label>
<item>C.I.R.A.D.</item>
</list>

<!-- here's the original table in case you disagree -->

<!-- <table rend='LL'> -->
<!-- <head>Example 1:  Sample terminological entry</head> -->
<!-- AM notes that the heading should not be over the right column only -->
<!-- <r><c>subject field                <c>appearance of materials -->
<!-- <r><c>English term                 <c>opacity -->
<!-- <r><c>grammatical information, part of speech, English term <c>noun -->
<!-- <r><c>definition, English term -->
<!-- <c>degree of obstruction to the transmission of visible light -->
<!-- <r><c>bibliographical source, English term information -->
<!-- <c>ASTM Standard E284 -->
<!-- <r><c>responsibility for English term information -->
<!-- <c>ASTM Technical Committee E12 -->
<!-- <r><c>German term -->
<!-- <c>Opazit&auml;t -->
<!-- <r><c>grammatical information, part of speech, German term <c>noun -->
<!-- <r><c>grammatical information, gender, German term <c>feminine -->
<!-- <r><c>definition, German term -->
<!-- <c>Ma&szlig; f&uuml;r die Lichtdurchsichtigkeit -->
<!-- <r><c>bibliographical source, German term information -->
<!-- <c>HFdn1983-382 -->
<!-- <r><c>responsibility, German term information -->
<!-- <c>DIN Technical Committee for paper products -->
<!-- <r><c>French term -->
<!-- <c>opacit&eacute; -->
<!-- <r><c>grammatical information, part of speech, French term <c>noun -->
<!-- <r><c>grammatical information, gender, French term <c>feminine -->
<!-- <r><c>definition, French term -->
<!-- <c>rapport du flux lumineux incident au flux lumineux transmis ou -->
<!-- r&eacute;fl&eacute;chi par un noircissement photographique -->
<!-- <r><c>bibliographical source, French term information -->
<!-- <c>HJdi1986 -->
<!-- <r><c>responsibility, French term information -->
<!-- <c>C.I.R.A.D. -->
<!-- </table> --></p></div2>

<div2 id="TEta"><head>Tags for Terminological Data</head>

<p>The following sections define elements for use in tagging
terminological data.  The elements and attributes listed are based on
empirical studies.  The studies indicated the use of a wide variety of
different data element types (data categories or database field types),
but this variety can be reduced to a relatively small set of SGML
elements and attributes expressing notions common to most, if not all,
TDBs.  Those elements and attributes are defined here.  In addition,
the global TEI attributes defined in section <ptr target="STga">, and
the elements and attributes defined in chapter <ptr target="CO">, can
all be used in terminological applications.</p>

<p>When tagging terminological data, three elements constitute the set
of <term>non-floating elements</term>:  <gi>term</gi>,
<gi>otherForm</gi>, and <gi>descrip</gi>.  All other elements function
as <term>floating elements</term>, including:  <gi>admin</gi>,
<gi>note</gi>, <gi>gram</gi>, <gi>bibl</gi>, <gi>biblFull</gi>,
<gi>date</gi>, <gi>table</gi>, <gi>formula</gi>, <gi>figure</gi>, and
the linking elements (<gi>ptr</gi>, <gi>xptr</gi>, <gi>ref</gi>, and
<gi>xref</gi>). The rules for combining floating with non-floating
elements are spelled out below in section <ptr target="TEne">, and in
section <ptr target="TEfl">.

<list type=gloss>
<label><gi>term</gi></label>
<item>contains a single-word, multi-word or symbolic designation 
which
is regarded as a technical term.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the term using some typology.</item>
</list>
</item>
<label><gi>termEntry</gi></label>
<item>contains a single complete entry for one concept
expressed 
in one language and comprising one or more terms and their

associated descriptive and administrative data, or, in 
bilingual and
multilingual terminology work, two or more 
very closely related concepts
comprising one or more terms 
in each language and their associated
descriptive and 
administrative data.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the term entry using some typology, preferably 
the dictionary of data element types specified in ISO WD 12 
620.</item>
</list>
</item>
<label><gi>tig</gi></label>
<item>within a <gi>termEntry</gi> element, contains information 
elements
associated with a single term.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the <gi>tig</gi> using some typology, preferably 
the dictionary of data element types specified in ISO WD 12 
620.</item>
</list>
</item>
<label><gi>otherForm</gi></label>
<item>contains an
alternate designation for the concept treated 
by the
term entry, such as a synonym.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the <gi>otherForm</gi> using some typology, 
preferably the dictionary of data element types specified 
in ISO WD 12 620.</item>
</list>
</item>
<label><gi>ofig</gi></label>
<item>within a <gi>tig</gi> element, contains information

elements relating to a single <gi>otherForm</gi>.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the other-form information group according to 
some convenient typology, preferably the dictionary of data 
element types specified in ISO WD 12 620.</item>
</list>
</item>
<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>descrip</gi></label>
<item>within a <gi>termEntry</gi> element, contains a definition,
context or explanation used to explain or define the 
concept represented
by a <gi>term</gi> or an 
<gi>otherForm</gi>.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the description using some convenient typology, 
preferably the dictionary of data element types specified 
in ISO WD 12 620.
Suggested values include:
<list type=gloss>
<label><term>definition</term></label>
<item>The description provides all the information needed to 
differentiate one concept from all other related concepts 
in the given domain.</item>
</list></item>
</list>
</item>
<label><gi>admin</gi></label>
<item>within a <gi>termEntry</gi> element, contains 
administrative
information pertaining to data management 
and documentation of the
entry.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>identifies the administrative event or information using 
some typology, preferably the dictionary of data element 
types specified in ISO WD 12 620.
Suggested values include:
<list type=gloss>
<label><term>updated</term></label>
<item>The <gi>admin</gi> element describes the update or 
modification of the data element or entry.</item>
<label><term>created</term></label>
<item>The <gi>admin</gi> element describes the creation of the 
data element or entry.</item>
<label><term>domain</term></label>
<item>The element indicates the subject area to which a concept 
pertains.</item>
<label><term>approved</term></label>
<item>The <gi>admin</gi> element describes the final approval of 
the data element or entry.</item>
<label><term>subdomain</term></label>
<item>The element indicates the subdomain of the subject area to 
which the concept pertains.</item>
<label><term>responsibility</term></label>
<item>The <gi>admin</gi> element identifies the agency or 
individual responsible for the data element or entry.</item>
</list></item>
</list>
</item>
</list>

<!-- need to add reference to gramGrp here when tagdoc available --></p>

<p>As indicated, these elements all possess a <att>type</att> attribute,
used to classify the generic elements so as to match the classifications
used by TDBs.  The <att>type</att> attributes allow specific
items of information not defined in the DTD to be tagged as one of
the defined elements with an appropriate <att>type</att> value.  The
possible values of <att>type</att> thus constitute a sizable open list.</p>

<p>At the time of publication, work is under way in ISO Technical
Committee 37, Sub-Committee 3, Working Group 1 to compile an official
dictionary of data element types (data categories) for use in
terminology work, which will eventually provide the core for a complete
list of <att>type</att> attribute values.  This data element dictionary
will appear as ISO 12 620.  The attribute values that occur in the
examples shown in this chapter represent a subset of those that will be
defined in ISO 12 620.

<!-- <p>The <gi>ofig</gi> element will only rarely be         -->
<!-- needed, since detailed information about other form      -->
<!-- terms will typically be found in another term entry,     -->
<!-- either pointed to, or contained by, another              -->
<!-- <gi>tig</gi>.                                            --></p>

<p>The <gi>ofig</gi> and <gi>otherForm</gi> elements are not necessary
if each potential <gi>otherForm</gi> element is recast as a term in
its own <gi>tig</gi>.  For example, a term could be placed in a
<tag>tig type=synonym</tag>.</p>

<p>When the base tag set described in this chapter is used, the
following attributes are added to the set
of global attributes:

<list type=gloss>
<label><att>group</att></label>
<item>indicates the group (term and related elements) to which 
this element should be associated by specifying a string 
matching the <att>n</att> attribute value on an appropriate 
element.</item>
<label><att>depend</att></label>
<item>indicates the parent element to which this element should 
be associated by specifying a string matching the 
<att>n</att> attribute value on an appropriate element.</item>
<label><att>grpPtr</att></label>
<item>indicates the group (term and related elements) to which 
this element should be associated by specifying its unique 
identifier, where this is available.</item>
<label><att>depPtr</att></label>
<item>indicates the parent element to which this element should 
be associated by specifying its unique identifier, where 
this is available.</item>
</list>

For discussion of the usage of these attributes, see below,
section <ptr target="TEfl">.</p>

<p>Among the TEI core elements, the following are most likely to be found
necessary in encoding terminological data; for fuller descriptions see
the appropriate sections in chapter <ptr target="CO">. In the case of the
<gi>date</gi> element, it should be noted that the ISO format (<code>YYYY-MM-DD</code>)
is preferred for terminology entries.

<list type=gloss>
<label><gi>note</gi></label>
<item>contains a note or annotation.</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>date</gi></label>
<item>contains a date in any format.</item>
<label><gi>bibl</gi></label>
<item>contains a loosely-structured bibliographic citation of 
which
the sub-components may or may not be explicitly 
tagged. </item>
<label><gi>biblStruct</gi></label>
<item>contains a structured bibliographic citation, in which only
bibliographic subelements appear and in a specified order. </item>
<label><gi>biblFull</gi></label>
<item>contains a fully-structured bibliographic citation, in 
which all
components of the TEI file description
are 
present.
<!-- except maybe the source.desc? --></item>
<label><gi>table</gi></label>
<item>contains text displayed in tabular form, in
rows and 
columns.</item>
<label><gi>figure</gi></label>
<item>indicates the location of a graphic, illustration, or 
figure.</item>
<label><gi>formula</gi></label>
<item>contains a mathematical or other formula.</item>
</list>
</p>

<p>Like all other elements defined in the TEI DTDs, all elements in the
base tag set for terminology possess the following global attributes:

<list type=gloss>
<label><att>lang</att></label>
<item>indicates the language of the element content, usually 
using a two- or three-letter code from ISO 639.</item>
<label><att>n</att></label>
<item>gives a number (or other label) for an element, which is 
not necessarily unique within the document.</item>
<label><att>id</att></label>
<item>provides a unique identifier for the element bearing the ID 
value.</item>
</list>
</p>

<p>Using the tags defined here, the example given above in section
<ptr target="TEen"> might be tagged thus:<note place="foot">In this example, as
in the others, white space has been liberally used for the sake of
legibility; in practice most actual encodings would use less white
space.</note>

<eg>
<![ CDATA [
<!-- Example 2a:  Nested Term Entry -->
<termEntry>
     <admin type='domain'> appearance of materials </admin>
     <tig lang=en>
	  <term> opacity </term>
	  <gram type=pos> n </gram>
	  <descrip type='definition'> degree of obstruction to the
	  transmission of visible light </descrip>
	  <ptr type='bibliographic' target='ASTM.E284'>
	  <admin type='responsibility' resp='ASTM E12'> </admin>
     </tig>
     <tig lang=de>
	  <term> Opazit&auml;t </term>
	  <gram type=pos> n </gram>
	  <gram type=gen> f </gram>
	  <descrip type='definition'> Ma&szlig; f&uuml;r die
	  Lichtdurchsichtigkeit </descrip>
	  <ref type='bibliographic' target='HFdn1983'> p. 383 </ref>
	  <admin type='responsibility' resp='DIN TC for paper
	  products'></admin>
     </tig>
     <tig lang=fr>
	  <term> opacit&eacute; </term>
	  <gram type=pos> n </gram>
	  <gram type=gen> f </gram>
	  <descrip type='definition'> rapport du flux lumineux
	  incident au flux lumineux transmis ou r&eacute;fl&eacute;chi
	  par un noircissement photographique </descrip>
	  <ptr type='bibliographic' target='HJdi1986'>
	  <admin type='responsibility' resp='C.I.R.A.D.'> </admin>
     </tig>
</termEntry>
]]>
</eg></p>

<p>Both the <tag>ptr type='bibliographic' target='ASTM.E284'</tag> and
<tag>ref type='bibliographic' target='HFdn1983'</tag> elements in the
example indicate links to complete bibliographical entries included in
the back matter element of the same document.  <mentioned>HFdn1983</mentioned>
is a source reference code for a book, generated according to ISO/TC 37
WI 18, <title>Coding of Bibliographic References in Terminology Work and
Terminography</title> (1991).  Its full bibliographic record would be:

<eg>
<![ CDATA [
<!-- Example 2b:  Full Bibliographic Entry -->
<biblFull>
       <titleStmt id=HFdn1983>
	      <title> W&ouml;rterbuch technischer Begriffe mit 4300
	      Definitionen nach DIN </title>
	      <editor> Henry G. Freeman </editor>
       </titleStmt>
       <editionStmt>
	      <edition> III </edition>
       </editionStmt>
       <extent> 703 pp </extent>
       <publicationStmt>
	      <publisher> Beuth Verlag GmbH </publisher>
	      <pubPlace> Berlin and K&ouml;ln </pubPlace>
	      <date> 1983 </date>
       </publicationStmt>
       <sourceDesc><p>Compiled for the standards of the DIN (Deutsches
	      Institut f&uuml;r Normung).</p>
       </sourceDesc>
</biblFull>
]]>
</eg></p>

<p>Further examples, including alternate encodings of this term entry,
are given below in section <ptr target="TEfl">, and section <ptr
target="TEflne">.</p>

<p>The formal definition of these elements depends on which style of
markup is being used; for discussion of the two styles, see the
following section, <ptr target="TEba">.  For the formal declarations for
the two styles, see sections <ptr target="TEdtN">, and <ptr
target="TEdtF">.</p></div2>

<div2 id="TEba"><head>Basic Structure of the Terminological Entry</head>

<p>A terminological entry is identified with the <gi>termEntry</gi> tag
and contains one or more terms marked with the tag <gi>term</gi>, which
may appear with associated SGML elements.  A single term and its
associated SGML elements (such as <gi>gram</gi>, <gi>descrip</gi>,
<gi>admin</gi>) constitute a <term>term information group</term>,
<gi>tig</gi>.  A <gi>termEntry</gi> may be made up of one or more
<gi>tig</gi>s.</p>

<p>There are two structural descriptions for <gi>termEntry</gi>s:
<list type="bullets">
<item><term>nested</term> <gi>termEntry</gi>s</item>
<item><term>flat</term> <gi>termEntry</gi>s</item>
</list>
The nested structure is preferred, especially for interchange with
unknown partners. The flat structure provides an option that can be
used between interchange partners whose systems exhibit fairly
similar structures. The flat structure may also be used as an intermediate
form for systems making the transition to the nested format.</p>

<div3 id="TEne"><head>Nested Term Entries</head>

<p>A nested <gi>termEntry</gi> uses SGML to represent the hierarchical
relationships implicit in the terminological entry by utilizing the
following principles of embedding and adjacency.
<list type="bullets">
<item>Rule of embedding in nested term entries:
      Elements that constitute a part of another element are embedded
      inside the parent element.</item>
<item>Rules of adjacency in nested term entries:
<list type="gloss">
<label>N1</label><item>Any element that appears in a <gi>termEntry</gi>
outside a <gi>tig</gi> applies to the entire <gi>termEntry</gi>.
</item>
<!-- changed from 'before first TIG':  inclusion exceptions   -->
<!-- allow admin, note, etc. between tigs, and after the      -->
<!-- last tig. -MSM					      -->

<label>N2</label><item>Any element that appears in a <gi>tig</gi> before the
<gi>term</gi> element applies to the entire <gi>tig</gi>.</item>
<label>N3</label><item>Any floating element that appears after a non-floating
element (i.e., after <gi>term</gi>, <gi>otherForm</gi> or
<gi>descrip</gi>) and before the next non-floating element, refers to
the immediately preceding non-floating element unless otherwise
indicated using the <att>depend</att> attribute. (See section <ptr
target="TEflne">, for a full discussion of the <att>depend</att>
attribute.)</item>
</list></item>
</list>

<!-- <p>As implied above, part-whole relationships are        -->
<!-- expressed by embedding parts within wholes.  Logical     -->
<!-- relationships such as super- and subordination, or       -->
<!-- thematic relationships, are represented by one of the    -->
<!-- rules of adjacency.                                      --></p>

<p>The conversion routine that creates the nested entry infers the
language of the <gi>tig</gi> from the language of the <gi>term</gi>, a
process that can be construed as <socalled>upward inheritance</socalled>
from <gi>term</gi> to <gi>tig</gi>.  Standard TEI <socalled>downward
inheritance</socalled> applies for all the elements embedded in the
<gi>tig</gi>:  their language is that of the <gi>tig</gi>, unless this
default value is overridden by stating a new value.</p>

<p>An example of a nested term entry was given in section <ptr
target="TEta">.</p></div3>

<div3 id="TEfl"><head>Flat Term Entries Using Rules of Adjacency</head>

<p>The flat terminological entry does not use the <gi>tig</gi> element
to enclose a term and its associated elements.	Instead, it provides
other mechanisms to express the relationships that occur within and
among entries in a TDB, while at the same time allowing the different
types of entries found in different source TDBs to be represented in
very natural ways.  The difference between the nested and flat
terminological entries is that, while both can express the same
information, the nested structure represents the logical hierarchy
implicit within the entry by embedding elements in one another, while
the flat entry does not represent the logical hierarchy within the entry
in this way.  Since many existing TDBs do not overtly indicate any
hierarchical structure such as that represented in a nested entry, the
flat entry may be more apt to reflect the organization of data elements
within an entry found in the particular source TDB, whereas the nested
entry more obviously characterizes an ideal abstract structure of the
term entry.  In flat entries, terms and their associated elements are
grouped by means of the following rules of adjacency:

<list type="gloss">
<head>Rules of adjacency in flat <gi>termEntry</gi>s:</head>

<label>F1</label><item>Any element that appears in a <gi>termEntry</gi> before
the first <gi>term</gi> is assumed to apply to the entire
<gi>termEntry</gi>.</item>
<label>F2</label><item>Any floating element that appears after a non-floating
element (i.e., after <gi>term</gi>, <gi>otherForm</gi> or
<gi>descrip</gi>) and before the next non-floating element refers to
the immediately preceding non-floating element unless otherwise
indicated using the <att>depend</att> attribute. (See section <ptr
target="TEflne">, for a full discussion of the <att>depend</att>
attribute.)</item>
</list></p>

<p>Encoded using the flat style, the example given in section <ptr
target="TEta">, might look like this:

<eg id="TEExfl"><![ CDATA[
<!-- Example 3:  Flat <TermEntry>			      -->
<termEntry>
     <admin type='domain'> appearance of materials </admin>
     <term lang=en> opacity </term>
     <gram type=pos> n </gram>
     <descrip type='definition'> degree of obstruction to the
     transmission of visible light </descrip>
     <ptr type='bibliographic' target='ASTM.E284'>
     <admin type='responsibility' resp='ASTM E12'></admin>
     <term lang=de> Opazit&auml;t </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> Ma&szlig; f&uuml;r die
      Lichtdurchsichtigkeit
     </descrip>
     <ref type='bibliographic' target='HFdn1983'> p. 383 </ref>
     <admin type='responsibility' resp='DIN TC for paper products'>
     </admin>
     <term lang=fr> opacit&eacute; </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> rapport du flux lumineux
     incident au flux lumineux transmis ou r&eacute;fl&eacute;chi
     par un noircissement photographique </descrip>
     <ptr type='bibliographic' target='HJdi1986'>
     <admin type='responsibility' resp='C.I.R.A.D.'> </admin>
</termEntry>
]]>
</eg></p></div3>

<div3 id="TEflne"><head>Flat Term Entries Using Group and Depend Attributes</head>

<p>In practice, there are term entries where elements are ordered in
such a way that the rules of adjacency cannot be used.	For instance, in
Example 3 the <gi>ptr</gi> and <gi>ref</gi> linking elements refer to the
immediately preceding <gi>descrip</gi> information.  The <gi>admin
type='responsibility'</gi> elements as represented here also refer to the
<gi>descrip</gi> element. It may, however, be desirable for the
bibliographic reference to refer not only to the quoted material in the
descriptive element, but also to the term itself. Because the second
rule of adjacency dictates that all floating elements following a non-
floating element refer to that non-floating element, a mechanism is
required to <socalled>point</socalled> to the <gi>term</gi> if the
floating element depends on the <gi>term</gi> itself.</p>

<p>There are also other exceptions to the adjacency rules: in some term
entries elements are associated with a <gi>term</gi> other than the
immediately preceding <gi>term</gi>.  Such entries may be called
<term>discontiguous flat term entries</term>, since the constituents of
a term information group may not be adjacent.  In such entries,
information pertaining to the entire terminological entry may not always
appear at the beginning of the entry (i.e., prior to the introduction of
a term).</p>

<p>Such an entry might be encoded as follows:

<eg id="Teexdi"><![ CDATA[
<!-- Example 4:  Discontiguous Flat <termEntry>  -->
<termEntry n=texyz>
     <term lang=en n=1> opacity </term>
     <gram type=pos depend=1> n </gram>
     <term lang=de n=2> Opazit&auml;t </term>
     <gram type=pos depend=2> n </gram>
     <gram type=gen depend=2> f </gram>
     <term lang=fr n=3> opacit&eacute; </term>
     <gram type=pos depend=3> n </gram>
     <gram type=gen depend=3> f </gram>

     <descrip type='definition' group=1 n=endes1> degree of
	obstruction to the transmission of visible light  </descrip>
     <descrip type='definition' group=2 n=dedes1> Ma&szlig; f&uuml;r die
	Lichtdurchsichtigkeit  </descrip>
     <descrip type='definition' group=3 n=frdes1> rapport du
	flux lumineux incident au flux lumineux transmis ou
	r&eacute;fl&eacute;chi par un noircissement photographique
	</descrip>
     <ptr type='bibliographic' depend=endes1 target='ASTM.E284'>
     <admin type='responsibility' depend=endes1 resp='ASTM E12'> </admin>
     <ref type='bibliographic' depend=dedes1 target='HFdn1983'>
	p. 383 </ref>
     <admin type='responsibility' depend=dedes1
	resp='DIN.TC.for.paper'></admin>
     <ptr depend=frdes1 type='bibliographic' target='HJdi1986'>
     <admin type='responsibility' depend=frdes1
	resp='C.I.R.A.D.'> </admin>
     <admin type='domain' depend=texyz> appearance of materials
     </admin>
</termEntry>
]]>
</eg></p>

<p>In the above example, <att>depend</att> elements indicate that the
material tagged with this attribute is related to the targeted element.
The <att>group</att> elements indicate that the information so marked is
part of an implicit <gi>tig</gi>, i.e. that it pertains either to the
term or to the entire implicit <gi>tig</gi>. Items linked to other
elements by <att>depend</att> do not require the <att>group</att>
attribute because they are associated with the group already by virtue
of their relation to elements that are themselves associated with the
group.</p>

<p>So as to describe appropriate relationships in discontiguous flat
<gi>termEntry</gi>s, it is necessary to define a pointing mechanism that
allows any non-adjacent element to be related to an implicit term
information group and therefore to the <gi>term</gi> with which it is
associated or to some other specific element.

<!-- LB added following para --></p>
<p>Two methods are provided to represent this association. For terminology
files in which unique identifiers for all <gi>term</gi> elements cannot
be assumed (as will often be the case in interchange), the <att>group</att>
and <att>depend</att> attributes should be used. For terminology files in
which unique SGML identifiers can be provided, the <att>grpPtr</att> and
<att>depPtr</att> attributes should be used. The two pairs of attributes
have identical significance as far as the association of elements is
concerned.</p>

<p>The <att>group</att> attribute associates an element with a specific
term, or with an implicit term information group:  its value must be the
same as the <att>n</att> attribute on the <gi>term</gi> element being
pointed to.  During interchange, the <att>group</att> attribute would be
used to extract and assemble all the elements related to a specific term
information group from a discontiguous flat <gi>termEntry</gi> by
matching them to the <att>n</att> attributes on the terms.
<!-- LB deleted following parenthesis as redundant -->
<!-- (Note:<att>id</att> values must be unique within the document, whereas -->
<!-- <att>n</att> values need not be unique; within the base tag set defined -->
<!-- in this chapter, <att>n</att> values are required to be unique only -->
<!-- within each individual terminological entry.  In other TEI bases, they -->
<!-- are not constrained at all.)  -->
The <att>group</att> pointer accounts for
the kind of relationship represented by the principle of embeddedness
within a <gi>tig</gi> in a nested term entry.


<!-- removed footnote LB -->
<!--  <note place=foot>An -->
<!-- alternative proposal would make <att>group</att> and <att>depend</att> -->
<!-- take allowed values of <term>IDREF</term> or <term>IDREFS</term>, and -->
<!-- thus perform the linkage based on the <att>id</att> attribute, rather -->
<!-- than the <att>n</att> attribute, of the target element.  This alternative -->
<!-- is still being explored by the responsible work groups.</note> --></p>

<p>The <att>depend</att> attribute associates an element with some
other specific element: its value must be the same as the <att>n</att>
attribute on the element being pointed to.  As shown in the last line
of Example 4, the <att>depend</att> attribute can also point to the
entire terminological entry by targeting a value of <att>n</att>
indicated in the <gi>termEntry</gi> element.  If for any reason the
grammatical information pertaining to a term does not follow the term
immediately, this information must be linked to the term with the
<att>depend</att> attribute.

<!-- LB added following para --></p>
<p>In terms of the extended pointer notation defined in chapter
<ptr target="SA">, the specification <code>group=2</code> is synonymous with
<code>HERE ANCESTOR  (1 TERMENTRY) DESCENDANT (1 TERM N 2)</code>, and the
specification <code>depend=3</code> is synonymous with <code>HERE ANCESTOR
(1 TERMENTRY) DESCENDANT (1 * N 3)</code>.</p>

<p>To summarize the behavior of <att>group</att> and <att>depend</att>,
the <att>group</att> attribute identifies an implicit <gi>tig</gi>,
whereas the <att>depend</att> attribute implies relatedness. If there
is any ambiguity with respect to the rules of adjacency, one should use
<att>depend</att>.</p>

<p>In Example 4, the English term <mentioned>opacity</mentioned> is identified
as <att>n</att>=1, and all other elements associated with this
<gi>tig</gi> are marked as <att>group</att>=1; in German, the term and
all its associated elements are identified as <att>n</att>=2 and
<att>group</att>=2, respectively; in French, the term and associated
elements are marked <att>group</att>=3.  Since the bibliographical
references are displaced from the descriptive information with which
they are associated, the descriptions are identified with
<att>n</att>=endes1, <att>n</att>=dedes1, and <att>n</att>=frdes1,
respectively. The <gi>ptr</gi> and <gi>ref</gi> elements are then
identified with <att>depend</att> attributes that target the
appropriate descriptions.  Even if the elements in the entry were
adjacent to each  other in the entry, this convention would be
essential if one wanted to indicate that the source applied to the
<gi>term</gi> and hence to the entire <gi>tig</gi>, rather than just to
the <gi>descrip</gi> element itself.</p></div3>


<div3 id="TEre"><head>References between Term Entries</head>

<p>Terminology documents utilize a variety of cross-references between
<gi>termEntry</gi>s, for instance to link to bibliographic entries or
between equivalents in different languages, synonyms and related terms
and concepts.  These references are usually implemented using the TEI
linking elements <gi>ptr</gi> and <gi>ref</gi>, together with a value of
the attribute <att>type</att>.  If, as is the case with the reference to
ASTM E284, the total bibliographic source description is contained in
the <socalled>target</socalled> element of the linking element, use
<gi>ptr</gi>.  If, on the other hand, a page number is included, this
page number must appear as the content of a linking element introduced
by the <gi>ref</gi> element.</p>

<p>Examples:
<eg>
<![ CDATA [
 <ptr type='bibliographic' target='ASTM.E284'>
]]>
</eg>
or
<eg>
<![ CDATA [
 <ref type='bibliographic' target='HFdn1983'> p. 383 </ref>
]]>
</eg></p>

<p>If the full bibliographical citation is included in the
<gi>termEntry</gi> itself, linking elements are unnecessary and the
citation can be marked using the <gi>bibl</gi>, <gi>biblStruct</gi>, or
<gi>biblFull</gi> elements.  For further discussion of bibliographic
citations and references, see section <ptr target="CObi">.</p></div3></div2>

<div2 id="TEdt"><head>Overall Structure of Terminological Documents</head>


<p>To enable the base tag set for terminology, a parameter entity
<ident type="pe">TEI.terminology</ident> must be declared within the
document type subset, the value of which is <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.terminology 'INCLUDE' >
 ]>
]]>
</eg>

This declaration makes available all of the elements described in this
chapter, in addition to the core elements described in chapter <ptr
target="CO">. The default structure for terminological documents
is similar to that
defined by chapter <ptr target="DS">:
within the <gi>TEI.2</gi> element they
contain a <gi>teiHeader</gi> and a <gi>text</gi>.  The <gi>text</gi>
element, in turn, contains as usual a <gi>body</gi> element, optionally
preceded by a <gi>front</gi> and followed by a <gi>back</gi>.  The
<gi>body</gi> may contain a series of <gi>termEntry</gi> elements,
which may optionally be grouped into sections tagged with the same
elements (<gi>div</gi>, <gi>div0</gi>, <gi>div1</gi>, etc.) as defined in
section <ptr target="DSdiv">.

<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>body</gi></label>
<item>contains the whole body of a single unitary
text, 
excluding any front or back
matter.</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>div2</gi></label>
<item>contains a second-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div3</gi></label>
<item>contains a third-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div4</gi></label>
<item>contains a fourth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div5</gi></label>
<item>contains a fifth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div6</gi></label>
<item>contains a sixth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div7</gi></label>
<item>contains the smallest possible subdivision of the front, 
body or
back of a text, larger than a paragraph.</item>
</list>


<!-- remainder of this section may need revision, but not just now --></p>

<p>In order to support both the flat and the nested styles of markup,
three distinct DTD fragments for terminology are provided.
<list type="bullets">
<item>teiterm2</item>
<item>teite2n</item>
<item>teite2f</item>
</list></p>

<p>In file <ident type="file">teiterm2.dtd</ident>, the top-level elements for the
terminology base are defined, and a subordinate parameter entity,
<ident type="ent">termtags</ident> is defined and referred to. By
default, this entity refers to file <ident type="file">teite2n.dtd</ident>, which defines the DTD for nested
markup; if the flat style of markup is to be used, the document's DTD
subset should define <ident type="ent">termtags</ident> as referring to
the file <ident type="file">teite2f.dtd</ident>, as shown in the
examples in section <ptr target="TEfl">.
<!-- this is not shown in the examples anywhere in that section (LB) -->


<eg id=dtetop>
<![ CDATA [
<!-- 13.4: TEIterm2.DTD: Base tag set for terminological data -->
<!-- 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, embed the default text structure elements.        -->

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


<!ENTITY % termtags system 'teite2n.dtd'                        >
%termtags;
]]>
</eg>

<!-- <tagDecl tagDoc=text>                                    -->
<!-- <tagDecl tagDoc=body>                                    -->
<!-- <tagDecl tagDoc=div>                                     -->
<!-- <tagDecl tagDoc=div0>                                    -->
<!-- <tagDecl tagDoc=div1>                                    -->
<!-- <tagDecl tagDoc=div2>                                    -->
<!-- <tagDecl tagDoc=div3>                                    -->
<!-- <tagDecl tagDoc=div4>                                    -->
<!-- <tagDecl tagDoc=div5>                                    -->
<!-- <tagDecl tagDoc=div6>                                    -->
<!-- <tagDecl tagDoc=div7>                                    --></p>

<p>In file <ident type="file">teiterm2.ent</ident>, terminology-specific
extensions to the TEI element class system are defined, including the
classes <ident type="class">terminology</ident>, <ident type="class">comp.terminology</ident>, <ident type="class">terminologyInclusions</ident>, and <ident type="class">terminologyMisc</ident>.

<eg id=dteent>
<![ CDATA [
<!-- 13.4: TEIterm2.ent: Base tag set for terminological data -->
<!-- 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.         -->


<!ENTITY % x.comp.terminology ''                                >
<!ENTITY % m.comp.terminology '%x.comp.terminology termEntry'   >
<!ENTITY % seq '(%m.common; | %m.comp.terminology;)* '          >
<!ENTITY % mix.terminology '| %m.comp.terminology'              >

<!ENTITY % x.terminologyInclusions ''                           >
<!ENTITY % m.terminologyInclusions '%x.terminologyInclusions 
           date | dateStruct | note | ptr | ref | xptr | xref'  >
<!ENTITY % x.terminologyMisc ''                                 >
<!ENTITY % m.terminologyMisc '%x.terminologyMisc admin | 
           descrip'                                             >

<!-- Add attributes to the set of global attributes:          -->

<!ENTITY % a.terminology '
          grpPtr             IDREF               #IMPLIED
          depend             CDATA               #IMPLIED
          depPtr             IDREF               #IMPLIED
          group              CDATA               #IMPLIED'      >

]]>
</eg>
</p>

<div3 id="TEdtN"><head>DTD Fragment for Nested Style</head>

<p>In file <ident type="file">teite2n.dtd</ident> the following
definitions are found, which define the elements used in the nested
markup style:

<eg id=dtene>
<![ CDATA [
<!-- 13.4.1:  Elements for nested-style terminological data   -->

<!-- The nested structure is used for data interchange and    -->
<!-- represents a canonical structured form for terminology   -->
<!-- entries, which differs from the less structured forms    -->
<!-- frequently used to store data in terminological          -->
<!-- databases.                                               -->

<!ELEMENT termEntry     - O  ((%m.terminologyMisc)*, tig+) 
                                                  
                                                 +(%m.terminologyInclusions)
                                                                >
<!ATTLIST termEntry          %a.global;
          type               CDATA               #IMPLIED       >
<!-- Notes, descrip(s) and admin(s) are allowed in the        -->
<!-- termEntry to provide documentation that applies to the   -->
<!-- whole entry.                                             -->


<!-- tig='term information group'                             -->

<!-- ofig='otherform information group'                       -->


<!ELEMENT tig           - O  ((%m.terminologyMisc)*, (term, 
                             gram*), (%m.terminologyMisc)*, 
                             ofig*)                             >
<!ATTLIST tig                %a.global;
          type               CDATA               #IMPLIED       >
<!-- Order is significant: term, descrip(s), ofig(s) or       -->
<!-- otherform(s)                                             -->


<!ELEMENT ofig          - O  ((%m.terminologyMisc)*, 
                             (otherForm, gram*), 
                             (%m.terminologyMisc)*)             >
<!ATTLIST ofig               %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT otherForm     - O  (%paraContent;)                    >
<!ATTLIST otherForm          %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT descrip       - O  (%paraContent;)                    >
<!ATTLIST descrip            %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT admin         - O  (%paraContent;)                    >
<!ATTLIST admin              %a.global;
          resp               CDATA               #IMPLIED
          date               CDATA               %ISO-date
          type               CDATA               #IMPLIED       >
<!-- We define a.dictionaries as the empty string, since we   -->
<!-- are not now using the tag set for dictionaries.          -->

<!ENTITY % a.dictionaries ''                                    >
<!ELEMENT gram          - O  (%paraContent;)                    >
<!ATTLIST gram               %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >
]]>
</eg>
</p></div3>


<div3 id="TEdtF"><head>DTD Fragment for Flat Style</head>

<p>In file <ident type="file">teite2f.dtd</ident> the following
definitions, which provide support for the flat markup style, are
found:

<eg id=dtefl>
<![ CDATA [
<!-- 13.4.2:  Elements for flat-style terminological data     -->
<!-- The flat structure is used to represent a variety of     -->
<!-- terminology documents that occur in practice and which   -->
<!-- do not follow the form of the nested interchange         -->
<!-- format. The flat representation allows for a less rigid  -->
<!-- structure, but provides a rich mechanism for reflecting  -->
<!-- inter-element relations.                                 -->


<!-- The declaration of termEntry enforces appearance of at   -->
<!-- least one term element in a termEntry, which may be      -->
<!-- preceded by descrip, admin, note, otherform, or gram.    -->
<!-- There may be multiple notes, admins, descrips            -->
<!-- otherforms, and grams appearing in any order. xRef,      -->
<!-- date, biblRef can appear in all positions in termEntry.  -->


<!ELEMENT termEntry     - O  ( (%m.terminologyMisc | otherForm 
                             | gram | 
                             %m.terminologyInclusions)*, (term, 
                             (%m.terminologyMisc | otherForm | 
                             gram | %m.terminologyInclusions)* 
                             )+ )                               >
<!ATTLIST termEntry          %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT otherForm     - O  (%paraContent;)                    >
<!ATTLIST otherForm          %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT descrip       - O  (%paraContent;)                    >
<!ATTLIST descrip            %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT admin         - O  (%paraContent;)                    >
<!ATTLIST admin              %a.global;
          resp               CDATA               #IMPLIED
          date               CDATA               %ISO-date
          type               CDATA               #IMPLIED       >
<!-- We define a.dictionaries as the empty string, since we   -->
<!-- are not now using the tag set for dictionaries.          -->

<!ENTITY % a.dictionaries ''                                    >
<!ELEMENT gram          - O  (%paraContent;)                    >
<!ATTLIST gram               %a.global;
                             %a.dictionaries;
          type               CDATA               #IMPLIED       >

]]>
</eg>
</p></div3></div2>

<div2 id="TEeg"><head>Additional Examples of Term Entries</head>

<p>The tag set defined in this chapter is designed to accommodate the
variety of structures that occur in TDBs; this section shows the
how the same information may be encoded in different ways, depending
on local convenience or preferences.  Example 5 gives an entry from an
ISO terminological standard.  Example 6 treats this English-French
equivalent pair as a single nested terminological entry, whereas Example
7 splits the information into two nested entries with cross-references.
Example 8 shows the same data as a flat terminological entry with
adjacent elements, whereas Example 9 groups the elements according to
element type, which requires the use of pointers in order to reconstruct
the implicit terminological information group from discontiguous
elements.</p>

<p>The interchange of terminological data between TDBs requires
an export routine (to E-TIF) and an import routine (from E-TIF).
For interchange between unknown partners, it may be desirable to
normalize the encoding method rather than allow all the options
presented in this section.  The effect of normalization would be that
import routines become easier to implement while export routines
become more difficult to implement.  At the time of this publication,
work is under way in ISO Technical Committee 37, Subcommittee 3,
Working Group 3 on a normalized version of E-TIF called ISO [DIS]
12 200.  Some aspects of normalization under consideration are to use
only the nested representation and avoid the use of the following
options:  divisions within the <gi>body</gi>, the <gi>otherForm</gi>
element, the <att>group</att> and <att>depend</att> attributes,
elements before the <gi>term</gi> element in a <gi>tig</gi>, inclusion
exceptions other than <gi>ptr</gi> and <gi>xptr</gi>, and paragraph
content other than <code type="kw">#PCDATA</code> in the elements
<gi>admin</gi> and <gi>gram</gi>.</p>

<div3 id="TEeg5"><head>Example Term Entry from ISO 472</head>
<!>
<!-- See hard copy to see how SEW used different fonts for    -->
<!-- different items within definition, below.                -->
<p>The following term entry is taken from ISO 472:1988, <title>Plastics
--- Vocabulary</title>, Bilingual edition (Geneva:  ISO, 1988), p. 84.
The original uses typographic characteristics to represent different
data element types within the term entry, not all of which have been
retained in the reproduction of this sample.  As prescribed by ISO
layout guidelines,<note place="foot">ISO 10241, <title>Preparation and
layout of international terminology standards</title>, 1993.</note>
the original text is printed in Helvetica, with English and French
information presented in two parallel columns; head terms appear in bold
face, notes in a smaller font size than the main text, and terms
referred to in the cross references are printed in italics.
<!>
<!-- LB moved paragraphs inside item -->
<list type="gloss">
<label>thermal degradation</label>
<item><p>The entirety of all deleterious chemical modifications of plastic
at elevated temperature.
</p><p rend="small">
NOTE --- It is essential to report the temperature and other
environmental conditions at which the phenomenon is studied.
</p><p>
See also <emph rend="it">ageing</emph>, <emph rend="it">degradation</emph> and
<emph rend="it">deterioriation</emph>.</p></item>
<label>d&eacute;composition thermique</label>
<item><p>Ensemble
de toutes les modifications chimiques nuisibles d'un plastique &agrave;
temp&eacute;rature &eacute;lev&eacute;e.
</p><p rend="small">
NOTE --- Il est essentiel d'indiquer la temp&eacute;rature et les
autres conditions d'environnement dans lesquelles le
ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;.
</p><p>
Voir aussi <emph rend="it">viellissement</emph>, <emph rend="it">d&eacute;gradation</emph>
et <emph rend="it">d&eacute;t&eacute;rioration</emph>.</p></item>
</list></p></div3>

<div3 id="TEeg6"><head>The Example Treated as a Single Term Entry in Nested Form</head>

<p>This treatment assumes that both the English and French terms are
treated together in the same entry. The elements grouped together at
the top of the term entry apply to the entire entry. Only the first of
the three cross-referenced terms is included in this example; it is
represented by a <gi>ptr</gi> link which targets a term entry (related
concept) contained in the same document.  The <att>id</att> values
used here are purely arbitrary.

<eg><![ CDATA[
<termEntry id=te84.11>
    <admin type='domain'> plastics </admin>
    <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
    <admin type='creation' date='1988'
           resp='ISO/TC 61, Plastics'> </admin>
    <ptr type='relatedTerm' target='te04.06'>

    <tig lang=en>
          <term> thermal degradation </term>
          <gram type=pos> n </gram>
          <descrip type='definition'> The entirety of all
          deleterious chemical modifications of plastic at
          elevated temperature. </descrip>
          <note> It is essential to report the temperature and
          other environmental conditions at which the phenomenon
          is studied.  </note>
     </tig>

     <tig lang=fr>
          <term> d&eacute;composition thermique </term>
          <gram type=pos> n </gram>
          <gram type=gen> f </gram>
          <descrip type='definition'> Ensemble de toutes les
          modifications chimiques nuisibles d'un plastique &agrave;
          temp&eacute;rature &eacute;lev&eacute;e. </descrip>
          <note> Il est essentiel d'indiquer la temp&eacute;rature et
          les autres conditions d'environnement dans lesquelles le
          ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>
     </tig>
</termEntry>

<!-- Referenced term entry: -->

<termEntry id=te04.06>
     <tig lang=en>
          <term> ageing </term>
          <!-- ... -->
     </tig>

     <tig lang=fr>
          <term> vieillissement </term>
          <!-- ... -->
     </tig>
 </termEntry>
]]>
</eg></p></div3>

<div3 id="TEeg7"><head>The Example Treated as Two Separate Term Entries in Nested Form</head>

<p>This example takes cognizance of the fact that some TDBs treat each
term in a single <gi>termEntry</gi> instead of grouping all the
information for a single concept into a single <gi>termEntry</gi>. The
rationale behind this approach is frequently that no two languages
truly provide harmonized concepts, although in the case of
standardized terminology it can generally be assumed that concepts
have been harmonized.  The significant difference in encoding that
occurs in this type of system is that <gi>ptr</gi> linking elements
are required more frequently to link to term equivalents and related
terms in other entries in the same document. Since there is only one
<gi>tig</gi> in each entry, the <gi>ptr</gi> element could come at the
beginning, as shown in the previous example, or inside the
<gi>tig</gi> as shown below.

<eg><![ CDATA[
<termEntry id=te84.11.en>

     <admin type='domain'> plastics </admin>
     <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
     <admin type='creation' date='1988' resp='ISO/TC 61, Plastics'></admin>

     <tig lang=en>
          <term> thermal degradation </term>
          <gram type=pos> n </gram>
          <descrip type='definition'> The entirety of all
          deleterious chemical modifications of plastic at
          elevated temperature. </descrip>
          <note> It is essential to report the temperature and
          other environmental conditions at which the phenomenon
          is studied.  </note>
          <ptr type='relatedTerm' target='te04.06.en'>
          <ptr type='equivalent' lang=fr target='te84.11.fr'>
     </tig>

</termEntry>

<termEntry id=te84.11.fr>

      <admin type='domain'> plastics </admin>
      <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
      <admin type='creation' date='1988'
             resp='ISO/TC 61, Plastics'> </admin>

     <tig lang=fr>
          <term> d&eacute;composition thermique </term>
          <gram type=pos> n </gram>
          <gram type=gen> f </gram>
          <descrip type='definition'> Ensemble de toutes les
          modifications chimiques nuisibles d'un plastique &agrave;
          temp&eacute;rature &eacute;lev&eacute;e. </descrip>
          <note> Il est essentiel d'indiquer la temp&eacute;rature et
          les autres conditions d'environnement dans lesquelles le
          ph&eacute;nom&grave;ne est &eacute;tudi&eacute;. </note>
          <ptr type='relatedTerm' target='te04.06.fr'>
          <ptr type='equivalent' lang=en target='te84.11.en'>

     </tig>

</termEntry>

<!-- Referenced term entry: -->

<termEntry id=te04.06.en>
     <tig lang=en>
          <term> ageing </term>
          <!-- ... -->
     </tig>
</termEntry>

<termEntry id=te04.06.fr>
     <tig lang=fr>
          <term> vieillissement </term>
          <!-- ... -->
     </tig>
</termEntry>
]]>
</eg></p></div3>

<div3 id="TEeg8"><head>The Example Treated as a Flat Term Entry Using Adjacency Rules</head>

<p>This version of Example 5 uses a flat style of encoding, following
the pattern of many existing TDBs; elements associated with a given
term follow it immediately:

<eg><![ CDATA[
<termEntry id=te84.11>
     <admin type='domain'> plastics </admin>
     <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
     <admin type='creation' date='1988'
            resp='ISO/TC 61, Plastics'> </admin>
     <term lang=en> thermal degradation </term>
     <gram type=pos> n </gram>
     <descrip type='definition'> The entirety of all deleterious
     chemical modifications of plastic at elevated temperature.
     </descrip>
     <note> It is essential to report the temperature and other
     environmental conditions at which the phenomenon is studied.
     </note>
     <term lang=fr> d&eacute;composition thermique </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> Ensemble de toutes les
     modifications chimiques nuisibles d'un plastique &agrave;
     temp&eacute;rature &eacute;lev&eacute;e. </descrip>
     <note> Il est essentiel d'indiquer la temp&eacute;rature et les
     autres conditions d'environnement dans lesquelles le
     ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>
     <ptr type='relatedTerm' target='te04.06'>
</termEntry>

<!-- Referenced term entry: -->

<termEntry id=te04.06>
     <term lang=en> ageing </term>
     <!-- ... -->
     <term lang=fr> vieillissement </term>
     <!-- ... -->
</termEntry>
]]>
</eg></p></div3>

<div3 id="TEeg9"><head>The Example Treated as a Flat Term Entry Not Using Adjacency Rules</head>

<p>Many translation-oriented terminologists who work with half-screen
popup windows
prefer the following layout because it enables them to see the
various <gi>term</gi> options at the top part of their display window
without having to scroll into the body of the <gi>termEntry</gi>. Note
in this case that the <gi>ref</gi> element links the bibliographic
information to the entire entry.

<eg><![ CDATA[
<termEntry id=te84.11 n=te84.11>
     <term lang=en n=1> thermal degradation </term>
     <gram type=pos depend=1> n </gram>
     <term lang=fr n=2> d&eacute;composition thermique
     </term>
     <gram type=pos depend=2> n </gram>
     <gram type=gen depend=2> f </gram>

     <descrip type='definition' group=1> The entirety of all
     deleterious chemical modifications of plastic at elevated
     temperature. </descrip>
     <descrip type='definition' group=2> Ensemble de toutes les
     modifications chimiques nuisibles d'un plastique &agrave;
     temp&eacute;rature &eacute;lev&eacute;e. </descrip>
     <note group=1> It is essential to report the temperature and
     other environmental conditions at which the phenomenon is
     studied. </note>
     <note group=2> Il est essentiel d'indiquer la temp&eacute;rature et
     les autres conditions d'environnement dans lesquelles le
     ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>

     <ptr type='relatedConcept' target='te04.06'>
     <admin depend=te84.11 type='domain'> plastics </admin>
     <ref type='bibliographic' depend=te84.11 target='ISO.472-1988'>
     p. 84 </ref>
     <admin depend=te84.11 type='creation' date='1988'
     resp='ISO/TC 61, Plastics'>
     </admin>
</termEntry>

<!-- Referenced term entry: -->
<termEntry id=te04.06 n=te04.06>
     <term lang=en n=1> ageing </term>
     <!-- ... -->
     <term lang=fr n=2> vieillissement </term>
     <!-- ... -->
</termEntry>
]]>
</eg>
</p></div3></div2></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:
-->
             <!-- 13 Terminological Data -->
<!-- &p2.cb;             Combined Bases -->
<!>

