SlideShare a Scribd company logo

Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, Composition and Orchestration

Download as PPT, PDF
Amit Sheth, profile picture
Amit Sheth

The document discusses the significance of the Semantic Web process lifecycle and its role in enhancing e-services through improved annotation, discovery, composition, and execution processes. It emphasizes that the integration of semantics allows for more efficient interactions among distributed organizations, facilitating global commerce and dynamic service provision. Benefits include increased productivity, reduced costs, and better scalability of services, transforming traditional business processes into comprehensive, automated interactions.

Education
1 of 63
Downloaded 22 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
Semantic Web Process Lifecycle: R ole of Semantics in Annotation, Discovery,Composition and Execution Invited talk: WWW 2003 Workshop on E-Services and the Semantic Web Budapest, Hungary, Tuesday, May 20, 2003 Amit Sheth LSDIS Lab, University of Georgia and Semagix , Inc. With Acknowledgements to METEOR-S Project team: Kaarthik Sivashanmugam, Kunal Verma,Abhijit Patil
Processes driving the Networked Economy Companies distributed over space, time, and capability will have to come together to deliver products and solutions in global marketplace. Processes are already becoming chief differentiating and the competitive force in the networked economy. Processes are becoming an organic part of doing business. * From Sheth, Aalst et al, “Processes driving the Networked Economy” 1999
Globalization of Processes Web Processes Workflows Distributed Workflows Global Enterprise Inter-Enterprise B2B E-Services Processes driving the Networked Economy
Architectures for Web Processes* Stages of architectural evolution Process Portal one stop for e-services, p2p interactions between buyer and sellers E-Gov, industry automation, Life Science Process Vortex Interactions between buyer and seller through a third party marketmaker, predefined processes, shared ontology Dynamically Trading Processes * From Sheth, Aalst et al, “Processes driving the Networked Economy” 1999
Process Portal Processes driving the Networked Economy
Process Portal One-stop shopping for products or information A portal is responsible for carrying out or coordinating a majority of activities using the data it has and the transactions it supports. Predefined, (relatively) static business processes also supporting P2P interactions A key characteristic of a portal is to own or manage much of the data and information it needs to meet its customers process needs.
Process Vortex Processes driving the Networked Economy
Process Vortex Interactions among buyers and sellers occur through governed marketplaces managed by third party market makers Market maker supports common ontology that buyers use to access products/services from multiple suppliers Focus on very specific product lines, predefined business processes, unified interface to catalogues and supplier aggregation
Dynamically Trading Processes
Dynamically Trading Processes Many complex interactions among enterprises Business processes are highly dynamic Based on the needs and preferences of a customer, a virtual process is constructed on the fly to meet this very particular demand of the customer. Participants are a group of semi-autonomous or autonomous organizations that need to cooperate: selective participation hiding details and providing partial visibility
BIG Challenges Scalability Heterogeneity Dynamic nature of business interactions Long duration Hypothesis: Semantics is the most important enabler (hence Semantic Web Process)
Scalability B8 A1 A4 A1 A2 A4 B3 A1 A4 A6 A2 A5 Before (Enterprise,Inter-enterprise workflows) A C D N1 N2 F E Discovery/Matchmaking should be accurate and scalable to the number of services available in Web A C D N1 N2 F E A4 A1 A1 A4 A1 A4 A1 A2 A1 A1 A1 A1 B3 A1 B3 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A2 A1 B3 A1 A4 A1 A2 B3 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A1 A4 A1 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A4 A4 A1 A4 A1 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 A4 A1 A4 A1 A1 A4 A1 A2 A1 A1 A4 A1 A2 A1 A1 A4 A1 B3 A1 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A1 A2 A1 A4 A2 A4 A2 A2 A1 A1 B3 A1 A4 A1 A2 A1 Now Semantics of the services Semantics of the activity (Data, Functional, Execution, QoS)
Dynamic Nature of Processes Different partners Different Interface for their services Need for dynamic partnerships
Challenges in Web Services* modeling, organizing collections discovery and comparison distribution and replication access and composition fulfillment (contracts, coordination versus transactions, compliance) quality aspects more general than correctness or precision, compliance) security and trust * From Amicalola report, Sigmod Record , Dec 2002
Contribution of Semantic Web* Semantic Web promises significant benefits to businesses Improves productivity and efficiency Reduce cost, time, effort etc. Improves scalablility to the size of the web Exploits unique opportunities of Web Converting processes from incomplete/discrete to comprehensive/continuous Diversify customer base and going global Volatility and dynamic nature * From Amicalola report, Sigmod Record , Dec 2002
Semantic Web Processes: What does it provide ? Information resource, person, organization, and many of the activities relating to them will be located on or be driven by the Web. Qualitatively improved interactions Quantitatively changes the scale and scope by automating the interactions All this is possible only by adding “meaning” to the resources and using them for automation * From Amicalola report, Sigmod Record , Dec 2002
SWS and SWP Semantic Web Services* Semantic Web Processes Intra/Inter EnterpriseWorkflows Semantic Web Processes ebXML B2B Processes * From Amicalola report, Sigmod Record , Dec 2002
(Backdrop) Industries, Technologies, Research and Vision meet at SWP Semantic Web Process ebXML Workflow, EAI Semantic Web Web Services
Semantics for Web Processes Data/Information Semantics Functional/Operational Semantics Execution Semantics QoS Semantics
Data or Information Semantics What ? Formal definition of data in input and output messages of a web service Why ? Discovery and Interoperability of Web Services How ? Annotating input/output data of web services using ontologies (METEOR-S’ WSDL-S), or formally describe I/O (DAML-S)
Function or Operational Semantics What ? Formally representing capabilities of each web service Why ? Discovery of Web Services How ? Annotate operations of Web Services as well as provide preconditions and effects; Annotating Trading Partner Agreement (TPA)/Service Level Agreement (SLA)
Execution Semantics What ? Formally representing the execution (status) or flow of a services in a process or operations in a service Why ? Analysis (verification) and validation (simulation) of the process models and exception handling How ? Using State charts, Petri nets or activity diagrams
QoS Semantics What ? Formally describes operational metrics of a web service/process Why ? To select the most suitable service to carry out an activity in a process How ? Using QoS model for web services Time, Cost, Reliability, (Fidelity): e.g., Cardoso and Sheth, 2002
B2B process between Distributor and Toy Manufacturer ElectonicToysDistributor 1 2 ToysManufacturer 3 4 Request for details given Order on number of toys Send the price and delivery details Place order Order confirmation PartsSupplierPartner DeliveryPartner Bank Get Details (1, 2) Place Order (3, 4) UDDI Discovery: Using data, functional and QoS semantics Execution and Exception handling using QoS and Execution semantics
Discovery in Semantic Web Process Management An Electronic Toy distributor wants to place an order to a Toy Manufacturer Discovery Template Functionality : What capabilities the distributor expects from the service (operational semantics) Inputs : What the distributor can give to the to the Manufacturer’s service (data semantics) Outputs : What the distributor expects as outputs from the service (data semantics) QoS : Quality of Service the distributor expects from the service (QoS semantics)
Execution / Invocation. After discovery, the service can be Invoked OR Simulated or verified if the details of the Manufacturer’s process is public (execution semantics) Verification can also be done by the Manufacturer before deploying the process
Features of Semantic Web Processes Different Functional and Data Semantics for competing Web services ManufacturerA’s service takes order for all kind of toys ManufacturerB’s service takes order specifically for electronic toys ManufacturerC takes Credit card as input and produces confirmation ManufacturerD takes PartnershipId as input and produces the confirmation with number of toys ordered and money that will be deducted from the account relevant to the PartnershipId given ManufacturerE deals only with distributors whose credit rating is more that ‘X’
Features of Semantic Web Processes Selecting correct partners (Using QoS) ManufacturerA delivers toys sooner but costs more ManufacturerB charges more but takes care of delivery ManufacturerC provides a service with best time and cost parameters but the failure rate is high Which one to select for business ? Should QoS (time, cost, reliability) be part of a general model, or application specific (or a combination)?
Features of Semantic Web Processes Verification of the process (Using execution semantics) ManufacturerA models his process and verifies its execution before deploying it DistributorA finds the ManufacturerB’s service, simulates its execution and if satisfied with the result invokes it
Features of Semantic Web Processes Process Management (Using execution semantics) Distributor wants to cancel the order when the product is about to be shipped to him. He can query the process management system if he is allowed to do that. If yes, at what penalty or cost ? May depends on the state of process (execution).
Features of Semantic Web Processes Exception handling during Process Management (Using execution semantics) The delivery partner of the manufacturer went on strike and he needs to find an alternative delivery service. How can he find a semantically equivalent alternative without compromising on the QoS of the entire process If he is finding an alternative that should be compatible with the preconditions and effects of the related services in the process Exception handling should be intelligent either to retry invocation of a service or attempt compensation action. It is difficult to hardcode/program exceptions for all possible failures
Advanced Features Future capabilities Semantic Web can lend to Web Processes Decision Making Manufacturer uses trust parameters during dynamic partner selection Inferencing Toy Distributor comes to know that all Manufacturers are going on strike. Toy manufacturer is a type of manufacturer. Hence he inferences that he will also go on strike. So places order for toys to meet demand for toys before the strike starts.
Semantic Web Process LifeCycle Data / Information Semantics Description / Annotation WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) Discovery UDDI WSIL, DAML-S METEOR-S (P2P model of registries) Composition / Choreography BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET) Execution / Orchestration BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow
Semantic Web Process LifeCycle Data / Information Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
Semantic Web Process LifeCycle Functional / Operational Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
Semantic Web Process LifeCycle QoS Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
Semantic Web Process LifeCycle Execution Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
Semantic Web Process LifeCycle Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Semantics Required for Web Processes Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET) Execution Semantics QoS Semantics Functional / Operational Semantics Data / Information Semantics
METEOR-S Applying Semantics in Annotation, Quality of Service, Discovery, Composition, Execution Focuses on two issues: semantic Web services and process composition. Process Composition: Functional perspective Web Service Discovery, handling semantic heterogeneity Operational perspective QoS specification for Web Services and Processes. 
METEOR-S components for SWP Discovery Infrastructure (MWSDI) Semantic Annotation of Web Services Semantic Peer-to-Peer network of Web Services Registries Composer SCET: Service Composition and Execution Tool Semantics Process Template Builder (under development) QoS Management Specify, compute, monitor and control QoS (SWR algorithm) Orchestrator Analysis and Simulation Execution Monitoring
Semantics in METEOR-S METEOR-S examples of using/supporting semantics: Annotation Discovery Composition (in development) QoS
MWSDI : Annotation
Present Discovery Mechanism UDDI :Keyword, taxonomy based search Example: “Quote” Microsoft UBR returned 12 services Human reading of description (Natural Language) helped me understand 8 of these: 6 Entries are to get Famous Quotes 1 Entry for personal auto and homeowners quoting 1 Entry for multiple supplier quotes on all building materials Categorization suggested for UDDI is useful but inadequate (what does the WS do?) : 1 Entry for Automobile Manufacturing 1 Entry for Insurance agents, brokers, & service Alternatively read and try to understand WSDL 1 Entry related to security details (Human Understanding) 1 Test Web service for Quotes (which quote?)
Simplest Example http://www.reluctantdba.com/webquotes/WebQuotes.asmx GetQuote, GetQuoteById, GetQuoteForPerson … Which one is suitable ? What does the signature mean ? <XS:ComplexType>:Quote GetQuote (String UserName, String Password, int QuoteType) ;; what is a QuoteType? Which interaction is suitable ? New users 1. Register 2. Confirm 3. GetQuote*() Exisitng users 1. GetQuote*() Confirm: “ This method is used to confirm your email address”. WSDL says input message part name is “UserGUID” of type “string”. What is this part? What are the restrictions for service invocation “ RegisterUser method is used to register to use WebQuotes. You won't be able to start using WebQuotes until we have confirmed your email address.” Solution: Precondition and effects
Example Contd.. Another WSDL http://213.153.38.215/webtoolbox/quote.asmx?WSDL GetRandomQuote Description: “ Returns a random quote, as GetRandomQuote, but this time just German ones.” How do we (user, programmer, software agent) understand this ? It does not have the same interface specification as the previous one. Which one is suitable to my application? With the same signature, how is GetRandomQuote different from GetJoke operation (both return complex type): http://www.interpressfact.net/webservices/getJoke.asmx
Example (today) TV Weather Channel Find Weather at a Particular Region Patil, Oundhakar, Sheth, SAWS Techincal Report Out of these results, some do not have formal WSDL implementation, some links are not working and it does not return all the results.
Semantic Discovery : Problems TV Weather Channel Find Weather at a Particular Region Patil, Oundhakar, Sheth, SAWS Techincal Report, [Cardoso,Sheth],[DAML-S] Can Semantic Annotation of Web Services help? Service Template Input WMOCode Output Weather Service Input Output FastWeather WMO code (string) Weather GlobalWeather WMO/ICAO code (string) Weather WorldWeather WMO code (string) Array of Strings FetchWeather Zip Code (string) Weather
How to Annotate ? Map Web service’s input & output data as well as functional description using relevant data and function/operation ontologies, respectively How ? Borrow from schema matching Semantic disambiguation between terms in XML messages represented in WSDL and concepts in ontology
Semantic Annotation IOParametersMatch (w,o) = LingusticMatch (w,o) + StructureMatch (w,o) + ContextMatch (w,o) LingusticMatch (w,o) => NameMatch with stemming Description Match SynonymsMatch HypernymRelation (w is a kind of o) : prevailing_speed is a type of speed of a wind i.e. windSpeed HyponymRelation (o is a kind of w) Acronyms : Sea Level Pressure has acronym SLP StructureMatch (w,o) => subTree(w) == subTree(o) ContextMatch Name of the parent concept provides some insight to the context of the term Patil, Oundhakar, Sheth, SAWS Techincal Report
Semantic Annotation: Data Semantics < xsd:complexType name =&quot; Wind &quot;> < xsd:sequence >   < xsd:element name =&quot; prevailing_speed &quot; type =&quot; xsd:double &quot; />   < xsd:element name =&quot; gust_speed &quot; type =&quot; xsd:double &quot; />   < xsd:element name =&quot; prevailing_direction &quot; type =&quot; xsd1:Direction &quot; /> </ xsd:sequence > </ xsd:complexType > < xsd:complexType name =“ Pressure &quot;> < xsd:sequence >   < xsd:element name =“ altimeter &quot; type =&quot; xsd:double &quot; />   < xsd:element name =“ slp &quot; type =&quot; xsd:double &quot; />   < xsd:element name =“ delta &quot; type =&quot; xsd:double &quot; /> </ xsd:sequence > </ xsd:complexType > Patil, Oundhakar, Sheth, SAWS Techincal Report Ontology : weather-ont.daml WSDL : GlobalWeather.wsdl 0.756 0.69 0.9 0.5 0.8 0.23 1.0 1.0 WindEvent windSpeed WeatherEvent windDirection PressureEvent AltimeterSetting windGustSpeed SeaLevelPressure PressureChangeEvent Class Property
Semantic Annotation: Functional Semantics Patil, Oundhakar, Sheth, SAWS Techincal Report < portType name =&quot; GlobalWeather &quot;> < operation name =&quot; getWeatherReport &quot;>   < input message =&quot; tns:getWeatherReport &quot; />   < output message =&quot; tns:getWeatherReportResponse &quot; /> </ operation > </ portType > < portType name =&quot; StationInfo &quot;> < operation name =&quot; searchByCountry &quot;>   < input message =&quot; tns:searchByCountry &quot; />   < output message =&quot; tns:searchByCountryResponse &quot; /> </ operation > A Sample Functional Ontology WSDL Operations WeatherFunctions getWeather getStation getWind getPressure getTemperature getStationByZip getStationByCountry
IOParametersMatch (w,o) = w1*LingusticMatch (w,o) + w2*StructureMatch (w,o) + w3*ContextMatch (w,o) w1+w2+w3 Semantic Annotation Weights w1, w2 and w3 can be decided by the user based on the confidence in the respective type of matching technique LingusticMatch uses a SynonymDictionary, also uses WordNet StructureMatch ( w , o ) =            /   LingusticMatch(w,o) ;  if o є O.subclasses max <          \   √ LingusticMatch (w,o)*RangeMatch(w,o);         if o є O.properties 
METEOR-S Discovery
State of the art in discovery Search retrieves lot of services ( irrelevant results included) Which service to select ? How to select? UDDI Business Registry is universal and provides non-semantic search Keyword match, taxonomy UBR
METEOR-S Semantic Discovery Approach Registries are categorized Select relevant registries (semantic filtering) Select service(s) of interest Registry is domain specific and supports semantic search Ontology Domain Registry
MWSDI details Large number of registry/repository implementations are anticipated [NIST report]. ( how to link all registries ?) Scalable environment for Web Service Discovery Scalability using p2p network of registries improved quality of discovery using Semantic Annotation Implemented JXTA based p2p network of UDDI & Peer Roles Peer interaction protocols implementation Registry addition to the registry community Publishing a Web Service with annotation Semantic discovery of Web Services Ontology (Registries Ontology) based Registry selection for querying the registry
QoS in METEOR-S
QoS Management End-to-End process analysis QoS management is indispensable for organizations striving to achieve a higher degree of competitiveness. Based on previous studies* and our experience with business processes, we have constructed a QoS model composed of the following dimensions: Time Cost Reliability Fidelity *Stalk and Hout,1990;Rommel et al.,1995;Garvin, 1988
Research Issues in QoS Specification. What dimensions need to be part of the QoS model for processes? Computation. What methods and algorithms can be used to compute, analyze, and predict QoS? Monitoring. What kind of QoS monitoring tools need to be developed? Control. What mechanisms need to be developed to control processes, in response to unsatisfactory QoS metrics?    x y z
QoS in METEOR-S QoS Model QoS Estimates for Tasks/Web services QoS Computation Enact Stochastic Process QoS Estimates for Transitions Design Log SWR algorithm Simulation
Composition SCET (Web Processes, no semantics) Static composition and centralized execution Semantic Process Template Builder (under development) Improved Discovery Mechanism Uses Data/Operational and QoS Semantics in Service Discovery Template Based Process Designer, Generic Web Process Template and support for any executable process specification standard (a) allows you to focus on semantics of the process rather than WSDL of constituent Web services, (b) better structure to help optimize Service selection, and (c) helps in validation
Broad Scope of Semantic (Web) Technology Other dimensions: how agreements are reached, … Lots of Useful Semantic Technology (interoperability, Integration) Gen. Purpose, Broad Based Scope of Agreement Task/ App Domain Industry Common Sense Degree of Agreement Informal Semi-Formal Formal Agreement About Data/ Info. Function Execution Qos Current Semantic Web Focus Semantic Web Processes
Conclusion Semantics can help address big challenges related to scalability, dynamic environments,.. But comprehensive approach to semantics will be needed: Data/information, function/operation, execution, QoS Semantic (Web) principles and technology bring new tools and capabilities that we did not have in EAI, workflow management of the past More at: http://swp.semanticweb.org, or http://lsdis.cs.uga.edu/SWP.htm Also, Talk Abstract

