Hi Matteo, Thanks very much for your explanations and guidelines. I think for the Composition Enablers it would be best to describe each of them in an own entry. However, I would recommend to use the term Enabler instead of Generic Enabler in the user interface of the catalog. Best regards, Torsten From: Matteo Melideo [mailto:matteo.melideo at eng.it] Sent: Dienstag, 24. Juli 2012 15:42 To: Leidig, Torsten Cc: Javier Soriano (FI-UPM); fiware-apps at lists.fi-ware.eu; Alvaro Arranz; Dalle Carbonare Davide; WP9_fi-ware Subject: Re: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue Hi Torsten, first of all thank you for this mail as this is a very valid approach to better explain the idea behind the catalogue. I also think that your explanation is very clear. However, I want to try to provide some additional clarifications apologising for the mail a bit long. You wrote: "You see a GE as a specific piece of code (or also a concrete instance exposing their services on certain endpoints?) that can be used by the developer to incorporate it within new applications." We deliberately decided to not provide constraints or boundaries to this as we know that each Chapter will offer their GEs in different ways. In this respect, I know that often I could talk nonsense in describing what a GE is (sorry about that) but my problem is that I cannot give an example "one size fits all". :-( But, being very pragmatic, I want to recall your text. Specifically, you wrote: 1) "a GE is a collection of generic functionalities, which can be accessed by a set of API (Open Specifications). Composition of services is such a generic functionality" --> agree 100% and if these open specifications are open then you can reference these in the GE "Download" section of the catalogue to be downloaded. Other info that can be added in the Download section are downloadable files which relate to the Generic Enabler, for example software libraries (if any), executable code (if any) or PDF-documents (if any). 2) if these API are available as services in the Testbed then you have to specify this in the GE "Instance" section of the Catalogue together with some additional info, for instance, on terms of use (if any). 3) in the Documentation "you write the juicy technical details directed to the coder who should use the GE. It should be detailed enough for a programmer to know how to e.g. include parameters in an API call etc. This can be achieved by linking to the Generic Enabler's architecture description and Open API, provided that they are detailed enough to serve this purpose. In the documentation part you are encouraged to link to downloadable libraries etc. that can make it easier for the developer to write code. Example code can also be written on this page." Then you wrote, .. " It now happens that we have 4 different implementations (different mechanisms, paradigms, technologies) for this GE." If this means that the same set of API mentioned before are implemented with four different approaches (i.e Mashup Composition, Data-driven Composition, Process-driven Composition and Semantic-driven Composition), this means that in the catalogue this will be reflected like that: - In the GE "Instances" section of the Catalogue, you will have to specify where the instances of the four different composition approaches are + info about the licence of use for each of these + Files which are only relevant for each specific instance. - In the GE "Download" section of the Catalogue,you will provide the open specification and (if available) you can add downloadable files which relate to the Generic Enabler, for example software libraries, executable code or PDF-documents. These files should be relevant for any instance of the GE. - in the GE "Documentation" section of the Catalogue you write the juicy technical details directed to the coder who should use each of the different composition tools. It should be detailed enough for a programmer to know how to e.g. include parameters in an API call etc. This can be achieved by linking to the Generic Enabler's architecture description and Open API, provided that they are detailed enough to serve this purpose. Example code can also be written on this page. The last option is that you can have GE Open Specification like the one you described (i.e. Composition of services) but the four different approaches that partially implement these open specifications. In this case my suggestion is the following: provide four different GEs entries in the Catalogue explaining briefly in each GE "Instance" section of the catalogue what part of the specifications are implemented recalling to the open specification document and more extensively in the Documentation section what part of the specifications have been implemented. I do not know if this clarify a bit more or, on the contrary, increases the confusion. However, this is to say that each WP Leader or Architects knows better than us how to sell and advertise the GEs belonging to their chapter in order to make them appealing and interesting for the potential stakeholders. In fact, as you may have noticed, we did not provide any sort of indication on what a GE is but just a place where to describe this in order to be exploited as better as possible. As you noticed I did not talk about what is a GEs (I am not the more appropriate person to do this and it is not important for me), what I know if that the UC projects want to use these GEs in their scenarios and want to have a unique, coherent and easy to navigate place where it is possible to browse the GEs and understand what these GEs are, where they are and how to use these. :-) Thanks again and best regards Matteo Il 24/07/2012 13:11, Leidig, Torsten ha scritto: Hi Matteo, I think there is still a lot of confusion. I hate to re- open the discussion what a GE actually is. For WP3 we more or less agreed, that a GE is a collection of generic functionalities, which can be accessed by a set of API (Open Specifications). Composition of services is such a generic functionality. It now happens that we have 4 different implementations (different mechanisms, paradigms, technologies) for this GE. On top of this very generic GE one can have specific GE, which reduces the options for the technologies and APIs. We haven't done this yet for the Composition but possible specific GE could be Mashup Composition, Data-driven Composition, Process-driven Composition, and Semantic-driven Composition. What we currently have is 4 different implementations of the GE made from assets of the individual partners. Some of them are only provided as a service (no code will be available for developers) some are Open Source and the code could be downloaded to run an own instance. I know other chapters (esp. Ch 9 ) has a slightly different view. You see a GE as a specific piece of code (or also a concrete instance exposing their services on certain endpoints?) that can be used by the developer to incorporate it within new applications. Therefore a sentence like "sell and advertise a GE" via the Catalog raises confusion. To make it very explicit: Should we make an entry in the catalog even if we provide only a service on demand and do not deliver any code or an instance in the Testbed infrastructure? Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prießnitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com<mailto:torsten.leidig 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. From: fiware-apps-bounces at lists.fi-ware.eu<mailto:fiware-apps-bounces at lists.fi-ware.eu> [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Matteo Melideo Sent: Dienstag, 24. Juli 2012 11:28 To: Javier Soriano (FI-UPM) Cc: fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>; Alvaro Arranz; Dalle Carbonare Davide Subject: Re: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue Dear Javier, sorry if I jump into the discussion but this is something me, as leader of the Wp9 should clarify. What a GE is will be up to each GE owner and each wp leader. If the Ericsson Composition Engine can be used a a stand alone application why not considering it a GE? If there is an instance of the engine running on the Testbed, why not considering this as a GE? It will be the GE providers (in line with the WP rule and policy) which should decide the strategy on what publish and how. The Catalogue is just a place where it is possible to sell and advertise about the GEs the PPP stakeholders and not only. In this respect, we suggested to publish before those GEs available on the Testbed and later the other just to be aligned with the Testbed and avoid giving false expectations. I hope this clarify Best Matteo Melideo Il 24/07/2012 11:14, Javier Soriano (FI-UPM) ha scritto: Dear Uwe, How can a GE (an abstract artefact) be available on the FIWARE Testbed? Am I wrong or is an instance of the GE (e.g. WireCloud Mashup Platform) and not the GE itself (e.g. Composition Editor GE) what have to be made available on the FIWARE Testbed? Who is/are the owner/s of both the Composition Editor GE and the Composition Execution Engine GE? Ericsson as Task leader? Sorry if I was wrong and should not have uploaded the descriptions :-( Best regards, Javier 2012/7/24 Riss, Uwe <uwe.riss at sap.com<mailto:uwe.riss at sap.com>> Dear Javier, I have checked the WPL/W PA minutes, which say that GE owners are expected to "submit description of GEs that will be available on the FI-WARE Testbed". That is the status. Best regards, Uwe From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es<mailto:jsoriano at fi.upm.es>] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>; Rafael Fernández; Alvaro Arranz Subject: IMPORTANT: About WP3 Composition GEs and the Catalogue Dear Uwe, Torsten, dear colleagues, Unfortunately, no one from UPM can attend today's conf call. We will any case catch up through the minutes. Nevertheless, we have some questions and concerns regarding a recent mail we've received (yesterday) from Osama Sammodi (from WP9). Osama asked us to provide in the FIWARE catalogue ( http://fi-ware.cloud.labs.ericsson.net/) information for the Composition Editor GE we are responsible for. Uwe, could you please include this matter in the agenda for today's conf call. End of July is a hard deadline to get it done. I think there is a general misunderstanding because most of the entries in the catalogue represents products (i.e. instances) instead of GEs on their own. For example, concerning WP3, Ericsson has already added the following entry: --- Ericsson Composition Engine<http://fi-ware.cloud.labs.ericsson.net/node/104> (http://fi-ware.cloud.labs.ericsson.net/node/104) The Ericsson Composition Engine is a toolset for creating and executing composed services and applications. It consists of a Composition Editor and an Execution Engine. --- Which clearly (at least for me) represents one instance of the Composition Execution Engine GE, but not the GE itself. Moreover, the description references the actual GEs that instance "implements": Composition Editor and Execution Engine. Am I wrong? The same occurs with other entries. For example: CEP GE refers to IBM technology: http://fi-ware.cloud.labs.ericsson.net/node/146 BigData Analysis refers to some components (SAMSON Platform, MongoDB, Apache HDFS): http://fi-ware.cloud.labs.ericsson.net/node/158 etc. The entries for "Service Description Repository" and "Marketplace", IMHO, are by far the best examples and reflect accurately the concept of GE. We should follow the same schema for the rest of GEs, shouldn't we? For the time being, in order progress in the matter, I have created two entries: Composition Editor<http://fi-ware.cloud.labs.ericsson.net/node/166> (http://fi-ware.cloud.labs.ericsson.net/node/166) UNPUBLISHED This Generic Enabler helps either the service provider or the end user (prosumer) to create composed services (from the back-end perspective) and application mashups (from the front-end perspective), respectively, in a graphical way APPLICATIONS/SERVICES ECOSYSTEMS AND DELIVERY FRAMEWORK Composition Execution Engine<http://fi-ware.cloud.labs.ericsson.net/node/170> (http://fi-ware.cloud.labs.ericsson.net/node/170) UNPUBLISHED Exposes and executes the composed services which result from using the Composition Editor Generic Enabler or are defined in a execution language supported by the tool APPLICATIONS/SERVICES ECOSYSTEMS AND DELIVERY FRAMEWORK Please find attached a doc with most of the content I've created for each entry. If you want to change or add anything, please let me know. For the time being, they are "under revision" and I'm not sure if you can edit my entries (to change the description of the GEs, to include new instances, etc.) or even see them. If necessary, I can share with you my credentials (user/password) I'm not sure about what is expected to be included in the "downloads" and the "documentation" sections: downloads/documentation regarding the GE? downloads/documentation regarding each instance? For example, in Ericsson Composition Engine<http://fi-ware.cloud.labs.ericsson.net/node/104> (http://fi-ware.cloud.labs.ericsson.net/node/104) Ericsson has included the "Ericsson Composition Engine, Advanced Composition Editor User's Guide", which refers to an instance of the Composition Execution Engine GE. Am I wrong? Best regards, Javier -- ************************************************ 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 ************************************************ --------------------- AVISO LEGAL: Este correo electrónico y cualquier documento adjunto contienen información confidencial destinada para ser leída exclusivamente por el destinatario. Su contenido no constituye un compromiso para la Universidad Politécnica de Madrid salvo ratificación escrita por ambas partes. Queda prohibida la reproducción, publicación, divulgación, total o parcial del mensaje así como el uso o reenvío no autorizado por el emisor. En caso de recibir el mensaje por error, se ruega su comunicación al remitente lo antes posible y su posterior eliminación. Gracias. DISCLAIMER: This e-mail and any attachments contain confidential information for the exclusive use of the recipient.Its contents do not constitute a commitment by Universidad Politécnica de Madrid except where provided for in a signed agreement between both parties. Any unauthorised disclosure, use, forwarding or dissemination, either whole or partial, is expressly prohibited. If you are not the intended recipient of the message, please notify the sender as soon as possible and delete it afterwards. Thank you. Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212<tel:%2B49%206227%207-70212> | F +49 6227 78-26158<tel:%2B49%206227%2078-26158> | M +49 151 16810936<tel:%2B49%20151%2016810936> | mailto: uwe.riss at sap.com<mailto:uwe.riss at sap.com> www.sap.com<http://www.sap.com/> Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdruecklich 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. -- ************************************************ 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 ************************************************ --------------------- AVISO LEGAL: Este correo electrónico y cualquier documento adjunto contienen información confidencial destinada para ser leída exclusivamente por el destinatario. Su contenido no constituye un compromiso para la Universidad Politécnica de Madrid salvo ratificación escrita por ambas partes. Queda prohibida la reproducción, publicación, divulgación, total o parcial del mensaje así como el uso o reenvío no autorizado por el emisor. En caso de recibir el mensaje por error, se ruega su comunicación al remitente lo antes posible y su posterior eliminación. Gracias. DISCLAIMER: This e-mail and any attachments contain confidential information for the exclusive use of the recipient.Its contents do not constitute a commitment by Universidad Politécnica de Madrid except where provided for in a signed agreement between both parties. Any unauthorised disclosure, use, forwarding or dissemination, either whole or partial, is expressly prohibited. If you are not the intended recipient of the message, please notify the sender as soon as possible and delete it afterwards. Thank you. _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-tools/attachments/20120725/94397758/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy