Date Added: Jan 2012
Service composition tools are usually based on an input/output mapping pattern. Inputs and output are declared by the service developer when publishing his service. However, services might also generate unstructured data such as email and instant messages content. That data are hardly expectable by developers. Consequently, much data are unavoidably left out by current service composition tools. In this paper, the authors firstly propose and implement an enhancement to current SOA in order to facilitate capturing unstructured data. Secondly, they define and implement a new service composition pattern and tool in order to enable end-users to easily create Mashups based on structured and unstructured data (unstructured data are neither declared nor formatted by the service developer when publishing services).