<?xml version="1.0" standalone="yes"?>
<Paper uid="W94-0316">
  <Title>Building Another Bridge over the Generation Gap</Title>
  <Section position="6" start_page="142" end_page="142" type="concl">
    <SectionTitle>
5 Concluding Remarks
</SectionTitle>
    <Paragraph position="0"> In this paper, we argued that in order to build up the link between discourse structure relations in the text plan and linguistic resources, it is useful to distinguish between two levels of discourse organization: a global discourse organization, which is not affected by linguistic means; and a finer discourse organization, which is clone in accordance with the linguistic materiM that is available for the meaning communicated. We reported on an ongoing attempt to define a situation-specific, multilayered model of lexical resources that is based on Mel'~uk's Lezical Functions.</Paragraph>
    <Paragraph position="1"> We have shown that the lexical phenomena represented at the most global layer of this model are suitable to serve as lexically biased discourse relations, and that these relations can be tailored to relations as specified in the output of an RST style text planner.</Paragraph>
    <Paragraph position="2"> The following distinctive features characterize the model proposed: * it makes sure that all relations defined are expressable in language, * it allows for a realization of lexical relations as intraclausal relations between discourse segments, * it is sensitive to lexical and syntactic variations during the realization of discourse relations.</Paragraph>
    <Paragraph position="3"> Although we decompose the LF information and represent it in a systemic framework, we think that we have shown that LFS as introduced in MTT can be used as constraints not only at the level of words (as argued in \[Meteer, 1991, p. 302\]). However, it should also be noted that the proposal we suggest works only if the arguments of a discourse relation communicate information on the same situation or on related situations.</Paragraph>
  </Section>
class="xml-element"></Paper>