More Related Content

PPT
Semantic Web Process Lifecycle:
Amit Sheth
 
PPT
Requirements Engineering for Services
Richard Claassens CIPPE
 
PDF
brocade-cosentry-ss
Katherine Tibedo Mechler
 
PPTX
Managing Contracts with SharePoint
Ram Prabhala
 
PDF
Addressing Contract Management Needs with SharePoint
Optimus BT
 
PDF
achievement_at_Barclays
Wei Zhang
 
PDF
Contract Management with SharePoint and Office365
Optimus BT
 
PDF
CDI-MDMSummit.290213824
ypai
 
Semantic Web Process Lifecycle:
Amit Sheth
 
Requirements Engineering for Services
Richard Claassens CIPPE
 
brocade-cosentry-ss
Katherine Tibedo Mechler
 
Managing Contracts with SharePoint
Ram Prabhala
 
Addressing Contract Management Needs with SharePoint
Optimus BT
 
achievement_at_Barclays
Wei Zhang
 
Contract Management with SharePoint and Office365
Optimus BT
 
CDI-MDMSummit.290213824
ypai
 

What's hot (12)

PPTX
Microsoft Online Services Partner Core Deck
jessiethe3rd
 
PPT
SSME Introduction
Richard Claassens CIPPE
 
PDF
Services Brochure - Keystone Logic
saikirani
 
PPTX
Dolphin Contract Lifecycle Manager for SharePoint
Barry Gervin
 
PDF
Step-by-Step Guide to Eval NSPs 2016
Eric Hyman
 
PDF
Managing Contract Obligations and Milestones with SharePoint
Optimus BT
 
PPTX
Simplifying Contract Lifecycle Management with SharePoint
Optimus BT
 
PPTX
Chap 1
Syed Ali Raza
 
PDF
Operational Excellence (2010)
Marc Jadoul
 
PDF
Contract lifecycle management webinar with cignex 22 apr2010
Alfresco Software
 
PPTX
02 Service Oriented Architecture Series - SOA Concepts
Pouria Ghatrenabi
 
PPT
Framework Guides The Examination Of Soa Business Benefits
Richard Claassens CIPPE
 
Microsoft Online Services Partner Core Deck
jessiethe3rd
 
SSME Introduction
Richard Claassens CIPPE
 
Services Brochure - Keystone Logic
saikirani
 
Dolphin Contract Lifecycle Manager for SharePoint
Barry Gervin
 
Step-by-Step Guide to Eval NSPs 2016
Eric Hyman
 
Managing Contract Obligations and Milestones with SharePoint
Optimus BT
 
Simplifying Contract Lifecycle Management with SharePoint
Optimus BT
 
Chap 1
Syed Ali Raza
 
Operational Excellence (2010)
Marc Jadoul
 
Contract lifecycle management webinar with cignex 22 apr2010
Alfresco Software
 
02 Service Oriented Architecture Series - SOA Concepts
Pouria Ghatrenabi
 
Framework Guides The Examination Of Soa Business Benefits
Richard Claassens CIPPE
 
Ad

Viewers also liked (7)

PPT
Twitter op jouw congres of evenement in 10 stappen
Gerrit Heijkoop
 
PPTX
Imagenes nut
Victor A. Reyes
 
PPTX
Lyncros eLearning
Matias O'Keefe
 
PPS
Renoir-Chopin
Alyla
 
PPTX
Pres 3
Victor A. Reyes
 
PDF
Usability studie inkl._costper_click_2013
Austrian National Tourist Office
 
PDF
Usability studie inkl.eyetracking_d 2012
Austrian National Tourist Office
 
Twitter op jouw congres of evenement in 10 stappen
Gerrit Heijkoop
 
Imagenes nut
Victor A. Reyes
 
Lyncros eLearning
Matias O'Keefe
 
Renoir-Chopin
Alyla
 
Pres 3
Victor A. Reyes
 
Usability studie inkl._costper_click_2013
Austrian National Tourist Office
 
Usability studie inkl.eyetracking_d 2012
Austrian National Tourist Office
 
Ad

Similar to Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, Composition and Orchestration (20)

PPT
How to Get Cloud Architecture and Design Right the First Time
David Linthicum
 
PPT
Ws Soa V6 Theory And Practice
Pini Cohen
 
PPS
Malta soa infrastructure
Angel Knight
 
PPT
Soa 101
David Linthicum
 
DOCX
ISYS40061 Service Oriented Cloud Technologies.docx
stirlingvwriters
 
PDF
Confluent Partner Tech Talk with BearingPoint
confluent
 
PDF
Evaluation of a Framework for Integrated Web Services
IRJET Journal
 
PDF
Modernising the Enterprise: An Evening with the AWS Enterprise User Group
Harley Young
 
PPT
Soa Test Methodology
Diwakar Venkata
 
PPT
SOA Presentation
Mark Goetsch
 
PPT
Iam suite introduction
wardell henley
 
PPT
Coghead Overview 21 Aug08
Tomoaki Sawada
 
PDF
VMworld 2013: Create a Key Metrics-based Actionable Roadmap to Deliver IT as ...
VMworld
 
PPT
Service Analysis And Design
Rody Middelkoop
 
PDF
Five Priorities for Quality Engineering When Taking Banking to the Cloud
Cognizant
 
PPTX
Automate the development lifecycle with cumulus ci on april 9th, 2020
Sudipta Deb ☁
 
PPT
Service Modelling and Representation Techniques - a holistic Enterprise Arch...
ServiceWave 2010
 
PPT
Service Modelling and Representation Techniques
ServiceWave 2010
 
PDF
Greetings david cutler inform and connect
Sales Strategy and Innovation Delivery
 
PDF
Metrics that Matter-Approaches To Managing High Performing Websites
Ben Rushlo
 
How to Get Cloud Architecture and Design Right the First Time
David Linthicum
 
Ws Soa V6 Theory And Practice
Pini Cohen
 
Malta soa infrastructure
Angel Knight
 
Soa 101
David Linthicum
 
ISYS40061 Service Oriented Cloud Technologies.docx
stirlingvwriters
 
Confluent Partner Tech Talk with BearingPoint
confluent
 
Evaluation of a Framework for Integrated Web Services
IRJET Journal
 
Modernising the Enterprise: An Evening with the AWS Enterprise User Group
Harley Young
 
Soa Test Methodology
Diwakar Venkata
 
SOA Presentation
Mark Goetsch
 
Iam suite introduction
wardell henley
 
Coghead Overview 21 Aug08
Tomoaki Sawada
 
VMworld 2013: Create a Key Metrics-based Actionable Roadmap to Deliver IT as ...
VMworld
 
Service Analysis And Design
Rody Middelkoop
 
Five Priorities for Quality Engineering When Taking Banking to the Cloud
Cognizant
 
Automate the development lifecycle with cumulus ci on april 9th, 2020
Sudipta Deb ☁
 
Service Modelling and Representation Techniques - a holistic Enterprise Arch...
ServiceWave 2010
 
Service Modelling and Representation Techniques
ServiceWave 2010
 
Greetings david cutler inform and connect
Sales Strategy and Innovation Delivery
 
Metrics that Matter-Approaches To Managing High Performing Websites
Ben Rushlo
 

Recently uploaded (20)

PPTX
Microbial diseases, their pathogenesis and prophylaxis
DevlinaSengupta
 
PDF
TR - Agricultural Crops Production NC III.pdf
avgilmegino3
 
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
Jonathan Hallett
 
PPTX
Pharma ospi slides which help in ospi learning
rameetkumar304
 
PPTX
master seminar digital applications in india
ananyaray35
 
PDF
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
pascalgumisiriza1
 
PPTX
BOWEL ELIMINATION FACTORS AFFECTING AND TYPES
PreetiSawant10
 
PPTX
Institutional Correction lecture only . . .
limvtheghins
 
PPTX
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
shilpa939953
 
PPTX
Cell Types and Its function , kingdom of life
ClaireMangundayao1
 
PDF
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
MarjorieLopezTiu
 
PPTX
Week 4 Term 3 Study Techniques revisited.pptx
mansk2
 
PDF
STATICS OF THE RIGID BODIES Hibbelers.pdf
pascualasturiaskaye4
 
PPTX
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
PPTX
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
RAKESH SAJJAN
 
PPTX
Cell Structure & Organelles in detailed.
DHANASHREESIVAKUMAR
 
PPTX
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
chetansingh379583
 
PDF
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
HakHe
 
PDF
01-Introduction-to-Information-Management.pdf
PrinceIbarra
 
PDF
Insiders guide to clinical Medicine.pdf
AbhishekPatil315128
 
Microbial diseases, their pathogenesis and prophylaxis
DevlinaSengupta
 
TR - Agricultural Crops Production NC III.pdf
avgilmegino3
 
Module 4: Burden of Disease Tutorial Slides S2 2025
Jonathan Hallett
 
Pharma ospi slides which help in ospi learning
rameetkumar304
 
master seminar digital applications in india
ananyaray35
 
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
pascalgumisiriza1
 
