Dear T3.1 partners, we discussed today in the WP3 call the question: "What are generic enablers in T3.1?". I had now a very intensive discussion with Juanjo about this issue and hope that you will perceive the outcome of this discussion as (hopefully) good news. WP3 will provide the business framework infrastructure as a generic enabler to monetize different types of apps/services and their compositions. We believe that it cannot be a responsibility or obligation of FI-WARE (or any other entity) to say what is the best technology for a certain type of composition or mashup so that it would be a major mistake to specify a set of generic enablers prescribing to the outside world an interface or infrastructure to implement a certain composition or mashup capability. Hence, the aim of T3.1 is to develop a rich set of technologies exemplary implementing different types of service and apps compositions and mashups and demonstrating their integration with the business framework. Now the practical advice :): Start the description of T3.1 with a high-level architecture showing the main building blocks of the Aggregator and Mediator and the relationships to other roles within and outside WP3 and describe them. Provide a classification of composition and mashup technologies you collectively intend to contribute to T3.1 (front-end, back-end, WS-based, data/process mashups, event-based, workflow-based, etc. try to find a meaningful classification scheme, the description in DoW could be a good starting point). Make the following statement: "It is not the intention of FI-WARE neither to prescribe nor to prevent use of specific techniques, technologies, standards, engines or development environments. We intend to provide to the user of the FI-WARE platform a choice from a rich set of different composition and mashup technologies demonstrating integration with the business framework. We are open to new technologies and will offer a guideline if a company wishes to integrate its technology with the FI-WARE business framework. The architectures and functional capabilities of the services and apps composition technologies we aim to contribute as part of the platform are described in the following subsections Describe the architectures and purpose of your systems (the already available example from DT is perhaps a good starting point)... I hope this helps to generate the first drafts until next Wednesday. Best regards, Andreas 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20110610/321127c1/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy