1. OntonutsOntonuts Reusable semantic components for multi-agent systems Sergiy Nikitin Industrial Ontologies Group, University of Jyväskylä, Finland

2. The paper

3. GUN Concept GUN – Global Understanding eNvironment GUN = Global Environment + Global Understanding = Proactive Self-Managed Semantic Web of Things = ( we believe ) = “Killer Application” for Semantic Web Technology

4. What is UBIWARE (in short) UBIWARE is a middleware tool to support:UBIWARE is a middleware tool to support:  design and installation of…,  autonomic operation of… and  interoperability among… … complex, heterogeneous, open, dynamic and self- configurable distributed industrial systems;…… complex, heterogeneous, open, dynamic and self- configurable distributed industrial systems;… … and to provide following services for system components:… and to provide following services for system components:  adaptation;  automation;  centralized or P2P organization;  coordination, collaboration, interoperability and negotiation;  self-awareness, communication and observation;  data and process integration;  (semantic) discovery, sharing and reuse.

5. UBIWARE Architecture.class Blackboard Roles RABRABRAB RAB Beliefs storage UBIWARE Agent (Live) Pool of Atomic Behaviours S-APL repository S-APL Data

6. S-APL language Key features:Key features:  Interpretable  N3 notation (proposed by Tim-Berners Lee)  Everything is a belief  Containers (“visibility areas” for beliefs)  Statement is a main construct: :John :loves :Mary  Commitment to execute: {:John :loves :Mary} => {:I :send :Mail}  Rules (a kind of permanent commitments) { {:John :loves :Mary} => {:I :send :Mail} } sapl:is sapl:Rule

7. Distributed Resource Histories: To develop means for an agent to plan and execute composite queries over the distributed sources as if the data from these sources was collected to one virtual graph Early Motivation Agent Beliefs Ontonut Bindings Files Data Service DB/KB agent-to-agent servicing adaptation of external sources Ontonuts Role Script

8. Example Use case Experts’ diary Scheduled Performance Monitoring Alarm History DB Paper Machine Agent Ontonut Bindings Files Expert Agent (Data Service) DB/KB Ontonuts Role Script

9. Characteristics: Three types of call:Three types of call: 1.Explicit 2.Goal-based 3.Query-based PlanningPlanning Backward chaining algorithmBackward chaining algorithm ExecutionExecution Handlers introduced to follow the state of the execution and change action planHandlers introduced to follow the state of the execution and change action plan Ontonuts architecture Web Service CSV fileRDBMS Agent Beliefs (S-APL code) SQLReader TextTableReader ExcelReader … MessageSender MessageReceiver Ontonuts Role Script Business Logic Script Reusable Atomic Behaviors (Java code) Excel sheet … Ontonut capability GoalAnalyser ActionPlanner Ontonuts triggering rule Plan Executor Agent Services External resources

10. WP2: Triggering Ontonuts (UbiBlog) ActivityActivityActivityActivityActivityActivityActivityActivityActivity OntonutOntonutOntonutOntonutOntonutOntonutOntonutOntonutOntonut Live Activity S-APL Ontonut definition: :nutid ont:precondition {A A ?x} :nutid ont:effect {B B ?x} :nutid ont:script {implementation} {B B ?x}=>{?x C C} Ontonuts triggering MetaRule Behavior Engine.class {sapl:I sapl:do :nutid} sapl:configuredAs { x:precondition sapl:is {A A A} } sapl:I ont:haveGoal :id :id ont:haveGoalDef {B B B} (1) (2) (3)

11. Triggering Ontonuts ActivityActivityActivityActivityActivityActivityActivityActivityActivity OntonutOntonutOntonutOntonutOntonutOntonutOntonutOntonutOntonut Live Activity S-APL Ontonut definition: :nutid ont:precondition {A A ?x} :nutid ont:effect {B B ?x} :nutid ont:script {implementation} {B B ?x}=>{?x C C} Ontonuts triggering MetaRule Behavior Engine.class {sapl:I sapl:do :nutid} sapl:configuredAs { x:precondition sapl:is {A A A} } sapl:I ont:haveGoal :id :id ont:haveGoalDef {B B B} (1) (2) (3)

12. Ontonut Definition

13. Example call entryDate diary.Entry author entryID title description position analysisDate pmon.analysis nodeID analysisID performanceIndex isautomatic alarmTime ahist.alarm tag alarmID alarmLimitHigh value Experts’ diary Scheduled Performance Monitoring Alarm History DB alarmLimitLow Query (execution) plan

14. Ontonuts: Provision of Dynamic Information An analog of platform-embedded constructs like: –sapl:Now sapl:is ?time (gets current system time) But can be flexibly (re-)defined by user –fingrid:CurrentVoltage sapl:is ?voltage –metso:CurrentOilLevel sapl:is ?oillevel –innow:CurrentUsersOnline sapl:is ?usersonline The approach simplifies the implementation of the agent’s business logic by introducing computable elements. The values of these elements are computed on-demand (only when a query appears in agent’s beliefs)The approach simplifies the implementation of the agent’s business logic by introducing computable elements. The values of these elements are computed on-demand (only when a query appears in agent’s beliefs)

15. Provision of Dynamic Information When extended to more abstract level, computable values can be applied for:When extended to more abstract level, computable values can be applied for:  Counting statistics over dynamically updated data (e.g. average alarm rate per day, or number of students at the lecture now)  Collecting dynamic information about others. E.g. request “what is John’s location at the moment” would look like: :John :currentLocation ?location

16. ConclusionsConclusions We introduce a unified mechanism for componentization within the UBIWARE agent:We introduce a unified mechanism for componentization within the UBIWARE agent:  Components can be: Internal (do some computations with local functions)Internal (do some computations with local functions) External (call external sources)External (call external sources)  Components are: Semantic by nature Support goal-driven planning Can be composite (include other components within)

17. ThanksThanks Thank you for your attention!Thank you for your attention!