Super ontology stack_review_m36_051

Ontology Stack

Pierre Grenon, OU

Berlin, 7 May 2009

Review Agenda, Day I

09.00 Briefing meeting

09.30 Welcome

09.40 SUPER Today, SUPER Successes and a SUPER Future

10.45 Technical Deep Dives

- Part I: Ontology Stack and COBRA

- Part II: Reasoner and WSMO Integration

- Part III: SBP Execution & Analysis

12.30 Lunch

Why Semantics?

Business ActivityModelAgent

Resources

Analyst

IT specialist

Reusable and sharable resource

SUPER Business Process Management

Business Process

Behavioural Reasoning

Semantic Web Services(WSMO)

analyse

transform

transformsupport

execute

BPEL4SWS

Reverse BusinessEngineering

MonitoringAnalysis

Organisational Context Applications

SUPER Ontology StackMonth 12

SUPER Ontology Stack Month 36

Why sBPMN?

■ BPMN is a widely used notation for BPM. ■ SUPER needs an entry point for BPMN

users.■ BPMN is a graphical notation that needs

explicit semantics (provided by sBPMN).

Lessons learnt:■ SUPER needs to create entry points. ■ SUPER needs to be independent of

specific notations.■ SUPER needs to remain up-to-date as

standards change.

sBPMN excerpt

ca. 100 concepts50+ axioms

Why sEPC?

■ SUPER’s proof of capability to handle multiple entry points corresponding to distinct perspectives.

■ EPC is different from BPMN.

■ The sematics for EPC is distinct from that for BPMN.

sEPC excerpt

40+ concepts

Why BPMO?

Intermediate representation for:■ Abstracting over different notations,

perspectives, levels of understanding■ Bridging different notations■ Bridging the world of modelling,

execution and analysis■ Providing a central platform for

connecting additional knowledge sources

The above facilitates inter-representational reasoning and querying.

► Eg, one can pose a query on a BPEL execution trace and the answer uses knowledge from the original BPMN diagram and the organisational context.

BPMO excerpt

ca. 70 concepts

Why sBPEL?

■ sBPEL is SUPER’s ontology at the receiving end of ontology-based model transformation (mediated by BPMO) hooking into execution (BPEL through its BPEL4SWS extension).

■ sBPEL and BPEL4SWS have hooks allowing for the execution of SWS and of their compositions.

■ We can reason about sBPEL, that which

is about to be executed and that which comes after execution (thus supporting analysis).

sBPEL excerpt

2 concepts

80 concepts8 instances7 axioms

15 concepts

Why BRO?

■ Support high level reasoning about behaviour

► E.g. compliance checking, composition validation

■ This reasoning can include any knowledge carried within the ontology stack.

(BPMO process)

20+ concepts3 instancesca. 20 axioms

Why UPO?

■ Umbrella ontology for the stack ■ Gathers common concepts and

relations■ Facilitates inter-ontology reasoning

50+ concepts20+ instancesca. 20 relations3 relation instances20+ axioms

UPO’s usage is embedded in that of BPMO

BPMO UPOBPMO

Why a domain ontology stack?

■ Resources for enriching the representation of BP models based on BPMO.

■ Domain ontologies provide values for attributes of BPMO process instances.

■ Vertical domain with three levels of generality:

► Generic business domain (organisation) ontologies ► Extended by telecommunication ontologies► Extended by use case specific ontologies.

UPO is extended by Organisation Ontologies

OSOOUO

ResOnt

BRONTO

BFO OSO & OUO

ca. 1K concepts8 axioms

Organisation Ontologies excerpt

9 concepts11 relations

& 19 concepts

Organisation Ontologies excerpt (2)

BRONTO ResOnt

50+ concepts 30+ instances10+ relations 3 relation instances30+ axioms

20+ concepts 3 instances4 relations ca. 20 axioms

40+ conceptsca. 900 instances10+ relations20 axioms

16 concepts 36 concepts

10 concepts25 concepts9 instances

SUPER Domain Ontology StackOrganisation Ontologies

Why NGOSS Ontologies (YATOSP)?

■ Support communication and inter-operability in the telecommunication domain

■ Provide an easy entry point for using SUPER in the telecommunication domain

■ NGOSS ontologies correspond to a set of industry standards

NGOSS excerpt

