Mapping Fundamental Business Process Modelling Language to the Web Services Ontology

1. Mapping Fundamental Business Process Modelling Language to the Web Services Ontology Gayathri Nadarajan and Yun-Heh Chen-Burger Centre for Intelligent Systems and their Applications, School of Informatics, University of Edinburgh, UK. G.Nadarajan@sms.ed.ac.uk, jessicac@inf.ed.ac.uk

2. Introduction – The Gap Enterprise Modelling (EM) methods such as Business Process Modelling (BPM) methods provide matureapproaches to describe organisational needs. The Semantic Web is a major research area where emerging technologies (RDF, RDFS, OWL, OWL-S, BPEL4WS, WSMO) are being developed rapidly. It would be fitting to utilise BPM methods within Semantic Web services (SWS). However, there is a lack of direct mapping between BPM methods and SWS.

3. FBPML (Chen-Burger et al. 2002) Merges the visual capabilities of Integration DEFinition Language (IDEF3) and the formal expressiveness of Process Specification Language (PSL). Provides precise semantics which promotes machine processibility and diagrammatic notations to provide intuitive representation.

4. FBPML Notation activity(ID, Name, Trigger, Precondition, Postcondition, Action, Description). start(ActivityName). junction(JunctionType, PreActivities, PostActivities). link(PrecedingActivities, ProceedingActivities).

5. OWL-S (Martin et al. 2004) A Web Services Ontology which provides a language to describe web services in unambiguous, computer-interpretable forms. Described in OWL and SWRL (FOL). Based on layering approach - above XML, RDF, RDFS and OWL.

6. OWL-S The slightly extended Semantic Web layering cake by Tim Berners-Lee

7. Rationale for selecting OWL-S Sept 2002 v1.1 Nov 2003 v1.2 Pre-Release Sept 2004 v1.2 Three emerging and competing Semantic Web based Languages BPEL4WS OWL-S WSMO

8. Conceptual Mapping Framework

9. Data Model Mapping (Scicluna et al. 2005) 1. Pre-processing (e.g. organise file into Prolog readable syntax) 2. Mapping of Data Model - Mapping of concepts - Mapping of instances - Mapping of relationships - Mapping of properties and restrictions 3. Mapping for rules and axioms

10. Methodology for PM Mapping • Decompose FBPML PM in top-down order. 2. Translate model into a sequence process in OWL-S. 3. All activities between start and finish are composite components of the sequence process. 4. Exhaustively decompose each composite component into a sequence of its basic process components, until the basic component is a simple process construct.

11. Implementation Architectural overview of FBPML to OWL-S Mapping Engine.

12. Simple Model Example Process diagram of a sequence of activities in FBPML. activity(01, ’Sequence’, Trigger, Precondition, Postcondition, Action, Description6). primitive_activity(’P1’, ’A’, Trigger, Precondition, Postcondition, Action, ’Comment for A’). primitive_activity(’P2’, ’B’, Trigger, Precondition, Postcondition, Action, ’Comment for B’). start(’A’). finish(’B’). link(’A’,’B’).

13. Translated OWL-S Syntax <process:CompositeProcess rdf:ID="Sequence Process"> <process:AtomicProcess rdf:ID=“A"> <process:composedOf> <-- Input and Output --> <process:Sequence> <rdfs:comment> <process:components> Comment for A <process:ControlConstructList> </rdfs:comment> <objList:first> </process:AtomicProcess> <process:Perform rdf:ID="A"> <process:process rdf:resource="#A"> <-- Data Flow and Parameter Bindings --> <-- Similar syntax as above --> </process:Perform> <-- for Atomic Process B --> </objList:first> <objList:rest> <process:ControlConstructList> <objList:first> <process:Perform rdf:ID="B"> <process:process rdf:resource="#B"> <-- Data Flow and Parameter Bindings --> </process:Perform> </objList:first> <objList:rest rdf:resource="&objList;#nil"/> </process:ControlConstructList> </objList:rest> </process:ControlConstructList> </process:components> </process:Sequence> </process:composedOf> </process:CompositeProcess>

