<?xml version="1.0" standalone="yes"?>
<Paper uid="H89-1013">
  <Title>PORTABILITY IN THE JANUS NATURAL LANGUAGE INTERFACE 1</Title>
  <Section position="13" start_page="116" end_page="116" type="relat">
    <SectionTitle>
RELATED WORK
</SectionTitle>
    <Paragraph position="0"> TEAM \[Grosz, 1987\] is most directly related, having many similar goals, though focussed on data bases rather than expert systems or knowledge bases. The novel aspects of KNACQ by contrast with TEAM are (1) accepting an expert system domain model as input (KNACQ) contrasted with the mathematically precise semantics of a relational data base (TEAM), and (2) how little information is required of the KNACQ user.</Paragraph>
    <Paragraph position="1"> A complementary facility is provided in TELI \[Ballard, 1986\] and in LIFER \[Hendrix, 1978\]. KNACQ is meant to be used by the (expert system's) knowledge engineer, who understands the expert system domain model, to define a large portion of the vocabulary, that portion corresponding to simple noun phrase constructions for each concept and role; one uses KNACQ to bootstrap the initially empty domain-dependent lexicon. TELI and LIFER, on the other hand, are meant to let the end user define additional vocabulary in terms of previously defined vocabulary, e.g., A ship is a vessel; therefore, those systems assume an extensive vocabulary provided by the system builder.</Paragraph>
    <Paragraph position="2"> Obviously, providing both kinds of capabilities is highly desirable.</Paragraph>
  </Section>
class="xml-element"></Paper>