| { | |
| "paper_id": "H01-1025", | |
| "header": { | |
| "generated_with": "S2ORC 1.0.0", | |
| "date_generated": "2023-01-19T03:31:00.510839Z" | |
| }, | |
| "title": "Exploring Speech-Enabled Dialogue with the Galaxy Communicator Infrastructure", | |
| "authors": [ | |
| { | |
| "first": "Samuel", | |
| "middle": [], | |
| "last": "Bayer", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Bryan", | |
| "middle": [], | |
| "last": "George", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "[email protected]" | |
| } | |
| ], | |
| "year": "", | |
| "venue": null, | |
| "identifiers": {}, | |
| "abstract": "This demonstration will motivate some of the significant properties of the Galaxy Communicator Software Infrastructure and show how they support the goals of the DARPA Communicator program.", | |
| "pdf_parse": { | |
| "paper_id": "H01-1025", | |
| "_pdf_hash": "", | |
| "abstract": [ | |
| { | |
| "text": "This demonstration will motivate some of the significant properties of the Galaxy Communicator Software Infrastructure and show how they support the goals of the DARPA Communicator program.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Abstract", | |
| "sec_num": null | |
| } | |
| ], | |
| "body_text": [ | |
| { | |
| "text": "The DARPA Communicator program [1], now in its second fiscal year, is intended to push the boundaries of speechenabled dialogue systems by enabling a freer interchange between human and machine. A crucial enabling technology for the DARPA Communicator program is the Galaxy Communicator software infrastructure (GCSI), which provides a common software platform for dialogue system development. This infrastructure was initially designed and constructed b y MIT [2] , and is now maintained and enhanced by the MITRE Corporation. This demonstration will motivate some of the significant properties of this infrastructure and show how they support the goals of the DARPA Communicator program.", | |
| "cite_spans": [ | |
| { | |
| "start": 461, | |
| "end": 464, | |
| "text": "[2]", | |
| "ref_id": "BIBREF0" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "The GCSI is a distributed hub-and-spoke infrastructure which allows the programmer to develop Communicator-compliant servers in C, C++, Java, Python, or Allegro Common Lisp. This system is based on message passing rather than CORBA-or RPC-style APIs. The hub in this infrastructure supports routing of messages consisting of key-value pairs, but also supports logging and rule-based scripting. Such an infrastructure has the following desirable properties:", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "HIGHLIGHTED PROPERTIES", | |
| "sec_num": "2." | |
| }, | |
| { | |
| "text": "The scripting capabilities of the hub allow the programmer to weave together servers which may not otherwise have been intended to work together, b y rerouting messages and their responses and transforming their keys.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "\u2022 The scripting capabilities of the hub allow the programmer to insert simple tools and filters to convert data among formats.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "\u2022 The scripting capabilities of the hub make it easy t o modify the message flow of control in real time.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "\u2022 The scripting capabilities of the hub and the simplicity of message passing make it simple to build up systems bit by bit.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "\u2022 The standard infrastructure allows the Communicator program to develop platform-and programminglanguage-independent service standards for recognition, synthesis, and other better-understood resources.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "\u2022 The standard infrastructure allows members of the Communicator program to contribute generally useful tools to other program participants.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "This demonstration will illustrate a number of these properties.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "\u2022", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "By way of illustration, this demo will simulate a process of assembling a Communicator-compliant system, while at the same time exemplifying some of the more powerful aspects of the infrastructure. The demonstration has three phases, representing three successively more complex configuration steps. We use a graphical display of the Communicator hub to make it easy to see the behavior of this system.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DEMO CONFIGURATION AND CONTENT", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "As you can see in Figure 1 , the hub is connected to eight servers: We will use the flexibility of the GCSI, and the hub scripting language in particular, to change the path that messages follow among these servers.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 18, | |
| "end": 26, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF0" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "DEMO CONFIGURATION AND CONTENT", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "\u2022 MITRE's", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "DEMO CONFIGURATION AND CONTENT", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "In phase 1, we establish audio connectivity. JDAS is MITRE's contribution to the problem of reliable access to audio resources. It is based on JavaSound 1.0 (distributed with JDK 1.3), and supports barge-in. We show the capabilities of JDAS by having the system echo the speaker's input; we also demonstrate the barge-in capabilities of JDAS bye showing that the speaker can interrupt the playback with a new utterance/input. The goal in building JDAS is that anyone who has a desktop microphone and the Communicator infrastructure will be able to use this audio server to establish connectivity with any Communicator-compliant recognizer or synthesizer.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Phase 1", | |
| "sec_num": "3.1" | |
| }, | |
| { | |
| "text": "The hub maintains a number of information states. The Communicator hub script which the developer writes can both access and update these information states, and we can invoke \"programs\" in the Communicator hub script by sending messages to the hub. This demonstration exploits this capability by using messages sent from the graphical display to change the path that messages follow, as illustrated i n Figure 2 . In phase 1, the hub script routed messages from JDAS back to JDAS (enabled by the message named \"Echo\"). In the next phase, we will change the path of messages from JDAS and send them to a speech recognizer. ", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 404, | |
| "end": 412, | |
| "text": "Figure 2", | |
| "ref_id": "FIGREF1" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Changing the message path", | |
| "sec_num": "3.2" | |
| }, | |
| { | |
| "text": "Now that we've established audio connectivity, we can add recognition and synthesis. In this configuration, we will route the output of the preferred recognizer to the preferred synthesizer. When we change the path through the hub script using the graphical display, the preferred servers are highlighted. Figure 3 shows that the initial configuration of phase 2 prefers SUMMIT and Festival.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 306, | |
| "end": 314, | |
| "text": "Figure 3", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Phase 2", | |
| "sec_num": "3.3" | |
| }, | |
| { | |
| "text": "The SUMMIT recognizer and the Festival synthesizer were not intended to work together; in fact, while there is a good deal of activity in the area of establishing data standards for various aspects of dialogue systems (cf. [3] ), there are n o programming-language-independent service definitions for speech. The hub scripting capability, however, allows these tools to be incorporated into the same configuration and t o interact with each other. The remaining incompatibilities (for instance, the differences in markup between the recognizer output and the input the synthesizer expects) are addressed b y the string server, which can intervene between the recognizer and synthesizer. So the GCSI makes it easy both to connect a variety of tools to the hub and make them interoperate, as well as to insert simple filters and processors to facilitate the interoperation.", | |
| "cite_spans": [ | |
| { | |
| "start": 223, | |
| "end": 226, | |
| "text": "[3]", | |
| "ref_id": "BIBREF1" | |
| } | |
| ], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Figure 3: Initial recognition/synthesis configuration", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "In addition to being able to send general messages to the hub, the user can use the graphical display to send messages associated with particular servers. So we can change the preferred recognizer or synthesizer. (as shown in Figure 4 ), or change the Festival voice (as shown in Figure 5 ). All these messages are configurable from the hub script. ", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 226, | |
| "end": 234, | |
| "text": "Figure 4", | |
| "ref_id": null | |
| }, | |
| { | |
| "start": 280, | |
| "end": 288, | |
| "text": "Figure 5", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Figure 3: Initial recognition/synthesis configuration", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Now that we've established connectivity with recognition and synthesis, we can add parsing and generation (or, in this case, input paraphrase). Figure 6 illustrates the final configuration, after changing recognizer and synthesizer preferences. In this phase, the output of the recognizer is routed to the parser, which produces a structure which is then paraphrased and then sent to the synthesizer. So for instance, the user might say \"I'd like to fly to Tacoma\", and after parsing and paraphrase, the output from the synthesizer might be \"A trip to Tacoma\". ", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 144, | |
| "end": 152, | |
| "text": "Figure 6", | |
| "ref_id": "FIGREF3" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Phase 3", | |
| "sec_num": "3.4" | |
| }, | |
| { | |
| "text": "The configuration at the end of phase 3 is obviously not a complete dialogue system; this configuration is missing context management and dialogue control, as well as an application backend, as illustrated by the remaining components in white in Figure 7 . However, the purpose of the demonstration is to illustrate the ease of plug-and-play experiments within the GCSI, and the role of these capabilities to assemble and debug a complex Communicator interface. The GCSI is available under an open source license at http://fofoca.mitre.org/download . ", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 246, | |
| "end": 254, | |
| "text": "Figure 7", | |
| "ref_id": "FIGREF4" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "CONCLUSION", | |
| "sec_num": "4." | |
| } | |
| ], | |
| "back_matter": [], | |
| "bib_entries": { | |
| "BIBREF0": { | |
| "ref_id": "b0", | |
| "title": "Galaxy-II: A Reference Architecture for Conversational System Development", | |
| "authors": [ | |
| { | |
| "first": "S", | |
| "middle": [], | |
| "last": "Seneff", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "E", | |
| "middle": [], | |
| "last": "Hurley", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "R", | |
| "middle": [], | |
| "last": "Lau", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "C", | |
| "middle": [], | |
| "last": "Pao", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "P", | |
| "middle": [], | |
| "last": "Schmid", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "V", | |
| "middle": [], | |
| "last": "Zue", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1998, | |
| "venue": "Proc. ICSLP 98", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "S. Seneff, E. Hurley, R. Lau, C. Pao, P. Schmid, and V. Zue. Galaxy-II: A Reference Architecture for Conversational System Development. Proc. ICSLP 98, Sydney, Australia, November 1998.", | |
| "links": null | |
| }, | |
| "BIBREF1": { | |
| "ref_id": "b1", | |
| "title": "Voice Browser' Activity", | |
| "authors": [], | |
| "year": null, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "\"'Voice Browser' Activity.\" http://www.w3.org/Voice.", | |
| "links": null | |
| } | |
| }, | |
| "ref_entries": { | |
| "FIGREF0": { | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Initial demo configuration", | |
| "uris": null | |
| }, | |
| "FIGREF1": { | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Modifying the hub information state", | |
| "uris": null | |
| }, | |
| "FIGREF2": { | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Preferring a recognizer Changing the Festival voice", | |
| "uris": null | |
| }, | |
| "FIGREF3": { | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "Adding parsing and paraphrase", | |
| "uris": null | |
| }, | |
| "FIGREF4": { | |
| "type_str": "figure", | |
| "num": null, | |
| "text": "A sample full dialogue system configuration 5. ACKNOWLEDGMENTS This work was funded by the DARPA Communicator program under contract number DAAB07-99-C201. \u00a9 2001 The MITRE Corporation. All rights reserved.", | |
| "uris": null | |
| } | |
| } | |
| } | |
| } |