<?tei:SOF p2fsal.odd ?>
<!-- $Id: p2fsal.odd,v 1.4 1998/02/01 17:45:38 tei Exp $ -->
<!--*
    * $Log: p2fsal.odd,v $
    * Revision 1.4  1998/02/01 17:45:38  tei
    * killing off extendargs
    *
    * Revision 1.3  94/03/21  14:12:03  lou
    * second mass typo clearup
    * 
    * Revision 1.2  1994/01/04  01:39:13  msmcq
    * revision for P3
    * -->
<!-- Revisions:                                               -->
<!-- 94-01-03 : MSM : change exx:  join, alt use TARGETS=     -->
<!-- 94-01-03 : MSM : Added RCS id                            -->
<!-- 93-12-20 : MSM : provide correct idrefs for chapter SA   -->
<div2 id=FSAL name='Alfalfa'>
<head>Alternative Features and Feature Values</head>
 
<p>In this section, two methods of representing the alternation (ambiguity
or uncertainty) of features and feature values are presented.  The first
of these methods is to be used for nonsystematic or sporadic markup of
alternation of individual features or values; it makes use of the
special-purpose <gi>fAlt</gi> and <gi>vAlt</gi> elements.  The other is to
be used for systematic markup of alternation and for the alternation of
groups of features or values; it makes use of the general-purpose
<gi>alt</gi> element introduced in section <xref type=div2 target=SAAT>.
The <gi>fAlt</gi> and <gi>vAlt</gi> elements have the following
description and attributes.
 
<tagList>
<tagDesc tagDoc=FALT atts='mutExcl'>
<tagDesc tagDoc=VALT atts='mutExcl'>
</tagList>
 
<p>To illustrate the use of the <gi>fAlt</gi> element to represent the
alternation of features, suppose one is uncertain whether a particular
real estate advertisement describes a house with two bedrooms or with two
bathrooms.  This uncertainty can be represented as follows.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <fAlt>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bedrooms><nbr value=2></f>
    </fAlt>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>This representation leaves unspecified whether or not the alternation
is <term>mutually exclusive</term> (i.e. whether having two bathrooms
excludes the possibility of having two bedrooms and vice versa).  To make
this aspect of the alternation explicit, one can specify a value for the
<att>mutExcl</att> attribute, as follows.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <fAlt mutExcl=N>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bedrooms><nbr value=2></f>
    </fAlt>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>The <gi>fAlt</gi> element can also be used to represent uncertainty
about whether the number of bathrooms is two or three, as follows; note
that the attribute value <att>mutExcl=Y</att> can be inferred for the
<gi>fAlt</gi> element in this example.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <fAlt>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bathrooms><nbr value=3></f>
    </fAlt>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>However, the <tag>f name=number.of.bathrooms</tag> element in this example
can be factored out of the alternation, and a <gi>vAlt</gi> element used
instead to represent the alternation of just the feature values, as
follows.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <f name=number.of.bathrooms>
    <vAlt><nbr value=2><nbr value=3></vAlt>
    </f>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>The <gi>fAlt</gi> and <gi>vAlt</gi> elements can also be used to
indicate certain alternations among values of features organized as sets,
bags or lists.  For example, suppose one uses a <tag>f name=extras
org=set</tag> element in feature structures for real estate listings to
represent items that are mentioned to enhance a property's sales
value, such as whether it has a pool or a good view.  Now suppose for a
particular listing, the extras include an alarm system and a fenced-in
yard, and either a pool or a jacuzzi (but not both).  This situation could
be represented, using the <gi>vAlt</gi> element, as follows.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <f name=extras org=set>
    <str>alarm system</str>
    <str>fenced-in yard</str>
    <vAlt mutExcl=Y>
      <str>pool</str>
      <str>jacuzzi</str>
      </vAlt>
    </f>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>Now suppose the situation is like the preceding except that one is
also uncertain whether the property has an alarm system or a fenced-in
yard, or possibly both.  This can be represented as follows.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <f name=extras org=set>
    <vAlt mutExcl=N>
      <str>alarm system</str>
      <str>fenced-in yard</str>
      </vAlt>
    <vAlt mutExcl=Y>
      <str>pool</str>
      <str>jacuzzi</str>
      </vAlt>
    </f>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>Finally, suppose that the listing specifies that the property has a
finished basement, and that it also has either an alarm system and a
pool or a fenced-in yard and a jacuzzi.  This situation cannot be
represented using the <gi>vAlt</gi> element, because the alternation
holds between subsets of two values each.  It can, however, be
represented using the <gi>fAlt</gi> element, as follows; note that the
<gi>str</gi> element with the value <code>finished basement</code>
element must be repeated.
 
<eg><![ CDATA [
<fs type='real estate listing'>
<!-- ... -->
  <fAlt mutExcl=Y>
    <f name=extras org=set>
      <str>finished basement</str>
      <str>alarm system</str>
      <str>pool</str>
      </f>
    <f name=extras org=set>
      <str>finished basement</str>
      <str>fenced-in yard</str>
      <str>jacuzzi</str>
      </f>
    </fAlt>
<!-- ... -->
  </fs>
]]>
</eg>
 
