Automatic Web Service Composition Models, Complexity and - PowerPoint PPT Presentation

Automatic Web Service Composition Models, Complexity and Applications PhD Defense Presentation PhD candidate Paul Diac Alexandru Ioan Cuza University of Iasi Faculty of Computer Science Supervisor: Prof. Dr. Dan Cristea 26 June, 2020

Contents Introduction 1 Models and Complexity 2 Name Matching Hierarchical Relational Object-Oriented Dynamic Others Applications 3 Software Development Natural Language Processing Conclusion 4

Automatic Web Service Composition - Models, Complexity and Applications Introduction What is (Automatic) Web Service Composition? web services provide a simple fine-grained functionality functionally described by input and output parameters composition of services enables new functionality automation of composition based on rules 3/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Motivation services are a popular and growing style of software design too many services to handle manually there is potential for automation interesting computational problems 4/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Example - services service providers web services repository getCityCenter getCityDistrict locatePhone getLatLon getMap getWeather trafficInfo nearbyStreet 5/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Example - the new request user service providers web services repository getCityCenter getCityDistrict request locatePhone getDrivingConditions getLatLon getMap getWeather trafficInfo nearbyStreet 5/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Example - can we solve the request? user composition service providers web services repository getCityCenter getCityDistrict request locatePhone ? getDrivingConditions getLatLon getMap getWeather trafficInfo nearbyStreet 5/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Example - yes, using some of the services user composition service providers web services repository getCityCenter getCityDistrict 1 request locatePhone 3 4 yes: getDrivingConditions getLatLon getMap 2 6 5 getWeather trafficInfo nearbyStreet 5/42

Automatic Web Service Composition - Models, Complexity and Applications Introduction Example - conclusions the composition is a sequence of services satisfies the user request and follows some rules it may not exist, or it may not be unique if these rules are formalized, automation is possible 6/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Models and Complexity by model we refer to the methods of representing the system in service composition most often refers to parameter matching expressivity is good, complicated models are hard to adopt models generate problems of various computational complexities 7/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Contents Introduction 1 Models and Complexity 2 Name Matching Hierarchical Relational Object-Oriented Dynamic Others 3 Applications Software Development Natural Language Processing Conclusion 4 8/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Name Matching Model parameters generally have a short and intuitive name name coincide ⇒ parameters most likely refer the same concept simplest and first formalism for matching parameters knowledge is a simple set of known and learned parameters 9/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - services service providers web services repository getCityCenter getCityDistrict locatePhone getLatLon getMap getWeather trafficInfo nearbyStreet 10/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - services, with parameter descriptions service providers web services input = { city, district } input = { city } repository getCityCenter getCityDistrict output = { lat, lon, altitude } output = { district } input = { phoneID } locatePhone output = { state, input = { lat, lon, input = { state, city } city, district } diameter } getLatLon getMap output = { lat, lon } output = { map } input = { state, city } input = { city, street } getWeather input = { city, lon, lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street, number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - parameters with the same name service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone output = { state , input = { lat , lon , input = { state , city } city , district } diameter } getLatLon getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - matching parameters service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone output = { state , input = { lat , lon , input = { state , city } city , district } diameter } getLatLon getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - matching parameters service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone output = { state , input = { lat , lon , input = { state , city } city , district } diameter } getLatLon getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - the request user composition service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict request output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone input = { phoneID, diameter } output = { state , getDrivingConditions input = { lat , lon , input = { state , city } city , district } diameter } output = { map, traffic, getLatLon weather } getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - request parameter matchings user composition service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict request output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone input = { phoneID , diameter } output = { state , getDrivingConditions input = { lat , lon , input = { state , city } city , district } diameter } output = { map , traffic , getLatLon weather } getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42

Automatic Web Service Composition - Models, Complexity and Applications Models and Complexity Name Matching Example - request parameter matchings user composition service providers web services input = { city , district } input = { city } repository getCityCenter getCityDistrict request output = { lat , lon , altitude } output = { district } input = { phoneID } locatePhone input = { phoneID , diameter } output = { state , getDrivingConditions input = { lat , lon , input = { state , city } city , district } diameter } output = { map , traffic , getLatLon weather } getMap output = { lat , lon } output = { map } input = { state , city } input = { city , street } getWeather input = { city , lon , lat } trafficInfo nearbyStreet output = { weather } output = { traffic } output = { street , number } 11/42