Cooperative service composition

Nikolay Mehandjiev, Freddy Lécué, Martin Carpenter, Fethi A. Rabhi

Research output: Chapter in Book/Report/Conference proceedingChapter

Abstract

Traditional service composition approaches are top-down(using domain knowledge to break-down the desired functionality), or bottom-up (using planning techniques). The former rely on available problem decomposition knowledge, whilst the latter rely on the availability of a known set of services, otherwise automatic composition has been considered impossible. We address this by proposing a third approach: Cooperative Service Composition (CSC),inspired by the way organisations come together in consortia to deliver services. CSC considers each service provider as proactive in service composition, and provides a semantics-based mechanism allowing innovative service compositions to emerge as result of providers' interactions. The key challenges we resolve are how to determine if a contribution brings the composition closer to its goal, and how to limit the number of possible solutions. In this paper we describe the approach and the solutions to the two key challenges, and demonstrate their application to the composition of financial web services. © 2012 Springer-Verlag Berlin Heidelberg.
Original languageEnglish
Title of host publicationLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)|Lect. Notes Comput. Sci.
PublisherSpringer Nature
Pages111-126
Number of pages15
Volume7328
DOIs
Publication statusPublished - 2012
Event24th International Conference on Advanced Information Systems Engineering, CAiSE 2012 - Gdansk
Duration: 1 Jul 2012 → …

Other

Other24th International Conference on Advanced Information Systems Engineering, CAiSE 2012
CityGdansk
Period1/07/12 → …

Keywords

  • semantic services
  • service composition
  • software agents

Fingerprint

Dive into the research topics of 'Cooperative service composition'. Together they form a unique fingerprint.

Cite this