<?xml version="1.0" standalone="yes"?>
<Paper uid="E93-1026">
  <Title>Inheriting Verb Alternations</Title>
  <Section position="3" start_page="213" end_page="214" type="intro">
    <SectionTitle>
1.2 Related work
</SectionTitle>
    <Paragraph position="0"> The work described here is at the meeting-point of lexical representation languages (as discussed above), lexical semantics (as in Atkins et al. and Levin and Rappoport Hovav; see also \[Levin, 1991\]) and formal accounts of alternations (see particularly \[Dowty, 1979\]).</Paragraph>
    <Paragraph position="1"> Recent work which aims to bring these three threads together in relation to the lexical representation of nouns includes \[Briscoe et ai., 1990; Pustejovsky, 1991; Copestake and Briscoe, 1991; Kilgarriff, 1993 forthcoming; Kilgarriff and Gazdar, 1993 forthcoming\]. (The latter two are companion papers to this, also using DATR in similar ways.) A paper addressing verbs is \[Sanfilippo and Poznanski, 1992\].</Paragraph>
    <Paragraph position="2"> This covers some of the same alternations as this  paper, and has similar goals. The formalism it uses is LRL, the typed default unification formalism of \[Copestake, 1992\]. Unlike DATR, this is both a lexical representation language and a grammar formalism. Whereas, in this paper, we represent the lexicon in DATR and then construct HPSG lexical entries, Sanfilippo and Poznanski need deal with only one formalism. This has a prima facie advantage but also a cost: the formalism must do two jobs. DATR is designed specifically for one, and offers more flexibility in the representation of exceptions and subregularities. In LRL, multiple default inheritance is restricted to the cases where there is no clash, with the condition enforced by a checking procedure, in contrast to DATR where the orthogonal nature of inheritance required by the syntax means that the problem does not arise. Also, LRL default inheritance must operate within the constraints of a type hierarchy, and the formalism requires two kinds of inheritance, default and non-default. In DATR, inheritance is not constrained by a type hierarchy, and inheritance, default or otherwise, invokes a single mechanism.</Paragraph>
  </Section>
class="xml-element"></Paper>