Availability of contents and services through technologies typical of the Web 2.0 philosophy such as RSS Feed, Atom, REST-WS, SOAP-WS, etc.
Availability of Telco services (e.g., phone calls, SMS messages, conference calls, etc) mainly due to Telecom Operators service exposure.
Availability of tools for the rapid development of convergent Composite Services (a.k.a. Mashups) that combine different resources such as Yahoo Pipes!, JackBe Presto, etc.
Such tools mainly support Data Mashups (i.e., those Mashups that combine data extracted by different sources), while they do not support Event Driven Mashups (i.e., those Mashups in which the basic components interact through events)
A reference model for the definition of Event Driven Mashups is proposed in this paper.
Web 2.0 Mashups: combination of data and services provided by means of technologies like RSS Feed, Atom, Web Services, etc. (for a complete list see the Programmable Web repository). Examples:
E-government info (e.g., closed roads, concerts, etc.) + Google Maps
Monitor RSS Feed + New Tweet on Twitter
Monitor Google Calendar + Send SMS
Enterprise Mashups: addressing the “Long Tail” 1 through combination of data and services belonging both to the private sphere of an Enterprise (e.g., the CRM system) and to the public Internet (e.g., the APIs listed in Programmable Web).
1 V. Hoyer, K. Stanoesvka-Slabeva, T. Janner, and C. Schroth. “Enterprise Mashups: Design Principles towards the Long Tail of User Needs.” In SCC '08: Proceedings of the 2008 IEEE International Conference on Services Computing, pages 601-602, Washington DC, USA.
The creation of a set of files called Facets that describes the new CSs.
The definition of the Composite Service logic by means of a graphical tool like the one showed in slide 4.
A CS is defined through a directed graph in which the blocks correspond to BS and the arrows to Event passing. This graph is saved in a repository when the creator presses the “save” button in the tool.
It is possible to define some assignments for each arrow.
The deployment of each CS:
is needed to make the new CS executable
needs the deployment of its facets and the parsing of the