Professional Documents
Culture Documents
E Rock@Ro Man2017pub
E Rock@Ro Man2017pub
Stefano Borgo
Laboratory for Applied Ontology
ISTC-CNR, Trento (IT) Tutorial at RO-MAN 2017
Table of Contents
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 2
Scenario: Robot + Worker
http://www.all-electronics.de
http://www.riken.jp
https://i.ytimg.com/vi/jC-AmPfInwU/maxresdefault.jpg
M6
M5 M7
M1
M6
M4 M5
S1
M4
M2
S2
M3 M2
NOITARUGIFNOC CONFIGURATION
2 CONFIGURATION
CONFIGURATION
2 2 CONFIGURATION 1 1 1 1
2CONFIGURATION
NOCONFIGURATION
ITARCONFIGURATION
UGICONFIGURATION
FNOC 2
F
F
F
F
F
F
F
F
F
Scenario: Robot + Controlled
2CLC2
R LC2 LC2LC2
2CL RC2RC2 RC2RC2
B
B
B
B
B
B
B
B
B
!
!
!
!
!
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 9
Applied ontology: about 30 years ago...
I Late 1980s (AI community):
the term ontology is used (along with others like “semantic
domain”, “knowledge view”) but it still conflates the world
representation and the knowledge system component.
I 1993: 1st Intern. workshop on Formal Ontology &
Information Systems
I mid 90s: “ontology” in the topic list of conferences and
international meetings
I mid 90s: IEEE SUO Working Group
I 1998: 1st event of the FOIS series
I 2002: Ontolog forum (virtual community of practice)
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 10
...untill today
I 2005:
- Applied Ontology Journal (IOS Press)
- ECOR, NCOR, JCOR...
- the FOMI series starts (Formal ontology meets industry)
I 2006: First public discussion on an ontology association at
FOIS (Baltimore)
I 2009: the International Association for Ontology and its
Applications (IAOA) is established
I TODAY: regular conferences and workshops on ontology
(e.g. JOWO Setp. 21-23, Bolzano IT; FOIS at Cape Town, Sept. 2018)
In parallel:
- ontology standardization initiatives (W3C, OMG, IEEE, ISO)
- ontology shapes various domains (Snomed, FMA, DB)
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 11
- ontology tool development (Protege, CommonKAD,OntoUML)
Ontology is a philosophical notion
“The piece is at 50 C”
“The piece is hot”
Are these consistent?
Can these be integrated?
Under which conditions?
one claim is objective – the other claim is relative and/or
contextual S. Borgo, Ro-Man Tutorial 28 Aug. 2017 15
From ontology to applied ontology
Sources of heterogeneity:
I system heterogeneity
I syntactic heterogeneity
I structural heterogeneity
I semantic heterogeneity
Artefact
Physical object(s)
Piece(s) of matter
Shape(s)
Outline(s)
Pattern(s) of colors
Shades
Holes
Bumps
...
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 22
Ontology in an information system
The ontology
I constrains the interpretation of the language
I constrains the possible situations that we can describe
with the language.
I gives a design rationale for knowledge:
– necessary vs possible vs impossible situations
– managing knowledge
– scaling up knowledge
– coherent and consistent knowledge accumulation
I Application
Application for production of X
Task in production of X
Drilling of X
Tip centering for drilling in X
I Application
Application for production of X
Task in production of X
Drilling of X
Tip centering for drilling in X
Change in application
Change in application for production of X
Change in task in production of X
Change in drilling of X
Change in tip centering for drilling of X
∀x(Screwdriver(x) → Tool(x))
Tool(Tester_A123)
“The individual Tester_A123 is a member of category Tool”
Spatial parthood
Part(Loc(Slot), Loc(Screwdriver))
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 39
Types of entities
We always talk of ontologies (plural) because different
ontological assumptions lead to different systems which
are motivated by different cognitive/conceptual systems.
These systems may differ even on the types of entities
they assume to exist.
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 43
The DOLCE-core ontology
Physical
Location-Quality Location-Space
Object
Is-part-of
Gripper_73
(the concrete object)
Positions: a,b,c,... Positions: Euclidean loci Positions: 0D, 1D, 2D, 3D, Other ....
[A space with infinite positions] [A geometric space] [A space with 5 positions]
....
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 55
Artifacts
Selection Constituted
(generic) entity
Attribution
Attributed
physical
property Agent Action
Definition
A device-centric function of a device for an agent is a set
of behavioral constraints that are
(1) satisfied by the device
(2) intended by the agent.
Definition
A environment-centric function of a device in an
environment is a set of behavioral constraints that are
(1) caused by the device
(2) intended by an agent.
This presupposes that the device is deployed in the
environment as specified by a mode of deployment.
Definition
A mode of deployment of a device in an environment is a
specification of all causal interactions between the device
and the environment.
Those interactions may include:
(1) structural relations between the device and the
objects in the environment
(2) actions such that
I they impact on the device
I the environment’s objects participate in them.
FUNCTION
(as effect)
CHANGE STABILIZE
BRANCH MAGNITUDE RECEIVE
CHANGE
OVER RELEASE
information change of change on change on information
collection operand(s) qualities relations sharing
FUNCTION
(as effect)
CHANGE STABILIZE
BRANCH MAGNITUDE
CHANGE
OVER RELEASE
information change of change on change on
collection operand(s) qualities relations
From “Classifying Compliant Manipulation Tasks for Automated
Planning in Robotics”,D. Leidner et al., IROS 2015
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 78
Classifying manipulation tasks /2
Problem 6b: Classify ontologically some tasks.
FUNCTION
(as effect)
TEST ACTION CO
CHANGE STABILIZE
BRANCH MAGNITUDE
CHANGE
OVER RELEASE
information change of change on change on
collection operand(s) qualities relations
From “Classifying Compliant Manipulation Tasks for Automated
Planning in Robotics”, D. Leidner et al., IROS 2015
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 84
Environment
http://www.wirecrafters.com/
http://www.wirecrafters.com/
https://www.thesun.co.uk/
Design science:
“Context knowledge identifies the exogenous variables for a
design situation and specifies that values for these variables
must come from outside the design prototype, that is, from the
context (C).”
“The context is defined by the available design prototypes. [....]
This move [outside the available design prototypes] can be
seen as the designer changing the context in which s/he is
working.” [J. Gero, 1990]
Context-aware systems:
“A real world entity to be represented is always related to a
context. A semantically consistent body of information in which
the entity makes sense.
The need of contexts? In mobile applications, where the
environment suffer dynamic reconfigurations.” [Cafezeiro et al.,
2008]
Guiding scenarios
Why ontology?
Managing information with an Ontology
Entities and their connections
An ontology: DOLCE
Artefacts, Functions and Agents
Environment and Context
Rules and Reasoning
S. Borgo, Ro-Man Tutorial 28 Aug. 2017 104
Recall the Robot in the controlled environment scenario
M6
M5 M7
M1
M6
M4 M5
S1
M4
M2
S2
M3 M2
F
F
F
F
F
F
F
F
2CLC2
R LC2 LC2LC2
2CL RC2RC2 RC2RC2
B
B
B
B
B
B
B
B
B
!
!
!
!
!
Knowledge)Processing)Mechanism)
Classifica.on(Rules( Capability((
Inference(Rules(
kb0
Taxonomy((
Contexts( of(Func.ons(
Low9level)Reasoning) High9level)Reasoning)
Mechatronic)
Module/Controller)
I list of engines/actuators
GLOBAL CONTEXT
module-t2 module-t4
module-t3 hasLoc
connection
connection module-t7
hasLoc hasLoc
connection LOCAL CONTEXT connection
connection
hasPart
conveyor hasLoc
hasPart
hasPart port-b
module-t1
INTERNAL CONTEXT
hasLoc
port-f port-b hasLoc
hasComp
hasComp
hasCollab
hasCollab
module-t1
Channel-‐F-‐B
Neighbor-‐F
TM Channel Channel-‐F-‐L1
F
Channel-‐L1-‐F
Idle
Channel-‐B-‐F
Neighbor-‐L1
SEMANTIC FUNCTIONAL
TU1
MAPPING
R1
L1
Cross Engine 1
L2
Main
Conveyor Forward
Cross Engine 3
SAll
Backward
Cross Engine 2
PRIMITIVE
TU3
RECONF
R3
L3
Online
Neighbor-L1
Neighbor-F
Offline
Failure
B
MalfuncAoning
Neighbor-B
Neighbor-‐B
EXTERNAL
Why ontology?
An ontology: DOLCE
More questions?