<?xml version="1.0" standalone="yes"?>
<Paper uid="P98-2198">
  <Title>Locating noun phrases with finite state transducers.</Title>
  <Section position="7" start_page="1217" end_page="1217" type="concl">
    <SectionTitle>
7 Conclusion
</SectionTitle>
    <Paragraph position="0"> In conclusion, we have developed this system first for the French language, with very good results. It partially solves the problem of Information Retrieval for this precise domain.</Paragraph>
    <Paragraph position="1"> In fact the &amp;quot;occupation&amp;quot; domain is not closed: is a &amp;quot;thief&amp;quot; an occupation ? To avoid such difficulties, and in order to reach a good coverage of the domain, we have described essentially institutional occupations. We know full well that if we want to be precise, a very deep semantic description should be done: for example, it is not sure that we can say a &amp;quot;prime minister&amp;quot; of France is comparable with a &amp;quot;prime minister&amp;quot; of UK ? One of strength of the described system is that it enables us to gather information present in different locations of the corpus, which improves punctual descriptions. Another interest of having such representations for different languages is a possibly automatic translation for such noun phrases. The output of the source language will be used in the target language of FSTs to identify paths having the same output, hence the same meaning. We are working to adapt the representation to other languages, such as English and the challenge is not only to repeat the same work on another language, but to keep the same output for two synonyms in French and English, which is not easy, because some occupations are totally specific to a language.</Paragraph>
    <Paragraph position="2"> Our method is totally text-based, and the appropriate tools allow us to enrich the database progressively. We strongly believe that the complete description of such noun phrases is needed (for all needs: IR, translation, syntactic analysis...), and our interactive method which is quite efficient to this aim.</Paragraph>
  </Section>
class="xml-element"></Paper>