language en

The Explanation Experience Ontology

Latest version:
https://www.w3id.org/iSeeOnto/explanationexperience
Contributors:
Anjana Wijekoon
Chamath Palihawadana
David Corsar
Ikechukwu Nkisi-Orji
Juan A. Recio-Garcia
Marta Caro Martínez
Imported Ontologies:
explanationPattern.owl
sio.owl
cpannotationschema.owl
prov-o#
aimodel
eo
Download serialization:
RDF/XML
License:
http://insertlicenseURIhere.org
Visualization:
Visualize with WebVowl
Cite as:
The Explanation Experience Ontology.
Ontology Specification Draft

Abstract

The Explainer Ontology is an ontology that models the technique used by an Explainer (as defined by the Explanation Ontology), to generate an Explanation. The concepts in this ontology reflect the a subset of the explanability fact sheet dimensions defined by Kacper Sokol and Peter Flach. 2020. Explainability fact sheets: a framework for systematic assessment of explainable approaches, in Proceedings of the 2020 Conference on Fairness, Accountability, and Transparency (FAT* '20) DOI:https://doi.org/10.1145/3351095.3372870. This ontology was created as part of the iSee project (https://isee4xai.com) which received funding from EPSRC under the grant number EP/V061755/1. iSee is part of the CHIST-ERA pathfinder programme for European coordinated research on future and emerging information and communication technologies.

Introduction back to ToC

Namespace declarations

Table 1: Namespaces used in the document
ee<https://www.w3id.org/iSeeOnto/explanationexperience>
schema<http://schema.org>
owl<http://www.w3.org/2002/07/owl>
xsd<http://www.w3.org/2001/XMLSchema>
skos<http://www.w3.org/2004/02/skos/core>
rdfs<http://www.w3.org/2000/01/rdf-schema>
cito<http://purl.org/spar/cito>
bt<https://www.w3id.org/iSeeOnto/BehaviourTree>
prov-o<http://www.w3.org/TR/prov-o>
terms<http://purl.org/dc/terms>
userevaluation<http://www.w3id.org/iSeeOnto/userevaluation>
xml<http://www.w3.org/XML/1998/namespace>
vann<http://purl.org/vocab/vann>
aimodel<http://www.w3id.org/iSeeOnto/aimodel>
prov<http://www.w3.org/ns/prov>
foaf<http://xmlns.com/foaf/0.1>
void<http://rdfs.org/ns/void>
resource<http://semanticscience.org/resource>
protege<http://protege.stanford.edu/plugins/owl/protege>
cpannotationschema<http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl>
eo<https://purl.org/heals/eo>
explanationexperience<http://www.w3id.org/iSeeOnto/explanationexperience>
core<http://purl.org/vocab/frbr/core>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns>
obo<http://purl.obolibrary.org/obo>
user<http://www.w3id.org/iSeeOnto/user>
explainer<http://www.w3id.org/iSeeOnto/explainer>
dc<http://purl.org/dc/elements/1.1>

The Explanation Experience Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

The Explanation Experience Ontology: Description back to ToC

Outline of the Explanation Experience ontology main classes and relationships
Outline of the Explanation Experience ontology main classes and relationships. Concepts highlighted in orange are defined in this ontology.

Cross reference for The Explanation Experience Ontology classes, properties and dataproperties back to ToC

This section provides details for each class and property defined by The Explanation Experience Ontology.

Classes

behaviour treec back to ToC or Class ToC

IRI: https://www.w3id.org/iSeeOnto/BehaviourTree#BehaviourTree

has super-classes
Solution c

Case Featurec back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#CaseFeature

Classes defined as subclasses of Case Feature are suitable to be used as types of features in a case description.
has sub-classes
Explanation Requirements c, user group c

Descriptionc back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#Description

Defines the description of a case using classes defined in other iSeeOnto ontologies to define the query in terms of the AIModel, eo:Explainer (defined in the Explainer Ontology), and eo:User (defined in the Explanation Ontology).
has super-classes

Explanation Criteriac back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#ExplanationCriteria

Defines a criteria that must be satisfied by an explanation or the generation of an explanation.
Example
Specifies a criteria of the form: 'created by an explainability technique that has concurrentness post-hoc'.
has super-classes

Explanation Experiencec back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#ExplanationExperience

The Explanation Experience classis intended to capture an individual case in terms of the eo:AIModel used, the Explainer being used, and the User and the Solution created as an Explanation Strategy to satisfy the explanation needs of a user.
has super-classes

Explanation Requirementsc back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#ExplanationRequirements

Defines the criteria that should be (ideally fully) satisfied when generating an explanation to be provided to an agent
has super-classes
Case Feature c

Outcomec back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#Outcome

A summary of the user evaluations conducted throughout the explanation experience
has super-classes

Solutionc back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#Solution

The Solution class is intended to describe the Workflow (defined in the workflow ontology) created as an Explanation Strategy to satisfy the Explanation needs of a user.
has sub-classes
behaviour tree c

user groupc back to ToC or Class ToC

IRI: http://www.w3id.org/iSeeOnto/user#User_Group

has super-classes
Case Feature c

Object Properties

has AI Modelop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasAIModel

Relationship between a Description and a AI Model.
has super-properties
top object property

has descriptionop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasDescription

Relationship between an Explanation Experience and a Description.

has explainerop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasExplainer

Relationship between a Description and an Explainer.

has explanation criteriaop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasExplanationCriteria

Relationship between the requirements an Explanation or the generation of an Explanation must satisfy and a Criteria specifying the requirements on a particular relationship.

has explanation requirementsop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasExplanationRequirements

has featureop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasFeature

has outcomeop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasOutcome

has solutionop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasSolution

Relationship between an Explanation Experience and a Solution.

has userop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasUser

Relationship between a Description and a User

has user groupop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasUserGroup

has workflowop back to ToC or Object Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#hasWorkflow

Relationship between a Solution and a Workflow
has super-properties
top object property

Data Properties

on propertydp back to ToC or Data Property ToC

IRI: http://www.w3id.org/iSeeOnto/explanationexperience#onProperty

has characteristics: functional

has range
any u r i

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals

References back to ToC

Add your references here. It is recommended to have them as a list.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.