Convology (Conversational Ontology)

IRI:
https://perkapp.fbk.eu/convology/ontology/core
Date:
2019-04-11
Current version:
1.00
Authors:
Giuseppe Rizzo
Mauro Dragoni
Publisher:
Process and Data Research Group, Fondazione Bruno Kessler <https://pdi.fbk.eu>
RDF version:
RDF/XML (.owl), Turtle (.ttl), NTriples (.nt)
CreativeCommons 4.0 NonCommercial-ShareAlike <https://creativecommons.org/licenses/by-nc-sa/4.0/>

Table of Content

  1. Classes
  2. Object Properties
  3. Data Properties
  4. Annotation Properties
  5. Namespace Declarations

Classes

Actorc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Actor

The Actor concept defines the different roles that can take part into a conversation. Within Convology, we foresee two main roles represented by the concepts Agent and User.
has sub-classes
Agentc, Userc
is in domain of
performed Eventop, received answerop, received questionop, sent answerop, sent questionop

Agentc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Agent

Instances of the Agent concept are conversational agents that interact with users. When Convology is deployed into an application, instances of Agent concept represents the different agents involved into the conversations with the users adopting the application. Within the same application, Convology will have a different instance of the Agent concept for each User even if the application is the same. The rationale behind is that different active conversations may be in different statuses. Hence, for favoring the efficiency of reasoning activity, different instances are created into the ontology. Finally, different instances of the Agent concept are associated with different instances of the Dialog concept.
has super-classes
Actorc
is in range of
has Botop

Conversation Itemc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#ConversationItem

A ConversationItem is an entity taking part into a conversation and that allows to represent relevant knowledge for supporting each interaction. Within Convology, we defined four subclasses of the ConversationItem concept: Question, Intent, Feedback, and DialogAction.
has sub-classes
Dialog Actionc, Feedbackc, Intentc, Questionc

Dialogc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Dialog

The Dialog concept represents a multi-turn interaction between a User and one or more Agent. A new instance of the Dialog concept is created when a user starts a conversation with one of the agents available within a specific application. The hasId datatype property associated with the Dialog instance works as tracker for all the interactions made during a single conversation between a User and the involved Agent. Furthermore, the value of this property is used at reasoning time for extracting from the knowledge repository only the data related to a single conversation in order to maintain the efficiency of the reasoner suitable for a real-time environment.
is in domain of
has Questionop, has feedbackop
is in range of
refers to Dialogop

Dialog Actionc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#DialogAction

Instances of the DialogAction concept describes the next action that an Agent individual has to perform. DialogAction individuals can be defined by domain experts as consequences of the detection of specific intents or can be generated as result of reasoning activities and associated with a DialogStatus instance. Individuals of type DialogAction are associated with a Question or a Feedback individual representing the next message sent to a User. Moreover, a DialogAction might have the datatype property waitTime set, i.e. the amount of seconds that the system must wait before sending the Question or the Feedback to the User.
has super-classes
Conversation Itemc
is in domain of
has Questionop, has feedbackop, wait timedp
is in range of
has DIalog Actionop, triggersop

Dialog Statusc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#DialogStatus

A DialogStatus individual provides a snapshot of a specific Dialog at a certain time. Entities associated with a DialogStatus individual are the Dialog which the status refers to, the identifiers of the User and of the one or more Agent involved into the conversation, and the DialogAction that has to be performed as next step. Individuals of type DialogStatus are created at reasoning time after the processing of the Intent recognized by the system.
has super-classes
Statusc
is in domain of
has Botop, has DIalog Actionop, has Userop, refers to Dialogop

Eventc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Event

The Event concept describes a single event that can occur during a conversation. Within Convology, we identified three kinds of events: EventQuestion, EventAnswer, and UserEvent. Instances of these concepts enable the storage of information within the knowledge repository, trigger the execution of the reasoning process, and allow the retrieval of information for both analysis and debugging purposes.
has sub-classes
Event Answerc, Event Questionc, User Eventc
is in domain of
has timestampdp
is in range of
performed Eventop

