<?tei:SOF p2fsfl.odd ?>
<!-- $Id: p2fsfl.odd,v 1.4 1998/01/31 19:56:11 tei Exp $ -->
<!--*
    * $Log: p2fsfl.odd,v $
    * Revision 1.4  1998/01/31 19:56:11  tei
    * remove extendarg from eg
    *
    * Revision 1.3  94/03/21  14:12:04  lou
    * second mass typo clearup
    * 
    * Revision 1.2  1994/01/04  01:39:13  msmcq
    * revision for P3
    * -->
<!-- Revisions:                                               -->
<!-- 94-01-03 : MSM : add BODY element to example             -->
<!-- 94-01-03 : MSM : Added RCS id                            -->
<!-- 93-12-23 : MSM : in example change ARGS att to targFunc  -->
<!-- 93-12-22 : MSM : fix a problem in an example             -->
 
<div2 id=FSFL>
<head>Feature, Feature-Structure and Feature-Value Libraries</head>
 
<p>As the example in the preceding section illustrates, the direct
encoding of features structures can be verbose.  Consequently, the effort
of encoding large numbers of feature structures in this manner could be
enormous, and could result in the creation of enormous files.  To reduce
the size and complexity of the task of encoding feature structures, one
may use the <att>feats</att> attribute of the <gi>fs</gi> element to point
to one or more of the features of that element.  This indirect method of
encoding feature structures presumes that the <gi>f</gi> elements are
assigned unique SGML <att>id</att> values, and are collected together in
<gi>fLib</gi> elements (<term>feature libraries</term>).  In turn, feature
structures can be collected together in <gi>fsLib</gi> elements
(<term>feature-structure libraries</term>).  Finally, one may use the
<att>fVal</att> attribute of the <gi>f</gi> element to point to its
values.  This indirect method of encoding feature values presumes that
the value elements are assigned <att>id</att> specifications, and are
collected together in <gi>fvLib</gi> elements (<term>feature-value
libraries</term>).  The elements which are used for representing feature,
feature-structure and feature-value libraries, along with their
descriptions and attributes, are the following.
 
<tagList>
<tagDesc tagDoc=FLIB atts='type'>
<tagDesc tagDoc=FSLIB atts='type'>
<tagDesc tagDoc=FVLIB atts='type'>
</tagList>
 
<p>For example, suppose a feature library for phonological feature
specifications is set up as follows.
 
<eg>
<![ CDATA [
<fLib type='phonological features'>
  <f id=CNS1 name=consonantal><plus> </f>
  <f id=CNS0 name=consonantal><minus></f>
  <f id=VOC1 name=vocalic>    <plus> </f>
  <f id=VOC0 name=vocalic>    <minus></f>
  <f id=VOI1 name=voiced>     <plus> </f>
  <f id=VOI0 name=voiced>     <minus></f>
  <f id=ANT1 name=anterior>   <plus> </f>
  <f id=ANT0 name=anterior>   <minus></f>
  <f id=COR1 name=coronal>    <plus> </f>
  <f id=COR0 name=coronal>    <minus></f>
  <f id=CNT1 name=continuant> <plus> </f>
  <f id=CNT0 name=continuant> <minus></f>
  <f id=STR1 name=strident>   <plus> </f>
  <f id=STR0 name=strident>   <minus></f>
<!-- ... -->
  </fLib>
]]>
</eg>
 
<p>Then the feature structures that represent the analysis of the
phonological segments (phonemes) <code>/t/</code>, <code>/d/</code>,
<code>/s/</code> and <code>/z/</code> can be defined as follows.
 
<eg>
<![ CDATA [
<fs feats='cns1 voc0 voi0 ant1 cor1 cnt0 str0'></fs>
<fs feats='cns1 voc0 voi1 ant1 cor1 cnt0 str0'></fs>
<fs feats='cns1 voc0 voi0 ant1 cor1 cnt1 str1'></fs>
<fs feats='cns1 voc0 voi1 ant1 cor1 cnt1 str1'></fs>
]]>
</eg>
 
<p>The preceding are but four of the 128 logically possible fully
specified phonological segments using the seven binary features listed in
the feature library.  Presumably not all combinations of features
correspond to phonological segments (there are no strident vowels, for
example).  The legal combinations, however, can be collected together in a
<term>feature-structure library</term>, with each element being given a
unique <att>id</att> attribute, as in the following example.
 
