<?xml version="1.0" standalone="yes"?>
<Paper uid="P97-1052">
  <Title>On Interpreting F-Structures as UDRSs</Title>
  <Section position="4" start_page="0" end_page="402" type="intro">
    <SectionTitle>
\['PRED ~COACH ~ \] SUBJ NUM
SG
/SPEC EVERY
</SectionTitle>
    <Paragraph position="0"> PRED 'pick (T SUB J, T OBJ)' \[PRED 'PLAYER'\] LdegB: iN'M s/ J LSPEC/ and QLF representations ?Scope : pick (t erm(+r, &lt;hUm= sg, spec=every&gt;, coach, ?Q, ?X), term (+g, &lt;num=sg, spec=a&gt;, player, ?P, ?R) )  both of which are fiat representations which allow underspecification of e.g. the scope of quantificational NPs. In this companion paper we show that f-structures are just as easily interpretable as UDRSs</Paragraph>
    <Paragraph position="2"> We do this in terms of a translation function r from f-structures to UDRSs. The recursive part of the definition states that the translation of an f-structure is simply the union of the translation of its component parts:</Paragraph>
    <Paragraph position="4"> r, ..... T r.)) u u... u While there certainly is difference in approach and emphasis between f-structures, QLFs and UDRSs  the motivation foi&amp;quot; flat (underspecified) representations in each case is computational. The details of the LFG and UDRT formalisms are described at length elsewhere: here we briefly present the very basics of the UDRS formalism; we define a language of wff-s (well-formed f-structures); we define a mapping 7&amp;quot; from f-structures to UDRSs together with a reverse mapping r -1 and we show correctness with respect to an independent semantics (Dalrymple et al., 1996). Finally, unlike QLF the UDRS formalism comes equipped with an inference mechanism which operates directly on the underspecified representations without the need of considering cases. We illustrate our approach with a simple example involving the UDRS deduction component (see also (KSnig and Reyle, 1996) where amongst other things the possibility of direct deductions on f-structures is discussed).</Paragraph>
  </Section>
class="xml-element"></Paper>