Academia.eduAcademia.edu

Outline

Promoting Portability in Dialogue Management

2003

Abstract

Introduction: One of the hardest parts of designing and building a conversational system is configuring and coding the dialogue manager. Components such as speech recognition and language understanding have both been modular- ized, with domain-specific information contained in external files and models. SPEECHBUILDER (1) was designed to make these two components even easier to configure, with a Web-based graphical interface to help developers write grammars and create language models for recognizers. However, dialogue management has resisted this push towards portability and modularity, since its role in planning and response generation was considered ultimately too domain-dependent. In the course of building dialogue managers for each of our separate systems (e.g., weather (2), air travel (3), flight status, urban navigation (4), and task delegation (5)), we have noticed that the basic functionality repeats itself across domains. For example, each system must gather information fro...

References (5)

  1. REFERENCES
  2. J. Glass and E. Weinstein, "SPEECHBUILDER: Facilitating spoken dialogue system development," in Proc. Eurospeech, 2001, Aalborg, Sept. 2001, pp. 1335-1338.
  3. V. Zue, S. Seneff, J. Glass, L. Hetherington, E. Hurley, H. Meng, C. Pao, J. Polifroni, R. Schloming, and P. Schmid, "From interface to content: Translingual access and delivery of on-line information," in Proc. Eurospeech, 1997, Rhodes, Sept. 1997, pp. 2227-2230.
  4. S. Seneff and J. Polifroni, "Dialogue management in the MERCURY flight reservation system," in Proc. ANLP-NAACL 2000 Satellite Workshop, Seattle, May 2000, pp. 1-6.
  5. S. Seneff, R. Lau, and J. Polifroni, "Organization, communi- cation, and control in the GALAXY-II conversational system," in Proc. Eurospeech, 1999, Budapest, Sept. 1999, pp. 1271- 1274.