<eg><![ CDATA [
<fsLib id=FSL1 type='phonological segment definitions'>
<!-- ... -->
  <fs id=T.df feats='cns1 voc0 voi0 ant1 cor1 cnt0 str0'></fs>
  <fs id=D.df feats='cns1 voc0 voi1 ant1 cor1 cnt0 str0'></fs>
  <fs id=S.df feats='cns1 voc0 voi0 ant1 cor1 cnt1 str1'></fs>
  <fs id=Z.df feats='cns1 voc0 voi1 ant1 cor1 cnt1 str1'></fs>
<!-- ... -->
  </fsLib>
]]>
</eg>
 
<p>Text elements can be linked to these feature structures in any of the
ways described in section <xref type=div2 target=AIATTS>.  In the
following example, a <gi>linkGrp</gi> element is used to link selected
characters in the text <cited>Caesar seized control</cited> to their
phonological representations.
 
<eg><![ CDATA [
<text id=TXT1> <!-- ... -->
<body> <!-- ... -->
<ab id=S1>
  <w id=S1W1>
    <c id=S1W1C1>C</c>ae<c id=S1W1C2>s</c>ar</w>
  <w id=S1W2>
    <c id=S1W2C1>s</c>ei<c id=S1W2C2>z</c>e<c id=S1W2C3>d</c></w>
  <w id=S1W3>
    con<c id=S1W3C1>t</c>rol</w>.
</ab>
<!-- ... -->
</body></text>
 
<fsLib id=FSL1 type='phonological segment definitions'>
<!-- as in previous example -->
  </fsLib>
 
<linkGrp type='phonological identification of characters'
    domains='fsl1 txt1'
    targFunc='phonological.segment character' >
<!-- ... -->
  <link id=LT targets='s.df s1w3c1'>
  <link id=LD targets='z.df s1w2c3'>
  <link id=LS targets='s.df s1w1c1'>
  <link id=LS targets='s.df s1w2c1'>
  <link id=LZ targets='z.df s1w1c2'>
  <link id=LZ targets='z.df s1w2c2'>
 
<!-- ... -->
  </linkGrp>
]]>
</eg>
 
<p>Because of the simplicity of the binary feature values, there is no
particular gain in pointing at those values rather than specifying them
directly.  However, the mechanism of using the <att>fVal</att> attribute
on <gi>f</gi> elements is useful for representing more complex feature
values, and can be illustrated using binary values.  Suppose the
<gi>plus</gi> and <gi>minus</gi> elements are collected together in a
<gi>fvLib</gi>, as follows.
 
<eg><![ CDATA [
<fvLib type='binary values'>
  <plus  id=B1>
  <minus id=B0>
  </fvLib>
]]>
</eg>
 
Then the feature library presented at the beginning of this section can be
represented as follows.
 
<eg>
<![ CDATA [
<fLib type='phonological features'>
  <f id=CNS1 name=consonantal fVal=b1></f>
  <f id=CNS0 name=consonantal fVal=b0></f>
  <f id=VOC1 name=vocalic     fVal=b1></f>
  <f id=VOC0 name=vocalic     fVal=b0></f>
  <f id=VOI1 name=voiced      fVal=b1></f>
  <f id=VOI0 name=voiced      fVal=b0></f>
  <f id=ANT1 name=anterior    fVal=b1></f>
  <f id=ANT0 name=anterior    fVal=b0></f>
  <f id=COR1 name=coronal     fVal=b1></f>
  <f id=COR0 name=coronal     fVal=b0></f>
  <f id=CNT1 name=continuant  fVal=b1></f>
  <f id=CNT0 name=continuant  fVal=b0></f>
  <f id=STR1 name=strident    fVal=b1></f>
  <f id=STR0 name=strident    fVal=b0></f>
<!-- ... -->
  </fLib>
]]>
</eg>
 
<p>Although <gi>fs</gi> elements are legitimate feature values (see
section <xref target=FSST>), they are not allowed within <gi>fvLib</gi>
elements.  They should be placed in <gi>fsLib</gi> elements.
 
<p>Here are the formal declarations of the <gi>fLib</gi>, <gi>fsLib</gi>
and <gi>fvLib</gi> elements.
 
<dtdFrag id=DFSFL n='Feature libraries' file=teifs2>
<tagDecl tagDoc=FLIB>
<tagDecl tagDoc=FSLIB>
<tagDecl tagDoc=FVLIB>
</dtdFrag>
<?tei:EOF p2fsfl.odd ?>