BOWEL ELIMINATION FACTORS AFFECTING AND TYPES
PreetiSawant10
 
Institutional Correction lecture only . . .
limvtheghins
 
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
shilpa939953
 
Cell Types and Its function , kingdom of life
ClaireMangundayao1
 
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
MarjorieLopezTiu
 
Week 4 Term 3 Study Techniques revisited.pptx
mansk2
 
STATICS OF THE RIGID BODIES Hibbelers.pdf
pascualasturiaskaye4
 
Final Presentation General Medicine 03-08-2024.pptx
ZaheerAhmad228692
 
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
RAKESH SAJJAN
 
Cell Structure & Organelles in detailed.
DHANASHREESIVAKUMAR
 
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
chetansingh379583
 
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
HakHe
 
01-Introduction-to-Information-Management.pdf
PrinceIbarra
 
Insiders guide to clinical Medicine.pdf
AbhishekPatil315128
 

Semantic Web Process Lifecycle: Role of Semantics in Annotation, Discovery, Composition and Orchestration

  • 1. Semantic Web Process Lifecycle: R ole of Semantics in Annotation, Discovery,Composition and Execution Invited talk: WWW 2003 Workshop on E-Services and the Semantic Web Budapest, Hungary, Tuesday, May 20, 2003 Amit Sheth LSDIS Lab, University of Georgia and Semagix , Inc. With Acknowledgements to METEOR-S Project team: Kaarthik Sivashanmugam, Kunal Verma,Abhijit Patil
  • 2. Processes driving the Networked Economy Companies distributed over space, time, and capability will have to come together to deliver products and solutions in global marketplace. Processes are already becoming chief differentiating and the competitive force in the networked economy. Processes are becoming an organic part of doing business. * From Sheth, Aalst et al, “Processes driving the Networked Economy” 1999
  • 3. Globalization of Processes Web Processes Workflows Distributed Workflows Global Enterprise Inter-Enterprise B2B E-Services Processes driving the Networked Economy
  • 4. Architectures for Web Processes* Stages of architectural evolution Process Portal one stop for e-services, p2p interactions between buyer and sellers E-Gov, industry automation, Life Science Process Vortex Interactions between buyer and seller through a third party marketmaker, predefined processes, shared ontology Dynamically Trading Processes * From Sheth, Aalst et al, “Processes driving the Networked Economy” 1999
  • 5. Process Portal Processes driving the Networked Economy
  • 6. Process Portal One-stop shopping for products or information A portal is responsible for carrying out or coordinating a majority of activities using the data it has and the transactions it supports. Predefined, (relatively) static business processes also supporting P2P interactions A key characteristic of a portal is to own or manage much of the data and information it needs to meet its customers process needs.
  • 7. Process Vortex Processes driving the Networked Economy
  • 8. Process Vortex Interactions among buyers and sellers occur through governed marketplaces managed by third party market makers Market maker supports common ontology that buyers use to access products/services from multiple suppliers Focus on very specific product lines, predefined business processes, unified interface to catalogues and supplier aggregation
  • 10. Dynamically Trading Processes Many complex interactions among enterprises Business processes are highly dynamic Based on the needs and preferences of a customer, a virtual process is constructed on the fly to meet this very particular demand of the customer. Participants are a group of semi-autonomous or autonomous organizations that need to cooperate: selective participation hiding details and providing partial visibility
  • 11. BIG Challenges Scalability Heterogeneity Dynamic nature of business interactions Long duration Hypothesis: Semantics is the most important enabler (hence Semantic Web Process)
  • 12. Scalability B8 A1 A4 A1 A2 A4 B3 A1 A4 A6 A2 A5 Before (Enterprise,Inter-enterprise workflows) A C D N1 N2 F E Discovery/Matchmaking should be accurate and scalable to the number of services available in Web A C D N1 N2 F E A4 A1 A1 A4 A1 A4 A1 A2 A1 A1 A1 A1 B3 A1 B3 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A2 A1 B3 A1 A4 A1 A2 B3 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A1 A4 A1 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A4 A4 A1 A4 A1 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 B3 A1 A4 A1 A2 A1 A4 A1 A4 A1 A1 A4 A1 A2 A1 A1 A4 A1 A2 A1 A1 A4 A1 B3 A1 A1 A1 B3 A1 A4 A1 A2 A1 B3 A1 A4 A1 A2 A1 A1 A2 A1 A4 A2 A4 A2 A2 A1 A1 B3 A1 A4 A1 A2 A1 Now Semantics of the services Semantics of the activity (Data, Functional, Execution, QoS)
  • 13. Dynamic Nature of Processes Different partners Different Interface for their services Need for dynamic partnerships
  • 14. Challenges in Web Services* modeling, organizing collections discovery and comparison distribution and replication access and composition fulfillment (contracts, coordination versus transactions, compliance) quality aspects more general than correctness or precision, compliance) security and trust * From Amicalola report, Sigmod Record , Dec 2002
  • 15. Contribution of Semantic Web* Semantic Web promises significant benefits to businesses Improves productivity and efficiency Reduce cost, time, effort etc. Improves scalablility to the size of the web Exploits unique opportunities of Web Converting processes from incomplete/discrete to comprehensive/continuous Diversify customer base and going global Volatility and dynamic nature * From Amicalola report, Sigmod Record , Dec 2002
  • 16. Semantic Web Processes: What does it provide ? Information resource, person, organization, and many of the activities relating to them will be located on or be driven by the Web. Qualitatively improved interactions Quantitatively changes the scale and scope by automating the interactions All this is possible only by adding “meaning” to the resources and using them for automation * From Amicalola report, Sigmod Record , Dec 2002
  • 17. SWS and SWP Semantic Web Services* Semantic Web Processes Intra/Inter EnterpriseWorkflows Semantic Web Processes ebXML B2B Processes * From Amicalola report, Sigmod Record , Dec 2002
  • 18. (Backdrop) Industries, Technologies, Research and Vision meet at SWP Semantic Web Process ebXML Workflow, EAI Semantic Web Web Services
  • 19. Semantics for Web Processes Data/Information Semantics Functional/Operational Semantics Execution Semantics QoS Semantics
  • 20. Data or Information Semantics What ? Formal definition of data in input and output messages of a web service Why ? Discovery and Interoperability of Web Services How ? Annotating input/output data of web services using ontologies (METEOR-S’ WSDL-S), or formally describe I/O (DAML-S)
  • 21. Function or Operational Semantics What ? Formally representing capabilities of each web service Why ? Discovery of Web Services How ? Annotate operations of Web Services as well as provide preconditions and effects; Annotating Trading Partner Agreement (TPA)/Service Level Agreement (SLA)
  • 22. Execution Semantics What ? Formally representing the execution (status) or flow of a services in a process or operations in a service Why ? Analysis (verification) and validation (simulation) of the process models and exception handling How ? Using State charts, Petri nets or activity diagrams
  • 23. QoS Semantics What ? Formally describes operational metrics of a web service/process Why ? To select the most suitable service to carry out an activity in a process How ? Using QoS model for web services Time, Cost, Reliability, (Fidelity): e.g., Cardoso and Sheth, 2002
  • 24. B2B process between Distributor and Toy Manufacturer ElectonicToysDistributor 1 2 ToysManufacturer 3 4 Request for details given Order on number of toys Send the price and delivery details Place order Order confirmation PartsSupplierPartner DeliveryPartner Bank Get Details (1, 2) Place Order (3, 4) UDDI Discovery: Using data, functional and QoS semantics Execution and Exception handling using QoS and Execution semantics
  • 25. Discovery in Semantic Web Process Management An Electronic Toy distributor wants to place an order to a Toy Manufacturer Discovery Template Functionality : What capabilities the distributor expects from the service (operational semantics) Inputs : What the distributor can give to the to the Manufacturer’s service (data semantics) Outputs : What the distributor expects as outputs from the service (data semantics) QoS : Quality of Service the distributor expects from the service (QoS semantics)
  • 26. Execution / Invocation. After discovery, the service can be Invoked OR Simulated or verified if the details of the Manufacturer’s process is public (execution semantics) Verification can also be done by the Manufacturer before deploying the process
  • 27. Features of Semantic Web Processes Different Functional and Data Semantics for competing Web services ManufacturerA’s service takes order for all kind of toys ManufacturerB’s service takes order specifically for electronic toys ManufacturerC takes Credit card as input and produces confirmation ManufacturerD takes PartnershipId as input and produces the confirmation with number of toys ordered and money that will be deducted from the account relevant to the PartnershipId given ManufacturerE deals only with distributors whose credit rating is more that ‘X’
  • 28. Features of Semantic Web Processes Selecting correct partners (Using QoS) ManufacturerA delivers toys sooner but costs more ManufacturerB charges more but takes care of delivery ManufacturerC provides a service with best time and cost parameters but the failure rate is high Which one to select for business ? Should QoS (time, cost, reliability) be part of a general model, or application specific (or a combination)?
  • 29. Features of Semantic Web Processes Verification of the process (Using execution semantics) ManufacturerA models his process and verifies its execution before deploying it DistributorA finds the ManufacturerB’s service, simulates its execution and if satisfied with the result invokes it
  • 30. Features of Semantic Web Processes Process Management (Using execution semantics) Distributor wants to cancel the order when the product is about to be shipped to him. He can query the process management system if he is allowed to do that. If yes, at what penalty or cost ? May depends on the state of process (execution).
  • 31. Features of Semantic Web Processes Exception handling during Process Management (Using execution semantics) The delivery partner of the manufacturer went on strike and he needs to find an alternative delivery service. How can he find a semantically equivalent alternative without compromising on the QoS of the entire process If he is finding an alternative that should be compatible with the preconditions and effects of the related services in the process Exception handling should be intelligent either to retry invocation of a service or attempt compensation action. It is difficult to hardcode/program exceptions for all possible failures
  • 32. Advanced Features Future capabilities Semantic Web can lend to Web Processes Decision Making Manufacturer uses trust parameters during dynamic partner selection Inferencing Toy Distributor comes to know that all Manufacturers are going on strike. Toy manufacturer is a type of manufacturer. Hence he inferences that he will also go on strike. So places order for toys to meet demand for toys before the strike starts.
  • 33. Semantic Web Process LifeCycle Data / Information Semantics Description / Annotation WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) Discovery UDDI WSIL, DAML-S METEOR-S (P2P model of registries) Composition / Choreography BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET) Execution / Orchestration BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow
  • 34. Semantic Web Process LifeCycle Data / Information Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
  • 35. Semantic Web Process LifeCycle Functional / Operational Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
  • 36. Semantic Web Process LifeCycle QoS Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
  • 37. Semantic Web Process LifeCycle Execution Semantics Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET)
  • 38. Semantic Web Process LifeCycle Discovery WSDL, WSEL DAML-S Meteor-S (WSDL Annotation) UDDI WSIL, DAML-S METEOR-S (P2P model of registries) BPWS4J, Commercial BPEL Execution Engines, Intalio n3, HP eFlow Semantics Required for Web Processes Description / Annotation Composition / Choreography Execution / Orchestration BPEL, BPML, WSCI, WSCL, DAML-S, METEOR-S (SCET) Execution Semantics QoS Semantics Functional / Operational Semantics Data / Information Semantics
  • 39. METEOR-S Applying Semantics in Annotation, Quality of Service, Discovery, Composition, Execution Focuses on two issues: semantic Web services and process composition. Process Composition: Functional perspective Web Service Discovery, handling semantic heterogeneity Operational perspective QoS specification for Web Services and Processes. 
  • 40. METEOR-S components for SWP Discovery Infrastructure (MWSDI) Semantic Annotation of Web Services Semantic Peer-to-Peer network of Web Services Registries Composer SCET: Service Composition and Execution Tool Semantics Process Template Builder (under development) QoS Management Specify, compute, monitor and control QoS (SWR algorithm) Orchestrator Analysis and Simulation Execution Monitoring
  • 41. Semantics in METEOR-S METEOR-S examples of using/supporting semantics: Annotation Discovery Composition (in development) QoS
  • 43. Present Discovery Mechanism UDDI :Keyword, taxonomy based search Example: “Quote” Microsoft UBR returned 12 services Human reading of description (Natural Language) helped me understand 8 of these: 6 Entries are to get Famous Quotes 1 Entry for personal auto and homeowners quoting 1 Entry for multiple supplier quotes on all building materials Categorization suggested for UDDI is useful but inadequate (what does the WS do?) : 1 Entry for Automobile Manufacturing 1 Entry for Insurance agents, brokers, & service Alternatively read and try to understand WSDL 1 Entry related to security details (Human Understanding) 1 Test Web service for Quotes (which quote?)
  • 44. Simplest Example http://www.reluctantdba.com/webquotes/WebQuotes.asmx GetQuote, GetQuoteById, GetQuoteForPerson … Which one is suitable ? What does the signature mean ? <XS:ComplexType>:Quote GetQuote (String UserName, String Password, int QuoteType) ;; what is a QuoteType? Which interaction is suitable ? New users 1. Register 2. Confirm 3. GetQuote*() Exisitng users 1. GetQuote*() Confirm: “ This method is used to confirm your email address”. WSDL says input message part name is “UserGUID” of type “string”. What is this part? What are the restrictions for service invocation “ RegisterUser method is used to register to use WebQuotes. You won't be able to start using WebQuotes until we have confirmed your email address.” Solution: Precondition and effects
  • 45. Example Contd.. Another WSDL http://213.153.38.215/webtoolbox/quote.asmx?WSDL GetRandomQuote Description: “ Returns a random quote, as GetRandomQuote, but this time just German ones.” How do we (user, programmer, software agent) understand this ? It does not have the same interface specification as the previous one. Which one is suitable to my application? With the same signature, how is GetRandomQuote different from GetJoke operation (both return complex type): http://www.interpressfact.net/webservices/getJoke.asmx
  • 46. Example (today) TV Weather Channel Find Weather at a Particular Region Patil, Oundhakar, Sheth, SAWS Techincal Report Out of these results, some do not have formal WSDL implementation, some links are not working and it does not return all the results.
  • 47. Semantic Discovery : Problems TV Weather Channel Find Weather at a Particular Region Patil, Oundhakar, Sheth, SAWS Techincal Report, [Cardoso,Sheth],[DAML-S] Can Semantic Annotation of Web Services help? Service Template Input WMOCode Output Weather Service Input Output FastWeather WMO code (string) Weather GlobalWeather WMO/ICAO code (string) Weather WorldWeather WMO code (string) Array of Strings FetchWeather Zip Code (string) Weather
  • 48. How to Annotate ? Map Web service’s input & output data as well as functional description using relevant data and function/operation ontologies, respectively How ? Borrow from schema matching Semantic disambiguation between terms in XML messages represented in WSDL and concepts in ontology
  • 49. Semantic Annotation IOParametersMatch (w,o) = LingusticMatch (w,o) + StructureMatch (w,o) + ContextMatch (w,o) LingusticMatch (w,o) => NameMatch with stemming Description Match SynonymsMatch HypernymRelation (w is a kind of o) : prevailing_speed is a type of speed of a wind i.e. windSpeed HyponymRelation (o is a kind of w) Acronyms : Sea Level Pressure has acronym SLP StructureMatch (w,o) => subTree(w) == subTree(o) ContextMatch Name of the parent concept provides some insight to the context of the term Patil, Oundhakar, Sheth, SAWS Techincal Report
  • 50. Semantic Annotation: Data Semantics < xsd:complexType name =&quot; Wind &quot;> < xsd:sequence >   < xsd:element name =&quot; prevailing_speed &quot; type =&quot; xsd:double &quot; />   < xsd:element name =&quot; gust_speed &quot; type =&quot; xsd:double &quot; />   < xsd:element name =&quot; prevailing_direction &quot; type =&quot; xsd1:Direction &quot; /> </ xsd:sequence > </ xsd:complexType > < xsd:complexType name =“ Pressure &quot;> < xsd:sequence >   < xsd:element name =“ altimeter &quot; type =&quot; xsd:double &quot; />   < xsd:element name =“ slp &quot; type =&quot; xsd:double &quot; />   < xsd:element name =“ delta &quot; type =&quot; xsd:double &quot; /> </ xsd:sequence > </ xsd:complexType > Patil, Oundhakar, Sheth, SAWS Techincal Report Ontology : weather-ont.daml WSDL : GlobalWeather.wsdl 0.756 0.69 0.9 0.5 0.8 0.23 1.0 1.0 WindEvent windSpeed WeatherEvent windDirection PressureEvent AltimeterSetting windGustSpeed SeaLevelPressure PressureChangeEvent Class Property
  • 51. Semantic Annotation: Functional Semantics Patil, Oundhakar, Sheth, SAWS Techincal Report < portType name =&quot; GlobalWeather &quot;> < operation name =&quot; getWeatherReport &quot;>   < input message =&quot; tns:getWeatherReport &quot; />   < output message =&quot; tns:getWeatherReportResponse &quot; /> </ operation > </ portType > < portType name =&quot; StationInfo &quot;> < operation name =&quot; searchByCountry &quot;>   < input message =&quot; tns:searchByCountry &quot; />   < output message =&quot; tns:searchByCountryResponse &quot; /> </ operation > A Sample Functional Ontology WSDL Operations WeatherFunctions getWeather getStation getWind getPressure getTemperature getStationByZip getStationByCountry
  • 52. IOParametersMatch (w,o) = w1*LingusticMatch (w,o) + w2*StructureMatch (w,o) + w3*ContextMatch (w,o) w1+w2+w3 Semantic Annotation Weights w1, w2 and w3 can be decided by the user based on the confidence in the respective type of matching technique LingusticMatch uses a SynonymDictionary, also uses WordNet StructureMatch ( w , o ) =            /   LingusticMatch(w,o) ;  if o є O.subclasses max <          \   √ LingusticMatch (w,o)*RangeMatch(w,o);         if o є O.properties 
  • 54. State of the art in discovery Search retrieves lot of services ( irrelevant results included) Which service to select ? How to select? UDDI Business Registry is universal and provides non-semantic search Keyword match, taxonomy UBR
  • 55. METEOR-S Semantic Discovery Approach Registries are categorized Select relevant registries (semantic filtering) Select service(s) of interest Registry is domain specific and supports semantic search Ontology Domain Registry
  • 56. MWSDI details Large number of registry/repository implementations are anticipated [NIST report]. ( how to link all registries ?) Scalable environment for Web Service Discovery Scalability using p2p network of registries improved quality of discovery using Semantic Annotation Implemented JXTA based p2p network of UDDI & Peer Roles Peer interaction protocols implementation Registry addition to the registry community Publishing a Web Service with annotation Semantic discovery of Web Services Ontology (Registries Ontology) based Registry selection for querying the registry
  • 58. QoS Management End-to-End process analysis QoS management is indispensable for organizations striving to achieve a higher degree of competitiveness. Based on previous studies* and our experience with business processes, we have constructed a QoS model composed of the following dimensions: Time Cost Reliability Fidelity *Stalk and Hout,1990;Rommel et al.,1995;Garvin, 1988
  • 59. Research Issues in QoS Specification. What dimensions need to be part of the QoS model for processes? Computation. What methods and algorithms can be used to compute, analyze, and predict QoS? Monitoring. What kind of QoS monitoring tools need to be developed? Control. What mechanisms need to be developed to control processes, in response to unsatisfactory QoS metrics?    x y z
  • 60. QoS in METEOR-S QoS Model QoS Estimates for Tasks/Web services QoS Computation Enact Stochastic Process QoS Estimates for Transitions Design Log SWR algorithm Simulation
  • 61. Composition SCET (Web Processes, no semantics) Static composition and centralized execution Semantic Process Template Builder (under development) Improved Discovery Mechanism Uses Data/Operational and QoS Semantics in Service Discovery Template Based Process Designer, Generic Web Process Template and support for any executable process specification standard (a) allows you to focus on semantics of the process rather than WSDL of constituent Web services, (b) better structure to help optimize Service selection, and (c) helps in validation
  • 62. Broad Scope of Semantic (Web) Technology Other dimensions: how agreements are reached, … Lots of Useful Semantic Technology (interoperability, Integration) Gen. Purpose, Broad Based Scope of Agreement Task/ App Domain Industry Common Sense Degree of Agreement Informal Semi-Formal Formal Agreement About Data/ Info. Function Execution Qos Current Semantic Web Focus Semantic Web Processes
  • 63. Conclusion Semantics can help address big challenges related to scalability, dynamic environments,.. But comprehensive approach to semantics will be needed: Data/information, function/operation, execution, QoS Semantic (Web) principles and technology bring new tools and capabilities that we did not have in EAI, workflow management of the past More at: http://swp.semanticweb.org, or http://lsdis.cs.uga.edu/SWP.htm Also, Talk Abstract

