|Date/Time||October 17 2018 16:00 GMT|
|9:00am PDT/12:00pm EDT|
|5:00pm BST/6:00pm CEST|
Ontology Summit 2019 Planning
An explanation is the answer to the question "Why?" as well the answers to followup questions such as "Where do I go from here?" Accordingly, explanations generally occur within the context of a process, which could be a dialog between a person and a system or could be an agent-to-agent communication process between two systems. Explanations also occur is social interactions when clarifying a point, expounding a view, or interpreting behavior. In all such circumstances in common parlance one giving/offering an explanation.
Some Views from Philosophy and Science
A brief history of why explanations provides some context and includes the observation that among the first known attempts at understanding the why of explanations were those documented among Greek intellectuals and philosophers. For example, to understand and explain the why there was a Peloponnesian War Thucydides defined explanations as a process where facts (indisputable data), which are observed, evaluated based on some common knowledge of human nature. This was then compared in order to reach generalized principles for why some events occur. In the writings of Plato (e.g. Phedus and Theaetetus), we see explanations as an expression using logos knowledge composable by Universal Forms, which are abstractions of the world's entities we come to experience and know. Facts, in this view are occurrences or states of affairs and may be a descriptive part of an explanation, but not the deep Why. Aristotle's view, such as in Posterior Analytics provides a more familiar view of explanation as part of a logical, deductive, process using reason to reach conclusions. Aristotle proposed 4 types of causes (aitiai) to explain things. These were from either the thing's
- end, or
- change-initiator (efficient cause).
Following Descartes, Leibniz and especially Newton, modern deterministic causality using natural mechanisms became central to causal explanations. To know what causes an event means to employ natural laws as the central means to understand and explain why it happened. As this makes clear some notions of the nature of knowledge, how we come to know and the nature of reality are part of explanation.
John Stuart Mill, provides a deductivist account of explanation as evidenced by these 2 quotes:
“An individual fact is said to be explained, by pointing out its cause, that is by stating the law or laws of causation, of which its production is an instance,”
“a law or uniformity of nature is said to be explained, when another law or laws are pointed out, of which that law is but a case, and from which it could be deduced.”
The Ontology Summit 2019 is concerned with the role of ontologies for explaining the reasoning of a system. More specifically, the summit will focus on critical explanation gaps and the role of ontologies for dealing with these gaps. The sessions will examine current technologies and real needs driven by risks and requirements to meet legal or other standards.
Inspired by the current DARPA Explainable AI (XAI) Project, (see: https://www.darpa.mil/program/explainable-artificial-intelligence ) the Ontology Summit theme considers the general problem of explanation. We are interested not only in AI systems that can explain their actions and what they believe but also in other smart engineering systems which may cooperate with and aid humans. With the increasing amount of software devoted to industrial automation and process control, it is becoming more important than ever for systems to be able to explain their behavior to humans. Explanations include expressing rationales, characterizing strengths and weaknesses, and projecting their behavior into the future.
Ontologies could play a significant role in explanations since such agents must represent the conceptual framework that supports explanation. Such explanations would include terms for domain and natural world concepts, relations, and activities. Some version of natural language may be used to describe states and actions in terms that people easily understand, as well as the conceptual structures within which dialog, plans and actions take place.
A benefit of the use of ontologies in support of explanations is the potential for improving interoperability between systems that otherwise would not have a common framework for interoperation. The danger is that current efforts for explainability will be brittle as well as siloed, which will produce a large variety of incompatible explanation techniques that individually satisfy the requirement of providing explanations but which are of little use when explainable subsystems are integrated into large scale systems.
In the usual sense, Ontologies are designed knowledge artifacts but exist in computational (operational) environments which allow reasoning and so should also include the ability to reason about/explain what they know and how they have reasoned with this knowledge. In particular, they should be able to express the rationale for the selected use of the relevant parts of an ontology or suite of ontologies; explain the strengths and weaknesses of the ontology; and, when the ontology is in use, explain data that conforms to the ontology.
Explanations and help facilities designed for people
Co-Champions: John Sowa
Basic principle: It's irrelevant how much you know about computer hardware, software, and systems design. When you are faced with some system designed by somebody else, you are as much a novice as anybody who walks in off the street.
Help facilities for any kind of system are abysmal, and they are getting worse -- primarily because the complexity of hardware/software systems is growing much faster than any help facilities that explain how they work.
People who buy a new car, for example, never learn how to use all its so-called "features" before they buy its replacement. Anybody who rents a car will be driving on a highway before discovering features that may be critical for safety.
Issues: How do current help and explanation facilities work? What are the underlying mechanisms for implementing them, invoking them, and using them? How can they be improved? What kinds of AI facilities could improve them? What are the R & D directions and possibilities for improved design?
Goal: Make help and explanation facilities as useful and usable as a guru or geek sitting next to you. Even better, make them as usable as a kind and forgiving friend who knows what you want.
Overview of Explainable AI
Main Tracks and Sessions
All co-champions introduce their tracks.
Explainable AI in Medicine has several facets.
- One facet is explaining a suggested decision made by an computer system and what justification supports it to the medical provider who is diagnosing a malady.
- Another is explaining a medical process to the patient who might be a participant and their support team.
- Similarly, there is the explanation and justification to the billed party of such a process and why it is coded the way it is, whether that billed party is the patient, an insurance company or some other financier.
- A final facet is explaining the medical record to a future reader tracing the process of care.
Some discussion of this is at https://medcitynews.com/2018/10/how-do-you-make-doctors-trust-machines-in-an-ai-driven-clinical-world/ Another useful set of papers by Peter Szolovitz are at http://groups.csail.mit.edu/medg/people/psz/home/Pete_MEDG_site/Publications.html
Co-Champions: Gary Berg-Cross and Torsten Hahmann (U of Maine) An early goal of AI was to teach/program computers with enough factual knowledge about the world so that they could reason about it in the way people do. The starting observation is that every ordinary person has "commonsense" or basic knowledge about the real world that is common to all humans. Spatial and physical reasoning are good examples. This is the kind we want to endow our machines with for several reasons including as part of conversation and understanding. System understanding of human perceptual and memory limitations might, for example, be an important thing for a dialog system to know about.
Early on this was describe as giving them a capacity for "commonsense". However, early AI demonstrated that the nature and scale of the problem was difficult. People seemed to need a vast store of everyday knowledge for common tasks. A variety of knowledge was needed to understand even the simplest children's story. A feat that children master with what seems an natural process. One resulting approach was an effort like CyC to encode a broad range of human commonsense knowledge as a step to understanding text which would bootstrap further learning. Some believe that today this problem of scale can be addressed in a new ways including via modern machine learning. But these methods do not build in an obvious way to provide machine generated explanations of what they "know." As fruitful explanations appeal to folks understanding of the world, common sense reasoning would be a significant portion of any computer generated explanations. How hard is this to build into smart systems? One difficult aspect of common sense is making sure the explanations are presented at multiple levels of abstraction, i.e. from not too detailed to tracing exact justifications for each inference step.
This track will explore these and other issues in light of current ML efforts and best practices for AI explanations.
- Select tracks and co-champions
Conference Call Information
- Date: Wednesday, 17-October-2018
- Start Time: 9:00am PDT / 12:00pm EDT / 6:00pm CEST / 5:00pm BST / 1600 UTC
- ref: World Clock
- Expected Call Duration: 1 hour
- The Video Conference URL is https://zoom.us/j/689971575
- iPhone one-tap :
- US: +16699006833,,689971575# or +16465588665,,689971575#
- Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8665
- Meeting ID: 689 971 575
- International numbers available: https://zoom.us/u/Iuuiouo
- iPhone one-tap :
- Chat Room
- Alex Shkotin
- Gary Berg-Cross
- Janet Singer
- Ken Baclawski
- Mike Bennett
- Ram D. Sriram
- Ravi Sharma
- Todd Schneider
[12:17] Gary Berg-Cross: I am back from travels.
[12:22] ToddSchneider: Are we assuming 'explanations' use 'reasoning'?
[12:22] RaviSharma: David Whitten did contribute last year and NIH and NLM folks might also be able to add to Ram's efforts / track
[12:23] Ken Baclawski: Gary would like a track on common sense.
[12:23] RaviSharma: Todd Yes I think but not always?
[12:23] AlexShkotin: @Todd - Yes.
[12:24] RaviSharma: Todd for example facts from database already accepted or known may not require reasoning again?
[12:24] Gary Berg-Cross: Reasoning and explanation - think of a Venn diagram. Some overlap but the dynamics of how they relate is the more interesting and complex Q.
[12:24] ToddSchneider: Then we may need a introductory presentation on 'reasoning', in its various forms.
[12:24] MikeBennett: @Todd good question.- at least for the business facing things (finance, medical) surely it's about a range of tech techniques (semantic query, inference processing) explained in terms that the stakeholder can understand.
[12:26] RaviSharma: Todd it is a good idea as it would create a notional Venn diagram that would list the extent Explanations and reasoning are related.
[12:36] ToddSchneider: Gary's suggestion on how a track could be organized, general situation, then how ontologies can help, would be very good.
[12:36] Gary Berg-Cross: The point on ontologies and explanation I tried to make in the EMycin example is that there is notable experience with explanations that involve rules and other artifacts and designs that do not use ontologies in a central way or at all.
[12:38] ToddSchneider: So we need a presentation on possible mechanisms for explanation?
[12:39] MikeBennett: Ontology is not just reasoning. You can do SPARQL (semantic) queries. You can use the reasoner to classify subject matter and you can dump the results in to some other data store to carry out mathematical operations, graphical explanations; you can run higher orders of logic / procedural code etc. over such data, and so on. All ontology based, not all reasoning.
[12:40] Gary Berg-Cross: If we do a fall session we should ask ourselves what we learned at this approach from last year.
[12:46] Gary Berg-Cross: If last Fall was more popular we should try to understand why. Is the ontology addition a bit more of a heavy lift??
[12:48] ToddSchneider: Ken, Gary, you need to isolate your microphone from the desktop and the keyboard.
[12:48] Gary Berg-Cross: One suggestion for improvement is that we should end the Fall session with some clearly stated idea of how the Spring sessions will build on the generated interest and address some issues identified.
[12:50] Gary Berg-Cross: We did have problems getting speakers for some tracks. Let's develop a spreadsheet on possible speakers for tracks that we can share. This has worked in the past.
[12:55] Ken Baclawski: Ram will help find speakers for one or two XAI sessions in the Fall, and John will find a speaker on help systems.
[12:56] RaviSharma: I think XAI will help us find examples and domains
[12:59] Gary Berg-Cross: I won't be able to be on the call next Wed. I am running my annual ontology VoCamp at NIH next week.
[13:00] Gary Berg-Cross: Nov. 7th session - John, maybe Donna???
[13:01] Gary Berg-Cross: I will also miss the meeting of the 7th - I am overseas that week.
[13:03] Gary Berg-Cross: The Workshop IJCAI 2017 Workshop on Explainable Artificial Intelligence (XAI) http://home.earthlink.net/~dwaha/research/meetings/ijcai17-xai/ Some speakers would likely come from that workshop.
[13:05] Gary Berg-Cross: Possible speaker http://home.earthlink.net/~dwaha/
Recent AI Magazine co-authored articles/covers:
Goal Reasoning (Summer 2018)
AI Rebel Agents (Fall 2018)
AAAI-19 Senior Member Presentation Track
XAI Meetings & Events
Special Issue in AI Communications: Goal Reasoning
Intelligent LL Processes
[13:09] Gary Berg-Cross: I will try to find a speaker on commonsense.