Izaskun Fernández (Tekniker) <mailto:izaskun.fernandez@tekniker.es>
Cristina Aceta (Tekniker) <mailto:cristina.aceta@tekniker.es>
Module for dialogue process and system output management.
TODODM: Dialogue Management Module for Task-Oriented Dialogue management Ontology (TODO)
Establishes the StepFunction corresponding to a SystemRequest or a ProcessStep.
Establishes the implications of the output of a StepFunction in the Dialogue Manager code.
Establishes the implications of an incorrect UserResponseType (e.g. when the request requires Yes/No as response and the user provides a ContentResponse).
Establishes the SystemRequest/Response that initiates a DialogueStep.
Establishes the SystemRequest that requires a given UserResponse type.
Establishes the SystemRequest or a ProcessStep corresponding to a StepFunction.
Establishes the implications when a StepFunction, in the Dialogue Manager code, returns more than one result as output and the length of the output is smaller than the number of maximum results previously defined.
Establishes the implications when a StepFunction, in the Dialogue Manager code, returns more than one result as output and the length of the output is higher than the number of maximum results previously defined.
Establishes the implications when a StepFunction, in the Dialogue Manager code, returns more than one result as output.
Establishes the implications when a StepFunction, in the Dialogue Manager code, returns no results as output.
Establishes the implications of a negative UserResponse.
Establishes the type of UserResponse required by a SystemRequest.
Establishes the implications when a StepFunction, in the Dialogue Manager code, returns one result as output.
Establishes the implications when the system does not understand a UserResponse.
Establishes the implications of a positive UserResponse.
Unique identification value for individuals.
Sets the order for StepFunctions/DialogueSteps.
String to be output by the system in order to communicate a SystemRequest/Response to the user.
Request that makes the user choose from a set of Actions obtained through inference.
[Previous SysResp: "I couldn't resolve the action from your request".] "Do you want to {ActionTag}? "Do you want to {go somewhere}?
[Previous SysResp: "No he podido resolver la acción a partir de tu petición"] "¿Quieres {ActionTag}? "¿Quieres {que te lleve a algún sitio}?"
Response in which the system tells the user that it has several options for an Action.
Response that the system gives when a command can be associated to more than one action.
Your command can be associated to many actions!
¡El comando puede asociarse a varias acciones!
Request that arises when the system has not been able to obtain an argument through an item + complement. The system suggests an alternative that contains the complement in the request.
Request: "Llévame a un laboratorio con micrófono". "No encuentro ningún/a {Item} con {Complement} como {argumentTag}, pero puedo sugerir {IDval_AlternativeItem}, que sí que tiene. ¿Le llevo ahí?" "No encuentro ningún/a {laboratorio} con {micrófono} como {el destino al que quiere que le lleve}, pero puedo sugerir {sala de reunión 1}, que sí que tiene. ¿Le llevo ahí?"
Request: "Take me to a laboratory with microphone". "I cannot find any {Item} with {Complement} as {ArgumentTag}, but I can suggest {IDval_AlternativeItem}, which it does have it. Do you want me to take you there?" "I cannot find any {laboratory} with {microphone} as {the destination you want to go}, but I can suggest {meeting room 1}, which it does have it. Do you want me to take you there?"
Request made to reassure the assignation of a value from the KEE to an Argument.
"El {Argument} es el {Argument_value}, ¿verdad?" "El Destino es el "Auditorio", ¿verdad?"
The {Argument} is {Argument_value}, isn't it? "The Destination is "Auditorium", isn't it?"
Request that demands a specific characteristic of the argument. This request is used when the argument provided is too broad and the system needs some characteristic that allows determining the specific element the user is refering to. For example, the user would require a "piece", and the system includes data for 300 types of pieces.
"Which {characteristic} is {too_broad_argument}?" "Which {colour} is (the) {piece}?"
"¿De qué {characteristic} es {too_broad_argument}? "¿De qué {color} es (la) {pieza}?"
Request that asks the user for some clarification for the value of an argument when a previously saved value generates too many options.
"Could you please be more specific with {ArgTag}?" "Could you please be more specific with {the destination you want me to take you}?"
"¿Puedes ser un poco más específico con el {ArgTag}?" "¿Puedes ser un poco más específico con el {destino al que quieres que te guíe}?"
Response that gives details about an Argument. For example, when the user does not understand what information conveys said Argument.
"El {Argument} corresponde a{ArgDescription}" "El {Error} corresponde a{l número de error que aparece en la máquina}"
"The {Argument} corresponds to {ArgDescription}" "The {Error} corresponds to {the ID of the error that appears in the machine}"
The system informs the user the Argument value provided is not valid according to what has been modelled in the KB.
This would imply an ArgumentRequest.
"{ArgumentValue} cannot be the {Argument}." "{Toilet} cannot be the {Error}."
"{ArgumentValue} no puede ser {Argument}." "{Baño} no puede ser {Error}."
Response given when the system has not been able to guess the value of the Argument through its characteristics.
This would imply an ArgumentRequest/ArgumentCharacteristicRequest
"Con las características que me has dado, no he podido averiguar el {Argument}." "Con las características que me has dado, no he podido averiguar el {Error}."
"I cannot guess the {Argument} with the information you provided." "I cannot guess the {Error} with the information you provided."
Response in which the system tells the user that it has several options for an Argument.
Response that the system gives when an item can be associated to more than one argument.
The item {item} can be associated to many arguments!
¡El item {item} puede asociarse a varios argumentos!
Request that demands for the value of an Argument.
"Can you tell me the {argument}? "Can you tell me the {Destination}?"
"¿Puedes decirme el {argument}?" "¿Puedes decirme el {Destino}?"
Request made when a value for an Argument can belong to different Arguments. The strategy is asking for each Argument option until the user confirms.
[Situation: the value "Mesa de reparación" could be Origin or Destination] [Previous SysResponse: "¡Lo que me has dicho podría ser varias cosas!"] "¿Es {el lugar al que quieres que te lleve}?" "¿Es {Argument}?"
[Situation: the value "Repairing table" could be Origin or Destination] [Previous SysResponse: "What you told me could correspond to many elements!"] "Is it {the place you want me to take you}?" "Is it {Argument}?"
Request that tries to obtain the value of the argument when it is ambiguous (e.g. "sala" may apply to "sala Ura", "sala Sua", etc.).
"Do you want {Action} {ArgumentConnector} {WorldElement}?" "Do you want {to go} {to} {Sala Ura}?"
"¿Quieres {Action} {ArgumentConnector} {WorldElement}?" "¿Quieres {que te guíe} {a} {Sala Ura}?"
Response in which the system tells the user that it has several options for an argument value.
Response that the system gives when it cannot associate an action/target to one or more actions.
I couldn't associate your command to an action. Can you please be more specific?
No he podido asociar tu comando a una acción. ¿Puedes repetir y ser más específico, por favor?
Response that informs the user that the command could not be resolved. [to be followed by an ArgRequest]
I could not resolve your command.
No he podido resolver tu petición.
Request that asks for specific information, other than "Yes" or "No" (and equivalents). Also known as "Non polar/Open question" in linguistics.
Which is the error code?
Step Function associated to a ContentRequest.
"Solo necesito que me digas sí o no, por favor"
"You only need me to tell me yes or no, please"
Reponse given to the user when the UserResponse is a ContentResponse and the SystemRequest requires a YesNoResponse.
Marker that conveys the idea of continuing with the dialogue process.
Elements that correspond to predefined or generic actions in dialogue control.
Response given by the system when the dialogue process has finished (i.e., when the user confirms the action and argument values)
Done!
¡Listo!
Step in the dialogue process that requires a system interaction with the user (SystemStep).
Marker that establishes that the dialogue must be finished.
Welcome message.
"Hi! I am {SystemName}. I am happy to help you." "Hi! I am {Teknibot}. I am happy to help you."
"¡Hola! Soy {SystemName}. Encantado de ayudarte." "¡Hola! Soy {Teknibot}. Encantado de ayudarte."
Request that checks which is the Argument/Action that has not been interpreter correctly, after a negative ReassureFeedbackRequest.
"Have I missed the {Argument}?" "Have I missed the {Origin}?"
"¿Me he equivocado con el {Argument}?" "¿Me he equivocado con el {Origen}?"
Request made when a UserRequest can belong to different Intents. The strategy is asking for each Intent option until the user confirms.
Situation: the Intent for the Request could be "Information" or "Guiding" "So many interpretations! See if you can help me! Do you need {Intent}?" "Then do you need {Intent}? SYS: "So many interpretations! See if you can help me! Do you need {Information}?" USR: "No" SYS: "Then do you need {Guiding}? USR: "Yes"
Situation: the intent for the Request could be "Information" or "Guiding" "¡Cuántas interpretaciones! ¡A ver si me puedes ayudar! ¿Quieres {Intent}?" "¿Entonces necesitas {Intent}? SYS: "¡Cuántas interpretaciones! ¡A ver si me puedes ayudar! ¿Quieres {que te dé información}?" USR: "No" SYS: "¿Entonces necesitas {que te lleve}? USR: "Sí"
El item {item} no es compatible con ningún argumento de la acción.
The item {item} is not compatible with any argument for this action.
The system informs the user the Item value provided is not compatible with any action argument, according to what has been modelled in the KB.
Response that is given when, after checking if all the core Arguments have been provided by the user command, there are core Arguments that are missing.
Hay información que me falta.
I still need some more information.
Request that asks the user whether they want to initiate a new dialogue process.
Do you need anything else?
¿Necesitas algo más?
Response that the system displays when it runs out of options. It is intended to continue with a full request of the element that the previous options corresponded to.
I do not have more options to offer you!
¡No tengo más opciones que mostrarte!
Response that the system displays when it runs out of options. It finishes the current Dialogue.
I do not have more options to offer you! Can you reformulate your command so I can understand better?
¡No tengo más opciones que mostrarte! ¿Puedes reformular tu comando para que te entienda mejor?
Response that the system returns when the clarification step of the value of an Argument does not return any results.
I cannot find anything that corresponds to your demand.
No encuentro ningún elemento que responda a lo que me pides.
Response that informs the user that the system has not understood the user command.
"I am sorry, but I haven't understood. Can you repeat, please?"
"Lo siento, no te he entendido. ¿Puedes repetir, por favor?
Response in which the system tells the user that it has several options for a specific element (e.g. WorldElement). Note the difference between OptionsAvailableResponse and TooManyAlternativesResponse: the first implies that there is a fair amount of options, whereas the latter implies that the options that are available are too many and it will require the user to be more specific.
"I have many options for your request."
"Tengo varias opciones para tu comando." "¡Lo que me has dicho puede ser varias cosas!"
Step in the dialogue process that does not require a system interaction with the user (SystemStep).
Step Function associated to a ProcessStep.
Request that is sent in order to obtain feedback whether the interpretation obtained is correct or not.
"Entonces, quieres que {Action} {ArgumentConnector} {Argument}, ¿verdad?" "Entonces, quieres que {te lleve} {a} {l baño}, ¿verdad?"
"So, you want me {Action} {ArgumentConnector} {Argument}, right?" "So, you want me {to take you} {to} {the toilet}, right?"
Request that demands the user to repeat the value of an Argument.
"Can you repeat the {Argument}? "Can you repeat the {Destination}?"
"¿Puedes repetir el {argument}?" "¿Puedes repetir el {Destino}?"
Reponse given to the user when the UserResponse does not correspond with the expected response of the SystemRequest.
Marker that requires the dialogue to restart.
Marker that returns to the last SystemResponse+Request/SystemRequest performed.
Element that is linked to a function in the Dialogue Manager code. This element also determines the implications of the output of said function in the code.
Act in which the system requires user input.
Ask for missing information, ask for confirmation.
Information that the system provides in response to a UserRequest or as a piece of information directed to the user without a prior UserRequest.
Step performed by the system in order to request information to the user or simply outputting information.
Response given when the number of possible Actions is too big.
Your command can be associated to too many actions! Can you repeat and be more specific, please?
¡Tu comando se puede asociar a demasiadas acciones! ¿Puedes repetir y ser un poco más específico, por favor?
Response given when the alternatives (in general) are too big.
"I have too many options taking into account the information you provided to me." "I have too many options taking into account the information you provided to me."
"Tengo demasiadas opciones con la información que me has dado." "Tengo demasiadas opciones con la información que me has dado."
Response given when the number of possible Arguments is too big.
Your command can be associated to too many arguments! Can you repeat and be more specific, please?
¡Tu comando se puede asociar a demasiados argumentos! ¿Puedes repetir y ser un poco más específico, por favor?
Response given when the number of possible World Elements is too big.
Your command can be associated to too many elements!
¡Tu comando se puede asociar a demasiados elementos!
Response given by the system to reassure the user that it has understood the request.
Request to the user to provide their (initial) command.
How can I help you? Tell me your command.
¿En qué puedo ayudarte? Dame tu comando.
Response given when the ArgValue for an Argument provided by the user is not compatible with said Argument.
"It cannot be the {Argument}". "It cannot be the {destination you want me to take you}".
"No puede ser {Argument}". "No puede ser {el lugar al que quieres que te lleve}".
Request that requires the user to repeat some information.
[Previous SysResponse: "This item cannot be {ArgTag}"] "Can you verify?" [Previous SysResponse: "This item cannot be {the destination}"] "Can you verify?"
[PreviousSysResponse: "Este elemento no puede ser {ArgTag}"] "¿Puedes verificarlo?" [PreviousSysResponse: "Este elemento no puede ser {el destino}"] "¿Puedes verificarlo?"
Request the response of which is expected to be limited to "Yes" or "No" (and equivalents). Also known as "Polar question" in linguistics.
Do you want to go to the laboratory?
Step Function associated to a YesNoRequest.
"Creo que no te he entendido. ¿Puedes ser un poco más concreto con tu respuesta?"
"I think I haven't understood. Can you be more specific?
Reponse given to the user when the UserResponse is a YesNoResponse and the SystemRequest requires a ContentResponse.