<?xml version="1.0" standalone="yes"?>
<Paper uid="H01-1017">
  <Title>Dialogue Interaction with the DARPA Communicator Infrastructure: The Development of Useful Software</Title>
  <Section position="9" start_page="0" end_page="0" type="concl">
    <SectionTitle>
8. LEVERAGE
</SectionTitle>
    <Paragraph position="0"> Ultimately, we hope that the GCSI, together with open-source servers such as recognizers, parsers, synthesizers and dialogue modules provided by application developers, will foster a vigorous explosion of work in speech-enabled dialogue systems. For example: * The programming-language-independent nature of the GCSI message-passing paradigm allows the Communicator program to develop implementationindependent service standards for recognition, synthesis, and other better-understood resources.</Paragraph>
    <Paragraph position="1"> * The freely available nature of the GCSI allows application developers to contribute dialogue system modules which are already configured to work with other components.</Paragraph>
    <Paragraph position="2"> * The availability of an &amp;quot;environment&amp;quot; for dialogue system development will support the development of an open source &amp;quot;toolkit&amp;quot; of state-of-the art, freely available modules. A number of Communicator sites are already releasing such modules.</Paragraph>
    <Paragraph position="3"> * A common infrastructure will contribute to the elaboration of &amp;quot;best practice&amp;quot; in dialogue system development.</Paragraph>
    <Paragraph position="4"> There are certainly a number of emerging and existing alternatives to the GCSI for dialogue system development (SRI's Open Agent Architecture, for instance). However, we believe that the combination of a software package like the GCSI and the critical mass generated by its use in the DARPA Communicator program presents a unique opportunity for progress in this area.</Paragraph>
    <Paragraph position="5"> The GCSI is available under an open source license at http://fofoca.mitre.org/download.</Paragraph>
  </Section>
class="xml-element"></Paper>