Dear Andreas, dear Calin, dear all, We have been working on 2 scenarios related to mashups. We want to share them to facilitate discussion during our next confcall. The AggregatorCreatesMashup scenario is quite similar to our proposed ContractOfferedGadgets scenario (we prefer AggregatorCreatesMashup as a definitive name if both scenarios are consolidated in a single one), but we want to highlight the following differences (criticisms are welcome, of course): - Gadgets are linked to the services they use, but we consider it worth separating them from the pricing/contracting/selling/revenue point of view to increase the number of possible business models. For example, we want to allow users to buy a "navigation gadget" separately from the maps, real-time traffic information services, etc. the want to contract. This is why we allow the aggregator (e.g. being she the ulterior consumer of the mashup) to enter the "ContractOfferedServices" scenario for each gadget she wants to use in the mashup. Alternatively, the ContractOfferedServices could also be entered by the store during "contract gadget" if we want to make the process transparent to the user, or even can be entered by the gadget developer when she creates the gadget (i.e the dependency is "hard coded"). Most of the times, the "ContractOfferedServices" will be used in a simplified way, without the need to compose services, nor create/deploy/publish a composite service (only find/contract service tasks will be needed). - We consider it valuable to allow the aggregator to create a RSS Model for the mashup itself, starting from the RSS Models of the mashups, gadgets (and the underlying services) being used. - In a mashup scenario, the aggregator and the consumer roles are quite related and are usually performed by the same user (i.e. prosumer) and we consider it worth conveying this particularity in the scenario. Therefore, in our proposal, once the mashup is created, the aggregator has the choice to deploy the mashup or, on the contrary, she has the choice to deploy and use the mashup (adquiring then the "role of prosumer"). Both alternatives can occur simultaneously in a single scenario. - In our proposal, we distinguish between aggregator, application mashup editor and mashup execution engine to convey ideas such as that the mashup is created by wiring the gadgets, the configuration of the gadget includes operations such as resizing, locating, assigning it to a tab, etc. The "DevelopPublishGadget" scenario has been derived from the "Develop/Deploy/Publish" scenario sent by Andreas in a previous email (PPT slide). Look forward to hearing from you soon! Best regards, Javier 2011/8/23 Friesen, Andreas <andreas.friesen at sap.com>: > Dear All, > > > > please find attached 3 scenarios for consumer, provider and aggregator > showing the interaction between the roles of the composition and mashup and > the components of the business framework. > > > > T3.3 partners please review/comment/revise. > > > > T3.1 partners please take a look from the perspective of the composition and > mashup. Are the assumptions about the process flow for the > consumer/aggregator/provider correct? Please take a look at the service > consumer diagram. Service fulfillment task needs refinement! > > > > Here the link to the tool used to create the diagrams: > http://www.yworks.com/en/products_yed_about.html > > > > Please provide your comments until Thurday, EOB. > > > > Thanks and best regards, > > Andreas and Torsten > > > > Dr. Andreas Friesen > Research Program Manager Service Science > SAP Research Center Karlsruhe > SAP AG > Vincenz-Priessnitz-Strasse 1 > 76131 Karlsruhe, Germany > T + 49 6227 752 586 > F + 49 6227 78-43567 > M +49 171 8674630 > mailto:andreas.friesen at sap.com > http://www.sap.com > > Pflichtangaben/Mandatory Disclosure Statements: > http://www.sap.com/company/legal/impressum.epx > > Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige > vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich > erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine > Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte > benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen > Dank. > > This e-mail may contain trade secrets or privileged, undisclosed, or > otherwise confidential information. If you have received this e-mail in > error, you are hereby notified that any review, copying, or distribution of > it is strictly prohibited. Please inform us immediately and destroy the > original transmittal. Thank you for your cooperation. > > > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -- ***************************************** Dr. Javier Soriano Dept. Lenguajes y Sistemas Informáticos e Ingeniería de Software Facultad de Informática Universidad Politécnica de Madrid Campus de Montegancedo 28660 - Boadilla del Monte, Madrid Spain ***************************************** -------------- next part -------------- A non-text attachment was scrubbed... Name: ContractOfferedGadgets_v2.graphml Type: application/octet-stream Size: 85269 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110824/085798ac/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: ContractOfferedGadgets_v2.pdf Type: application/pdf Size: 650691 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110824/085798ac/attachment.pdf> -------------- next part -------------- A non-text attachment was scrubbed... Name: DevelopPublishGadget_v2.graphml Type: application/octet-stream Size: 30233 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110824/085798ac/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: DevelopPublishGadget_v2.pdf Type: application/pdf Size: 193077 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110824/085798ac/attachment-0001.pdf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy