Hi, I see that Javier has supplied you with detailed info for the ashup editor/execution. Are we going to write 3 sections to that or we keep the generic? /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Javier Soriano (FI-UPM) Sent: den 21 november 2011 13:02 To: Heller, Markus Cc: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu); Fasse, Axel Subject: Re: [Fiware-apps] [Fiware-wpa] FW: URGENT: Slides for the review (status and more detailed template) --> Contribution WP3 Apps and Services Ecosystem and Delivery Framework Hi Markus, What follows is our (UPM's) input to the composition editor and the execution engine from the perspective of Application Mashups: (2) Composition Editor: * <what role it plays, major features>: The Application Mashup Editor allows end-users to mashup/compose service front-ends from GUI building blocks connecting to back-end services (also known as gadgets/widgets) in order to create their own composite applications. The Application Mashup Editor conforms the web-based composition editor that end-users utilize to create their mashup applications. It consists of a workspace where end-users can place gadgets coming from a catalogue in a spatial manner, a wiring tool to set the interconnection between gadgets, a piping tool to set the interconnection between gadgets and external services/data, and a catalogue/marketplace where end-users can access and look for the gadgets they need. * <what APIs will offer>: Gadget API to communicate with the execution engine * <relevant standards> EMML from the Open Mashup Alliance, Metadata 1.0 Specification and Mashup Security initiatives from the OpenAjax Alliance (3) Execution Engine: * <what role it plays, major features> The Mashup Execution Engine offers gadget interconnection, mashup state persistance, and cross-domain proxy facilities through an API to the mashup. The decentralized nature of mashups demands this execution engine to coordinate gadget execution and communication within the mashup. Thanks to the plugin API, extra functionality can be added to the execution engine as external modules, mainly security, publish/subscribe, or piping modules. * <what APIs will offer>: Gadget API to communicate with the gadgets executing in a mashup, including support for Pub/Sub, Plugin API to communicate with external modules, including support for Pub/Sub, Security and Piping * <relevant standards>: EMML from the Open Mashup Alliance, Metadata 1.0 Specification and Mashup Security initiatives from the OpenAjax Alliance And some input for the delivery channel: (1) Delivery Channel * <what role it plays, major features> § Creating a channel/device-specific user interface from a device/channel-independent definition language. § Storing and delivering specific data regarding capabilities, features, and constrains of all targeted devices and channels. § Using data from device description knowledge bases to adapt the user interface. § Handling the channel specific workflow and perform the backend invocations when necessary, redirecting to the adapted interface. § Rendering the specific channel user interface according to the Device & Channel Knowledge Base. § Rendering the specific device user interface according to the Device & Channel Knowledge Base and the targeted channel. * <what APIs will offer> TBD * <relevant standards> W3C's initiative DIAL Best regards, Javer 2011/11/21 Heller, Markus <markus.heller at sap.com<mailto:markus.heller at sap.com>> Dear WP3 partners, this is the second part of my TODO wish list now to a different set of colleagues that are asked to provide their input. I have attached a newer, minor version 0.5.2 of the PPT (Attachment) for your information with only slide 6 manipulated. This is a TODO for the owner of the components (1) Delivery Channel, (2) Composition Editor: (3) Execution Engine: (4)Mediation. Please fill in the text/data on Slide 6 for your mentioned components as soon as possible and send your contributions to me until 12:00 today: (1) Delivery Channel * <what role it plays, major features> * <what APIs will offer> * <relevant standards> (2) Composition Editor: * <what role it plays, major features> * <what APIs will offer> * <relevant standards> (3) Execution Engine: * <what role it plays, major features> * <what APIs will offer> * <relevant standards> (4) Mediation: * <what role it plays, major features> * <what APIs will offer> * <relevant standards> Please simply reply here - for your convenience - within this text email. I will combine the replied contributions into the PPT version and send an update to juanho along with other open points that need to be addressed today then later in the day. Best wishes Markus From: Heller, Markus Sent: Montag, 21. November 2011 10:31 To: 'fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>' (fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>) Cc: Bohnert, Thomas Michael; Friesen, Andreas; Leidig, Torsten; Fasse, Axel Subject: FW: [Fiware-wpa] FW: URGENT: Slides for the review (status and more detailed template) --> Contribution WP3 Apps and Services Ecosystem and Delivery Framework Dear WP3 partners, I have made demanded modifications to our WP3 review PPT. Current version 0.4 is in the Attachment. This is a TOD for the owners of components (1) BE&BM Provisioning, (2) Revenue Sharing System, (3) SLA MAnagement: Please fill in the text/data on Slide 4 (currently hidden) for your mentioned components as soon as possible and send your contributions to me until 12:00 today. * BE&BM Provisioning, * <what role it plays, major features> * <what APIs will offer> * <relevant standards> * Revenue Sharing: * <what role it plays, major featurest * <what APIs will offer> * <relevant standards> * SLA Management: * <what role it plays, major features> * <what APIs will offer> * <relevant standards> Please simply reply here - for your convenience - within this text email. I will combine the replied contributions into the PPT version and send an update to juanho along with other open points that need to be addressed today then later in the day. Best wishes Markus From: Heller, Markus Sent: Montag, 21. November 2011 10:23 To: jhierro at tid.es<mailto:jhierro at tid.es> Cc: 'fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>' (fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>); Bohnert, Thomas Michael; Friesen, Andreas; Leidig, Torsten; Fasse, Axel Subject: RE: [Fiware-wpa] FW: URGENT: Slides for the review (status and more detailed template) --> Contribution WP3 Apps and Services Ecosystem and Delivery Framework Dear Juanho, I have attached the current version of our WP3 PPT for your information. The current version is 0.4 (Attachment). Changes: - Your proposal to use the WP3 Motto : I included in the blue box with the mission statement beneath overview architecture (first slide) - I have added desired text for (SAP's) components added for Marketplace, Store, Registry, Repository - Revenue Sharing Engine removed as open call candidate (according to request from Pablo/TID) Open points: - We have to think what to do for the "zoom" slide proposed by you. - Text for the other framework components need to be filled in by WP3 partners. (see separate mail to WP3 mailing list). The partners will do this. - Your question "One thing I would like to doublecheck ... In the slide titled "Target features for the first release" we intend to mean "major release" ... was this your interpretation when you develop the slide ? Does it summarizes what UC projects will found in the FI-WARE testbed by end of July 2012 ? Just wanted to be sure ..." is NOT addressed yet, needs to be checked. We are working on the open points. A new update of the PPT may be done here later. Best wishes Markus From: fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu> [mailto:fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu>] On Behalf Of Juanjo Hierro Sent: Freitag, 18. November 2011 16:19 To: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Subject: Re: [Fiware-wpa] FW: URGENT: Slides for the review (status and more detailed template) --> Contribution WP3 Apps and Services Ecosystem and Delivery Framework Hi Torsten, Sounds like in a good shape for a first approach (minor things pending). Some comments: * Text missing in the slides dealing with zoom in of the architecture (Vision 2/3 and Vision 3/3). Maybe you need develop four slides where you have now two (two slides covering a fragment of current Vision 2/3 and two other covering a fragment of current Vision 3/3). I have tried to illustrate what I mean in the attached version ... * One thing I would like to doublecheck ... In the slide titled "Target features for the first release" we intend to mean "major release" ... was this your interpretation when you develop the slide ? Does it summarizes what UC projects will found in the FI-WARE testbed by end of July 2012 ? Just wanted to be sure ... Cheers, -- Juanjo On 18/11/11 15:35, Leidig, Torsten wrote: FYI From: Heller, Markus Sent: Freitag, 18. November 2011 15:31 To: jhierro at tid.es<mailto:jhierro at tid.es> Cc: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; Bohnert, Thomas Michael; Leidig, Torsten; Fasse, Axel Subject: RE: [Fiware-wpa] URGENT: Slides for the review (status and more detailed template) --> Contribution WP3 Apps and Services Ecosystem and Delivery Framework Dear Juanho, I have attached the review ppt contribution for the WP3 Apps and Services Ecosystem and Delivery Framework (second draft version). Please contact me or my colleagues with any questions. With best wishes Markus Heller Dr. Markus Heller Senior Researcher SAP RESEARCH Karlsruhe, Vincenz-Priessnitz-Str. 1, 76131 Karlsruhe , Germany T +49 6227 7-52673<tel:%2B49%206227%207-52673> Pflichtangaben/Mandatory Disclosure Statements: www.sap.com/corporate-en/impressum<http://www.sap.com/corporate-en/impressum> 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. From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Thursday, November 17, 2011 07:19 PM To: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> <fiware-wpl at lists.fi-ware.eu><mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> <fiware-wpa at lists.fi-ware.eu><mailto:fiware-wpa at lists.fi-ware.eu> Subject: [Fiware-wpa] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review <name-of-chapter> 11-11-<day>.ppt" * In Re: to this email Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu<mailto: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 -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20111121/b7837ecb/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy