DOLCE and Pi-Calculus Rendezvous Semantics for Business Processes

769 views
696 views

Published on

1st International Workshop on Knowledge Reuse and Reengineering over the Semantic Web (KRRSW 2008) hosted by the 5th ESWC 2008, Costa Adeje, Tenerife, Canary Islands

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
769
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
12
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

DOLCE and Pi-Calculus Rendezvous Semantics for Business Processes

  1. 1. DOLCE and Pi-Calculus Rendezvous Semantics for Business Processes Violeta Damjanović Salzburg Research, Austria 01-05 June, 2008 1 st International Workshop on Knowledge Reuse and Reengineering over the Semantic Web (KRRSW 2008) hosted by the 5 th ESWC 200 8 , Costa Adeje , Tenerife, Canary Islands
  2. 2. Problem Description <ul><li>ImportNET real business domains </li></ul><ul><li>Staticity of ontological models vs. dynamicity of business processes </li></ul><ul><li>Semantic reengineering of the static knowledge domains to support dynamic business processes </li></ul><ul><li>OMG’ ODM standard for model driven ontology development </li></ul><ul><li>OMG’ MOF that defines the metadata architecture for MDA </li></ul>
  3. 3. Approaches to Business Modeling <ul><li>Abstract framework to business process specification </li></ul><ul><ul><li>Functional view – Behavioral view – Structural view </li></ul></ul><ul><li>Functional specification based on IDEF (Integration DEFinition language) </li></ul><ul><ul><li>Well formalized; standardized by NIST; resulting specification is too complex </li></ul></ul><ul><li>Process specification using EPC </li></ul><ul><ul><li>Not formally defined; Syntax and semantics is not precise enough </li></ul></ul><ul><li>OO approach to structural modeling </li></ul><ul><ul><li>Objects + Classes + Relationships (association, aggregation, generalization) </li></ul></ul><ul><li>Using UML for business processes </li></ul><ul><ul><li>Semi-formal method; the semantics is not precisely defined </li></ul></ul><ul><li>Meta-model of business processes </li></ul><ul><ul><li>The idea is to combine formal methods with meta-models </li></ul></ul>
  4. 4. Business Process Transformation Trinity <ul><li>DDPO – OWL </li></ul><ul><li>BPEL, WSDL </li></ul><ul><li>Pi-Calculus </li></ul>Ontological models Business Processes Process theory
  5. 5. DDPO <ul><li>DDPO (DOLCE D&S Plan & Task Ontology) </li></ul><ul><li>DDPO theoretical model: </li></ul><ul><ul><li>to help us getting a good understanding of business models at the different levels of abstraction and </li></ul></ul><ul><ul><li>to provide implicit rules for expressing the facts that explain behavior and structure of the abstract business processes </li></ul></ul>
  6. 6. BPEL, WSDL <ul><li>BPEL enables realization of SOA through composition, coordination and orchestration of WS </li></ul><ul><li>BPEL syntax is defined by a BPEL XMLS which describes the BPEL basic activities, partner activities and structural activities </li></ul>
  7. 7. <ul><li>What is the Pi-Calculus? </li></ul><ul><ul><li>mathematical formalisms for describing and analyzing properties of concurrent computation developed by Robin Milner in the 1990s </li></ul></ul><ul><ul><li>CCS, CSP, ACP… </li></ul></ul><ul><ul><li>widely used in AI (Artificial Intelligence) </li></ul></ul><ul><ul><li>major areas that use the Pi-calculus: </li></ul></ul><ul><ul><ul><li>ERLANG language (Robin Milner – consultant to ATT and British Telephone) </li></ul></ul></ul><ul><ul><ul><li>LOTOS (very complex and delicate temporal reasoning problems in the NASA space missions) </li></ul></ul></ul><ul><ul><ul><li>a foundation for the methodologies for BPM (Business Process Modeling) </li></ul></ul></ul>Pi-C alculus
  8. 8. The core syntax of Pi- C alculus
  9. 9. <ul><li>P rocesses are written using the following syntax (formal model): </li></ul>summation parallel composition process expression process definition transition
  10. 10. Mapping the DDPO Elementary task to the Pi-Calculus Operator <ul><li>1. transforming the DDPO Elementary task </li></ul><ul><ul><li>An elementary task is an atomic task </li></ul></ul><ul><ul><li>ElementaryTask(x) = df  y. Component(x,y)  Task(y) </li></ul></ul>
  11. 11. <ul><li>2. transforming the DDPO Component </li></ul><ul><ul><li>A component relation is a proper part relation qualified by a description in which the proper part are involved </li></ul></ul><ul><ul><li>Component(x,y) = df ProperPart(x,y)   d,z,w. Description(d)  Role(z)  Role(w)  Uses(d,z)  Uses(d,w)  Selects(z,x)  Selects(w,y) </li></ul></ul>
  12. 12. <ul><li>3. transforming the DPPO Task </li></ul><ul><ul><li>A task is a course defined by a plan in which at least one intentional agentive role or intentional figure has a desire attitude towards task </li></ul></ul><ul><ul><li>Task(x) = df Course(x)   y,z. Plan(y)   Defines(y,x)   ((IntentionalAgentiveRole(z)  IntentionalFigure(z))   Uses(y,z)  DesireTowards(z,x) </li></ul></ul>
  13. 13. OWL2BPEL Metamodels and Transformation Models <ul><li>The main objectives of the MOF specification </li></ul><ul><ul><ul><li>To support multiple metamodels and models, and </li></ul></ul></ul><ul><ul><ul><li>To enable their extensibility, integration, and generic model and metamodel management </li></ul></ul></ul><ul><li>Mapping the source model to the target model </li></ul><ul><ul><ul><li>Source model : Ontology based on DDPO model </li></ul></ul></ul><ul><ul><ul><li>Target model : BPEL process that can be deployed to a standalone BPEL workflow engine </li></ul></ul></ul>
  14. 14. <ul><li>Transformation scenario </li></ul>
  15. 15. <ul><li>Transformation plan </li></ul>
  16. 16. Summary and Conclusion <ul><li>ImportNET is trying to bring the Semantic Web technologies to mechatronic engineering </li></ul><ul><li>Mechatronic engineering is multi disciplinary and therefore needs multiple ontologies </li></ul><ul><li>The engineering process needs process modeling </li></ul><ul><li>The engineering artifacts need structural modeling </li></ul><ul><li>Therefore our ontologies need to capture the dynamic and the static aspects of the domains </li></ul>
  17. 17. <ul><li>Thank you ! </li></ul><ul><li>Questions ? </li></ul><ul><li>Contact : </li></ul><ul><ul><li>violeta.damjanovic @ salzburgresearch.at </li></ul></ul><ul><ul><li>http://www.salzburgresearch.at </li></ul></ul>

×