File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/93/e93-1012_metho.xml
Size: 33,681 bytes
Last Modified: 2025-10-06 14:13:17
<?xml version="1.0" standalone="yes"?> <Paper uid="E93-1012"> <Title>Morphonology in the Lexicon</Title> <Section position="3" start_page="87" end_page="91" type="metho"> <SectionTitle> 2 Phonological Structures </SectionTitle> <Paragraph position="0"> In many previous approaches to morphology, particularly in the English-dominated NLP community, it was assumed that morphology consisted fundamentally of &quot;sticking together&quot; morphemes, and making the necessary adjustments to allow for spelling peculiarities. \[Cahill, 1990b\] suggested that this was too narrow a view, even for the rather impoverished inflection displayed by English. That there are several subclasses of English verbs which inflect by means other than affixation (e.g. &quot;bring&quot;- &quot;brought&quot; , &quot;sit&quot;- &quot;sat&quot; ) would seem to be a strong argument in itself, but looking at other languages such as the Semitic languages shows that there is an enormous body of interesting morphological phenomena which needs to be addressed. \[Cahill, 1990b\] showed that a view of morphological alternations as mappings between tree-structured syllables permitted a natural and succinct way of defining such Mternations. It also showed that levels of structure above the level of the syllable, while clearly vital for phonological description, were not necessary for morphological description. Thus the approach used structures which consisted only of linear sequences of tree-structured syllables.</Paragraph> <Paragraph position="1"> The question of structure above the level of the syllable is an interesting one. The use of metrical or tonal structure is clearly relevant to the phonology of a language, but it is debatable whether it has any place at all in the lexicon. While certain metrical notions such as stress are relevant to the lexicon (consider the noun-verb alternation &quot;re'ject&quot;-&quot;'reject&quot;), the actual metrical structure of even a polysyllabic word is dependent on the context in which it appears.</Paragraph> <Paragraph position="2"> Thus, it would seem reasonable to assume that the lexicon specifies the actual level of stress on each syllable of a word 1 but that the structure derived from this is extra-lexical.</Paragraph> <Paragraph position="3"> In the two-tiered DATR/MOLUSC lexicon, the phonological structures were assumed to be defined fully at each lexical entry. This meant that we could not make use of the inheritance mechanisms in DATR, even though the structures lent themselves to such definition. In the present work we shall define the structures hierarchically in DATR, thus avoiding 1There is an issue of how many levels we may want to differentiate in the lexicon, but it is not one which we propose to address in the current work.</Paragraph> <Paragraph position="4"> redundancy and enabling generalisations about the structures which were previously impossible.</Paragraph> <Paragraph position="5"> The formal semantics of MOLUSC (\[Cahill and Gazdar, 1990\]) defined the structures as having sets of feature definitions at each node. Although this facility was not used in the examples provided nor in the implementation, it is an aspect of the theory which we shall build upon in the current work.</Paragraph> <Section position="1" start_page="87" end_page="89" type="sub_section"> <SectionTitle> 2.1 Trees </SectionTitle> <Paragraph position="0"> In the first instance, let us consider the simple situation, where there are onset, peak, coda and rhyme nodes which consist of (sequences of) phonemes. A simple mono-syllabic root may be defined in DATR by the following: Word: <root> == (&quot;<onset>&quot; &quot;<rhyme>&quot;)</Paragraph> <Paragraph position="2"> Here the root is said to consist of an onset and a rhyme (which are provided at the original query node), and a rhyme (if not explicitly defined at the query node) consists of a peak and a coda. The onset, peak and coda are by default 0. Now we can define the root &quot;spell&quot; as follows:</Paragraph> <Paragraph position="4"> The structure is inherited from the Word node, with just the values of the onset, peak and coda defined at the node Spell 2.</Paragraph> <Paragraph position="5"> In our example theory defining a fragment of the English verb system, we only have mono- and disyllabic roots to contend with, but we need to consider how to handle a root consisting of an arbitrary number of syllables. We need to allow for a potentially infinite number of syllables in a root, but we also need each syllable in a root to maintain its own identity so as to permit both the definition of the values of the onset, peak and coda of the individual lexemes, and to allow for the definition of alternations in particular syllables. In MOLUSC this was achieved by means of a simple numbering convention where +N referred to the Nth syllable from the left and -N referred to the Nth syllable from the right.</Paragraph> <Paragraph position="6"> In our DATR-only account, we achieve the linear structures by means of a path prefix &quot;struct&quot;, and by defining the number of syllables in a root at its own lexical entry by means of a sequence of symbols one for each syllable more than one. In the example below, we use the term &quot;ext&quot; (for &quot;extension&quot;) to denote each syllable above one. Thus, a disyllabic root could be defined by the line: <sylls> == ext and a tri-syllabic root: <sylls> == (ext ext) and so on. At a higher node (in our case, &quot;VERB&quot;) we can then define the structure of a root with the following:</Paragraph> <Paragraph position="8"> Let us run through how this works by looking at the example of a tri-syllabic root which does not have values for any <sy11> paths defined at its node, so we can ignore the quotes on the <syll> paths. A tri-syllabic root will have the value (ext ext) for the path <sylls> at its own entry, so the first line defines the root in this case to be <struct ext ext>. The second line defines the value for the path <struct ext>, and this is the closest match for the path we want to evaluate. It is defined to be the list (<struct ext> &quot;<syll ext ext>&quot;), as the extra &quot;ext&quot;from the path we are evaluating gets added to any paths to be evaluated on the right hand side. Taking the second part of this first, <syll ext ext>, assuming it isn't explicitly defined at the word's entry, is defined as (&quot;<onset ext ext>&quot; &quot;<rhyme ext ext>&quot;). This again is because we carry over the extra elements from a left-hand side path to the right-hand side.</Paragraph> <Paragraph position="9"> The path <struct ext> is defined explicitly as (<struct> &quot;<syll ext>&quot;), and <struct> is defined as being the same as <sy11>. The derivation can be viewed as follows~ with the numbers of the lines from which values are derived in brackets:</Paragraph> <Paragraph position="11"> The root which results is therefore, (&quot;<onset>&quot; &quot;<rhyme>&quot; &quot;<onset exl;>&quot; &quot;<rhyme ext>&quot; &quot;<onset ext ext>&quot; &quot;<rhyme ext ext>&quot;) so that we can refer to the initial syllable and its constituents with paths without any &quot;ext&quot;s, the second syllable and its constituents with paths with one &quot;ext&quot; suffixed and so on.</Paragraph> <Paragraph position="12"> The idea of having to define the number of syllables in a root at each lexical entry may seem a little undesirable, but we will need to define each syllable separately at the entry anyway, so the explicit information of how many syllables there are is a very small cost. In addition, since in our example fragment below most roots are monosyllabic anyway, this will not have to be defined for each entry. We can have a default value for <sylls> at the VERB node of &quot;()&quot;. Although this is a language specific advantage, it is expected that it would not often be necessary to define polysyllabic roots for any language, since very long words will usually be made up of either compounded roots (as happens frequently in German) or a single root plus several affixes (as happens in agglutinative languages such as Turkish).</Paragraph> <Paragraph position="13"> The structures as defined above allow us to refer to an individual syllable provided we know its position from the left. But if we want to refer to the last syllable in a root, for example, we need to know how many syllables are in each root, thus preventing us from making generalisations over classes of verbs which do not all have the same number of syllables.</Paragraph> <Paragraph position="14"> This is clearly undesirable, but it can be avoided. In the example of English verbs, it is a feature of the verb roots that while most roots are monosyllabic:.</Paragraph> <Paragraph position="15"> those which are not only require reference to their final syllable, never their initial syllable. We therefore want to reverse the structure definition above, which can be very simply achieved by reversing the order of the paths <struct> and &quot;<syll ext>&quot; in the list on the right-hand side of the second line 3.</Paragraph> <Paragraph position="16"> What this means is that we must define for each language or language fragment (it may be different for nouns and verbs, for example) whether any alternations take place at the right- or left-hand end of the root. It is possible to refer to a syllable any number in from either side, not just the initial or final Sin our example fragment, we have replaced the term &quot;ext&quot; with &quot;pref&quot; to reflect the fact that it is prefixing which extends the structure. The actual term used is, of course, irrelevant.</Paragraph> <Paragraph position="17"> and any form or set of forms which show a deviation from the norm can be accommodated in DATR simply by means of overriding structure definitions at a lower node in the hierarchy. However, the definition of structure at the higher node(s) make for a generalisation about the set of forms covered by that node. This is in marked contrast to MOLUSC, which permitted equally easy reference to either end, and even permitted mixing within a single alternation definition. MOLUSC was much too powerful in this respect, and permitted the definition of alternations which do not occur in any language, so this is clearly a desirable restriction.</Paragraph> </Section> <Section position="2" start_page="89" end_page="89" type="sub_section"> <SectionTitle> 2.2 Segments within onset, peak and coda </SectionTitle> <Paragraph position="0"> As well as accessing syllables within a sequence, MOLOSC permitted the accessing of segments within the onset, peak and coda in a similar way. Although we do not want to go into detail here, as we do not propose to ultimately use discrete segments, we can do the same in the DATR framework outlined above, by means of a similar mechanism to that used for syllables. Again, we need to decide whether we want to extend leftwards or rightwards, and this again gives us a highly desirable restriction, which in this case we can use to restrict onsets to extend rightwards and codas to extend leftwards. Thus, we may refer to initial, second etc. segments within the onset and final, penultimate etc. segments within the coda but not vice versa. Of course, DATR itself does not force such restrictions, but the framework we have defined forces the lexicon writer to decide on how to apply the restrictions.</Paragraph> </Section> <Section position="3" start_page="89" end_page="91" type="sub_section"> <SectionTitle> 2.3 Phonological features </SectionTitle> <Paragraph position="0"> As mentioned above, we have used segments in the examples given so far for clarity of explanation. In MOLOSC and in the current work we intend the real unit of description to be the phonological feature or event rather than the segment. Much recent work, both computational and theoretical, has shown that the use of such units permits a more accurate, and above all, a declarative description of phonological phenomena such as ellision, epenthesis and assimilation (e.g. \[Coleman, 1992\], \[Bird and Klein, 1990\]). As mentioned above, \[Cahill and Gazdar, 1990\] defined a formal semantics for the MOLOSC language which permitted the definition of phonological features at any level in the structure, although the implementation and examples did not make use of feature definitions except at terminal nodes. Thus, the segment labels below the onset, peak and coda nodes were deemed to be abbreviations for a set of features, any one or more of which could be altered by a morphological alternation. It is possible to talk about inheritance of phonological features up or down the tree. For example, a \[+ voice\] feature at a rhyme node may be considered to be inherited by the peak and coda nodes below it, so that any segments within either of those two will contain the feature \[+ voice\]. Alternatively, the value of a coda node (null or non-null) may be inherited by the rhyme and syllable nodes above it in order to specify stress vMues which may be affected by whether a syllable is &quot;open&quot; or &quot;closed&quot;.</Paragraph> <Paragraph position="1"> In the account we are proposing here, we only require the latter type of inheritance, where the higher nodes inherit features from the lower nodes. This is because we are advocating an approach to phonology like that proposed by \[Bird and Klein, 1990\], \[Coleman, 1992\]. In both of these approaches, phonological features consist of a feature (or &quot;event&quot;) name, a value for that feature and an argument which defines how it relates temporally to the other features in the word 4. Thus, for example, in the word &quot;bat&quot; there may be features such as \[+ voice\], \[+ labial\], \[+ alveolar\], \[+ consonant\] and \[+ vowel\] amongst others 5. The voice feature would have a temporal argument which expressed the fact that it lasts for the entire word, the labial feature would be defined as lasting for some time from the beginning of the word until the onset of the vowel feature and the alveolar feature would be defined as commencing at the end of the vowel feature and ending at the end of the word. Of course, this is very approximate, but it is intended only to give the flavour of the treatment.</Paragraph> <Paragraph position="2"> In an account of this nature, it is not necessary for the features at higher nodes to be &quot;trickled&quot; down to lower nodes, since the temporal arguments define how they relate. However, that is not to say that the structure is unimportant. Both of the theories from which we are borrowing here make use of the notion of a tree-structured syllable, and phonological restrictions are defined as holding within such structures. In particular, from the point of view of the current account, reference to parts of the structure is necessary for the definition of morphological alternations (see below). In our definition of the structure given above, the result is a simple list (of segments in the example we gave). If we use features instead of segments, the same result is achieved, but insteaxi of a list of segments, considered to be temporally ordered, we end up with a list of features, not temporally ordered, but with explicit temporal arguments defining their relationship to each other.</Paragraph> <Paragraph position="3"> Although we will not be using segments, we maintain the notion of segmental units in the temporal 4\[Bird and Klein, 1990\] does not use features in this form exactly, but the notion of temporal relations between the events is vital to their account 5It is important to note here that in this and all subsequent examples of actual phonological features, no claim is being made as to the accuracy of the actual features used. They axe meant purely to demonstrate the applicability of the framework to (morpho)phonological description and not to demonstrate a full phonological theory. arguments in our examples below. We argue that segments, although possibly unnecessary in strict phonological terms, do seem to have a role at some level. The very fact that our writing system makes use of segment-type units appears to be an argument in favour of maintaining their existence at some level, and in morphological terms it is clear that many alternations seem to require reference to such units.</Paragraph> <Paragraph position="4"> For example, the English alternation &quot;bend&quot;-&quot;bent&quot; can be defined as an alternation in the voicing feature of only the final segment of the coda. We are therefore assuming timing boundaries at what would have been segment boundaries. Thus the word &quot;spell&quot; is assumed to have four &quot;timing sections&quot;, one for each of the conventional segments. The stem &quot;spell&quot; can thus be redefined as follows: The third element in each list is a (very simple) temporal argument. The sibilant feature, for example, lasts from 0 to 1, i.e. the first &quot;segmentsworth&quot;; the approximant feature of the onset goes from 1 to 2, i.e. the second &quot;segmentsworth&quot;; the voice feature of the onset covers the whole two segmentsworth of the onset. These are of course extremely simplified, both in the definition of the temporal arguments, and in the descriptions of the features themselves.</Paragraph> <Paragraph position="5"> But the theories from which we are borrowing have plenty to say about these aspects of phonology which is not relevant to how it might be expressed in a DATR lexicon combining phonological and morphological description. Note that in the example above, since we have temporal arguments, it is possibly not necessary to differentiate the rhyme features (just the voicing feature in the above example) from syllable features. We can have the feature \[ + voice 2-4 \] defined at either the rhyme or syllable node. Since all rhyme features are inherited by the syllable, it will only be relevant to make the distinction if an alternation requires reference to the rhyme features specifically. However, it is more accurate to maintain the distinction, and so we shall do so.</Paragraph> <Paragraph position="6"> The description above requires that every feature for which we want to define a value in a stem must be explicitly defined. In addition, every value for every feature must be explicitly defined. There is no room for a marked/unmarked distinction, for example. In doing this, we are not making use of DATR's default inheritance mechanisms to define default values for features. What we can do to improve on this situation is to define a set of features for which a value and a timing must be given (although the value may be &quot;undef&quot; or some such), and provide default values for each feature at a very high node.</Paragraph> <Paragraph position="7"> The set of features we have chosen are not intended to be comprehensive or even necessarily consistent, but are simply those sufficient to describe the stems and alternations involved in our example fragment.</Paragraph> <Paragraph position="8"> The feature set is as follows:</Paragraph> <Paragraph position="10"> The default value for all features is &quot;-&quot; and the default timing is rl, for &quot;root length&quot; - i.e. the whole length of the root.</Paragraph> <Paragraph position="11"> The definition of the structure of a stem (i.e. the number of syllables) is as before, but the definition of a syllable needs to take into account the fact that we are now dealing with lists of features and their values and timings, rather than linear sequences of segments. Since we are going to permit the permeation of features up the tree, we want the syllable node to contain all of the features for the onset and rhyme nodes, and the rhyme node to contain all of the features for the peak and coda nodes. One consequence of this is that we cannot simply allow the definition of features shared by say the peak and coda nodes at the rhyme node, since they will not then be inherited downwards, and any alternation which is dependent on the value of a feature at the coda node will need to look at the rhyme and syllable nodes' features, taking the timings into account as well. It would undoubtedly be possible to get around this problem but for our present purposes the extra cost of defining a shared feature at both nodes which share it is not a problem.</Paragraph> <Paragraph position="12"> The feature sets can be defined as follows:</Paragraph> <Paragraph position="14"> The paths are not quoted in this because we want the actual feature set to be defined at the top node, with just the values and timings defined at the terminal nodes. Thus, the feature set can be defined: <feats> == ( \[ alv &quot;<val alv>&quot; &quot;<time alv>&quot; approx &quot;<val approx>&quot; &quot;<time approx>&quot; fric &quot;<val fric>&quot; &quot;<time fric>&quot; high &quot;<val high> .... <time high>&quot; lab &quot;<val lab>&quot; &quot;<time lab>&quot; lat &quot;<val lat>&quot; &quot;<time fat>&quot; low &quot;<val low>&quot; &quot;<time low>&quot; nasal &quot;<val nasal>&quot; &quot;<time nasal>&quot; round &quot;<val round>&quot; &quot;<time round>&quot; sib &quot;<val sib>&quot; &quot;<time sib>&quot; stop &quot;<val stop>&quot; &quot;<time stop>&quot; vel &quot;<val vel>&quot; &quot;<time vel>&quot; voice &quot;<val voice> .... <time voice>&quot; \]) Then to find the set of features at the peak node, for example, the word peak is appended to all of the (quoted) paths in the feature list, thus evaluating the val and time for each feature at that node. The paths:</Paragraph> <Paragraph position="16"> then define default values for the val and time paths.</Paragraph> <Paragraph position="17"> With these definitions, we can define a stem by simply providing values for all those features which have the value ,,+,,6 and times for these. The example stem &quot;spell' can therefore be defined as: Spell: <> == VERB_A <val sib onset> == + <val lab onset> == + <val stop onset> == + <val front peak> == + <val voice peak> == + <val lat coda> == + <val voice coda> == + <time sib onset> == 0-1 <time lab onset> == 1-2 <time stop onset> == 1-2 <time front peak> == 2-3 <time voice peak> == 2-3 <time voice coda> == 3-4 <time lat coda> =- 3-4.</Paragraph> <Paragraph position="18"> Although the timings we are using here are extremely approximate, they can provide a starting point for phonological/phonetic systems, such as YorkTalk (\[Coleman, 1992\]). The YorkWalk system defines phenomena such as epenthesis as adjustments in the timings of such features, so as to blur the boundaries between &quot;segment&quot; sections. For example, the epenthesis which occurs in words such as &quot;mince&quot; (/mints/) is a result of the fact that the closure aspect of the nasal/n/is carried over to the non-nasal eWe are using simple boolean valued features here, but this is not a restriction. Multi-valued features, such as stress (see section 2 above), can be just as easily accommodated.</Paragraph> <Paragraph position="19"> /s/, resulting in a/t/sound. This type of phonological phenomenon is not something we would expect to be represented in the lexical entry for the word &quot;mince&quot;, but having approximate, relative timings of the features gives a system like YorkTalk something with which it can work more easily than simple segmental structures. They also eliminate the need to refer to individual segments within onset, peak and coda. The stem &quot;bend&quot; for example has a coda which consists of an &quot;n&quot; and a &quot;d&quot; (in conventional terms). This can be expressed in our account by the features voice, alveolar, nasal and stop having the value &quot;+&quot; in the coda, but with the following timings:</Paragraph> <Paragraph position="21"> The voice and alveolar features carry across the whole coda, but the nasal feature is only on the first section and the stop feature is only on the second.</Paragraph> <Paragraph position="22"> There would appear to be a problem here, resulting from the decision to only allow inheritance of features up the tree, in that it is possible for a feature at a particular node to be given a value at that node but a timing which only covers part of the node. For example, the stem &quot;swell&quot; has an onset whose voice feature has the value &quot;-&quot; for the first section and &quot;+&quot; for the second section. However, as we noted in the example of &quot;spell&quot; above, it is possible for the syllable node to contain features whose temporal arguments do not cover the whole syllable. Thus, the onset of &quot;swell&quot; would have a feature &quot;f- voice\]&quot; which has the timing &quot;0-1&quot; and the syllable node would have the feature &quot;\[+ voice\]&quot;, with the temporal argument &quot;1-4&quot;.</Paragraph> </Section> </Section> <Section position="4" start_page="91" end_page="93" type="metho"> <SectionTitle> 3 Morphological Alternations </SectionTitle> <Paragraph position="0"> Let us momentarily return to the use of segments for clarity, and consider how to define alternations between forms. In our example case of English verbs, most of the inflections take the form of suffLxation, which can be defined trivially. For example, the present participle form might be defined: <pres part> == (&quot;<root pres>&quot; ing) (with the suffix itself having its structure defined - we are not concerned with that here). What is more interesting, however, is the definition of alternations such as that in the forms &quot;bereave&quot;-&quot;bereft&quot;, &quot;cleave'-&quot;cleft&quot;. Such verbs, although only in small groups, do exhibit consistent, phonologically determined, but not strictly phonological, alternations. In MOLUSC, these could be defined by means of functions such as the following: There are two aspects to these alternations. On the one hand, defining the alternation between, say, a peak of/ii/with a peak of/e/is extremely straightforward, simply requiring path extensions to the &quot;<peak> ''7 definitions for past and present. Thus, the following would define the alternation:</Paragraph> <Paragraph position="2"> However, in the account of English verbs in \[Cahill, 1990b\], such verbs were grouped together with a large number of other verbs which did not exhibit this precise alternation, with the peak alternation being dependent on the original peak. Thus, the past tense peak is/e/if the present tense peak is/ii/and the same as the present tense peak otherwise.</Paragraph> <Section position="1" start_page="92" end_page="92" type="sub_section"> <SectionTitle> 3.1 Defining context-dependent alternations </SectionTitle> <Paragraph position="0"> We can define this type of context-dependent alternation in our framework by evaluating the present tense value for the peak and using that as an argument in a path for defining the past tense peak. The code for this is:</Paragraph> <Paragraph position="2"> This says that the peak of the past tense root (<peak past>) is found by evaluating the path which has the word peak_change followed by whatever the value of the present tense peak is (&quot;<peak pres>&quot;). If this results in the path <peak_change ii> (i.e. if the present tense peak is &quot;ii&quot;) then the past tense peak is &quot;e&quot;. In any other case (the path with the present peak value unspecified) the past tense peak is the same as the present tense peak (&quot;<peak pres>&quot;).</Paragraph> </Section> <Section position="2" start_page="92" end_page="93" type="sub_section"> <SectionTitle> 3.2 Defining feature value alternations </SectionTitle> <Paragraph position="0"> The coda change function is given in MOLUSC in two different forms - one with segments and the other with features. The version with segments can, unsurprisingly, be defined in exactly the same way as the peak change above. Let us consider the alternation defined as an alternation in the value of the voicing feature. The voicing feature of the set of verbs we are talking about is altered if the final segment of the coda is either a labial fricative (&quot;v&quot;) or an alveolar stop (&quot;d&quot;). There are therefore four features in whose values we are interested: lab, fric, alv and stop. We can define the value of the voicing feature of the coda in the past tense form to be dependent on the values of all four of these features: <val voice coda past> == <coda_change &quot;<val fric coda pres>&quot; ~This is the peak of the final syllable in all cases. We have already discussed above how to define roots as extending from either the right or the left, and we assume here that the roots all extend from the right.</Paragraph> <Paragraph position="1"> &quot;<val lab coda pres>&quot; &quot;<val stop coda pres>&quot; &quot;<val alv coda pres>&quot;> and we can define the actual value simply by means of the following two DATR sentences:</Paragraph> <Paragraph position="3"> The first says that, if the values of both the fric and lab features are &quot;+&quot; then the voice feature has the value &quot;-&quot;, regardless of what the values of the stop and alv features are. The second says that if the fric and lab features both have the value &quot;-&quot; and the stop and sly features both have the value &quot;+&quot; then the value of the voice feature is &quot;-&quot;. Note that the asymmetry is necessary but insignificant. It is not possible to define the alternation so that it is unimportant what the values of either the fric and lab features or the stop and alv features are, but it should be clear that in a consistent phonology, it would not be possible to have both the fric and stop features having the value &quot;+&quot; and even if it were possible to have the alv and lab features with the value &quot;+&quot;, it is highly unlikely that it would affect such an alternation. That is to say, in the examples of alternations we have looked at, such conflicts have never arisen.</Paragraph> <Paragraph position="4"> Two more alternations which can interestingly be handled very neatly in this framework are the sibilant/voice and alveolar/voice dependent &quot;s&quot; and &quot;d&quot; suffixes in English. The plural noun and present tense third person singular verb suffixes in English both have three realisations: /iz/after sibilants,/s/ after unvoiced non-sibilants and/z/after voiced nonsibilants. Traditionally this is defined with rules such as, S ~/iz//\[+ sib\] _ s -. Is//\[- voice\] __ S --+/z//\[+ voice\] __ where the first rule must apply before the other two.</Paragraph> <Paragraph position="5"> Alternatively, the feature \[- sib\] must be specified in the second and third rules in order to eliminate the need for ordering. In our account, we can define this alternation declaratively and succinctly. As with the coda voicing alternation described above, we need to evaluate a path which contains values of features in this case the sib and voice features. The present tense third person singular form is defined as: <pres third sing> == (&quot;<root pres>&quot; <ssuff &quot;<val sib coda>&quot; &quot;<val voice coda>&quot;>) and the value of the suffix (&quot;ssuff&quot;) is defined very simply with the following linesS:</Paragraph> <Paragraph position="7"> 8We have left the suffix forms as segments rather than expanding them out to features for simplicity.</Paragraph> <Paragraph position="8"> This says that if the value of the sib feature is &quot;+&quot; then the ssuff is &quot;iz&quot;, regardless of what the value of the voice feature is, and if the sib feature has the value &quot;-&quot; then the ssuff is &quot;z&quot; if the voice feature has the value &quot;+&quot; and &quot;s&quot; otherwise. We can do a similar thing for the past tense /id/-/d/-/t/ suffix with the sly and voice features. This analysis permits us to define the alternation declaratively, and hence without anyneed for rule ordering, but we can specify one feature value less than is necessary to avoid ordering in the traditional description.</Paragraph> </Section> </Section> class="xml-element"></Paper>