<?xml version="1.0" standalone="yes"?>
<Paper uid="C94-1051">
  <Title>Anticipating the Reader's Problems and the Automatic Generation of Paraphrases</Title>
  <Section position="5" start_page="0" end_page="0" type="relat">
    <SectionTitle>
3. RELATED WORK IN CL
</SectionTitle>
    <Paragraph position="0"> Quite a lot of work exists on the use of paraphrases in connection with Nl.-database frontentks, cf. e.g.</Paragraph>
    <Paragraph position="1"> (McKeown 1979), (Meteer &amp; Shaked 1988). &amp;quot;ll~e formal representation g~fined from the user's query is translated back to NI, ag~dn and the user is requested to indicate if the system understood him correctly. This fits nicely into the framework from section 1.</Paragraph>
    <Paragraph position="2"> As indicated atxwe, much of the work presenlcd under the title &amp;quot;p,-uaphmse generation&amp;quot; should better be called &amp;quot;periphrase generation&amp;quot;. Reiter's (1990) system IN generates - depending on the user model entry for the problematic word &amp;quot;shark&amp;quot;- one of the following alternative fonnulations: I a) 'll~crc is a shark in the water lb) There is a dangerous fish in the water Similarly, the system WISBER (Iloracek 1990) generatcs one of the following formulations, where the problematic word is &amp;quot;Notgroschctf' (nfiuy day fund): 2a) 1 \[aben Sic cinch Notgroschen? \[Do you have a rainy &amp;ly lhnd't\] 2b) 1 laben Sic ein Sparbuch mit zwci Ncttomonatseinkommcn? \[l)o you have a savings account with two montlfs net income?\] In the terminology advocated here, the b)-c,-tses ,are periphrases of the a)-cases. Real tormulations with p~u'aphrases would look so,nethiug like this: lc) There is a shark,that is, a dangerous fish, in the water 2c) l tabcn Sic einen Nolgroschcn, d.h. ein Sparbuch nfit zwei Ncltomonatseinkommcn? \[1)o you have a rainy day fund, that is, a a savings account with two mouth's net income? It will be discussed below under which circumstances such uttcnmccs could be superior to the ~0- or b)-cases.</Paragraph>
  </Section>
class="xml-element"></Paper>