ca. 370 concepts 360 instances4 axioms

Telco business process functionseTOM TAM

IT systems for process execution

200+ concepts 1K+ instances5 axioms

NGOSS excerpt (2)

ca. 1.3K concepts ca. 1.2K instances4 relation instances8 axioms

Common domain vocabulary

Telco business process contract

14 concepts ca. 220 instances3 relations

Domain Ontology Stack YATOSP (NGOSS Ontologies)

Why use case ontologies and knowledge bases?

■ Each enterprise has its specifics:► Organisational structure► Variants and additions to BP models► Data structure.

■ Each enterprise has its own data.

■ Common umbrella framework and common representation formalism.

Use Case Ontologies

Example of Application (from TID Use Case)

Ontology Extension Process Instance

To be continued

Appendix

SUPER Process

Ontology Stack

UPO excerpt

50+ concepts20+ instancesca. 20 relations3 relation instances20+ axioms

BRONTO excerpt

20+ concepts3 instances4 relationsca. 20 axioms

OSO & OUO excerpt

9 concepts11 relations

19 concepts

ResO excerpt

NGOSS Ontologies

ca. 370 concepts 360 instances4 axioms

Telco business process functions

ca. 1.3K concepts ca. 1.2K instances4 relation instances8 axioms

Common domain vocabulary

14 concepts ca. 220 instances3 relations

Telco business process contract

200+ concepts 1K+ instances5 axioms

IT systems for process execution

Process ontologies

in relation to

architecture

sBPMN usage in SUPER tools and components

ModellingTool

Monitoring & Management

Semantic BPEL

Execution Engine

Semantic Execution

EnvironmentAnalysis Tool

Transformation

SBP Discovery

SBP Process Mediation

SBP Composition

Data Mediation

Semantic Web Services

Repository

ExecutionHistory

Business Process Library

SUPER Repositories

SUPER Plafform Services

SUPER ToolingSUPER Execution

Semantic Service Bus

Event Sink

Deployment

SBP Reasoner

Protocol BinderXPDL2sBPMN

sBPMN2BPMO

translators

sEPC usage in SUPER tools and components

ModellingTool

Semantic BPEL

Execution Engine

Semantic Execution

Transformation

SBP Discovery

SBP Composition

Data Mediation

Repository

ExecutionHistory

SUPER Repositories

Event Sink

Deployment

SBP Reasoner

Protocol Binder

sEPC2BPMO

translator

BPMO usage in SUPER tools and components

ModellingTool

Semantic BPEL

Execution Engine

Semantic Execution

Transformation

SBP Discovery

SBP Composition

Data Mediation

Repository

ExecutionHistory

SUPER Repositories

Event Sink

Deployment

SBP Reasoner

Protocol Binder

BPMO Modeller

BP Mediator design-time

Translators: BPMO2SBPEL sEPC2BPMO sBPMN2BPMO

BPMO API

sBPEL usage in SUPER tools and components

ModellingTool

Semantic BPEL

Execution Engine

Semantic Execution

Transformation

SBP Discovery

SBP Composition

Data Mediation

Repository

ExecutionHistory

SUPER Repositories

Event Sink

Deployment

SBP Reasoner

Protocol Binder

BPMO2sBPEL

sBPEL2BPEL4SWS

translators

BRO usage in SUPER tools and components

ModellingTool

Semantic BPEL

Execution Engine

Semantic Execution

Transformation

SBP Discovery

SBP Composition

Data Mediation

Repository

ExecutionHistory

SUPER Repositories

Event Sink

Deployment

SBP Reasoner

Protocol Binder

BP Mediator Reasoning

Support validation of composition

BPMO2BRO translator

RBEO usage in SUPER tools and components

ModellingTool

Semantic BPEL

Execution Engine

Semantic Execution

Transformation

SBP Discovery

SBP Composition

Data Mediation

Repository

ExecutionHistory

SUPER Repositories

Event Sink

Deployment

SBP Reasoner

Protocol Binder

Semantic Business Process Discovery Engine (sRBE tool)

Detailed whys

Why NGOSS Ontologies (YATOSP)?

■ The Telemanagement Forum (TMF) is an association of telecommunication enterprises and IT providers.

■ The TMF’s development of the New Generation Operation Support Systems (NGOSS) results, among other things, in a set of standards.

■ These were ontologised in SUPER.

