<?xml version="1.0" standalone="yes"?>
<Paper uid="J89-1001">
  <Title>PARSING WITH FLEXIBILITY~ DYNAMIC STRATEGIES~ AND IDIOMS IN MIND</Title>
  <Section position="13" start_page="16" end_page="16" type="concl">
    <SectionTitle>
CONCLUSIONS
</SectionTitle>
    <Paragraph position="0"> We have focused on some important features of a parser, e.g., able to perform unification while working on structures, able to analyze idiomatic forms, providing a good testbed for ideas about dynamic strategies. The parser we have introduced is based on linguistic knowledge distributed fundamentally through the lexicon and uses a chart with unification activity developed when new edges are established. Especially if word order is flexible, it is important to avoid redundancy and detect useless hypotheses at an early stage. Here, chart Computational Linguistics, Volume 15, Number 1, March 1989 Oiiviero Stock Parsing with Flexibility, Dynamic Strategies, and Idioms in Mind parsing is based on a bottom up with left context confirmation strategy and unification is based on the Principle of the Good Clerk. Also, we have proposed a view of the idiom recognition process that is completely integrated with the parser, so that, in particular, idiom recognition can take advantage of the flexibility of the approach without redundancy. We think that this is important, because idioms are on a continuum with literal language, and, share the &amp;quot;normal&amp;quot; characteristics, including the flexibility, of the particular language involved. Moreover, given that the algorithm is of a multiprocessing type, one can consider what strategies can be introduced in order to select dynamically the tasks that have best chances of leading to the (preferable) final analysis. These heuristics can also take advantage of measures of likelihood associated with each partial analysis. An integrated interactive environment has been built to experiment with these ideas, which can also be used to define sublanguages and select strategies for particular applications.</Paragraph>
  </Section>
class="xml-element"></Paper>