Editor's Notes

  • #9: Telecommunications industry: service provider needs to support different classes of customers (e.g., individual residences, small businesses, and large businesses) and require flexibility to deal with a limited set of partners. For example, a CLEC may need flexibility in leasing network capacities for long distance services from QWEST communications or Level 3 communications.
  • #11: Telecommunications industry: one of the visions of the future networks includes the facility to allow consumer devices to interact with other devices and humans on the network in an integrated fashion. The device may be able to specify a need for a specific type and quality of network services required and the network dynamically composes a customized process to allow processing of the request.
  • #22: TPA = Trading Partner Agreement Some URLs: 1. http://xml.coverpages.org/tpa.html 2. http://www.hud.gov/offices/cpd/systems/idis/faq.cfm#agreement &amp;quot;A Trading Partner Agreement is a legal document which gives the guidelines of business between you and your Trading Partner. You may need a Trading Partner Agreement for each new Trading Partner. By signing the Agreement, you agree that any transactions done via EDI are as legal and binding as a transaction done through the mail or over the phone. &amp;quot; from http://www.esisinc.com/support/faq.htm
  • #34: Intalio n3 : Completor BPMS..design, deploy, execute, analyze and optimize processes…brochure says it supports BPML specification WSEL: Web Service End Point Language-- Non-operational specification of Web service WSIL: The WS-Inspection specification provides an XML format for assisting in the inspection of a site for available services and a set of rules for how inspection related information should be made available for consumption. A WS-Inspection document provides a means for aggregating references to pre-existing service description documents which have been authored in any number of formats. These inspection documents are then made available at the point-of-offering for the service as well as through references which may be placed within a content medium such as HTML.
  • #44: UDDI supports only text based keyword search and taxonomy based search. But they are not sufficient. For example: if you search for services using the keyword &amp;quot;Quote&amp;quot; in Microsoft UBR (Universal Business Registry), it results in 12 services. The services range from &amp;quot;famous quotations&amp;quot; to &amp;quot;automobile quote&amp;quot; Of these 12 services, 8 services are understood using their descriptions Out of this 8, 6 services are described as services that give out famous quotations, 1 service description says it is related to &amp;quot;personal auto and home owners quoting&amp;quot;, 1 service describes itself as &amp;quot;multiple supplier quotes on all building materials&amp;quot; Though these descriptions are helpful to understand the purpose/capability of the services, they are in Natural Language and hence it is not feasible to understand all kind of descriptions. Out of the 12 service returned from UDDI, 2 services are categorized under &amp;quot;Automobile Manufacturing&amp;quot; and &amp;quot;Insurance agents, borkers and service&amp;quot;. But these categorizations are too broad and do not characterise the capabilities of the services Of the 12 services, 2 services were neither described well, nor categorized, so to understand the capabilities of the service one needs to use the data types and comments in WSDL file. So simply speaking the discovery mechanism supported by UDDI is inadequate.
  • #45: This slide tells the problems in understanding/using/invoking even a simplest service. From the list of services shown previous slide we have taken a service that returns &amp;quot;world famous quotes&amp;quot;. It is available in the URL given in the slide. To use this service we need to understand the different kind of operations available in its WSDL file. Looking at this WSDL file, shows that it has different operations called &amp;quot;GetQuote&amp;quot;, &amp;quot;GetQuoteById&amp;quot;, &amp;quot;GetQuoteForPerson&amp;quot; etc. So we need to select the one that is suitable for our purpose. Selecting a particular operation may involve understanding the signature of the the operations. for example &amp;quot;GetQuote&amp;quot; service has the signature as shown in the slide. But it does not describe what a quote type is, apart from saying it is of type integer. This Web service also supports different kind of interactions. New users have to register, confirm before invoking the GetQuote() method. Existing users can directly invoke the method. How do we understand these different kind of interaction patterns. The description of the &amp;quot;confirm&amp;quot; operation says it &amp;quot;This method is used to confirm your email address&amp;quot;. From the signature of the method we can see that it takes a string &amp;quot;UserGUID&amp;quot; as input. How are we going to interpret the signature and decide if it is suitable. The WSDL description of &amp;quot;Register&amp;quot; operation says that &amp;quot;registeruser method is used to register to use.....&amp;quot;. To use the service properly we need to understand this description&amp;quot;. Preconditions and effects are helpful to specify these conditions which can be made easy to understand using the ontologies. Preconditions and effects along with a &amp;quot;Conversation specification&amp;quot; like WSCI or WSCL could be of use.
  • #47: Out of these results, some do not have formal WSDLimplementation, some links are not working and it does not return all the results. As it is a Business registry. SOme are just names of the businesses and I did not find WSDL descriptions for them. Some of the links they have given for the implementation are not working. So i couldn&apos;t find if they are really working or not. And there are some more services which are named not as weather service but do provide same functionality. But due to keyword based search we cant find them in UDDI by searching for Weather Services. We need to have some idea about the name of the service or provider in order to get really good results from UDDI which is in most of the cases may not be possible.
  • #48: The solution to this problem are Formally describing Inputs and outputs of the services [DAML-S] approach Our way : Annotating WSDL constructs
  • #49: This slide shows URL to another WSDL file. It has a method called GetRandomQuote. The description says &amp;quot;Returns a random quote, as GetRandomQuote, but this time just German ones&amp;quot;. How do we understand this kind of descriptions. Also the interface (signature) supported by the operations in this service are different from the operations in WSDL given in previous slide. Inspite of the fact that both the services are used to get world famous quotes&amp;quot;, they differ in the terminologies (data and message names) used in their WSDL file and in their signatures. So the discovery system should also support analysing these different operations in WSDL to find a relevant and suitable service to invoke. Just to reiterate the point that WSDL descriptions are inadequte to represent a service, here is an example. There is another service with an operation called getJoke which has similar signature as that of getQuote. But the purpose is entirely different. WSDL descriptions do not capture this kind of differences.
  • #50: The description of the Concept in WSDL file can be there as a comment or we can get it from Wordnet. In DAML-s ontologies we do have the description of the concept. Now regarding Name matches, we can apply stemming algorithms and stop word processing which removes unnecessary words, like &amp;quot;Event in case of windEvent“ or &amp;quot;_ in case of gust_speed to give gustSpeed&amp;quot; and then do the name matching. Then synonyms, meronyms etc could be obtained from Word net or similar dictionary. Abbreviations and acronyms would be provided by the user. It could be a file or some customized class for the same.
  • #51: Both ontology and WSDL are from real world Red Arrow : Acronym Green Arrow : Structural Match Light green arrow : Description Match Blue Arrow : Hypernym relation Violet Arrow : Name Matching with stemming
  • #56: Registry Types * [JP2P Unleashed]: Corporate Registries (Public/Non-public) CRM/ERP vendor Registries (Package of services) E-market places (Private/Open) Consortia Registries (Industry specific/Standards specific) etc..
  • #59: From Cardoso’s PhD dissertation
  • #60: From Cardoso’s dissertation
  • #62: Three value propositions for using templates: (a) allows you to focus on semantics of the process rather than WSDL of constituent Web services, (b) better structure to help optimize Service selection, and © help in validation
  • #63: Semantics (of information, communication) is a very old area, and extensive work on Semantic Technology has been going on for well over a decade (many projects on semantic interoperability, semantic information brokering) Semantic Web and related visions are being achieved in various depth and scope – mostly starting with targeted applications where requirements are much better understood and scope is manageable