1 Proposal on MFI-5: Process model registration based on ontology (MFI4Process) He Keqing Wang Chong 2006/08/29

2 Content Background ISO Process Specification Language W3C OWL-S MFI4Process & other standards Overall design of MFI4Process Future work

3 Why we need MFI4Process (1/2) Process model Modeling processes  A process is one or more activities that occurs over a period of time in which objects participate.* Dynamic features  Data flow  State changing  …… Ontology: a knowledge representation mechanism for semantics. Semantic annotation Constraints Process model registration based on ontology Effective discovery and sharing Process model management within or across enterprises and domains * from “ISO 18629: A standardized language for specifying and exchanging process information”

4 Why we need MFI4Process (2/2) Web service one of the important resources on the semantic web characterized with dynamic features and processes. Current version of MFI concentrates on the registration of ontology and static models, rather than semantic web service or annotated process models. Register process models based on ontology Govern the construction of customized services Reduce the cost of service development Extending MFI

5 Brief introduction of OWL-S (1/3) -- Layered approach to language development SWRL (Rules) XML (Extensible Markup Language) RDF (Resource Description Framework) RDFS (RDF Schema) OWL ([DLP], Light, DL, Full) OWL-S (Services) OWL-S (W3C) is an extended ontology language a specific OWL profile for Web Service SWRL: Semantic Web Rule Language (W3C)

6 Brief introduction of OWL-S (2/3) (from W3C, OWL Web Ontology Language for Services (OWL-s) Specification) OWL-s is used as a language for describing services, reflecting the fact that it provides a standard vocabulary that can be used together with the other aspects of the OWL description languages to create service description.

7 Brief introduction of OWL-S (3/3) --Top level of the Process Ontology

8 Process Specification Language (1/3) Process Specification Language (PSL, ISO18629) PSL is a modular, extensible ontology capturing concepts required for process specification In PSL, ontology is defined as a specification – in a given domain of a set of concepts, of their relation and of the rules that apply to them. From ISO 18629

9 What PSL will be : a language enabling interoperability of process information among industrial applications What is a process ? A process is one or more activities that occurs over a period of time in which objects participate PSL ObjectTimePointActivity Inf-Inf+ Process Specification Language (2/3) From “ISO 18629: A standardized language for specifying and exchanging process information”

10 Process Specification Language (3/3) From ISO

11 Content Background MFI4Process & other standards MFI4Process & MFI Core MFI4Process & MFI4Onto Overall design of MFI4Process Future work

12 MFI4Process & MFI & PSL

13 MFI4Process & MFI Core from MFI Corefrom MFI4Process

14 MFI4Process & MFI4Onto from MFI4Processfrom MFI4Onto

15 Content Background MFI4Process & other standards Overall design of MFI4Process Basic idea of MFI4Process Models in MFI4Process Example Future work

16 Basic Idea of MFI4Process

17 Registration information (1) Process Input (precondition) Output (postcondition) subProcess Atomic process  Input/Output Composite process  Input/Output  Component (subProcess) Process_Unit ： the smallest, reusable and undecomposable element in process model Control construct  Connecting subProcess  formed as an ordered n-tuple Artifact I/O of Composite Process = I/O of Atomic Processes + I/O of smaller Composite Processes - the ones that Inputi ＝ Outputj

18 Atomic Process & Composite Process Input Output Atomic Process 1 Atomic Process 2 Input 1 Input 2 Input 3 Output 1 Output 3 Output 4 Output 2 Input 4 Input 5 Atomic Process 1 Atomic Process 2 Composite Process Input 1, Input 2, Input 3, Input 5 Output 1, Output 3, Output 4

19 Registration information (2) OccurrenceTree – to record and manage the execution of processes OccurrenceNode  Process (root)  Atomic Process  Composite Process OccurrenceFlow  Input (with corresponding artifact)  Output (with corresponding artifact)

20 OccurrenceTree (1/3) Process Atomic Process 1Atomic Process 2Composite Process 1 Atomic Process 3Atomic Process 4 occurrence flow

21 OccurrenceTree (2/3) - This is the top level process for BravoAir BravoAir_Process is a composite process. It is composed of a sequence whose components are 2 atomic processes, GetDesiredFlightDetails and SelectAvailableFlight, and a composite process, BookFlight. true - s/1.1/Concepts.owl#Airport - s/1.1/Concepts.owl#Airport …… ……

22 OccurrenceTree (3/3) ……

23 Key concepts in MFI4Process (1/3) Control Construct: specify how the process is organized. Anyorder Choice  If-then-else Sequence Merge  Split  Split-Join

24 Key concepts in MFI4Process (2/3) Control Construct Anyorder Choice  If-then-else Sequence Merge  Split  Split-Join Actor: the role that one process plays in process execution  Client: the agent that requests services.  Server: the agent that provides services.

25 Key concepts in MFI4Process (3/3) Control Construct Anyorder Choice  If-then-else Sequence Merge  Split  Split-Join Artifact: the resources that participate in one process predefined concepts in relevant OWL document datatype elements from XML schema Actor the role that one process plays in process execution  Client  Server

26 Models in MFI4Process

27 Overview of MFI4Process dependency MFI4Process

28 Process Core Model from Process Core Modelfrom PSL

29 Process Control Model from Process Core Modelfrom PSLfrom Process Control Model

30 Control Construct Model from Process Core Modelfrom Control Construct Model

31 Example -- BravoAir Reservation Service from W3C,

32 BravoAir Reservation Service

33 For process model Process Ontology: BravoAirReservation_ProcessModel attribute of Process OntologyValue nameBravoAir_ProcessModel URIURI_ BravoAir_ProcessModel administration_Record# modelTypeOWL-S consistsOfAtomicProcess: GetDesiredFlightDetails AtomicProcess: SelectAvailableFlight CompositeProcess: BookFlight

34 For subProcess CompositeProcess: BookFlight attribute of CompositeProcessValue nameBookFlight URIURI_ BookFlight administration_Record# modelTypeOWL-S consistsOfAtomicProcess: Login CompositeProcess: CompleteReservation AtomicProcess: GetDesiredFlightDetails attribute of AtomicProcessValue nameGetDesiredFlightDetails URIURI_ GetDesiredFlightDetails administration_Record# modelTypeOWL-S consistsOfInput: DepartureAirport_In …… Output: FlightsFound ……

35 For Process_Unit Process_Unit01 attribute of Process_UnitControl_Construct nameIf_Then URIURI_ If_then administration_Record# modelTypeOWL-S connectingLogIn ConfirmReservation Process_Unit02 attribute of Process_UnitArtifact nameAirport URIhttp:// > s/1.1/Concepts.owl#Airport

36 For OccurrenceTree (1/3) OccurrenceNode GetDesiredFlightDetails SelectAvailableFlight BookFlight …… OccurrenceFlow Input: DepartureAirport_In Output: FlightsFound …… StateOfNode: Precondition: none Postcondition: hasFlightItinerary

37 For OccurrenceTree (2/3) OccurrenceTree: BravoAir_Process nameBravoAir_Process URIURI_ BravoAir_Process administration_Record# modelTypeOWL-S consistsOfOccurrenceFlow01: BookFlight_PerferredFlightItinerary …… Process_Unit03:Sequence …… OccurrenceNode: GetDesiredFlightDetails OccurrenceNode:SelectAvailableFlight OccurrenceNode:BookFlight ……

38 For OccurrenceTree (3/3) OccurrenceNode attributeOfOccurrenceNodevalue nameBookFlight URIURI_ BookFlight administration_Record# modelTypeOWL-S preconditionnone PostconditionhasFlightItinerary OccurrenceFlow attributeOfOccurrenceFlowvalue nameBravoAir_Process URIURI_ BravoAir_Process administration_Record# modelTypeOWL-S fromProcessBookFlight toParameterPerferredFlightPerferred

39 Content Background MFI4Process & other standards Overall design of MFI4Process Future work

40 Future work MFI4Process Improve these models in detail Applications Logistics domain Other domains

41 Thank you!