E-services: a look behind the curtain
Proceedings of the twenty-second ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Automated Synthesis of Composite BPEL4WS Web Services
ICWS '05 Proceedings of the IEEE International Conference on Web Services
Specifying Data-Flow Requirements for the Automated Composition of Web Services
SEFM '06 Proceedings of the Fourth IEEE International Conference on Software Engineering and Formal Methods
Automated composition of web services by planning at the knowledge level
IJCAI'05 Proceedings of the 19th international joint conference on Artificial intelligence
A minimalist approach to semantic annotations for web processes compositions
ESWC'06 Proceedings of the 3rd European conference on The Semantic Web: research and applications
Towards semi-automated workflow-based aggregation of web services
ICSOC'05 Proceedings of the Third international conference on Service-Oriented Computing
Composition of services with nondeterministic observable behavior
ICSOC'05 Proceedings of the Third international conference on Service-Oriented Computing
Towards the composition of stateful and independent semantic web services
Proceedings of the 2008 ACM symposium on Applied computing
Automated composition of Web services via planning in asynchronous domains
Artificial Intelligence
Composing web services enacted by autonomous agents through agent-centric contract net protocol
Information and Software Technology
| Hi-index | 0.00 |
In this paper we compare two different approaches to specify data-flow requirements in Web service composition problems, i.e., requirements on data that are exchanged among component services. Implicit data-flow requirements are a set of rules that specify how the functions computed by the component services are to be combined by the composite service. They implicitly define the required constraints among exchanged data. Explicit data-flow requirements are a set of explicit specifications on how the composition should manipulate messages and route them from/to components. In the paper, we compare these two approaches through an experimental evaluation, both from the point of view of efficiency and scalability and from that of practical usability.