Hey, This is our description of the service composition and publishing from the point of view of an aggregator. For illustration we describe an example - a bible service - which could be build as mashed application by a composition tool. The bible SMS service sends daily bible verses via SMS to a consumer. This is a commercially running service (in englisch e.g. http://dailybiblesms.com/eng/sms/bible/, in german e.g. http://www.ekd.de/bibel/bibel_sms.html). A prosumer creates this mashed application with the mashup factory combining specific web services like SMS, bible verses, time-controler, storage, user-management, etc. first for himself, and then for selling via a market. The SMS service is of special interest because it produces costs. Thus, in the Mashup factory the prosumer may choose between different SMS providers (e.g. ericsson labs https://labs.ericsson.com/apis/sms-send-and-receive/, Telefonicas https://bluevia.com/en/knowledge/APIs.API-Guides.SMS or Deutsche Telekoms SMS). The prosumer selects bluevias SMS, because bluevia has realised a revenue sharing mechanism for its APIs usage with 10% share per use ( https://bluevia.com/en/page/view/menupath/main.gotomarket.sell.businessModels, http://www.slideshare.net/bluevia/bluevia-business-models-developer-guide) The business related information about the SMS services is retrieved from the USDL repository or market place, the technical from the aggregators repository. After composing the mashed application, the prosumer tests the application in a sandbox with the execution engine. For a productization the prosumer has to contract the SMS service with bluevia (get a SMS commercialization ID), the revenue share module is informed about the SMS share of bluevia for the prosumer. Then he has to define a business model, e.g. subscription or pay per single bible verse, etc. This information is provided by the Business Model Enabler. For example: a subscription for one month is proposed. Then a price for the application is calculated by the pricing tool, e.g. 4 € per month. With that information the application can be published, i.e. it is deployed to the execution engine, described in USDL, exposed in the marketplace, where a consumer can find it. Best regards Horst ________________________________________________ Deutsche Telekom AG Laboratories Dr. Horst Stein Winterfeldtstrasse 21, D-10781 Berlin +49 30 835358637 (Tel) +49 391 53477987 +49 1605326264 (Mobil) http://www.laboratories.telekom.com E-Mail: horst.stein at telekom.de<mailto:horst.stein at telekom.de> Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: René Obermann (Vorsitzender), Hamid Akhavan, Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus Höttges, Guido Kerkhoff, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110825/93579c56/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ServiceComposition_DT_V1.pdf Type: application/pdf Size: 144283 bytes Desc: ServiceComposition_DT_V1.pdf URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110825/93579c56/attachment.pdf> -------------- next part -------------- A non-text attachment was scrubbed... Name: ServiceComposition_DT_V1.graphml Type: application/octet-stream Size: 62817 bytes Desc: ServiceComposition_DT_V1.graphml URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110825/93579c56/attachment.obj>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy