Benjamin Aw
Add updated pkl file v3
6fa4bc9
raw
history blame contribute delete
No virus
72.1 kB
{
"paper_id": "A00-1016",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T01:12:48.192924Z"
},
"title": "A Compact Architecture for Dialogue Management Based on Scripts ond Meta-Outputs",
"authors": [
{
"first": "Manny",
"middle": [],
"last": "Rayner",
"suffix": "",
"affiliation": {},
"email": ""
},
{
"first": "Beth",
"middle": [
"Ann"
],
"last": "Hockey",
"suffix": "",
"affiliation": {},
"email": ""
},
{
"first": "Frankie",
"middle": [],
"last": "J~mes",
"suffix": "",
"affiliation": {},
"email": ""
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "We describe an architecture for spoken dialogue interfaces to semi-autonomous systems that transforms speech signals through successive representations of linguistic, dialogue, and domain knowledge. Each step produces an output, and a meta-output describing the transformation, with an executable program in a simple scripting language as the final result. The output/meta-output distinction permits perspicuous treatment of diverse tasks such as resolving pronouns, correcting user misconceptions, and optimizing scripts.",
"pdf_parse": {
"paper_id": "A00-1016",
"_pdf_hash": "",
"abstract": [
{
"text": "We describe an architecture for spoken dialogue interfaces to semi-autonomous systems that transforms speech signals through successive representations of linguistic, dialogue, and domain knowledge. Each step produces an output, and a meta-output describing the transformation, with an executable program in a simple scripting language as the final result. The output/meta-output distinction permits perspicuous treatment of diverse tasks such as resolving pronouns, correcting user misconceptions, and optimizing scripts.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "The basic task we consider in this paper is that of using spoken language to give commands to a semiautonomous robot or other similar system. As evidence of the importance of this task in the NLP community note that the early, influential system SHRDLU (Winograd, 1973) was intended to address just this type of problem. More recent work on spoken language interfaces to semi-antonomous robots include SRrs Flakey robot (Konolige et al., 1993) and NCARArs InterBOT project (Perzanowski et al., 1998; Perzanowski et al., 1999) . A number of other systems have addressed part of the task. Com-mandTalk (Moore et al., 1997) , Circuit Fix-It Shop (Smith, 1997) and (Traum and Allen, 1994; Tranm and Andersen, 1999) are spoken language systems but they interface to simulation or help facilities rather than semi-autonomous agents. Jack's MOOse Lodge (Badler et al., 1999 ) takes text rather than speech as natural language input and the avatars being controlled are not semi-autonomous. Other researchers have considered particular aspects of the problem such as accounting for various aspects of actions (Webber, 1995; Pyre et al., 1995) . In most of this and other related work the treatment is some variant of the following. If there is a speech interface, the input speech signal is converted into text. Text either from the recognizer or directly input by the user is then converted into some kind of logical formula, which abstractly represents the user's intended command; this formula is then fed into a command interpreter, which executes the command.",
"cite_spans": [
{
"start": 253,
"end": 269,
"text": "(Winograd, 1973)",
"ref_id": "BIBREF16"
},
{
"start": 420,
"end": 443,
"text": "(Konolige et al., 1993)",
"ref_id": "BIBREF2"
},
{
"start": 473,
"end": 499,
"text": "(Perzanowski et al., 1998;",
"ref_id": "BIBREF6"
},
{
"start": 500,
"end": 525,
"text": "Perzanowski et al., 1999)",
"ref_id": "BIBREF7"
},
{
"start": 600,
"end": 620,
"text": "(Moore et al., 1997)",
"ref_id": "BIBREF4"
},
{
"start": 643,
"end": 656,
"text": "(Smith, 1997)",
"ref_id": "BIBREF10"
},
{
"start": 661,
"end": 684,
"text": "(Traum and Allen, 1994;",
"ref_id": null
},
{
"start": 685,
"end": 710,
"text": "Tranm and Andersen, 1999)",
"ref_id": null
},
{
"start": 846,
"end": 866,
"text": "(Badler et al., 1999",
"ref_id": "BIBREF0"
},
{
"start": 1101,
"end": 1115,
"text": "(Webber, 1995;",
"ref_id": "BIBREF15"
},
{
"start": 1116,
"end": 1134,
"text": "Pyre et al., 1995)",
"ref_id": "BIBREF9"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "We do not think the standard treatment outlined above is in essence incorrect, but we do believe that, as it stands, it is in need of some modification. This paper will in particular make three points. First, we suggest that the output representation should not be regarded as a logical expression, but rather as a program in some kind of scripting language. Second, we argue that it is not merely the case that the process of converting the input signal to the final representation can sometimes go wrong; rather, this is the normal course of events, and the interpretation process should be organized with that assumption in mind. Third, we claim, perhaps surprisingly, that the first and second points are related. These claims are elaborated in Section 2.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The remainder of the paper describes an architecture which addresses the issues outlined above, and which has been used to implement a prototype speech interface to a simulated semi-autonomous robot intended for deployment on the International Space Station. Sections 3 and 4 present an overview of the implemented interface, focussing on representational issues relevant to dialogue management. Illustrative examples of interactions with the system are provided in Section 5. Section 6 concludes.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Theoretical Ideas",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "2",
"sec_num": null
},
{
"text": "Let's first look in a little more detail at the question of what the output representation of a spoken language interface to a semi-autonomous robot/agent should be. In practice, there seem to be two main choices: atheoreticai representations, or some kind of logic. Logic is indeed an excellent way to think about representing static relationships like database queries, but it is much less clear that it is a good way to represent commands. In real life, when people wish to give a command to a computer, they usually do so via its operating system; a complex command is an expression in a scripting language like CSHELL, Perl, or VBScript. These languages are related to logical formalisms, but cannot be mapped onto them in a simple way. Here are some of the obvious differences:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Scripts vs Logical Forms",
"sec_num": "2.1"
},
{
"text": "\u2022 A scripting language is essentially imperative, rather than relational.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Scripts vs Logical Forms",
"sec_num": "2.1"
},
{
"text": "\u2022 The notion of temporal sequence is fundamental to the language. \"Do P and then Q\" is not the same as \"Make the goals P and Q true\"; it is explicitly stated that P is to be done first. Similarly, \"For each X in the list (A B C), do P(X)\" is not the same as \"For all X, make P(X) true\"; once again, the scripting language defines an or: der, but not the logical language 1.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Scripts vs Logical Forms",
"sec_num": "2.1"
},
{
"text": "\u2022 Scripting languages assume that commands do not always succeed. For example, UNIX-based scripting languages like CSHELL provide each script with the three predefined streams stdin, stdout and sl;derr. Input is read from stdin and written to sCdout; error messages, warnings and other comments are sent to stderr.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Scripts vs Logical Forms",
"sec_num": "2.1"
},
{
"text": "We do not think that these properties of scripting language are accidental. They have evolved as the result of strong selectional pressure from real users with real-world tasks that need to be carried out, and represent a competitive way to meet said users' needs. We consequently think it is worth taking seriously the idea that a target representation produced by a spoken language interface should share many of these properties.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Scripts vs Logical Forms",
"sec_num": "2.1"
},
{
"text": "We now move on to the question of modelling the interpretation process, that is to say the process that converts the input (speech) signal to the output (executable) representation. As already indicated, we think it is important to realize that interpretation is a process which, like any other process, may succeed more or less well in achieving its intended goals. Users may express themselves unclearly or incompletely, or the system may more or less seriously fail to understand exactly what they mean. A good interpretation architecture will keep these considerations in mind.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Meta-outputs",
"sec_num": null
},
{
"text": "Taking our lead from the description of scripting languages sketched above, we adapt the notion of the \"error stream\" to the interpretation process. In the course of interpreting an utterance, the system translates it into successively \"deeper\" levels of representation. Each translation step has not only an input (the representation consumed) and an output 1In cases like these, the theorem prover or logic programruing interpreter used to evaluate the logical formula typically assigns a conventional order to the conjuncts; note however that this is part of the procedural semantics of the theorem prover/interpreter, and does not follow from the declarative semantics of the logical formalism.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Meta-outputs",
"sec_num": null
},
{
"text": "(the representation produced), but also something we will refer to as a \"meta-output\": this provides information about how the translation was performed.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Meta-outputs",
"sec_num": null
},
{
"text": "At a high level of abstraction, our architecture will be as follows. Interpretation proceeds as a series of non-deterministic translation steps, each producing a set of possible outputs and associated metaoutputs. The final translation step produces an executable script. The interface attempts to simulate execution of each possible script produced, in order to determine what would happen if that script were selected; simulated execution can itself produce further meta-outputs. Finally, the system uses the meta-output information to decide what to do with the various possible interpretations it has produced. Possible actions include selection and execution of an output script, paraphrasing meta-output information back to the user, or some combination of the two.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Meta-outputs",
"sec_num": null
},
{
"text": "In the following section, we present a more detailed description showing how the output/metaoutput distinction works in a practical system.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Meta-outputs",
"sec_num": null
},
{
"text": "A Prototype Implementation",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "3",
"sec_num": null
},
{
"text": "The ideas sketched out above have been realized as a prototype spoken language dialogue interface to a simulated version of the Personal Satellite Assistant (PSA; (PSA, 2000) ). This section gives an overview of the implementation; in the following section, we focus on the specific aspects of dialogue management which are facilitated by the output/meta-output architecture.",
"cite_spans": [
{
"start": 163,
"end": 174,
"text": "(PSA, 2000)",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "3",
"sec_num": null
},
{
"text": "The real PSA is a miniature robot currently being developed at NASA Ames Research Center, which is intended for deployment on the Space Shuttle and/or International Space Station. It will be capable of free navigation in an indoor micro-gravity environment, and will provide mobile sensory capacity as a backup to a network of fixed sensors. The PSA will primarily be controlled by voice commands through a hand-held or head-mounted microphone, with speech and language processing being handled by an offboard processor. Since the speech processing units are not in fact physically connected to the PSA we envisage that they could also be used to control or monitor other environmental functions. In particular, our simulation allows voice access to the current and past values of the fixed sensor readings. The initial PSA speech interface demo consists of a simple simulation of the Shuttle. State parameters include the PSA's current position, some environmental variables such as local temperature, pressure and carbon dioxide levels, and the status of the Shuttle's doors (open/closed). A visual display gives direct feedback on some of these parameters.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "The speech and language processing architecture is based on that of the SRI CommandTalk system (Moore et al., 1997; Stent et al., 1999) . The system comprises a suite of about 20 agents, connected together using the SPd Open Agent Architecture (OAA; (Martin et al., 1998) ). Speech recognition is performed using a version of the Nuance recognizer (Nuance, 2000) . Initial language processing is carried out using the SRI Gemini system (Dowding et al., 1993) , using a domain~independent unification grammar and a domain-specific lexicon. The language processing grammar is compiled into a recognition grarnm~kr using the methods of (Moore et al., 1997) ; the net result is that only grammatically wellformed utterances can be recognized. Output from the initial language-processing step is represented in a version of Quasi Logical Form (van Eijck and Moore, 1992) , and passed in that form to the dialogue manager. We refer to these as linguistic level representations.",
"cite_spans": [
{
"start": 95,
"end": 115,
"text": "(Moore et al., 1997;",
"ref_id": "BIBREF4"
},
{
"start": 116,
"end": 135,
"text": "Stent et al., 1999)",
"ref_id": "BIBREF11"
},
{
"start": 250,
"end": 271,
"text": "(Martin et al., 1998)",
"ref_id": "BIBREF3"
},
{
"start": 348,
"end": 362,
"text": "(Nuance, 2000)",
"ref_id": "BIBREF5"
},
{
"start": 436,
"end": 458,
"text": "(Dowding et al., 1993)",
"ref_id": "BIBREF1"
},
{
"start": 633,
"end": 653,
"text": "(Moore et al., 1997)",
"ref_id": "BIBREF4"
},
{
"start": 853,
"end": 865,
"text": "Moore, 1992)",
"ref_id": "BIBREF14"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "The aspects of the system which are of primary interest here concern the dialogue manager (DM) and related modules. Once a linguistic level representation has been produced, the following processing steps occur:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "\u2022 The linguistic level representation is converted into a discourse level representation. This primarily involves regularizing differences in surface form: so, for example, \"measure the pressure\" and '~hat is the pressure?\" have different representations at the linguistic level, but the same representation at the discourse level.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "\u2022 If necessary, the system attempts to resolve instances of ellipsis and anaph*oric reference. For example, if the previous command was \"measure temperature at flight deck\", then the new command \"lower deck\" will be resolved to an expression meaning \"measure temperature at lower deck\". Similarly, if the previous command was \"move to the crew hatch\", then the command \"open it\" will be resolved to \"open the crew hatch\". We call the output of this step a resolved discourse level representation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "\u2022 The resolved discourse level representation is converted into an executable script in a language essentially equivalent to a subset of CSHELL. This involves two sub-steps. First, quantified variables are given scope: for example, \"go to the flight deck and lower deck and measure pressure\" becomes something approximately equivalent to the script foreach x (flight_deck lower_deck) go_to $x measure pressure end The point to note here is that the foreach has scope over both the go_to and the meeusmre actions; an alternate (incorrect) scoping would be foreachx (flight_deck lower_deck) go_to $x end measure pressure",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "The second sub-step is to attempt to optimize the plan. In the current example, this can be done by reordering the list (flight.deck louer_deck). For instance, if the PSA is already at the lower deck, reversing the list will mean that the robot only makes one trip, instead of two.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "The final step in the interpretation process is plan evaluation: the system tries to work out what will happen if it actually executes the plan. (The relationship between plan evaluation and plan execution is described in more detail in Section 4.1). Among other things, this gives the dialogue manager the possibility of comparing different interpretations of the original command, and picking the one which is most efficient.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Levels of Representation",
"sec_num": "3.1"
},
{
"text": "Tr---qlation , The above sketch shows how context-dependent interpretation is arranged as a series of nondeterministic translation steps; in each case, we have described the input and the output for the step in question. We now go back to the concerns of Section 2. First, note that each translation step is in general fallible. We give several examples:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "One of the most obvious cases arises when the user simply issues an invalid command, such as requesting the PSA to open a door D which is already open. Here, one of the meta-outputs issued by the plan evaluation step will be the term presupposition_failure(already_open(D)); the DM can decide to paraphrase this back to the user as a surface string of the form \"D is already open\". Note that plan evaluation does not involve actually executing the final script, which can be important. For instance, if the command is \"go to the crew hatch and open it\" and the crew hatch is already open, the interface has the option of informing the user that there is a problem without first carrying out the \"go to\" action.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "The resolution step can give rise to similar kinds of metaooutput. For example, a command may include a referring expression that has no denotation, or an ambiguous denotation; for example, the user might say \"both decks\", presumably being unaware that there are in fact three of them. This time, the meta-output produced is presupposition_failure ( incorrect_size_of_set (2,3) )",
"cite_spans": [],
"ref_spans": [
{
"start": 348,
"end": 378,
"text": "( incorrect_size_of_set (2,3)",
"ref_id": null
}
],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "representing the user's incorrect belief about the number of decks. The DM then has the possibility of informingthe user of this misconcelfi tion by realizing the meta-output term as the surface string \"in fact there are three of them\". Ambiguous denotation occurs when a description is under-specified. For instance, the user might say \"the deck\" in a situation where there is no clearly salient deck, either in the discourse situation or in the simulated world: here, the meta-output will be presupposition_failure ( underspecif ied_def inite (deck))",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "which can be realized as the clarification question \"which deck do you mean?\"",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "\u2022 A slightly more complex case involves plan costs. During plan evaluation, the system simulates execution of the output script while keeping track of execution cost. (Currently, the cost is just an estimate of the time required to execute the script). Execution costs are treated as meta-outputs of the form",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "cost (C)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "and passed back through the interpreter so that the plan optimization step can make use of them. \u2022 Finally, we consider what happens when the system receives incorrect input from the speech recognizer. Although the recognizer's language model is constrained so that it can only produce grammatical utterances, it can still misrecognize one grammatical string as another one. Many of these cases fall into one of a small number of syntactic patterns, which function as fairly reliable indicators of bad recognition. A typical example is conjunction involving a pronoun: if the system hears \"it and flight deck\", this is most likely a misrecognition of something like \"go to flight deck\". During the processing phase which translates linguistic level representations into discourse level representations, the system attempts to match each misrecognition pattern against the input linguistic form, and if successful produces a meta-output of the form presupposition_failure ( dubious_If (<Type>))",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "These meta-outputs are passed down to the DM, which in the absence of sufficiently compelling contrary evidence will normally issue a response of the form \"I'm sorry, I think I misheard you\".",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "How Meta-outputs Participate in the",
"sec_num": "3.2"
},
{
"text": "Based on Scripts and Meta-Outputs None of the individual functionalities outlined above are particularly novel in themselves. What we find new and interesting is the fact that they can all be expressed in a uniform way in terms of the script output/meta-output architecture. This section presents three examples illustrating how the architecture can be used to simplify the overall organization of the system.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "A Compact Architecture for Dialogue Management",
"sec_num": "4"
},
{
"text": "Recall that the DM simulates evaluation of the plan before running it, in order to obtain relevant metainformation. At plan execution time, plan actions result in changes to the world; at plan evaluation time, they result in simulated changes to the world and/or produce meta-outputs.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Integration of plan evaluation, plan execution and dialogue management",
"sec_num": "4.1"
},
{
"text": "Conceptualizing plans as scripts rather than logicai formulas permits an elegant treatment of the execution/evaluation dichotomy. There is one script interpreter, which functions both as a script executive and a script evaluator, and one set of rules which defines the procedural semantics of script actions. Rules are parameterized by execution type which is either \"execute\" or \"evaluate\". In \"evaluate\" mode, primitive actions modify a state vector which is threaded through the interpreter; in \"execute\" mode, they result in commands being sent to (real or simulated) effector agents. Conversely, \"meta-information\" actions, such as presupposition failures, result in output being sent to the metaoutput stream in \"evaluate\" mode, and in a null action in \"execute\" mode. The upshot is that a simple semantics can be assigned to rules like the following one, which defines the action of attempting to open a door which may already be open: if_then_else (status (D, open_closed, open) , change_status (D, open_closed, open) ",
"cite_spans": [],
"ref_spans": [
{
"start": 943,
"end": 986,
"text": "if_then_else (status (D, open_closed, open)",
"ref_id": null
},
{
"start": 989,
"end": 1025,
"text": "change_status (D, open_closed, open)",
"ref_id": null
}
],
"eq_spans": [],
"section": "Integration of plan evaluation, plan execution and dialogue management",
"sec_num": "4.1"
},
{
"text": "procedure ( open_door (D),",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Integration of plan evaluation, plan execution and dialogue management",
"sec_num": "4.1"
},
{
"text": "presupposition_failure (already_open(D)),",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Integration of plan evaluation, plan execution and dialogue management",
"sec_num": "4.1"
},
{
"text": "As described in the preceding section, the resolution step is in general non-deterministic and gives rise to meta-outputs which describe the type of resolution carried out. For example, consider a command involving a definite description, like \"open the door\". Depending on the preceding context, resolution will produce a number of possible interpretations; \"the door\" may be resolved to one or more contextually available doors, or the expression may be left unresolved. In each case, the type of resolution used appears as a meta-output, and is available to the dialogue manager when it decides which interpretation is most felicitous. By default, the DM's strategy is to attempt to supply antecedents for referring expre~.. sious, preferring the most recently occurring sortally appropriate candidate. In some cases, however, it is desirable to allow the default strategy to be overridden: for instance, it may result in a script which produces a presupposition failure during plan evaluation. Treating resolution choices and plan evaluation problems as similar types of objects makes it easy to implement this kind of idea.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ") ) 4.2 Using meta-outputs to choose between interpretations",
"sec_num": null
},
{
"text": "Perhaps the key advantage of our architecture is that collecting together several types of information as a bag of meta-outputs simplifies the top-level structure of the dialogue manager. In our application, the critical choice of dialogue move comes after the dialogue manager has selected the most plausible interpretation. It now has to make two choices. First, it must decide whether or not to paraphrase any of the meta-outputs back to the user; for example, if resolution was unable to fill some argument position or find an antecedent for a pronoun, it may be appropriate to paraphrase the corresponding metaoutput as a question, e.g. \"where do you mean?\", or \"what do you mean by 'it' ?'. Having all the metaoutputs available together means that the DM is able to plan a coherent response: so if there are several recta-outputs which could potentially be worth paraphrasing, it typically realizes only the most important one. Second, if interpretation was able to produce a well-formed plan, the DM currently has the three options of executing it, paraphrasing it back to the user as a confirmation question, or doing nothing. Once again, this decision often requires global information about what has happened during the interpretation process. For example, knowing that plan evaluation showed that the plan would take significant time to execute makes it more plausible that the user would prefer to receive a confirmation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Using meta-outputs to choose between dialogue management moves",
"sec_num": "4.3"
},
{
"text": "This section presents a commented sample dialogue with the implemented PSA interface demo chosen to illustrate the points discussed in the previous sec-tions. We focus in particular on the role that metaoutputs play in interpretation. Text preceded by USER represents spoken utterances from the user. Text preceded by PSA represents synthesized spoken responses from the PSA. Text inside square brackets describes the actions carried out by the PSA.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "1. The PSA can move to various locations and measure environmental factors. In the first exchange, reference resolution is used to interpret the phrase \"all three decks\" as referring to the lower deck, mid deck and flight deck. Plan op-timiT.ation finds the most efficient way to order the locations, and paraphrases the resulting plan back to the user.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: Go to all three decks and measure carbon dioxide.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "PSA: I will move to flight deck, mid deck and then lower deck and I will measure carbon dioxide level, okay? 3. Resolution of ellipsis can involve filling in unspecified semantic parameters to a syntactically complete command. It is not meaningful to talk about a sensor reading without reference to the place at which that reading was carried out; in the following example, resolution assumes that the location in question is the one most recently mentioned in the dialogue. Note also that since the PSA does not have to move in order to carry out the command, and hence can execute it immediately, the DM reasonably decides to skip the confirmation question. This decision is made based on the metaoutput encoding the estimated cost of executing the script.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: What was the carbon dioxide level at fifteen oh five according to the fixed sensors?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "PSA: According to the fixed sensors, at fifteen oh five the carbon dioxide level at the pilot's seat was one percent. 4. The system encounters a user misconception, which results in a \"presupposition failure\" meta-output being produced during reference resolution. It consequently decides to alert the user to this, rather than attempt to carry out the command.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: Close both doors.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "PSA: There are in fact three of them.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "5. The user utterance includes a pronoun, \"it\". The system resolves \"it\" to \"the crew hatch\", and issues an appropriate paraphrase in order to confirm that this is what the user meant.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: Go to crew hatch and close it.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "PSA: I will go to crew hatch and I will close crew hatch, okay?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: Yeah.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "[PSA moves to crew hatch and closes it]",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "6. The user asks the system to close the door, but it is unclear which door they are referring to. An \"ambiguous reference\" meta-output is produced by reference resolution, resulting in the DM issuing a clarification question.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: Close the door.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "PSA: Which door do you mean?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "7. The user response is successfully interpreted by reference resolution as an instance of ellipsis. Trying to close the crew hatch a second time however causes a presupposition failure metaoutput to be generated during plan evaluation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "The system informs the user of this and takes no action.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "USER: The crew hatch.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Examples",
"sec_num": "5"
},
{
"text": "The crew hatch is already closed.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "8. The user presents three locations in a suboptimal order. Plan evaluation finds a more efficient ordering.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "USER: Move to storage lockers, commander's seat and flight deck and measure temperature.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "PSA: I will move to flight deck, commander's seat and then storage lockers and I will measure temperature, okay? USER: Sure.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "[PSA moves to flight deck, commander's seat and storage lockers in that order and reports temperature at each location]",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "9. The user asks the system to repeat the previous command. Since the PSA is now starting from a different position, its most efficient plan is no longer the same, and it informs the user of this.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "USER: Do that again.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
},
{
"text": "PSA: I will move to storage lockers, commander's seat and then flight deck and I will measure temperature, okay? 10. The user interrupts the PSA in the middle of the plan, and asks it to go back to its last stopping place. Since \"stop\" may involve a potentially hazardous condition, the interface obeys immediately, without attempting to confirm first. We have described a generic architecture for spoken language dialogue interfaces to semi-autonomous agents, based on the standard notion of translating to successively deeper levels of representation. The novel aspects of our scheme center around two ideas: first, that the final output representations are best conceptualized not as logical expressions but rather as programs in a scripting language; second, that steps in the translation process should produce not only a simple output, but also meta-information describing how the output was produced. We have presented examples suggesting how several apparently diverse types of dialogue behavior can be captured simply within our framework, and outlined a prototype implementation of the scheme.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "PSA:",
"sec_num": null
}
],
"back_matter": [],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "Real time virtual humans",
"authors": [
{
"first": "N",
"middle": [],
"last": "Badler",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Bindiganavale",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Bourne",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Allbeck",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Shi",
"suffix": ""
},
{
"first": "M",
"middle": [],
"last": "Palmer",
"suffix": ""
}
],
"year": 1999,
"venue": "International Conference on Digital Media Futures",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "N. Badler, R. Bindiganavale, J. Bourne, J. Allbeck, J. Shi, and M. Palmer. 1999. Real time virtual humans. In International Conference on Digital Media Futures.",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "Gemini: A natural language system for spoken language understanding",
"authors": [
{
"first": "J",
"middle": [],
"last": "Dowding",
"suffix": ""
},
{
"first": "M",
"middle": [],
"last": "Gawron",
"suffix": ""
},
{
"first": "D",
"middle": [],
"last": "Appelt",
"suffix": ""
},
{
"first": "L",
"middle": [],
"last": "Cherny",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Moore",
"suffix": ""
},
{
"first": "D",
"middle": [],
"last": "Moran",
"suffix": ""
}
],
"year": 1993,
"venue": "Proceedings of the Thirty-First Annual Meeting of the Association for Computational Linguistics",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "J. Dowding, M. Gawron, D. Appelt, L. Cherny, R. Moore, and D. Moran. 1993. Gemini: A nat- ural language system for spoken language un- derstanding. In Proceedings of the Thirty-First Annual Meeting of the Association for Computa- tional Linguistics.",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Flakey in action: The 1992 AAAI robot competition",
"authors": [
{
"first": "K",
"middle": [],
"last": "Konolige",
"suffix": ""
},
{
"first": "K",
"middle": [],
"last": "Myers",
"suffix": ""
},
{
"first": "E",
"middle": [],
"last": "Ruspini",
"suffix": ""
},
{
"first": "A",
"middle": [],
"last": "Saffiotti",
"suffix": ""
}
],
"year": 1993,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "K. Konolige, K. Myers, E. Ruspini, and A. Saf- fiotti. 1993. Flakey in action: The 1992 AAAI robot competition. Technical Report SRI Techni- cal Note 528, SKI, AI Center, SKI International, 333 Ravenswood Ave., Menlo Park, CA 94025.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "Building distributed software systems with the open agent architecture",
"authors": [
{
"first": "D",
"middle": [],
"last": "Martin",
"suffix": ""
},
{
"first": "A",
"middle": [],
"last": "Cheyer",
"suffix": ""
},
{
"first": "D",
"middle": [],
"last": "Moran",
"suffix": ""
}
],
"year": 1998,
"venue": "Proceedings of the Third International Conference on the Practical Application of Intelligent Agenta and Multi-Agent Technalogy",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. Martin, A. Cheyer, and D. Moran. 1998. Build- ing distributed software systems with the open agent architecture. In Proceedings of the Third International Conference on the Practical Appli- cation of Intelligent Agenta and Multi-Agent Tech- nalogy.",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "CommandTalk: A spoken-language interface for battlefield simulations",
"authors": [
{
"first": "R",
"middle": [],
"last": "Moore",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Dowding",
"suffix": ""
},
{
"first": "H",
"middle": [],
"last": "Bratt",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Gawron~",
"suffix": ""
},
{
"first": "-Y",
"middle": [],
"last": "Gorfu",
"suffix": ""
},
{
"first": "A",
"middle": [],
"last": "Cheyer",
"suffix": ""
}
],
"year": 1997,
"venue": "Proceedings of the Fifth Conference on Applied Natural Language Processing",
"volume": "",
"issue": "",
"pages": "1--7",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "R. Moore, J. Dowding, H. Bratt, J. Gawron~- Y. Gorfu, and A. Cheyer. 1997. CommandTalk: A spoken-language interface for battlefield simu- lations. In Proceedings of the Fifth Conference on Applied Natural Language Processing, pages 1-7.",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "Nuance Communications",
"authors": [
{
"first": "",
"middle": [],
"last": "Nuance",
"suffix": ""
}
],
"year": 2000,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Nuance, 2000. Nuance Communications, Inc. http://www.nuance.com. As of 9 March 2000.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "Integrating natural language and gesture in a robotics domain",
"authors": [
{
"first": "D",
"middle": [],
"last": "Perzanowski",
"suffix": ""
},
{
"first": "A",
"middle": [],
"last": "Schnltz",
"suffix": ""
},
{
"first": "W",
"middle": [],
"last": "Adams",
"suffix": ""
}
],
"year": 1998,
"venue": "IEEE International Symposium on Intelligent Control",
"volume": "",
"issue": "",
"pages": "247--252",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. Perzanowski, A. Schnltz, and W. Adams. 1998. Integrating natural language and gesture in a robotics domain. In IEEE International Sympo- sium on Intelligent Control.\" ISIC/CIRA/ISAS Joint Conference, pages 247-252, Gaithersburg, MD: National Institute of Standards and Tech- nology.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "Goal tracking in s natural language interface: Towards achieving adjustable autonomy",
"authors": [
{
"first": "D",
"middle": [],
"last": "Perzanowski",
"suffix": ""
},
{
"first": "A",
"middle": [],
"last": "Schnltz",
"suffix": ""
},
{
"first": "W",
"middle": [],
"last": "Adams",
"suffix": ""
},
{
"first": "E",
"middle": [],
"last": "Marsh",
"suffix": ""
}
],
"year": 1999,
"venue": "ISIS/CIRA99 Conference",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. Perzanowski, A. Schnltz, W. Adams, and E. Marsh. 1999. Goal tracking in s natural lan- guage interface: Towards achieving adjustable au- tonomy. In ISIS/CIRA99 Conference, Monterey, CA. IEEE.",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "Personal Satellite Assistant (PSA) Project",
"authors": [],
"year": 2000,
"venue": "PSA",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "PSA, 2000. Personal Satellite Assistant (PSA) Project. http://ic.arc.nasa.gov/ic/psa/. As of 9 March 2000.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "Actions as processes: a position on planning",
"authors": [
{
"first": "D",
"middle": [],
"last": "Pyre",
"suffix": ""
},
{
"first": "L",
"middle": [],
"last": "Pryor",
"suffix": ""
},
{
"first": "D",
"middle": [],
"last": "Murphy",
"suffix": ""
}
],
"year": 1995,
"venue": "Working Notes, AAAI Symposium on Eztending Theories of Action",
"volume": "",
"issue": "",
"pages": "169--173",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. Pyre, L. Pryor, and D. Murphy. 1995. Actions as processes: a position on planning. In Working Notes, AAAI Symposium on Eztending Theories of Action, pages 169-173.",
"links": null
},
"BIBREF10": {
"ref_id": "b10",
"title": "An evaluation of strategies for selective utterance verification for spoken natural language dialog",
"authors": [
{
"first": "R",
"middle": [
"W"
],
"last": "Smith",
"suffix": ""
}
],
"year": 1997,
"venue": "Proceedings of the Fifth Con-]erence on Applied Natural Language Processing",
"volume": "",
"issue": "",
"pages": "41--48",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "R. W. Smith. 1997. An evaluation of strategies for selective utterance verification for spoken natural language dialog. In Proceedings of the Fifth Con- ]erence on Applied Natural Language Processing, pages 41-48.",
"links": null
},
"BIBREF11": {
"ref_id": "b11",
"title": "The CommandTalk spoken dialogue system",
"authors": [
{
"first": "A",
"middle": [],
"last": "Stent",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Dowding",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Gawron",
"suffix": ""
},
{
"first": "E",
"middle": [],
"last": "Bratt",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Moore",
"suffix": ""
}
],
"year": 1999,
"venue": "Proceedings of the Thirty-Seventh Annual Meeting of the Association for Computational Linguistics",
"volume": "",
"issue": "",
"pages": "183--190",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "A. Stent, J. Dowding, J. Gawron, E. Bratt, and R. Moore. 1999. The CommandTalk spoken di- alogue system. In Proceedings of the Thirty- Seventh Annual Meeting of the Association for Computational Linguistics, pages 183-190.",
"links": null
},
"BIBREF12": {
"ref_id": "b12",
"title": "Discourse obligations in dialogue processing",
"authors": [
{
"first": "D",
"middle": [
"R"
],
"last": "Tranm",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Allen",
"suffix": ""
}
],
"year": 1994,
"venue": "Proceedings of the Thirty-Second Annual Meetiitg of the Association for Computational Linguistics",
"volume": "",
"issue": "",
"pages": "1--8",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. R. Tranm and J. Allen. 1994. Discourse obliga- tions in dialogue processing. In Proceedings of the Thirty-Second Annual Meetiitg of the Association for Computational Linguistics, pages 1-8.",
"links": null
},
"BIBREF13": {
"ref_id": "b13",
"title": "Representations of dialogue state for domain and task independent meta-dialogue",
"authors": [
{
"first": "D",
"middle": [
"R"
],
"last": "Traum",
"suffix": ""
},
{
"first": "C",
"middle": [
"F"
],
"last": "Andersen",
"suffix": ""
}
],
"year": 1999,
"venue": "Proceedings of the IJ-CAI'gg Workshop on Knowledge and Reasoning in Practical Dialogue Systems",
"volume": "",
"issue": "",
"pages": "113--120",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "D. R. Traum and C. F. Andersen. 1999. Represen- tations of dialogue state for domain and task inde- pendent meta-dialogue. In Proceedings of the IJ- CAI'gg Workshop on Knowledge and Reasoning in Practical Dialogue Systems, pages 113-120.",
"links": null
},
"BIBREF14": {
"ref_id": "b14",
"title": "Semantic rules for English",
"authors": [
{
"first": "J",
"middle": [],
"last": "Van Eijck",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Moore",
"suffix": ""
}
],
"year": 1992,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "J. van Eijck and R. Moore. 1992. Semantic rules for English. In H. Alshawi, editor, The Core Lan- guage Engine. MIT Press.",
"links": null
},
"BIBREF15": {
"ref_id": "b15",
"title": "Instructing animated agents: Viewing language in behavioral terms",
"authors": [
{
"first": "B",
"middle": [],
"last": "Webber",
"suffix": ""
}
],
"year": 1995,
"venue": "Proceedings of the International Conference on Cooperative Multi-modal Communication",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "B. Webber. 1995. Instructing animated agents: Viewing language in behavioral terms. In Proceed- ings of the International Conference on Coopera- tive Multi-modal Communication.",
"links": null
},
"BIBREF16": {
"ref_id": "b16",
"title": "A procedural model of language understanding",
"authors": [
{
"first": "T",
"middle": [
"A"
],
"last": "Winograd",
"suffix": ""
}
],
"year": 1973,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "T. A. Winograd. 1973. A procedural model of lan- guage understanding. In R. C. Shank and K. M.",
"links": null
},
"BIBREF17": {
"ref_id": "b17",
"title": "Computer Models of Thought and Language",
"authors": [
{
"first": "Colby",
"middle": [],
"last": "",
"suffix": ""
}
],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Colby, editors, Computer Models of Thought and Language. Freeman, San Francisco, CA.",
"links": null
}
},
"ref_entries": {}
}
}