next up previous
Next: Completing the Data Up: Tracking the Dialogue Previous: Topics

Dialogue Manager

We do not keep an explicit dialogue model with a range of legal states and transitions. Instead we have a set of internal actions triggered mainly by the segment's dialogue act and using different sorts of information as arguments (topic, focus, stored suggestions etc.). It is certainly possible to formulate a dialogue model based on a formal definition of dialogue states but this may be of more importance in an interactive system where one wants strict control over the system's (visible) behaviour.

The dialogue manager needs to handle content: anaphoric references and ellipses in suggestions have to be resolved. The dialogue manager also keeps track of the speakers' attitudes towards the content objects (accept/reject etc.) and handles topic (see above) as well as focus. Each new segment/utterance is processed according to its dialogue act:

suggest:
propositional content is completed (see 4.3), stored and kept in focus
feedback:
the speaker's attitude (accept/reject) is annotated in focussed suggestion; a strong accept/reject is an utterance that mentions the accepted/rejected proposal explicitly, e.g.
A01:
let's meet on Tuesday then.
B02:
Tuesday is fine.

confirmations are annotated as strong accepts, e.g.
A03:
so I see you Tuesday, 2 o'clock in
your office

The annotation of the speakers' attitudes serves as evidence for the summarization (see section 4.4).

Question-answer pairs are dealt with by pushing the question item to a temporary short-term storage and waiting for a reply. The reply then triggers the treatment of the content data. We distinguish two types

yes/no-questions:
in case of a positive reply, the propositional content is treated as if introduced as a fact at the point of the positive reply.

information requests:
in this case the question usually provides one part of the object and the reply the other, e.g.

A01:
when's that flight going?
tex2html_wrap_inline270 [plane, has_date: ?DATE]
B02:
two thirty.
tex2html_wrap_inline270 {time_of_day:2:30}
tex2html_wrap_inline274 [plane, has_date: {time_of_day:2:30}]

Again the fact is added as if stated at the time of the answer.

 

  figure146


Figure 4: principal temporal units (capital letters) and their possible specifications


next up previous
Next: Completing the Data Up: Tracking the Dialogue Previous: Topics

Jan Alexandersson
Thu Nov 11 15:15:06 MET 1999