Event Answerc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#EventAnswer

The EventAnswer concept represents an Answer provided by an Actor. The timing information associated with individuals of this concept is defined through the hasTimestamp datatype property, while the sender and the receiver are defined by the sentAnswer and receivedAnswer object properties.
has super-classes
Eventc
is in range of
received answerop, sent answerop

Event Questionc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#EventQuestion

An EventQuestion represents the fact that a Question has been submitted to an Actor. Here, we do not make distinctions between the actors because, from a general perspective, the model supports scenarios where questions are sent from a User to an Agent. Instances of this concept are associated with knowledge allowing to identify the timing (hasTimestamp datatype property), the Actor instance that sent the question (sentQuestion object property), and the Actor instance that received the question (receivedQuestion object property).
has super-classes
Eventc
is in range of
received questionop, sent questionop

Feedbackc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Feedback

A Feedback represents a simple sentence that an Agent can send to users and for which it does not expect any reply. Feedback are used for closing a conversation as result of the reasoning process or simply for sending single messages to users without requiring any further interaction.
has super-classes
Conversation Itemc
is in range of
has feedbackop

Intentc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Intent

An Intent represents a relevant information, detected within a natural language answer provided by a User, that the NLU module is able to recognize and that the reasoner is able to process. Concerning the mention to the NLU module, it is important to clarify that the detection of an Intent within a user's answer requires the integration of a NLU module able to classify the content of users' answers with respect to each Intent associated with the Question sent to a User. Hence, one of the pre-requisites for deploying Convology into a real-world system is the availability of a module that maps the content of users' answers with the instances of the Intent concept defined into the ontology. The possible strategies that can be implemented for supporting such a mapping operation are out of scope of this paper. An Intent is then associated with a StatusItem through the activated object property: once a specific Intent is recognized, a StatusItem instance is created into the knowledge repository for supporting the inference of the user's status.
has super-classes
Conversation Itemc
is in domain of
activatesop, triggersop
is in range of
has Intentop, has recognized intentop, has relevant intentop

Questionc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Question

An individual of type Question represents a possible question that an instance of type Agent can send to a User. Instances of Question are defined by domain experts together with all the Intent individuals that are associated with each Question through the hasRelevantIntent object property. A Question can be associated with also a specific UserEvent through the hasTriggerQuestion object property.
has super-classes
Conversation Itemc
is in domain of
has relevant intentop
is in range of
has Questionop, has trigger Questionop

Statusc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#Status

This Status concept subsumes concepts describing the possible statuses of users, through the UserStatus and StatusItem concepts, or of dialogues, through the DialogStatus concept.
has sub-classes
Dialog Statusc, Status Itemc, User Statusc

Status Itemc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#StatusItem

\rdf{StatusItem} individuals represent atomic conditions under which a UserStatus can be activated. Generally, not all StatusItem has to be activated for inferring, in turn, a UserStatus.
has super-classes
Statusc
is in domain of
is activateddp
is in range of
activatesop, has Status Itemop

Userc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#User

Instances of the User concept represents the actual users that are dialoguing with the conversational agent. A new instance of the User concept is created when a new user starts a conversation within a specific application. An instance of the User concept can be associated with different instances of the Dialog and Agent concepts. The reasons for which this does not happen for the Agent concept (i.e. an Agent instance can be associated with one and only one instance of User) is because the focus of Convology is to track and support the conversations from the user perspective. Thus, the ontology maintains a single instance of User for each deployment of \convology due to the necessity of tracing the whole history of users.
has super-classes
Actorc
is in domain of
has User Statusop
is in range of
has Userop

User Eventc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#UserEvent