14. Complex Model example Process diagram for a complex FBPML process model. FBPML formal notation 01 start(’A’). 02 activity(08, ’Xor-Xor’, Trig1, Precond1, Postcond1, Act1, ’Desc2’). 03 junction(’Xor’, ’A’, [’And-And’, ’D’]). 04 junction(’Xor’, [’And-And’, ’D’], ’E’). 05 primitive_activity(001, ’E’, Trig2, Precond2, Postcond2, Act2, ’Desc2’). 06 finish(’E’). 07 activity(09, ’And-And’, Trig3, Precond3, Postcond3, Act3, ’Desc3’). 08 junction(’And’, ’J1’, [’B’, ’C’]). 09 junction(’And’, [’B’, ’C’], ’J2’). 10 primitive_activity(002, ’A’, Trig4, Precond4, Postcond4, Act4, ’Desc4’). 11 primitive_activity(003, ’B’, Trig5, Precond5, Postcond5, Act5, ’Desc5’). 12 primitive_activity(004, ’C’, Trig6, Precond6, Postcond6, Act6, ’Desc6’). 13 primitive_activity(005, ’D’, Trig7, Precond7, Postcond7, Act7, ’Desc7’).

15. Decomposition of FBPML PM

16. <process:CompositeProcess rdf:ID="Complex Model"> <process:composedOf> <process:Sequence> <process:components> <process:ControlConstructList> <objList:first> <process:Perform rdf:ID="A"> <process:process rdf:resource="#A"> <-- Data flow and Parameter bindings --> ... <objList:first> <process:Perform rdf:ID="Xor-Xor"> <process:process rdf:resource="#Xor-Xor"> ... <process:ControlConstructList> <objList:first> <process:Perform rdf:ID="E"> <process:process rdf:resource="#E"> ... <objList:rest rdf:resource="&objList;#nil"/> </process:ControlConstructList> </process:components> </process:Sequence> </process:composedOf> </process:CompositeProcess> <process:CompositeProcess rdf:ID="Xor-Xor"> <process:composedOf> <process:Choice> <process:components> <process:ControlConstructBag> <objList:first> <process:Perform rdf:ID="And-And"> ... <process:Perform rdf:ID="D"> ... <objList:rest rdf:resource="&objList;#nil"/> ... <-- End of Xor-Xor --> <process:CompositeProcess rdf:ID="And-And"> <process:composedOf> <process:Split-Join> <process:components> <process:ControlConstructBag> <objList:first> <process:Perform rdf:ID="B"> ... <process:Perform rdf:ID="C"> ... <-- End of And-And --> Translated OWL-S Syntax

17. Challenges & Contributions Complex problem solving using advanced techniques of mapping. Familiarity of rapidly evolving technologies in a short period: - RDF, RDFS, OWL, OWL-S, SWRL - FBPML DL, FBPML PL Pitfalls of OWL-S as a SW based language. Recommendations for OWL-S, contributes towards its development as an emerging SW standard.

18. Conclusions & Extensions Mapping between FBPML and OWL-S is partial and incomplete. Bridging business process modelling and workflow community to the semantic web community. Given a FBPML model, the corresponding OWL-S description may be generated automatically, based on the mapping method provided. Use ontologies to represent data and process models, along with sound mapping principles to enhance translation. Recommendations for OWL-S 1. Complete formalism for rules and conditions 2. Combine OWL-S with WSMO

19. References Chen-Burger, Y.-H., Tate, A., and Robertson, D. (2002). Enterprise modelling: A declarative approach for FBPML. In In Proceedings European Conference of Artificial Intelligence, Knowledge Management and Organisational Memories Workshop. Martin et al. (2004), OWL-S: Semantic Web Markup for Web Services v1.1 (www.daml.org/services/owl-s/1.1/overview) Antoniou, G. and van Harmelen, F. (2004). A Semantic Web Primer. MIT Press, Cambridge, MA, USA. Scicluna, J., Lara, R., Polleres, A., and Lausen, H. (2005). Formal Mapping and Tool to OWL-S, WSMO Working Draft (www.wsmo.org/TR/d4/d4.2/v0.1) Lara, R., Polleres, A., Lausen, H., Roman, D., de Bruijn, J., and Fensel, D. (2005). A conceptual comparison between WSMO and OWL-S. WSMO Final Draft.

20. End of SlidesThank you