<?xml version="1.0" standalone="yes"?>
<Paper uid="C90-1011">
  <Title>Knowledge Acquisition Environment Integrating Natural Language and Logic&amp;quot;. Proceedings IJCAI</Title>
  <Section position="6" start_page="0" end_page="0" type="concl">
    <SectionTitle>
4. CONCLUSIONS
</SectionTitle>
    <Paragraph position="0"> A knowledge base produced with CODE can be seen as a &amp;quot;blueprint&amp;quot; for a documentation project, in that it clarifies the conceptual structure and terminology of the project from the outset. Just as one does not construct buildings without blueprints, systematic and computer-assisted concept analysis should be a prerequisite for the documentation process in general, particularly the terminology component.</Paragraph>
    <Paragraph position="1"> The following are just a few examples of the positive implications we foresee for our approach:  !. Greater quality and multifunctionality of terminological data, through a large and well-structured knowledge component.</Paragraph>
    <Paragraph position="2"> 2. Terminological consistency between all phases of the documentation process, (i.e. less of the &amp;quot;pass-my-confusion-onto-the-nextperson&amp;quot; phenomenon). 3. Enhanced communication among  terminologists, other documentalists, and experts through a shareable knowledge base. The documentalist's and terminologist's better understanding of the conceptual structure of an expert's field is also bound to enhance his credibility with the expert.</Paragraph>
    <Paragraph position="3"> 4. Efficient training. A knowledge base that offers efficient, on-line retrieval of information ensures conceptual continuity, and prevents a new documentalist from having to relearn his predecessor's field &amp;quot;from scratch&amp;quot;.</Paragraph>
    <Paragraph position="4"> 5. Improved transfer of knowledge across linguistic borders. The translation process is a great bottleneck for efficient inter-linguistic knowledge transfer: both human and machine translation are greatly enhanced by correct terminology and conceptual clarity.</Paragraph>
  </Section>
class="xml-element"></Paper>