A UserEvent represents an Event associated with a specific user. The purpose of having a specific UserEvent concept instead of inferring UserEvent objects from the EventQuestion and EventAnswer individuals is that a UserEvent does not refer only to questions and answers but also to other events that can occur. Examples are the presence of one or more Intent within users' answer (this kind of knowledge cannot be associated with EventAnswer individuals because Agent instances do not provide Intent within an answer) or information about users' action that are not directly connected with the conversation (the storage of these information is important in case of it is of interest to analyze users' behaviors). The relationship between a UserEvent and an Intent is instantiated through the hasRecognizedIntent object property. Finally, instances of UserEvent can trigger the activation of a specific UserStatus (explained below) as result of the reasoning process. Triggering events are instantiated through the hasTriggerQuestion and triggers object properties. The former allows to put in relationship a UserEvent with a Question. The latter associates a UserEvent with a specific UserStatus. Both relationships are defined as result of the reasoning process.
has super-classes
Eventc
is in domain of
has recognized intentop, has trigger Questionop, triggersop
is in range of
has User Eventop

User Statusc back to ToC or Class ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#UserStatus

Instances of the UserStatus concept are defined by the domain experts and they represent which are the relevant statuses of a User that the conversational agent should discover during the execution of a Dialog. A UserStatus is associated with a set of UserEvent that, in turn, are associated with Intent individuals. This path describes which is the list of Intent enabling the classification of a User with respect to a specific UserStatus.
has super-classes
Statusc
is in domain of
has Status Itemop, has User Eventop, is activateddp
is in range of
has User Statusop, triggersop

Object Properties

activatesop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#activates

has domain
Intentc
has range
Status Itemc

has Botop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasBot

has domain
Dialog Statusc
has range
Agentc

has DIalog Actionop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasDialogAction

has domain
Dialog Statusc
has range
Dialog Actionc

has feedbackop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasFeedback

has domain
Dialogc
Dialog Actionc
has range
Feedbackc

has Intentop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasIntent

has sub-properties
has recognized intentop, has relevant intentop
has domain
thingc
has range
Intentc

has Questionop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasQuestion

has domain
Dialogc
Dialog Actionc
has range
Questionc

has recognized intentop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasRecognizedIntent

has super-properties
has Intentop
has domain
User Eventc
has range
Intentc

has relevant intentop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasRelevantIntent

has super-properties
has Intentop
has domain
Questionc
has range
Intentc

has Status Itemop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasStatusItem

has domain
User Statusc
has range
Status Itemc

has trigger Questionop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasTriggerQuestion

has domain
User Eventc
has range
Questionc

has Userop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasUser

has domain
Dialog Statusc
has range
Userc

has User Eventop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasUserEvent

has domain
User Statusc
has range
User Eventc

has User Statusop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasUserStatus

has domain
Userc
has range
User Statusc

performed Eventop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#performedEvent

has sub-properties
received answerop, received questionop, sent answerop, sent questionop
has domain
Actorc
has range
Eventc

received answerop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#receivedAnswer

has super-properties
performed Eventop
has domain
Actorc
has range
Event Answerc

received questionop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#receivedQuestion

has super-properties
performed Eventop
has domain
Actorc
has range
Event Questionc

refers to Dialogop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#refersToDialog

has domain
Dialog Statusc
has range
Dialogc

sent answerop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#sentAnswer

has super-properties
performed Eventop
has domain
Actorc
has range
Event Answerc

sent questionop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#sentQuestion

has super-properties
performed Eventop
has domain
Actorc
has range
Event Questionc

triggersop back to ToC or Object Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#triggers

has domain
Intentc
User Eventc
has range
Dialog Actionc
User Statusc

Data Properties

has timestampdp back to ToC or Data Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#hasTimestamp

has domain
Eventc
has range
long

is activateddp back to ToC or Data Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#isActivated

has domain
Status Itemc
User Statusc
has range
int

wait timedp back to ToC or Data Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#waitTime

has domain
Dialog Actionc
has range
int

Annotation Properties

idap back to ToC or Annotation Property ToC

IRI: https://perkapp.fbk.eu/convology/ontology/core#id

Namespace Declarations back to ToC

default namespace
https://perkapp.fbk.eu/convology/ontology/core#
core
https://perkapp.fbk.eu/convology/ontology/core#
ontology
https://perkapp.fbk.eu/convology/ontology/
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
terms
http://purl.org/dc/terms/
vann
http://purl.org/vocab/vann/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.