<p>If a large number of ambiguities or uncertainties involving a
relatively small number of features and values need to be represented,
it is recommended that the general-purpose <gi>alt</gi> element
discussed in section <xref target=SAAT> be used, rather than
the special-purpose <gi>fAlt</gi> and <gi>vAlt</gi> elements.  The use of
the <gi>alt</gi> element avoids the need to explictly represent the
alternating elements more than once.
 
<p>For example, suppose one has set up a <gi>fsLib</gi> element
containing feature structures representing the morphological
structures of classical Greek inflected words, along with collections
of individual features and feature values, encoded by <gi>fLib</gi>
and <gi>fvLib</gi> elements as appropriate.  The following example
shows how one might then represent the morphological structure of a
feminine gender, accusative case, plural number noun form in classical
Greek, such as <cited>the&aacute;s</cited> <gloss>goddesses</gloss>
discussed in section <xref target=FSSY>:
 
<eg>
<![ CDATA [
<fsLib type='noun structures'>
  <!-- ... -->
  <!-- plural accusative feminine noun -->
  <fs id=WNGFKANP type='noun structure' feats='Wn Gf Ka Np'></fs>
  <!-- ... -->
  </fsLib>
 
<fLib type='morphological features'>
  <f id=WN  name=word.class fVal=nn></f>
  <!-- ... -->
  <f id=GF  name=gender fVal=fe></f>
  <!-- ... -->
  <f id=KA  name=case fVal=ac></f>
  <!-- ... -->
  <f id=NP  name=number fVal=pl></f>
  <!-- ... -->
  </fLib>
 
<fvLib type='morphological feature values'>
  <!-- ... -->
  <sym id=NN value=noun>
  <!-- ... -->
  <sym id=FE value=feminine>
  <!-- ... -->
  <sym id=AC value=accusative>
  <!-- ... -->
  <sym id=PL value=plural>
  <!-- ... -->
  </fvLib>
]]>
</eg>
 
<p>Now consider the noun form <cited>thea&iacute;</cited>
<gloss>goddesses</gloss>, which is analyzable as a feminine plural
noun form in either the nominative or the vocative case.  We may represent
this ambiguity by adding the following entries to the <gi>fsLib</gi>,
<gi>fLib</gi>, and <gi>fvLib</gi> elements in the preceding example;
assume that appropriate entries for unambiguous nominative and vocative
case forms have already been entered.
 
<eg><![ CDATA [
<!-- Add the following to the feature-structure library (FSLIB) -->
  <!-- plural nominative-or-vocative feminine noun -->
  <fs id=WNGFKNVNP type='noun structure' feats='Wn Gf Knv Np'></fs>
 
<!-- Add the following to the feature library (FLIB) -->
  <!-- CASE=nominative or vocative -->
  <f id=KNV name=case fVal=novo></f>
 
<!-- Add the following to the feature value library (FVLIB) -->
  <!-- nominative or vocative -->
  <alt id=NOVO targets='no vo'>
]]>
</eg>
 
<p>If the <gi>fvLib</gi> element is not used, and specifications for
particular feature values are entered as content of the <tag>f
name=...</tag> elements in the <gi>fLib</gi> element, then the ambiguity
can be represented as follows.
 
<eg>
<![ CDATA [
<fsLib type='noun structures'>
  <!-- ... -->
  <!-- plural nominative-or-vocative feminine noun -->
  <fs id=WNGFKNVNP type='noun structure' feats='Wn Gf Knv Np'></fs>
  <!-- ... -->
  </fsLib>
 
<fLib type='morphological features'>
  <!-- ... -->
  <f id=KN name=case><sym value=nominative>
  <!-- ... -->
  <f id=KV name=case><sym value=vocative>
  <!-- ... -->
  <alt id=KNV targets='Kn Kv'>
  <!-- ... -->
  </fLib>
]]>
</eg>
 
<p>The <gi>alt</gi> element together with the <gi>join</gi> element can,
unlike the <gi>fAlt</gi> and <gi>vAlt</gi> elements, be used to express
alternations between sets of features.  An example of such an
alternation is found in certain feminine gender Greek noun forms ending
in <cited>-as</cited>, such as <cited>pe&iacute;ras</cited>
<gloss>attempt(s)</gloss>, which may be analyzed as having either
genitive case and singular number features or accusative case and plural
number features, as follows (again, assuming the existence of other
elements and identifier attributes for simple features and values).
 
<eg><![ CDATA [
<!-- Add the following to the FSLIB element -->
  <!-- feminine noun, either genitive singular or accusative plural -->
  <fs id=WNGFKG.NsKa.Np type='noun structure' feats='Wn Gf Kg.NsKa.Np'>
    </fs>
 
<!-- Add the following to the FLIB element  -->
  <join id=KG.Ns targets='Kg Ns'> <!-- genitive singular -->
  <join id=KA.Np targets='Ka Np'> <!-- accusative plural -->
 
  <!-- alternation:  gen. sg. or acc. plural -->
  <alt id=KG.NsKa.Np targets='Kg.Ns KaNp'>
]]>
</eg>
 
<p>Here are the formal declarations of the <gi>fAlt</gi> and
<gi>vAlt</gi> elements.
 
<dtdFrag id=DFSAL n='Alternative features and feature values'
         file=teifs2>
<tagDecl tagDoc=FALT>
<tagDecl tagDoc=VALT>
</dtdFrag>
<?tei:EOF p2fsal.odd ?>
