• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Super ontology stack_review_m36_051
 

Super ontology stack_review_m36_051

on

  • 409 views

The ontology stack from the EU SUPER project on combining Semantic Web, Services and Business Process Modelling

The ontology stack from the EU SUPER project on combining Semantic Web, Services and Business Process Modelling

Statistics

Views

Total Views
409
Views on SlideShare
409
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Super ontology stack_review_m36_051 Super ontology stack_review_m36_051 Presentation Transcript

    • SUPEROntology Stack Pierre Grenon, OUBerlin, 7 May 2009
    • Review Agenda, Day I09.00 Briefing meeting09.30 Welcome09.40 SUPER Today, SUPER Successes and a SUPER Future10.45 Technical Deep Dives - Part I: Ontology Stack and COBRA - Part II: Reasoner and WSMO Integration - Part III: SBP Execution & Analysis © SUPER 18.06.12 John Kayser (PC/SAP) 2
    • Why Semantics? ReusableAgent Business and Model Activity sharable resource Analyst Resources Data Time IT specialist © SUPER 18.06.12 Pierre Grenon, OU 3
    • SUPER Business Process Management Organisational Context Applications Business Process analyse execute BPEL Reverse Monitoring BPEL4S Business Behavioural Analysis sBPEL WS model Engineering Reasoning BPMO transformBPMN support sBPMN Semantic Web transform Services sEPC (WSMO)EPC © SUPER 18.06.12 Pierre Grenon, OU 4
    • SUPER Ontology Stack Month 12© SUPER 18.06.12 Pierre Grenon, OU 5
    • SUPER Ontology Stack Month 24© SUPER 18.06.12 Pierre Grenon, OU 6
    • SUPER Ontology Stack Month 36© SUPER 18.06.12 Pierre Grenon, OU 7
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 8
    • sBPMN excerpt ca. 100 concepts 50+ axioms© SUPER 18.06.12 Pierre Grenon, OU 9
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 10
    • sEPC excerpt40+ concepts © SUPER 18.06.12 Pierre Grenon, OU 11
    • 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 sourcesThe 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. © SUPER 18.06.12 Pierre Grenon, OU 12
    • BPMO excerpt ca. 70 concepts© SUPER 18.06.12 Pierre Grenon, OU 13
    • 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). © SUPER 18.06.12 Pierre Grenon, OU 14
    • sBPEL excerpt2 concepts80 concepts8 instances7 axioms15 concepts © SUPER 18.06.12 Pierre Grenon, OU 15
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 16
    • BRO 20+ concepts 3 instances ca. 20 axioms(BPMO process) © SUPER 18.06.12 Pierre Grenon, OU 17
    • Why UPO?■ Umbrella ontology for the stack■ Gathers common concepts and relations■ Facilitates inter-ontology reasoning 50+ concepts 20+ instances ca. 20 relations 3 relation instances 20+ axioms © SUPER 18.06.12 Pierre Grenon, OU 18
    • UPO’s usage is embedded in that of BPMO BPMOBPMO UPO © SUPER 18.06.12 Pierre Grenon, OU 19
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 20
    • UPO is extended by Organisation Ontologies BFO BMO BPRO OSO OUO BRONTO ResOnt© SUPER 18.06.12 Pierre Grenon, OU 21
    • Organisation Ontologies excerptBFO OSO & OUO ca. 1K concepts 9 concepts & 19 concepts 8 axioms 11 relations © SUPER 18.06.12 Pierre Grenon, OU 22
    • Organisation Ontologies excerpt (2)BRONTO ResOnt20+ concepts 3 instances 50+ concepts 30+ instances4 relations ca. 20 axioms 10+ relations 3 relation instances 30+ axioms © SUPER 18.06.12 Pierre Grenon, OU 23
    • Organisation Ontologies excerpt (3) BMO40+ conceptsca. 900 instances10+ relations20 axioms © SUPER 18.06.12 Pierre Grenon, OU 24
    • Organisation Ontologies excerpt (4)16 concepts 36 concepts BPRO deo dpo dro ecao25 concepts 10 concepts9 instances © SUPER 18.06.12 Pierre Grenon, OU 25
    • SUPER Domain Ontology Stack Organisation Ontologies© SUPER 18.06.12 Pierre Grenon, OU 26
    • 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 © SUPER 18.06.12 Pierre Grenon, OU 27
    • NGOSS excerpt Telco business IT systemseTOM process functions TAM for process execution ca. 370 concepts 200+ concepts 360 instances 1K+ instances 4 axioms 5 axioms © SUPER 18.06.12 Pierre Grenon, OU 28
    • NGOSS excerpt (2) CommonSID domain NBC vocabulary Telco business process contract ca. 1.3K concepts ca. 1.2K instances 14 concepts 4 relation instances ca. 220 instances 8 axioms 3 relations © SUPER 18.06.12 Pierre Grenon, OU 29
    • Domain Ontology Stack YATOSP (NGOSS Ontologies)© SUPER 18.06.12 Pierre Grenon, OU 30
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 31
    • Use Case Ontologies© SUPER 18.06.12 Pierre Grenon, OU 32
    • Example of Application (from TID Use Case)Ontology Extension Process Instance © SUPER 18.06.12 Pierre Grenon, OU 33
    • To be continued© SUPER 18.06.12 Pierre Grenon, OU 34
    • Appendix© SUPER 18.06.12 Pierre Grenon, OU 35
    • SUPER Process Ontology Stack© SUPER 18.06.12 Pierre Grenon, OU 36
    • SUPER Ontology Stack Month 36© SUPER 18.06.12 Pierre Grenon, OU 37
    • UPO excerpt 50+ concepts 20+ instances ca. 20 relations 3 relation instances 20+ axioms© SUPER 18.06.12 Pierre Grenon, OU 38
    • BRONTO excerpt 20+ concepts 3 instances 4 relations ca. 20 axioms© SUPER 18.06.12 Pierre Grenon, OU 39
    • OSO & OUO excerpt9 concepts11 relations19 concepts © SUPER 18.06.12 Pierre Grenon, OU 40
    • ResO excerpt 50+ concepts 30+ instances 10+ relations 3 relation instances 30+ axioms© SUPER 18.06.12 Pierre Grenon, OU 41
    • ResO excerpt 50+ concepts 30+ instances 10+ relations 3 relation instances 30+ axioms© SUPER 18.06.12 Pierre Grenon, OU 42
    • NGOSS Ontologies© SUPER 18.06.12 Pierre Grenon, OU 43
    • eTOM ca. 370 concepts 360 instances 4 axiomsTelco businessprocess functions © SUPER 18.06.12 Pierre Grenon, OU 44
    • SIDCommondomainvocabularyca. 1.3K conceptsca. 1.2K instances4 relation instances8 axioms © SUPER 18.06.12 Pierre Grenon, OU 45
    • NBC 14 concepts ca. 220 instances 3 relationsTelco businessprocess contract © SUPER 18.06.12 Pierre Grenon, OU 46
    • TAM IT systems for process execution200+ concepts1K+ instances5 axioms © SUPER 18.06.12 Pierre Grenon, OU 47
    • Process ontologies in relation to architecture© SUPER 18.06.12 Pierre Grenon, OU 48
    • sBPMN usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Execution Tool Management Analysis Tool Environment Tool EngineSemantic Service Bus Deployment Event Sink XPDL2sBPMN Protocol Binder and SBP SBP Process Composition Mediation Business Semantic Web Services Execution sBPMN2BPMO Process Library History SBP Discovery Data Mediation Repository translators SUPER Repositories SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 49
    • sEPC usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Execution Tool Management Analysis Tool Environment Tool EngineSemantic Service Bus Deployment Event Sink Protocol Binder SBP SBP Process Composition Mediation Semantic Web Business Execution Services SBP Discovery Data Mediation Process Library Repository History sEPC2BPMO SUPER Repositories translator SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 50
    • BPMO usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Management Analysis Tool Execution Engine Environment Tool Tool BPMO ModellerSemantic Service Bus Deployment BP Mediator design-time Event Sink Translators: Protocol Binder BPMO2SBPEL sEPC2BPMO SBP SBP Process Composition Mediation sBPMN2BPMO Semantic Web Business Execution Services Process Library History SBP Discovery Data Mediation Repository BPMO API SUPER Repositories SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 51
    • sBPEL usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Management Analysis Tool Execution Engine Environment Tool Tool BPMO2sBPELSemantic Service Bus Deployment and Event Sink sBPEL2BPEL4SWS Protocol Binder translators SBP SBP Process Composition Mediation Semantic Web Business Execution Services Process Library History SBP Discovery Data Mediation Repository SUPER Repositories SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 52
    • BRO usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Management Analysis Tool Execution Engine Environment Tool Tool BP Mediator ReasoningSemantic Service Bus Deployment Support validation of Event Sink composition Protocol Binder BPMO2BRO translator SBP SBP Process Composition Mediation Semantic Web Business Execution Services Process Library History SBP Discovery Data Mediation Repository SUPER Repositories SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 53
    • RBEO usage in SUPER tools and components SUPER Execution SUPER Tooling Semantic Semantic Monitoring & BPEL Modelling Execution Management Analysis Tool Execution Engine Environment Tool Tool Semantic Business Process DiscoverySemantic Service Bus Deployment Engine Event Sink (sRBE tool) Protocol Binder SBP SBP Process Composition Mediation Semantic Web Business Execution Services Process Library History SBP Discovery Data Mediation Repository SUPER Repositories SBP Reasoner Transformation SUPER Plafform Services © SUPER 18.06.12 Pierre Grenon, OU 54
    • Detailed whys© SUPER 18.06.12 Pierre Grenon, OU 55
    • 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.SID Shared Information Domain Common domain vocabularyNBC NGOSS Business Contract Telco business process contracteTOM Enhanced Telco Operation Map Telco business process functionsTAM Telco Applications Map IT systems for process execution■ These were ontologised in SUPER. © SUPER 18.06.12 Pierre Grenon, OU 56
    • 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. © SUPER 18.06.12 Pierre Grenon, OU 57
    • 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 © SUPER 18.06.12 Pierre Grenon, OU 58
    • 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 18.06.12 Pierre Grenon, OU 59