SID Shared Information Domain Common domain vocabulary

NBC NGOSS Business Contract Telco business process contract

eTOM Enhanced Telco Operation Map Telco business process functions

TAM Telco Applications Map IT systems for process execution

Why an ontology stack?

■ A stack is formed of elements which are putatively independent to some degree.

■ The degree of independence depends on application context sampling the stack (facilitating partial reuse).

■ Also in some cases, size matters and the break down of ontological resources can be motivated by efficiency and technical parameters.

■ Finally, SUPER is a collaborative project with distributed competences and responsibilities.

Why ontologies?

■ Representing reality■ Bridging between different representations, possibly

of the same things using different representation formalisms

■ Providing explicit semantics to existing representation formalisms

■ Abstracting from existing representations■ Supporting updatable and potentially growing

interoperability with centralised mapping■ Supporting scalability through mechanisation and

automatised translation ■ Supporting sharing and reuse over the Semantic Web

Why Ontology-based Representation for BPM?

■ Heterogeneous sources and viewpoints abstracted into a single ontology-based representation of processes, their structures, relations, and properties for which BPMO provides the backbone.► Translation from and/or to BPMN, sEPC, BPEL

■ Heterogeneous formalisms streamlined into a single knowledge representation formalism (WSML):► bringing BP Models to machines► facilitating integration and interoperability► allowing automatisation, execution, reuse► in an accessible and scalable manner.

Super ontology stack_review_m36_051

Education

Transcript of Super ontology stack_review_m36_051

Ontology and RadLex Robert Arp, Ph.D. Ontology Research Group (ORG) National Center for Biomedical Ontology (NCBO) .

Lecture 10: Ontology Alignmentusers.jyu.fi/~olkhriye/ties4520/lectures/Lecture10.pdf · UNIVERSITY OF JYVÄSKYLÄ n Ontology alignment or ontology matching Ontology Alignment It is

The Gene Ontology & Gene Ontology Annotation resources

Ontology and Ontology Libraries: a critical study

Ontology Tool Benchmarks and Their Constructionof ontology benchmarks for a speci c ontology tool category. The ontology tool categoriza-tion serves rstly for the grouping of ontology

24 January 2013 Track B: Ontology Evaluation Across the Ontology Lifecycle 1 Ontology Summit 2013: Ontology Evaluation Across the Ontology Lifecyle Track.

Ontology-enhanced retrieval (and Ontology-enhanced applications)

Ontology and Information Systems - Buffalo Ontology …ontology.buffalo.edu/ontology(PIC).pdf1 Ontology and Information Systems Barry Smith1 Philosophical Ontology Ontology as a branch

Operative Constructivism Introduction The end of ontology ... · Ontology, Reality and Construction in Niklas Luhmann’s Theory Introduction The end of ontology? Ontology, Reality

Ontology and Information Systemsontology.buffalo.edu/ontology_long.pdf · 1 Ontology and Information Systems Barry Smith1 Philosophical Ontology Ontology as a branch of philosophy

Ontology - Ceweb.brceweb.br/webbr2016/apresentacoes/Riichiro-Mizoguchi.pdf · – DOLCE, BFO, UFO, YAMATO, etc. Domain ontology – Disease ontology, Gene ontology, etc. ...

Semantic Web & Ontology. Introduction Semantic Web and Ontology.

OCM Ontology and Ontology Services

Knowledge representation and the Internet – Ontology Ddesign What is an ontology? Why develop an ontology? Step-By-Step: Developing an ontology Going deeper:

Ontology Engineering: Ontology Use

Integrated Demand REsponse - DEXMA Deliverables... · 4.1 Ontology Development 18 4.1.1 Ontology Reuse 19 4.1.2 Ontology Alignment 20 4.1.3 Tools for ontology modelling 20 4.2 Ontology

Ontology Summit 2013: Ontology Evaluation Across the Ontology Lifecyle

Constructing Railway Ontology using Web Ontology Language and

Ontology Alignment. Ontology alignment Ontology alignment Ontology alignment strategies Evaluation of ontology alignment strategies Ontology alignment.

Event Ontology: A Pathway-Centric Ontology for Biological ...psb.stanford.edu/psb-online/proceedings/psb06/kushida.pdf · Event Ontology: A Pathway-Centric Ontology for Biological