THE 4 X 4 SEMANTIC MODEL : Semantics to Empower Services Science: Using Semantics at Middleware, Web Services and Business Levels
•Download as PPT, PDF•
0 likes•271 views
Keynote at the 9th International Conference on Enterprise Information Systems, Funchal, Portugal, June 12–16, 2007.
![Outline ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
Viewers also liked
Viewers also liked (19)
Similar to THE 4 X 4 SEMANTIC MODEL : Semantics to Empower Services Science: Using Semantics at Middleware, Web Services and Business Levels
Similar to THE 4 X 4 SEMANTIC MODEL : Semantics to Empower Services Science: Using Semantics at Middleware, Web Services and Business Levels (20)
Recently uploaded
Recently uploaded (20)
THE 4 X 4 SEMANTIC MODEL : Semantics to Empower Services Science: Using Semantics at Middleware, Web Services and Business Levels
- 1. THE 4 X 4 SEMANTIC MODEL “ Semantics to Empower Services Science: Using Semantics at Middleware, Web Services and Business Levels ” Keynote at 9th International Conference on Enterprise Information Systems , Funchal, Madeira – Portugal, 12-16, June 2007. Amit Sheth* Kno.e.sis center, Wright State University, Dayton, OH Thanks: paper with Karthik Gomadam
- 17. SAWSDL at a glance Ack: Jacek Kopecky
- 21. Modeling : Using Radiant
- 22. Execution: WS Discovery using Lumina (MWSDI)
- 23. Execution: WS Discovery using Lumina (MWSDI)
- 29. Semantics for Technical Services Development / Description / Annotation WSDL, WSDL-S, SAWSDL, WSMO, OWL-S METEOR-S (MWSAF) Execution, Adaptation and Mediation BPWS4J, activeBPEL, WSMX METEOR-S Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI) Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF)
- 30. Semantics for Technical Services Data / Information Semantics Development / Description / Annotation Execution, Adaptation and Mediation BPWS4J, activeBPEL. WSMX METEOR-S WSDL, SAWSDL, (OWL-S, WSMO, WSDL-S) METEOR-S (MWSAF) Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF) Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI)
- 31. Semantics for Technical Services Functional Semantics Development / Description / Annotation Execution, Adaptation and Mediation BPWS4J, activeBPEL, WSMX METEOR-S WSDL, WSDL-S, SAWSDL, WSMO, OWL-S METEOR-S (MWSAF) Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF) Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI)
- 32. Semantics for Technical Services Non Functional Semantics Development / Description / Annotation Execution, Adaptation and Mediation BPWS4J, activeBPEL, WSMX METEOR-S WSDL, WSDL-S, SAWSDL, WSMO, OWL-S METEOR-S (MWSAF) Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF) Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI)
- 33. Semantics for Technical Services Execution Semantics Development / Description / Annotation Execution, Adaptation and Mediation BPWS4J, activeBPEL, WSMX METEOR-S WSDL, WSDL-S, SAWSDL, WSMO, OWL-S METEOR-S (MWSAF) Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF) Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI)
- 34. Semantics for Technical Services Semantics Required for Web Processes Development / Description / Annotation Execution, Adaptation and Mediation BPWS4J, activeBPEL, WSMX METEOR-S WSDL, WSDL-S, SAWSDL, WSMO, OWL-S METEOR-S (MWSAF) Execution Semantics QoS Semantics Functional Semantics Data / Information Semantics Composition, Configuration and Negotiation BPEL, WS-Agreement, WS-Policy METEOR-S (MWSCF) Publication / Discovery (Semantic) UDDI METEOR-S (MWSDI)
- 39. Example of a semantic template in the supply chain domain
- 40. What semantics at what level?
- 44. 4 X4 Model in Action
Editor's Notes
- In Role of Semantics for Workflow Enactment Tier: change consistence to consistency. In Technologies for Business Process Tier, add BPMN
- What Who point: In the insurance example, the fact that we need a DMV partner, a credit bureau and cc processing are identified. Who are the actual partners that we will bind to is not. This is deferred to execution time. This is important to understand the dynamism of the 4 X 4.
- What Who point: In the insurance example, the fact that we need a DMV partner, a credit bureau and cc processing are identified. Who are the actual partners that we will bind to is not. This is deferred to execution time. This is important to understand the dynamism of the 4 X 4.
- What Who point: In the insurance example, the fact that we need a DMV partner, a credit bureau and cc processing are identified. Who are the actual partners that we will bind to is not. This is deferred to execution time. This is important to understand the dynamism of the 4 X 4.
- In a state beyond a proposal
- Intalio n3 : Completer BPMS..design, deploy, execute, analyze and optimize processes…brochure says it supports BPML specification
- This picture illustrates the coming together of the 4 tiers of business process and how the 4 types of semantics facilitates this. At the heart of this modeling, is the grounding to ontologies. Further this slide also illustrates the interaction between the different tiers. The specifications in the process tier are enacted as workflows in the enactment tier. These workflows are deployed in a middleware that provides deployment and messaging services. The partner services are also deployed in middleware systems. In addition to these, the middleware services tier providers services such as discovery and mediation and message routing. Process Modeling Tier: Conventional workflow specifications or Mashup/Smashup specifications are captured at this tier. Conventional workflow specifications are captured using semantic templates for SOAP services while Smashup specifications are captured using micro-format enhanced SAREST. Workflow Enactment Tier: Based on the process level specifications, partner level specifications are created and workflows are enacted with these partner level specifications. The various tasks in the workflow are described by the operations in the corresponding semantic template. For example, in a supply chain workflow for procuring various components, the partner level specifications for each component is captured. A workflow is then created where a task corresponding to a functional requirement in the partner level specifications. In the context of light weight services, Smashups are created to enact out service compositions. Service compositions are captured as client side objects, which are annoated with micro formats. The service at the server side based on the semantics of the client side objects that are sent to it, invokes the relevant services in the order while making sure of the interaction and role. Service discovery and process configuration is done using the partner level specifications. Adaptation strategies such as events that are relevant, event subscription and notification management are done based on the functional and non-functional processs and partner level specifications. Partner service tier: IN the classical service context, partner services capture their capabilities and requirements in SAWSDL. In case of light weight services, annotated pages with RDFA and annotated XML inputs/ output allows for publication and discovery of these services. Middleware Services Tier: The capabilities of the middleware to support semantic web services, deployment, message processing, event handling and data mediation can be captured. As we can see in the example, the middleware services tier provides container services for both the enacted workflow as well as for partner services.
- fo