From uwe.riss at sap.com Tue Jul 3 20:01:42 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 3 Jul 2012 20:01:42 +0200 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782046BF713030@DEWDFECCR02.wdf.sap.corp> Dear WP3 Colleagues, Please find the access to the minutes of today's conf call here: https://forge.fi-ware.eu/docman/view.php/12/1148/2012-07-03-FI-WARE_Minutes.docx The FI-WARE Apps wiki page for our planning can be found here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/apps/index.php/Main_Page Please check whether you appear in the participant list and whether the minutes are complete. Best regards, Uwe 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed Jul 4 11:30:04 2012 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 4 Jul 2012 11:30:04 +0200 Subject: [Fiware-apps] FW: [Fiware-testbed] Administrative IPs Range Specification In-Reply-To: <6B70AA768BE8401A97D960FC93568A13@FSC461216100407> References: <6B70AA768BE8401A97D960FC93568A13@FSC461216100407> Message-ID: Dear colleagues, Please provide the needed information as mentioned by Paolo by the end of this week. Any questions? Don't hesitate to ask. Thanks, /Thorsten From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Paolo Zampognaro Sent: Mittwoch, 4. Juli 2012 11:27 To: fiware-testbed at lists.fi-ware.eu Subject: [Fiware-testbed] Administrative IPs Range Specification Importance: High Hi All, this mail to inform all chapter representatives, inside WP10, about a pending action for them. They should ask each GE owner, inside their specific chapter, to provide the IPs address range they want to exploit to access the Testbed (the VM which will contain the GE) for administrative purposes (installation/managing etc...) How to Each GE owner has to put such information by (i) accessing the cockpit implementation page [1] and (ii) by filling the "IP range for administrative access (please specify company network W.X.Y.Z/32, ...)" field of the form associated to its GE. Deadline It is needed to complete such activity by the end of this week at most. Please don't hesitate to contact the Testbed team for clarification about this really critical action. Cheers, Paolo [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit Ing. Paolo Zampognaro Software Engineer Direzione Centrale Ricerca & Innovazione paolo.zampognaro at eng.it Engineering Ingegneria Informatica spa Via Gianturco, 15 - 80146 Napoli Tel. +39-081.6103524 Mob. +39-3451227587 Fax. +39-081.6103200 www.eng.it -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jsoriano at fi.upm.es Thu Jul 5 19:26:42 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Thu, 5 Jul 2012 19:26:42 +0200 Subject: [Fiware-apps] OUTSMART / FI-WARE synchronization In-Reply-To: <5255_1341491759_4FF58A2F_5255_9893_1_2f564782-7708-4c91-8f36-6f5879cd19ec@PEXCVZYH02.corporate.adroot.infra.ftgroup> References: <5255_1341491759_4FF58A2F_5255_9893_1_2f564782-7708-4c91-8f36-6f5879cd19ec@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: Dear Fano, I've removed the rest of recipients to avoid overwhelming their mailbox with specific expressions of interest. Please feel free to forward my email to any potentially interested colleague. Thank you very much for showing interest in WireCloud during the FIWARE educational sessions, and for taking the initiative with this email. At least two additional projects showed interest in the platform, including Finest, so we are very excited about starting our collaboration. We've been working hard during last months to change the architecture of the platform and its interfaces, so as to ease its integration with FIWARE GEs (USDL, marketplace, store, repository and even the Pub/Sub broker) and to align it with the specification of the composition editor and execution GEs. We've also tried to make the most of this effort (and opportunity) by introducing some major updates to the platform itself. We've changed the metaphor used for wiring and piping (i.e. the wiring editor) and we've developed a pub-sub broker that can be plugged in the platform and used through its javascript pub-sub API in order to easily develop event-driven widgets and mashups. This is why we've postponed the launch of the "sandbox" deployment and test accounts we promised during the meetings. The preparation of the first year review of FIWARE also helped to increase the delay :-( Nevertheless, we're about to release an almost stable version of the platform. We plan to deliver that almost stable version by July the 20th, and the next release of the platform by August the 1st, with many improvements in usability (live tutorials on how to create a mashup by wiring and piping widgets and operators, a -still quite small- catalogue of generic, fully-documented widgets and operators, as well as some pre-built mashups, etc.). Please follow us in http://conwet.fi.upm.es/wirecloud/ and let me get back to you in a few days with more information about those test accounts. Besides, we will try to attend the confcall next week and follow the proposed process. In the mean time, we could start working together in the definition of a simple scenario in which Wirecloud can be useful to deliver some functionality of Outsmart to its end users. WireCloud (like any other composition tool, or even more, bearing in mind it targets end users) is of little use without a catalogue of widgets and operators that can be considered useful for those users. Some can be considered generic (maps, statistical graphs, etc.) but most of them need to be considered specific for a given domain or project. Do you have any information that could serve us for this purpose or, even better, can you imagine a simple scenario where the Outsmart end user could be empowered by allowing her to pick some widgets and operators from a catalogue and mash-up them to obtain a useful information or control dashboard in the context of the Outsmart project. It could even be a good idea to consider such scenario in the context of FIWARE WP3's releases. Let me check with WP3 leader (SAP). Best regards, Javier 2012/7/5 > Dear FI-WARE-ior and OUTSMART-er,**** > > ** ** > > The OUTSMART project will shorty be engaged in the development of its PoC > and thus, would like to maximize the benefit of using the FIWARE CP. **** > > Through the FIWARE documentation and the two FIPPP architecture weeks > (FIWARE educational sessions) we came up with a set of FIWARE GEs that we > believe are quite relevant to our project.**** > > ** ** > > You were identified as the "official contact" of at least one GE (*) and > would like to invite you to a short confcall next week in order to > establish a first contact and to establish and initiate a mode of > collaboration between our two projects on this issue. **** > > ** ** > > We would like to propose a 2 phases process:**** > > - up until end of august mail/phone discussions focussing on specific GE > or FIWARE chapters, for the OUTSMART team to better know the FIWARE GEs > features and their roadmaps, and for the FIWARE team to understand better > the OUTSMART requirements.**** > > - beginning of september a joint physical meeting for reviewing the > OUTSMART architecture and evaluating how well the FIWARE CP cover it. **** > > ** ** > > for this first confcall, could you please enter your availability in the > following doodle before tomorrow (friday) noon.:**** > > http://www.doodle.com/z9bwyxw5nudxn4tn**** > > The definitive date will be set on friday afternoon.**** > > ** ** > > Thank you very much in advance for your cooperation,**** > > ** ** > > Fano Ramparany**** > > ** ** > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > -- ************************************************ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Fri Jul 6 11:58:49 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Fri, 6 Jul 2012 11:58:49 +0200 Subject: [Fiware-apps] Deadlines for deliverables Message-ID: Dear WP 3 partners, There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Fri Jul 6 16:56:32 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Fri, 6 Jul 2012 16:56:32 +0200 Subject: [Fiware-apps] Deadlines for deliverables In-Reply-To: References: Message-ID: <84DE6B7638096349804AC8EC332FE124567723C899@ESESSCMS0361.eemea.ericsson.se> Hi Torsten, User Guide and Installation deliverables updates, Unit Testing plan still pending. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: den 6 juli 2012 11:59 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] Deadlines for deliverables Dear WP 3 partners, There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.ughetti at telecomitalia.it Fri Jul 6 16:57:11 2012 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Fri, 6 Jul 2012 16:57:11 +0200 Subject: [Fiware-apps] R: Deadlines for deliverables In-Reply-To: <84DE6B7638096349804AC8EC332FE124567723C899@ESESSCMS0361.eemea.ericsson.se> References: , <84DE6B7638096349804AC8EC332FE124567723C899@ESESSCMS0361.eemea.ericsson.se> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A53846903C148C@GRFMBX707BA020.griffon.local> Hi all, I have updated Mediator deliverables Even in my case Unit Test is still in progress Marco ________________________________________ Da: fiware-apps-bounces at lists.fi-ware.eu [fiware-apps-bounces at lists.fi-ware.eu] per conto di Calin Curescu [calin.curescu at ericsson.com] Inviato: venerd? 6 luglio 2012 16.56 A: Leidig, Torsten; fiware-apps at lists.fi-ware.eu Oggetto: Re: [Fiware-apps] Deadlines for deliverables Hi Torsten, User Guide and Installation deliverables updates, Unit Testing plan still pending. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Leidig, Torsten Sent: den 6 juli 2012 11:59 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] Deadlines for deliverables Dear WP 3 partners, iv> There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From thorsten.sandfuchs at sap.com Tue Jul 10 08:49:04 2012 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 10 Jul 2012 08:49:04 +0200 Subject: [Fiware-apps] FI-WARE WP3 Call In-Reply-To: References: Message-ID: Dear colleagues, due to the absense of Torsten and Uwe, we have to unfortunately CANCEL this telephone conference. AFAIK next conference will be in one week. If you have any urgent questions or requests, don't hesitate to approach Torsten via email. Thanks in advance & best regards, /Thorsten -----Original Appointment----- From: Riss, Uwe Sent: Dienstag, 20. M?rz 2012 11:25 To: Riss, Uwe; 'fiware-apps at lists.fi-ware.eu'; Fasse, Axel; Klein, Andreas; 'Ronco Enrico'; Sandfuchs, Thorsten; 'matteo.melideo at eng.it'; Magerkurth, Carsten; 'Froese, Andreas'; 'miguel.huerta at atos.net'; 'Calin Curescu'; 'Jonischkat, Tim'; Leidig, Torsten Subject: FI-WARE WP3 Call When: Dienstag, 10. Juli 2012 10:00-11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_apps When: Occurs every Dienstag effective 27.03.2012 until 31.12.2012 from 10:00 to 11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_apps Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear WP3 Partners, I'd like to invite you to the next FI-WARE Apps calls, regularly on Tuesday. I will send the agenda separately. I have corrected the link in the subject now. Best regards, Uwe To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_apps Participant Passcode: 656 085 0596 Austria, Vienna: +43 1 2530 21750 tel:+431253021750,,6560850596# Belgium, Brussels: +32 2 404 0657 tel:+3224040657,,6560850596# Czech Republic, Prague: +420 228 882 890 tel:+420228882890,,6560850596# Denmark, Copenhagen: +45 32 71 16 49 tel:+4532711649,,6560850596# Estonia, Tallinn: +372 622 6444 tel:+3726226444,,6560850596# Finland, Helsinki: +358 9 2310 1631 tel:+358923101631,,6560850596# France, Paris: +33 1 70 70 17 77 tel:+33170701777,,6560850596# Germany, Frankfurt: +49 69 2222 10764 tel:+4969222210764,,6560850596# Germany, Munich: +49 89 7104 24682 tel:+4989710424682,,6560850596# Greece, Athens: +30 21 1181 3805 tel:+302111813805,,6560850596# Hungary, Budapest: +36 1 778 9215 tel:+3617789215,,6560850596# Ireland, Dublin: +353 1 247 6192 tel:+35312476192,,6560850596# Israel, Tel Aviv: +972 3 763 0750 tel:+97237630750,,6560850596# Italy, Milan: +39 02 3600 9839 tel:+390236009839,,6560850596# Italy, Rome: +39 06 4523 6623 tel:+390645236623,,6560850596# Latvia, Riga: +371 6778 2556 tel:+37167782556,,6560850596# Lithuania, Vilnius: +370 5205 5165 tel:+37052055165,,6560850596# Luxembourg: +352 2487 1454 tel:+35224871454,,6560850596# Netherlands, Amsterdam: +31 20 716 8291 tel:+31207168291,,6560850596# Norway, Oslo: +47 21 50 27 61 tel:+4721502761,,6560850596# Poland, Warsaw: +48 22 212 0699 tel:+48222120699,,6560850596# Portugal, Lisbon: +351 21 781 0275 tel:+351217810275,,6560850596# Romania, Bucharest: +40 21 529 3917 tel:+40215293917,,6560850596# Slovakia, Bratislava: +421 2 3300 2610 tel:+421233002610,,6560850596# Slovenia, Ljubljana: +386 1 888 8261 tel:+38618888261,,6560850596# Spain, Barcelona: +34 93 800 0782 tel:+34938000782,,6560850596# Spain, Madrid: +34 91 769 9443 tel:+34917699443,,6560850596# Sweden, Stockholm: +46 8 5033 6514 tel:+46850336514,,6560850596# Switzerland, Geneva: +41 22 592 7995 tel:+41225927995,,6560850596# Switzerland, Zurich: +41 43 456 9248 tel:+41434569248,,6560850596# UK, London: +44 20 3364 5639 tel:+442033645639,,6560850596# US and Canada: 1-866-312-7353 tel:18663127353,,6560850596# Adobe Connectivity Test: https://admin.acrobat.com/common/help/en/support/meeting_test.htm Phone Type: Please note countries listed with a city are local access, all others are International Toll Free. If you need assistance, please contact Premiere Global Services support via this link: https://sap.support.pgiconnect.com/marketing/contacts.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jul 10 13:12:56 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 10 Jul 2012 13:12:56 +0200 Subject: [Fiware-apps] FW: FW: Re: FI-WARE WP3 Call In-Reply-To: <2C6296E1876B5C49962495FDACDC7A63616509F056@DEWDFECCR01.wdf.sap.corp> References: , <2C6296E1876B5C49962495FDACDC7A63616509F056@DEWDFECCR01.wdf.sap.corp> Message-ID: Dear WP3 participants, please read the quoted mail from Miguel according to the deadlines for the deliverables. Many of the Wiki pages for Unit Tests, Programmers Guide, User Manual and Administration Guide are already there in a first version. For the remaining ones I would like to add the following instructions: * please provide any input for each of the deliverables. Even if you don't think you can or have to provide information, write a notice ore explaination, W H Y you do not provide more specific descriptions. * For the Unit Tests, refer to the guidlines on how to include the Unit Test descriptions into the "Materialzing the FI-WARE Vision" page! I don't know why the tests are not described in the same way as the other deliverables but that's how it is. Additionally it is expected from you to 1. work on the reviewer comments from M9 review regarding the Archtecture (please send me a notice if you feel you've done this, together with a reference to the changed content) 2. We have to provide more elaborated content according to the Exploitation, Dissemination and Standardisation reports. 3. Your input is expected according to the report on "Third party innovation". Instructions will follow. Best 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 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. ________________________________________ Von: Miguel Carrillo [mailto:mcp at tid.es] Gesendet: Tuesday, July 10, 2012 08:56 AM An: Sandfuchs, Thorsten; Fasse, Axel Betreff: Re: [Fiware-apps] FI-WARE WP3 Call Dear Thorsten and Axel, Yesterday there was a WPL/WPA confcall that was attended by Axel. In this confcall it was a clear statement that we expect to close deliverables by July, 23. Failing to meet the deadline would result in penalties in the reporting of the involved partner (i.e. losing money). Sending out this message is urgent. Are the WP3 partners informed? It is pretty obvious that this has to be communicated right away and that it cannot wait for one week. BR miguel El 10/07/2012 8:49, Sandfuchs, Thorsten escribi?: Dear colleagues, due to the absense of Torsten and Uwe, we have to unfortunately CANCEL this telephone conference. AFAIK next conference will be in one week. If you have any urgent questions or requests, don?t hesitate to approach Torsten via email. Thanks in advance & best regards, /Thorsten -----Original Appointment----- From: Riss, Uwe Sent: Dienstag, 20. M?rz 2012 11:25 To: Riss, Uwe; 'fiware-apps at lists.fi-ware.eu'; Fasse, Axel; Klein, Andreas; 'Ronco Enrico'; Sandfuchs, Thorsten; 'matteo.melideo at eng.it'; Magerkurth, Carsten; 'Froese, Andreas'; 'miguel.huerta at atos.net'; 'Calin Curescu'; 'Jonischkat, Tim'; Leidig, Torsten Subject: FI-WARE WP3 Call When: Dienstag, 10. Juli 2012 10:00-11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_apps When: Occurs every Dienstag effective 27.03.2012 until 31.12.2012 from 10:00 to 11:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: https://sap.emea.pgiconnect.com/fi-ware_apps Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear WP3 Partners, I?d like to invite you to the next FI-WARE Apps calls, regularly on Tuesday. I will send the agenda separately. I have corrected the link in the subject now. Best regards, Uwe To join the meeting: https://sap.emea.pgiconnect.com/fi-ware_apps Participant Passcode: 656 085 0596 Austria, Vienna: +43 1 2530 21750 tel:+431253021750,,6560850596# Belgium, Brussels: +32 2 404 0657 tel:+3224040657,,6560850596# Czech Republic, Prague: +420 228 882 890 tel:+420228882890,,6560850596# Denmark, Copenhagen: +45 32 71 16 49 tel:+4532711649,,6560850596# Estonia, Tallinn: +372 622 6444 tel:+3726226444,,6560850596# Finland, Helsinki: +358 9 2310 1631 tel:+358923101631,,6560850596# France, Paris: +33 1 70 70 17 77 tel:+33170701777,,6560850596# Germany, Frankfurt: +49 69 2222 10764 tel:+4969222210764,,6560850596# Germany, Munich: +49 89 7104 24682 tel:+4989710424682,,6560850596# Greece, Athens: +30 21 1181 3805 tel:+302111813805,,6560850596# Hungary, Budapest: +36 1 778 9215 tel:+3617789215,,6560850596# Ireland, Dublin: +353 1 247 6192 tel:+35312476192,,6560850596# Israel, Tel Aviv: +972 3 763 0750 tel:+97237630750,,6560850596# Italy, Milan: +39 02 3600 9839 tel:+390236009839,,6560850596# Italy, Rome: +39 06 4523 6623 tel:+390645236623,,6560850596# Latvia, Riga: +371 6778 2556 tel:+37167782556,,6560850596# Lithuania, Vilnius: +370 5205 5165 tel:+37052055165,,6560850596# Luxembourg: +352 2487 1454 tel:+35224871454,,6560850596# Netherlands, Amsterdam: +31 20 716 8291 tel:+31207168291,,6560850596# Norway, Oslo: +47 21 50 27 61 tel:+4721502761,,6560850596# Poland, Warsaw: +48 22 212 0699 tel:+48222120699,,6560850596# Portugal, Lisbon: +351 21 781 0275 tel:+351217810275,,6560850596# Romania, Bucharest: +40 21 529 3917 tel:+40215293917,,6560850596# Slovakia, Bratislava: +421 2 3300 2610 tel:+421233002610,,6560850596# Slovenia, Ljubljana: +386 1 888 8261 tel:+38618888261,,6560850596# Spain, Barcelona: +34 93 800 0782 tel:+34938000782,,6560850596# Spain, Madrid: +34 91 769 9443 tel:+34917699443,,6560850596# Sweden, Stockholm: +46 8 5033 6514 tel:+46850336514,,6560850596# Switzerland, Geneva: +41 22 592 7995 tel:+41225927995,,6560850596# Switzerland, Zurich: +41 43 456 9248 tel:+41434569248,,6560850596# UK, London: +44 20 3364 5639 tel:+442033645639,,6560850596# US and Canada: 1-866-312-7353 tel:18663127353,,6560850596# Adobe Connectivity Test: https://admin.acrobat.com/common/help/en/support/meeting_test.htm Phone Type: Please note countries listed with a city are local access, all others are International Toll Free. If you need assistance, please contact Premiere Global Services support via this link: https://sap.support.pgiconnect.com/marketing/contacts.html -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 From torsten.leidig at sap.com Wed Jul 11 09:09:41 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 11 Jul 2012 09:09:41 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE In-Reply-To: <4FFD15BF.4030105@tid.es> References: <4FFD15BF.4030105@tid.es> Message-ID: From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 11. Juli 2012 07:57 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE Hi all, Just to make sure where the Epics linked to topics you wish to incorporate in the 2nd Open Call are available in the Materializing the FI-WARE Vision part of the wiki ... I can find the ones linked to the Cloud Proxy: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit Regarding Security, I understand that we are referring to the two following Epics: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack I was expecting the description of the Security Epics a bit more concrete ... Note that they should provide enough detailed information as to make sure that submitters really make proposals along the lines of what we are expecting ... Do you think that such need would be covered with the provided descriptions ? Initially, unless changed during approval of the agenda (first thing this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am until 11:15am ... this gives you a last change to incorporate further refinements. I would also like to check whether you would be available for joining the FI-PPP AB and elaborate on the topics if needed (we would have to find out how, depending on the facilities provided by the host of this meeting) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jsoriano at fi.upm.es Wed Jul 11 12:15:34 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 11 Jul 2012 12:15:34 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE In-Reply-To: References: <4FFD15BF.4030105@tid.es> Message-ID: Hi torsten, Am I wrong or the Epics linked to our topics (Multi-channel and Multidevice Access System) are missing? Best regards, Javier 2012/7/11 Leidig, Torsten > ** ** > > ** ** > > *From:* fiware-wpa-bounces at lists.fi-ware.eu [mailto: > fiware-wpa-bounces at lists.fi-ware.eu] *On Behalf Of *Juanjo Hierro > *Sent:* Mittwoch, 11. Juli 2012 07:57 > *To:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > *Subject:* [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be > proposed by FI-WARE**** > > ** ** > > Hi all, > > Just to make sure where the Epics linked to topics you wish to > incorporate in the 2nd Open Call are available in the Materializing the > FI-WARE Vision part of the wiki ... > > I can find the ones linked to the Cloud Proxy: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit > > Regarding Security, I understand that we are referring to the two > following Epics:**** > > - > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence > **** > - > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack > **** > > > I was expecting the description of the Security Epics a bit more > concrete ... Note that they should provide enough detailed information as > to make sure that submitters really make proposals along the lines of what > we are expecting ... Do you think that such need would be covered with the > provided descriptions ? > > Initially, unless changed during approval of the agenda (first thing > this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am > until 11:15am ... this gives you a last change to incorporate further > refinements. I would also like to check whether you would be available > for joining the FI-PPP AB and elaborate on the topics if needed (we would > have to find out how, depending on the facilities provided by the host of > this meeting) > > Cheers, > > > **** > > -- Juanjo**** > > ** ** > > -------------**** > > Product Development and Innovation (PDI) - Telefonica Digital**** > > website: www.tid.es**** > > email: jhierro at tid.es**** > > twitter: twitter.com/JuanjoHierro**** > > ** ** > > FI-WARE (European Future Internet Core Platform) Chief Architect**** > > ** ** > > You can follow FI-WARE at:**** > > website: http://www.fi-ware.eu**** > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242**** > > twitter: http://twitter.com/FIware**** > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932**** > > ** ** > ------------------------------ > > > 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 > 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Wed Jul 11 12:37:41 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 11 Jul 2012 12:37:41 +0200 Subject: [Fiware-apps] [Fiware-wpl] URGENT REMINDER: Topics for 2nd Open Call In-Reply-To: References: <4FD74956.7070806@tid.es> <1491C91A94302A448D73CD9C6B7A782046BC483865@DEWDFECCR02.wdf.sap.corp> Message-ID: Hi again Torsten, This is the chain of emails we sent to Juanjo Hierro regarding the preparation of the 2nd open call, where you can find the Epics we proposed (attached is a doc with detailed information). Best regards, Javier 2012/6/13 Javier Soriano (FI-UPM) > Dear Juanjo, dear all, > > Please find attached a doc with an updated description of the topic and of > its two associated EPICs. We've done our best to cover the UC requirements > expressed as EPICs in the backlog, which IMHO can not be considered EPICs > for themselves. Nevertheless, please feel free to take them back again into > consideration when needed. > > When doing so, we have also found and considered these other EPICs defined > by the UC projects (most of them can not be found in the tracker, but in > the wiki at > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Unclassified_Enablers > ): > > > FIContent.Epic.Applications.MultiChannelMultiDeviceAccessForMobileVideo > ** > > The recording and the distribution of the videos should be possible for > different channels and devices. Especially mobile devices should be > supported. The network should support the transmission of multiple videos. > Up to 50 streams should be sent over the network without any significant > delay. Streaming is not addressed in the existing > Multi-channel/Multi-device Access System enabler. > > FIContent.Epic.ContentAdaptation -- > Provide a better interaction with Social Networks. Contents can be > generated by a large range of devices. The user must be able to upload all > of them (whatever their format, size, etc.) to any Social Network. The > reading of those contents on the Social Networks must be optimal. > > SMARTAGRIFOOD.Epic.Apps.Multi-channel/Multi-device Access > System.SeamlessTransition > > > #1505 > SMARTAGRIFOOD.Epic.apps.MultiChannelMultiDeviceAccessSystem.DevicesOnTheFly > which is a refinement of the previous one. > > > I think we now have an almost complete picture of the topic and of its > associated EPICs, including those reflecting requirements from the UC > projects. Nevertheless, do not hesitate to contact us if you need further > information. > > Looking forward to hearing from you soon. > > Best regards, > Javier > > 2012/6/13 Riss, Uwe > >> Dear Juanjo,**** >> >> ** ** >> >> Javier, Rafael, Miguel, Calin, and I just had a conf call on the EPICS >> for this 2nd Open Call to cover the issues of *WP3 T3.4 Multi-channel & >> multi-device delivery and access* that we want suggest as topic of the 2 >> nd Open Call. The particular EPICS that are related to this task in the >> FI-WARE APPS tracker are:**** >> >> ** ** >> >> **? **#909: >> FIWARE.EPIC.Apps.MultiChannel-Device.MultiDeviceAccess >> **** >> >> **? **#910: >> FIWARE.EPIC.Apps.MultiChannel-Device.MultiChannelAccess >> **** >> >> ** ** >> >> The topic also concerns the following EPICS defined by the UC projects in >> the FI-WARE tracker:**** >> >> ** ** >> >> **? **#301: >> SMARTAGRIFOOD.Epic.Apps.MultiChannelAccessSystem.PlatformIndependence >> **** >> >> **? **#302: >> SMARTAGRIFOOD.Epic.Apps.MultiChannelAccessSystem.ProvisionToUserWithUpToDateCertification >> **** >> >> **? **#375: >> SMARTAGRIFOOD.Epic.apps.MultiChannelMultiDeviceAccessSystem.Visualization >> **** >> >> ** ** >> >> However, as I remember correctly form the Educational Sessions, there >> were also other projects interested in this task, for which there are >> unfortunately no EPICS in the backlog.**** >> >> ** ** >> >> Miguel is currently working on an update of the FI-WARE Epics to cover >> the UC requirements but should have completed this within the next 2 hours >> so that you have the current state.**** >> >> ** ** >> >> Best regards,**** >> >> Uwe**** >> >> ** ** >> >> PS If you have further immediate questions please contact Javier or >> Miguel directly since I am not in the office for the next few hours.**** >> >> ** ** >> >> ** ** >> >> *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 | F +49 6227 78-26158 | M +49 151 16810936 >> | mailto: uwe.riss at sap.com **** >> >> 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.**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> ** ** >> >> -----Original Message----- >> From: fiware-wpl-bounces at lists.fi-ware.eu [mailto: >> fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro >> Sent: Dienstag, 12. Juni 2012 15:51 >> To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu >> Subject: [Fiware-wpl] URGENT REMINDER: Topics for 2nd Open Call**** >> >> ** ** >> >> Hi,**** >> >> ** ** >> >> This is a reminder that this Thursday, June 14th, we have a virtual*** >> * >> >> meeting of the FI-PPP AB. One of the hot topics for that confcall will* >> *** >> >> be the selection of topics for the FI-WARE 2nd Open Call. In this**** >> >> respect, it was agreed that only those topics for which a 1st draft of*** >> * >> >> Epics is ready by June 14th, will be considered for this 2nd Open Call.** >> ** >> >> ** ** >> >> During the last FI-PPP AB meeting, I announced that FI-WARE were**** >> >> preparing some topics that we wanted to include in this 2nd Open Call.*** >> * >> >> ** ** >> >> I would kindly ask those chapters that had plans to include a topic*** >> * >> >> for the 2nd Open Call to send me an email summarizing the status.**** >> >> Again, I would like to emphasize that no draft of Epics by June 14th,**** >> >> will mean not getting in the 2nd Open Call.**** >> >> ** ** >> >> Best regards,**** >> >> ** ** >> >> -- Juanjo**** >> >> ** ** >> >> -------------**** >> >> Product Development and Innovation (PDI) - Telefonica Digital**** >> >> website: www.tid.es**** >> >> email: jhierro at tid.es**** >> >> twitter: twitter.com/JuanjoHierro**** >> >> ** ** >> >> FI-WARE (European Future Internet Core Platform) Chief Architect**** >> >> ** ** >> >> You can follow FI-WARE at:**** >> >> website: http://www.fi-ware.eu**** >> >> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242**** >> >> twitter: http://twitter.com/FIware**** >> >> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932**** >> >> ** ** >> >> ** ** >> >> ________________________________**** >> >> ** ** >> >> 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-wpl mailing list**** >> >> Fiware-wpl at lists.fi-ware.eu**** >> >> http://lists.fi-ware.eu/listinfo/fiware-wpl**** >> > > > > -- > ************************************************ > 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE2ndOpenCall-Multi-channelMulti-DeviceAccessSystem (1).doc Type: application/msword Size: 29184 bytes Desc: not available URL: From torsten.leidig at sap.com Wed Jul 11 12:43:16 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 11 Jul 2012 12:43:16 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE In-Reply-To: References: <4FFD15BF.4030105@tid.es> Message-ID: That's what came to my mind too and why I forwarded the mail. You should ask Juanjo what was happening to your nicely documented epics. Torsten From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] Sent: Mittwoch, 11. Juli 2012 12:16 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu Subject: Re: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE Hi torsten, Am I wrong or the Epics linked to our topics (Multi-channel and Multidevice Access System) are missing? Best regards, Javier 2012/7/11 Leidig, Torsten > From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 11. Juli 2012 07:57 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE Hi all, Just to make sure where the Epics linked to topics you wish to incorporate in the 2nd Open Call are available in the Materializing the FI-WARE Vision part of the wiki ... I can find the ones linked to the Cloud Proxy: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit Regarding Security, I understand that we are referring to the two following Epics: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack I was expecting the description of the Security Epics a bit more concrete ... Note that they should provide enough detailed information as to make sure that submitters really make proposals along the lines of what we are expecting ... Do you think that such need would be covered with the provided descriptions ? Initially, unless changed during approval of the agenda (first thing this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am until 11:15am ... this gives you a last change to incorporate further refinements. I would also like to check whether you would be available for joining the FI-PPP AB and elaborate on the topics if needed (we would have to find out how, depending on the facilities provided by the host of this meeting) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Wed Jul 11 12:59:53 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 11 Jul 2012 12:59:53 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be proposed by FI-WARE In-Reply-To: References: <4FFD15BF.4030105@tid.es> Message-ID: Ok! He doesn't answer the phone, so I've sent him an email. Regards, Javier 2012/7/11 Leidig, Torsten > That?s what came to my mind too and why I forwarded the mail. You should > ask Juanjo what was happening to your nicely documented epics.**** > > ** ** > > Torsten**** > > ** ** > > *From:* Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] > *Sent:* Mittwoch, 11. Juli 2012 12:16 > *To:* Leidig, Torsten > *Cc:* fiware-apps at lists.fi-ware.eu > *Subject:* Re: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Topics for the > 2nd Open Call to be proposed by FI-WARE**** > > ** ** > > Hi torsten,**** > > ** ** > > Am I wrong or the Epics linked to our topics (Multi-channel and > Multidevice Access System) are missing?**** > > ** ** > > Best regards,**** > > Javier**** > > ** ** > > 2012/7/11 Leidig, Torsten **** > > **** > > **** > > *From:* fiware-wpa-bounces at lists.fi-ware.eu [mailto: > fiware-wpa-bounces at lists.fi-ware.eu] *On Behalf Of *Juanjo Hierro > *Sent:* Mittwoch, 11. Juli 2012 07:57 > *To:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > *Subject:* [Fiware-wpa] IMPORTANT: Topics for the 2nd Open Call to be > proposed by FI-WARE**** > > **** > > Hi all, > > Just to make sure where the Epics linked to topics you wish to > incorporate in the 2nd Open Call are available in the Materializing the > FI-WARE Vision part of the wiki ... > > I can find the ones linked to the Cloud Proxy: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy_Software_Development_Kit > > Regarding Security, I understand that we are referring to the two > following Epics:**** > > - > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Digital_forensics_for_evidence > **** > - > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Security_Monitoring.Business_Continuity_under_Attack > **** > > > I was expecting the description of the Security Epics a bit more > concrete ... Note that they should provide enough detailed information as > to make sure that submitters really make proposals along the lines of what > we are expecting ... Do you think that such need would be covered with the > provided descriptions ? > > Initially, unless changed during approval of the agenda (first thing > this morning), the 2nd Open Call will be addressed tomorrow, from 09:30am > until 11:15am ... this gives you a last change to incorporate further > refinements. I would also like to check whether you would be available > for joining the FI-PPP AB and elaborate on the topics if needed (we would > have to find out how, depending on the facilities provided by the host of > this meeting) > > Cheers, > > **** > > -- Juanjo**** > > **** > > -------------**** > > Product Development and Innovation (PDI) - Telefonica Digital**** > > website: www.tid.es**** > > email: jhierro at tid.es**** > > twitter: twitter.com/JuanjoHierro**** > > **** > > FI-WARE (European Future Internet Core Platform) Chief Architect**** > > **** > > You can follow FI-WARE at:**** > > website: http://www.fi-ware.eu**** > > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242**** > > twitter: http://twitter.com/FIware**** > > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932**** > > **** > ------------------------------ > > > 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 > 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 > ************************************************ > --------------------- > 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel.huerta at atosresearch.eu Wed Jul 11 15:57:52 2012 From: miguel.huerta at atosresearch.eu (Miguel Angel Huerta Docasar) Date: Wed, 11 Jul 2012 15:57:52 +0200 Subject: [Fiware-apps] Deadlines for deliverables In-Reply-To: References: Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40EF2@INTMAIL03.es.int.atosorigin.com> Dear Torsten, I have seen there a couple of User Guides already uploaded in pdf by other partners but If I use the "upload file " button in the wiki it only allows me to upload jpg files. How can I upload the Atos Semantic Composer User Guide pdf to the wiki for the deliverable D3.8.4? Regards On 07/06/2012 11:58 AM, Leidig, Torsten wrote: Dear WP 3 partners, There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jul 11 17:08:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 11 Jul 2012 17:08:42 +0200 Subject: [Fiware-apps] Deadlines for deliverables In-Reply-To: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40EF2@INTMAIL03.es.int.atosorigin.com> References: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40EF2@INTMAIL03.es.int.atosorigin.com> Message-ID: <4FFD96FA.9090700@tid.es> Hi Sorry to break in the WP list but this is way too serious. pdf guides are not acceptable. User guides are in wiki format always. Then the WPA/WPL generates a pdf. But the source is wiki pages. The page for instructions for all the deliverables is here: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables All deliverables that do not comply with them strictly will be rejected by the coordination. When someone creates a deliverable he/she has to read the instructions carefully and make sure that they stick to them. Please let me know in private who are producing pdf stuff for the user guides to warn them asap. BR Miguel El 11/07/2012 15:57, Miguel Angel Huerta Docasar escribi?: Dear Torsten, I have seen there a couple of User Guides already uploaded in pdf by other partners but If I use the "upload file " button in the wiki it only allows me to upload jpg files. How can I upload the Atos Semantic Composer User Guide pdf to the wiki for the deliverable D3.8.4? Regards On 07/06/2012 11:58 AM, Leidig, Torsten wrote: Dear WP 3 partners, There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel.huerta at atosresearch.eu Thu Jul 12 10:11:01 2012 From: miguel.huerta at atosresearch.eu (Miguel Angel Huerta Docasar) Date: Thu, 12 Jul 2012 10:11:01 +0200 Subject: [Fiware-apps] Deadlines for deliverables In-Reply-To: <4FFD96FA.9090700@tid.es> References: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40EF2@INTMAIL03.es.int.atosorigin.com> <4FFD96FA.9090700@tid.es> Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40EF3@INTMAIL03.es.int.atosorigin.com> Ok Miguel, I will upload the document following the guidelines. Thanks for the clarification. Best Regards. Miguel ?ngel Huerta Software Architect Service Engineering & IT Platforms Lab IT Sector Telecom, IT & Media Market Research & Innovation T +34 912148718 F +34 917543252 miguel.huerta at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu On 07/11/2012 05:08 PM, Miguel Carrillo wrote: Hi Sorry to break in the WP list but this is way too serious. pdf guides are not acceptable. User guides are in wiki format always. Then the WPA/WPL generates a pdf. But the source is wiki pages. The page for instructions for all the deliverables is here: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables All deliverables that do not comply with them strictly will be rejected by the coordination. When someone creates a deliverable he/she has to read the instructions carefully and make sure that they stick to them. Please let me know in private who are producing pdf stuff for the user guides to warn them asap. BR Miguel El 11/07/2012 15:57, Miguel Angel Huerta Docasar escribi?: Dear Torsten, I have seen there a couple of User Guides already uploaded in pdf by other partners but If I use the "upload file " button in the wiki it only allows me to upload jpg files. How can I upload the Atos Semantic Composer User Guide pdf to the wiki for the deliverable D3.8.4? Regards On 07/06/2012 11:58 AM, Leidig, Torsten wrote: Dear WP 3 partners, There is still no content for our important M12 deliverables: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.4 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.5 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D2.3-8.3_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Please put your contributions here as soon as possible, so I can generate the PDF documents today. Regards, Torsten _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: blue_strip.gif Type: image/gif Size: 78 bytes Desc: blue_strip.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: atos_logotype.gif Type: image/gif Size: 816 bytes Desc: atos_logotype.gif URL: From torsten.leidig at sap.com Thu Jul 12 11:11:13 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 12 Jul 2012 11:11:13 +0200 Subject: [Fiware-apps] Third-party innovation enablement in FI-WARE Message-ID: Dear Partners, as you know, we have to contribute to a deliverable about "Third party innovation enablement in FI-WARE" that should be finished within the next week until 20.07.2012. You will find the complete timeline within the following Google-Docs document. https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit?pli=1#heading=h.o4fda49w1fqp Within this document, you will find details information about the requested information about your GE. Please add the requested information for you GE directly in the Google-Docs document or send a dedicated document via Mail to me (Torsten Leidig ( torsten-leidig at sap.com ) and Axel Fasse ( axel.fasse at sap.com ). Because we have to consolidate (our and) your contributions, it would be necessary to provide your information until the 18.07.2012 (EOB). If you have any questions, please feel free to contact me directly in order to avoid any delays. Best regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Mon Jul 16 13:12:45 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 16 Jul 2012 13:12:45 +0200 Subject: [Fiware-apps] Message from the coordinator Message-ID: Hi folks, Junanjo wants me to forward the following information to you: _______ AP: Telef?nica will review overall status of deliveries for M12 in each chapter and will report on it to each WPL. Telef?nica will make a proposal for the PCC: after reiterative delays, action must be taken. Failing to deliver in time (before the end of July - deadline: 23 of July) would result in the rejection of a fraction of the costs of the involved partner. Percentages of the penalties to be decided in the next PCC meeting. Round table to check on opinion: general acceptance or "no comment". Additional info (further to a question from Thierry): WPL opinion will be a fundamental input to fine tune the process. Proposal accepted by the PCC: Now, it is time to fix the details of what these measures will be. TID proposes the following (we will also develop a similar formula to FI-WARE GEs we commited to be available on the testbed by end of September, using September 10th instead of July 23rd): * Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver. Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted. Planning of PMs for the remaining of the project will be adjusted accordingly. * Delivery of software that doesn't work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered. This intends to prevent that some partner delivers software which doesn't meet enough quality by July 23rd just to avoid costs rejections. * Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point). This means they would not suffer any impact. * PMs of any partner within a given WP (WP3-8) are distributed from month 10 on across deliverables as follows (note: we propose to include whatever distribution gets approved in the next amendment of the DoW): o Contributions to WP2 deliverables: 10% o FI-WARE Open Specifications: 20% o SW Release: 40% o Installation and Admin Guides: 7,5% o Users' and Programmers' Guides: 7,5% o Unit Testing Plan and Report: 15% * Deliverables of a given WP rejected by the WPL will be rejected. TID and the WPL agree on any amendment of the above rules that may apply (e.g., failing to deliver a given GE may not be the fault of all partners involved in development of that GE so they may agree not to apply penalizations to some partners). TID may reject some additional deliverables if it considers that they do not meet the defined guidelines or expected quality, after discussion with the WPL. * Similar rules would apply to WP9 (development tools) _________ We can discuss this in our concall tomorrow morning. Regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jul 17 09:28:23 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 17 Jul 2012 09:28:23 +0200 Subject: [Fiware-apps] FW: Review of deliverables In-Reply-To: <500511A4.4080301@tid.es> References: <500511A4.4080301@tid.es> Message-ID: From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Dienstag, 17. Juli 2012 09:18 To: Riss, Uwe; Fasse, Axel; Leidig, Torsten Cc: JUAN JOSE HIERRO SUREDA Subject: Review of deliverables Dear WPL/WPA, This is the summary of my review of the deliverables due on July, 23. I may also check the status of the binaries on SCM nearer the date. Take into account that this is a first pass (I might have time to do more) and that: * This is the snapshot of the deliverable as I saw it when I reviewed each one of them (take into account that there are 6 chapters and 4 deliverables per chapter, this takes a lot of time to inspect). Same of them may have changed so the situation could have improved depending on the changes your chapter have made since then. * The review for new Features on the wiki and Unit Testing was already sent to you if I am right * This review is more formal than technical and it is performed to filter out the most obvious mistakes. This could be subject to a later review by technical staff that may reject deliverables that have an "OK" in my review In this speadsheet you will find 4 columns with comments to: * Features added in the backlog per GE * Unit Testing Plan & Report * Installation & Administration Guides * User and Programmers Guide Please let the partners concerned know ASAP to allow them to react. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_WP3.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12409 bytes Desc: Audit_Release_WP3.xlsx URL: From torsten.leidig at sap.com Tue Jul 17 12:55:38 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 17 Jul 2012 12:55:38 +0200 Subject: [Fiware-apps] FW: Naming convention for enablers with more than one implementation In-Reply-To: <50053D91.1060703@tid.es> References: <50000061.3080803@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AB40F03@INTMAIL03.es.int.atosorigin.com> <500016B4.7040207@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9AF1ED24@INTMAIL03.es.int.atosorigin.com> <50053D91.1060703@tid.es> Message-ID: Dear WP partners, pls. find the clarification according to the handling of different GE "instances" for the same GE. I hope this helps to clarify the situation for the Composition and Mediation Enablers. Regards, Torsten From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Dienstag, 17. Juli 2012 12:25 To: Leidig, Torsten; BISSON Pascal Cc: JUAN JOSE HIERRO SUREDA; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Naming convention for enablers with more than one implementation Dear Torsten, dear Pascal, As regards those deliverables not following the naming convention now let us follow these rules: * Enablers with a single implementation. There is no reason to use an alternative name. The User & Prog. Manual, The Install. and Admin guide etc. must follow the convention expressed in the guidelines. * Enablers with more than one implementation: I understand that this is undefined as it is now. Let us proceed this way: * Under the section "Materializing ... " in the wiki we will have entries with the usual names: * - Unit Testing Plan * - Installation and Administration Guide * - User and Programmers Guide * Example: [cid:part1.00010008.00080500 at tid.es] * Then each one of these takes to a page with a list of all the manuals, one line per manual, and you can have something like this per line/manual. * - * Example: clicking on "Composition Editor - Unit Testing Plan" will take us to a page where the first line is: * Composition Editor - Light Semantic Composition Unit Testing Plan * there will be others in the future, one per implementation of the GE * each one of these lines will link to a dedicated page with the manual for that concrete implementation Hope this is clear and helps you to organize thing. Note that this is not added work, you do not need to do it in the private wiki if you do not want to, it can be done in 5 minutes as you take the contents to the public wiki. Regards, Miguel ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ecjdcije.png Type: image/png Size: 4332 bytes Desc: ecjdcije.png URL: From torsten.leidig at sap.com Tue Jul 17 14:55:54 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 17 Jul 2012 14:55:54 +0200 Subject: [Fiware-apps] Meeting minutes Message-ID: Dear WP 3 members, please find the minutes of today's meeting here: https://forge.fi-ware.eu/docman/view.php/12/1181/2012-07-17-FI-WARE_Minutes.docx Regards, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Jul 18 10:43:42 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 18 Jul 2012 10:43:42 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] Clarification on task dealing with documentation of Features describing FI-WARE GEs In-Reply-To: <50064F9A.7070308@tid.es> References: <50064F9A.7070308@tid.es> Message-ID: FYI From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 18. Juli 2012 07:55 To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Clarification on task dealing with documentation of Features describing FI-WARE GEs Dear all, Let me clarify, at the risk of repeating myself a bit, some aspects about the task dealing with documentation of Features describing FI-WARE GEs. I believe that what I'm going to explain in this email has already been explained several times, at leas communicated to WPLs and WPAs, but I hope that repeating it again is not harmful and may be helpful. The target goal of the task is to end up with a set of "Features" for each FI-WARE GE that provides a complete description of the functionalities supported by that GE. When we created the first version of the backlogs linked to all FI-WARE GEs back in month 7, it was agreed that it was only necessary to include entries (Themes, Epics, Features, User Stories) linked to new functionalities that we were going to develop on top of selected baseline assets during the course of the FI-WARE project. This agreement was captured on the wiki page where we describe how we were planning to use Agile: In defining how we were going to use Agile in FI-WARE, we have had to deal with a fundamental characteristic of the project: it is not about developing from the scratch but from a set of selected products (assets) resulted from previous projects, many of which hadn't been developed using Agile. If we had started development of every FI-WARE Generic Enabler (that's the way we name components in FI-WARE) from the scratch, the FI-WARE GE backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of FI-WARE. But this is not the case. When creating the backlog for a given FI-WARE GE, we have considered that it should contain the Themes/Epics/Features/User-stories that, at the start of the FI-WARE project, map to "functionality to be developed" in the reference implementation of the GE we are building based on a number of baseline products. We won't capture all the functionality that was already implemented in the baseline products. That would mean trying to carry out a kind of "reverse engineering" of baseline products, deriving User-Stories from what those baseline products already support. This, apart from meaning a huge effort would not be be that useful to development teams and would simply delay start of our development. This didn't prevent the development team behind a given FI-WARE GE to define the whole set of Features characterizing all the functionalities of a given FI-WARE GE, including functionality already supported by the selected baseline assets. We simply didn't force them to do so (it was not mandatory). However, apparently some of the teams did this at month 7. That's fine and this only means they don't need to add entries for Features now. Remember: the target goal now is to end up with a set of "Features" per FI-WARE GE that provides a complete description of the functionalities supported by the GE. Why are we doing this exercise if we had agreed that documenting Features already supported in baseline assets was not mandatory ? Essentially because we have had to deal with a comment made by reviewers on the Technical Roadmap deliverable that was the major cause why they rejected that deliverable: we were not giving enough details of what was going to be provided by each GE in each major release (including functionalities supported already by baseline assets in the case of the first major release). The decision was to handle this comment by means of completing the backlogs of FI-WARE GEs to add "Features" that describe the complete set of functionalities of the GE. Those teams that already identified the complete set of Features describing a FI-WARE GE back in month 7 would not need to do anything. On the other hand, this shouldn't be that difficult for the rest of the teams that didn't include features describing functionalities supported by baseline assets at that time. And we will solve the comment for sure (do you want to know what a given FI-WARE GE will give in the first major release ? just take a look a the following Features description). It's true that it would be something that overrides what we explained on the wiki about following Agile (the text copied above) but we will certainly fix that text on the wiki after the task is finished. Do we need to create entries in the trackers corresponding to added Features ? I would say it is not mandatory but certainly highly desirable and a goal to achieve not later than September (it would be a matter of one hour - two hours maximum once the Features are registered on the Wiki). When doing so, we agreed that teams should assign a value "FI-WARE.Release.0" to the "FI-WARE Release Id" field. Note that you don't need to derive any short of User Story from Features linked to functionality supported by baseline assets. User stories should map to Features that have been planned for development during the course of the FI-WARE project. How are we going to elaborate on what Features of a given GE are going to go for the first major release and what Features are going to go for later major releases within the revised version of the Technical Roadmap deliverable ? This is something that we have not closed yet but will be closed in the joint WPLs/WPAs follow-up confcall that will take place on July 23rd. For the time being, we prefer that you concentrate on all what is needed to meet the July 23rd deadline (maximum extension of the original deadline by end of June that we communicated to our POs regarding late delivery of deliverables linked to FI-WARE GEs). Are we going to distinguish between Features planned to be developed in the first Release and Features already supported by baseline assets within the Technical Roadmap deliverable ? I believe it is not needed. All of them together comprise the Features that describe what is going to be supported in the first major release and that is what really matters to a potential user of a given FI-WARE GE in the first major release: what is the set of features that the GE will support that they can use. Hope this helps, although I guess most of what is being explained was already understood by you. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From torsten.leidig at sap.com Fri Jul 20 16:47:45 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Fri, 20 Jul 2012 16:47:45 +0200 Subject: [Fiware-apps] Status of Deliverables Message-ID: Dear WP3 partners, my table https://docs.google.com/spreadsheet/ccc?key=0AhoJeaXzXTH9dFBuel9oa3QweHVLLUZneDI1YTNFNXc reflects my understanding of the current status of deliverables. Please have a look at it and see if everything is correct. On Monday we will generate the PDF documents. So you have chance for last minute changes over the weekend. Best regads, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Tue Jul 24 09:34:36 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 24 Jul 2012 09:34:36 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue Message-ID: 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) 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) 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) 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) 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Catalogue Descriptions_Composition Editor & Execution Engine GEs.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 110763 bytes Desc: not available URL: From uwe.riss at sap.com Tue Jul 24 09:43:58 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 24 Jul 2012 09:43:58 +0200 Subject: [Fiware-apps] FW: [Fiware-wpl] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Message-ID: <1491C91A94302A448D73CD9C6B7A782046C02D0EBE@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Some clarification from Juanjo that I like to forward to you. Best regards, Uwe 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 24. Juli 2012 00:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpl] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From uwe.riss at sap.com Tue Jul 24 09:45:21 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 24 Jul 2012 09:45:21 +0200 Subject: [Fiware-apps] FW: [Fiware-wpl] Report on conversation with our PO on status of the FI-WARE project Message-ID: <1491C91A94302A448D73CD9C6B7A782046C02D0EC6@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Here you find a summary of the information I sent before. Best regards, Uwe 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?? |?? F +49 6227 78-26158?? |?? M +49 151 16810936?? |?? mailto: uwe.riss at sap.com 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. -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 24. Juli 2012 01:14 To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] Report on conversation with our PO on status of the FI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From uwe.riss at sap.com Tue Jul 24 09:50:00 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 24 Jul 2012 09:50:00 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: Message-ID: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> Dear Javier, I have checked the WPL/WPA 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jul 24 10:01:29 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 24 Jul 2012 10:01:29 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] Report on conversation with our PO on status of the FI-WARE project In-Reply-To: <500DDAB8.3060303@tid.es> References: <500DDAB8.3060303@tid.es> Message-ID: FYI -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 24. Juli 2012 01:14 To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Report on conversation with our PO on status of the FI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From torsten.leidig at sap.com Tue Jul 24 10:03:28 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 24 Jul 2012 10:03:28 +0200 Subject: [Fiware-apps] FW: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs In-Reply-To: <500DCFB7.4020404@tid.es> References: <500D8E9A.4050506@tid.es> <500DCFB7.4020404@tid.es> Message-ID: FYI From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 24. Juli 2012 00:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jsoriano at fi.upm.es Tue Jul 24 11:14:39 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 24 Jul 2012 11:14:39 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> Message-ID: 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 > Dear Javier,**** > > ** ** > > I have checked the WPL/WPA 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] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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)**** > > 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)**** > > 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)**** > > 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)**** > > ** ** > > 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 | F +49 6227 78-26158 | M +49 151 16810936 > | mailto: uwe.riss at sap.com **** > > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Tue Jul 24 11:27:56 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 24 Jul 2012 11:27:56 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> Message-ID: <500E6A9C.7070105@eng.it> 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 > > > 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 > ] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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) > > 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) > > 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) > > 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) > > 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 | F +49 6227 > 78-26158 | M +49 151 16810936 > | mailto:uwe.riss at sap.com > > > 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 > http://lists.fi-ware.eu/listinfo/fiware-apps -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From calin.curescu at ericsson.com Tue Jul 24 11:37:46 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Tue, 24 Jul 2012 11:37:46 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> Message-ID: <84DE6B7638096349804AC8EC332FE1245920C4048E@ESESSCMS0361.eemea.ericsson.se> I have the same understanding, it's not GEs it's their implementation, and this can be different with different guides, etc. We cannot have a 1:1 mapping here. How can one "own" a GE? /C 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 24 juli 2012 11:15 To: Riss, Uwe Cc: fiware-apps at lists.fi-ware.eu; Alvaro Arranz Subject: Re: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue 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 > Dear Javier, I have checked the WPL/WPA 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Jul 24 13:11:48 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 24 Jul 2012 13:11:48 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: <500E6A9C.7070105@eng.it> References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: 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 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] 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; 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 > 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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 http://lists.fi-ware.eu/listinfo/fiware-apps -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Tue Jul 24 15:42:13 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 24 Jul 2012 15:42:13 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: <500EA635.8070107@eng.it> 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 > > 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] *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; 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 > > > 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 > ] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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) > > 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) > > 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) > > 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) > > 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 | F +49 6227 > 78-26158 | M +49 151 16810936 > | mailto:uwe.riss at sap.com > > > 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 > http://lists.fi-ware.eu/listinfo/fiware-apps > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jsoriano at fi.upm.es Tue Jul 24 16:00:48 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 24 Jul 2012 16:00:48 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: Dear all, I fully agree with Torsten! Indeed, the first paragraph is a good summary of what we have agreed/achieved in WP3. I got surprised when I surfed the catalogue and found a great level of "freedom" in what is considered as a GE, that may confuse its users. Torsten, I still have a couple of doubts regarding WP3 GEs: When adding our Composition GEs to the Catalogue, I used the same terminology as in: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware This is why I added two separate GEs: "Composition Editor" and "(Composition) Execution Engine" instead of a single "Composition GE". Please note that in the catalogue "Execution Engine" appears out of context and hence the prefix "Composition". Moreover, if you enter the "Composition Editor" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware You can find the current implementations of that GE made from assets of the individual partners: - Mashup Factory ( https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware ) - Wirecloud ( https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware ) Following the same idea, I added Wirecloud as an Instance of the "Composition Editor" GE in the catalogue, but the other instance (the "Mashup Factory") is still missing. I imagine that our colleagues from DT will be responsible for providing the content, but I'm not sure if they will have the rights to do so because for the time being I'm the owner of the GE. Finally, if you enter the "Execution Engine" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware You will see that "Wirecloud" is replicated there. This is because Wirecloud is an instance (OSS reference implementation) of both the Composition Editor and the Execution Engine GEs. The same will occur in the catalogue: Wirecloud will appear as an instance of both GEs. Am I right? Does it make sense for you? Last, but not least: regarding the "ownership" of the GEs. I think I'm now the "owner" of both the Composition Editor and the Composition Execution Engine GEs just because I created the two entries in the catalogue :-( Of course I will agree with any change in this respect. And of course I volunteer to upload / copy&paste any information you provide (instances, descriptions, documentation, etc.). Best regards, Javier 2012/7/24 Leidig, Torsten > 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**** > > 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] *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; 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 **** > > 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] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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)**** > > 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)**** > > 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)**** > > 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)**** > > **** > > 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 | F +49 6227 78-26158 | M +49 151 16810936 > | mailto: uwe.riss at sap.com **** > > 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**** > > 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Tue Jul 24 16:37:22 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 24 Jul 2012 16:37:22 +0200 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782046C0348093@DEWDFECCR02.wdf.sap.corp> Dear WP3 Colleagues, Please find the access to the minutes of today's conf call here: https://forge.fi-ware.eu/docman/view.php/12/1195/2012-07-24-FI-WARE_Minutes.doc The FI-WARE Apps wiki page for our planning can be found here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/apps/index.php/Main_Page Please check whether you appear in the participant list and whether the minutes are complete. Best regards, Uwe 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Tue Jul 24 19:42:08 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 24 Jul 2012 19:42:08 +0200 Subject: [Fiware-apps] Draft for a new DoW part for WP3 Message-ID: <1491C91A94302A448D73CD9C6B7A782046C034825A@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, as announced some time ago we have worked on a revision of the WP3 part of the DoW that takes all changes into account that are clear for the time being. I would now like to ask you to check the attached document whether the changes are reasonable from your perspective, in particular if they concern your own activities. Since I have already asked you to send me an update of your planned activities the changes that you have sent to me are already included. However, they might need some justification from your side. The next steps are as follows: ? Please read the draft carefully and respond to the TODOs specified at the end of the documents that relate to comments for the particular partners where justification for changes are required. ? If you want to make additional changes please provide a justification for each additional change and use the tracker to make the changes visible. ? After the consolidation by all involved partners it seems to be necessary to have a look at the assigned PMs since from the current perspective there seems to be a significant imbalance in some cases. Please provide your responses by the end of this week so that we can discuss it at the next conf call. Thanks and best regards, Uwe 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Draft_DoW_WP3.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 186631 bytes Desc: Draft_DoW_WP3.docx URL: From torsten.leidig at sap.com Wed Jul 25 10:54:32 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 25 Jul 2012 10:54:32 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: <500EA635.8070107@eng.it> References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> <500EA635.8070107@eng.it> Message-ID: 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 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] 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; 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 > 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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 http://lists.fi-ware.eu/listinfo/fiware-apps -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Jul 25 10:59:56 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 25 Jul 2012 10:59:56 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: Hi Javier, I agree, we should only put the specific enablers into the Catalog. So the generic "Compsition Editor" should be removed and "Mashup Factory" and "Wirecloud" should be added. In some cases it is not possible to separate the Composition Editor and Execution. In these cases I would argue that there is one specific enabler in the catalog called for example "Mashup Factory", which comprises two GE actually. Regards, Torsten From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] Sent: Dienstag, 24. Juli 2012 16:01 To: Leidig, Torsten Cc: matteo.melideo at eng.it; 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 all, I fully agree with Torsten! Indeed, the first paragraph is a good summary of what we have agreed/achieved in WP3. I got surprised when I surfed the catalogue and found a great level of "freedom" in what is considered as a GE, that may confuse its users. Torsten, I still have a couple of doubts regarding WP3 GEs: When adding our Composition GEs to the Catalogue, I used the same terminology as in: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware This is why I added two separate GEs: "Composition Editor" and "(Composition) Execution Engine" instead of a single "Composition GE". Please note that in the catalogue "Execution Engine" appears out of context and hence the prefix "Composition". Moreover, if you enter the "Composition Editor" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware You can find the current implementations of that GE made from assets of the individual partners: * Mashup Factory (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware) * Wirecloud (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware) Following the same idea, I added Wirecloud as an Instance of the "Composition Editor" GE in the catalogue, but the other instance (the "Mashup Factory") is still missing. I imagine that our colleagues from DT will be responsible for providing the content, but I'm not sure if they will have the rights to do so because for the time being I'm the owner of the GE. Finally, if you enter the "Execution Engine" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware You will see that "Wirecloud" is replicated there. This is because Wirecloud is an instance (OSS reference implementation) of both the Composition Editor and the Execution Engine GEs. The same will occur in the catalogue: Wirecloud will appear as an instance of both GEs. Am I right? Does it make sense for you? Last, but not least: regarding the "ownership" of the GEs. I think I'm now the "owner" of both the Composition Editor and the Composition Execution Engine GEs just because I created the two entries in the catalogue :-( Of course I will agree with any change in this respect. And of course I volunteer to upload / copy&paste any information you provide (instances, descriptions, documentation, etc.). Best regards, Javier 2012/7/24 Leidig, Torsten > 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 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] 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; 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 > 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Jul 25 11:20:26 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 25 Jul 2012 11:20:26 +0200 Subject: [Fiware-apps] FW: Review of Unit Test Plan (WP3 - Apps) In-Reply-To: <500EBAD6.5060208@tid.es> References: <500EBAD6.5060208@tid.es> Message-ID: Dear Project Partners, please find attached the review report from TID according to the Unit Test Plan. As far as I can see, the comments mainly address SAP (Registry) and TI (Mediator). Please have a look at the respective pages and try to improve them. Regards, Torsten -----Original Message----- From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Dienstag, 24. Juli 2012 17:10 To: Riss, Uwe; Leidig, Torsten Cc: JUAN JOSE HIERRO SUREDA Subject: Review of Unit Test Plan (WP3 - Apps) Dear Uwe & Torsten, This is the review of the Unit Testing plan. As told by Juanjo, there is a very short time to put it right. I assume that you already have the Report ready to append at the end of the deliverable and that such manual complies with the guidelines (one single report, not one per GE). Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_1.0_b_WP3.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 11245 bytes Desc: Audit_Release_1.0_b_WP3.xlsx URL: From jsoriano at fi.upm.es Wed Jul 25 11:25:32 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 25 Jul 2012 11:25:32 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: Hi Torsten, hi Horst, hi Matteo, hi all, Torsten, Matteo has just approved the two GEs I added to the catalogue: Composition Editor and Execution Engine GEs. I will forward the email Matteo has sent me to the WP3 list because it contains very useful information about how to complete the entries in the catalogue and how to organize the information. We should use it when adding new entries. Torsten, following your instructions, I will not make the two GEs public for the moment. Instead, I will create a new entry for the Wirecloud mashup platform. This makes sense to me. I didn't take this decision from the very beginning because, as you explained yesterday, in WP3 we agreed a different definition for GEs. But it makes sense to me to introduce the notion of "Enabler" to refer to a particular implementation of a GE (or of part of it, as is the case for our Composition GEs) which is to be offered through the catalogue. Horst has to do the same for the "Mashup Factory" Do you agree Horst? The entries from Ericsson can be considered already aligned with this decision. Do you agree Calin? Later, we can ask Matteo to remove the entries for the GEs I created a couple of days ago. In the meantime, we can reuse some content from these entries. For example, when I highlighted the relationships among different entries in the catalogue: the composition GEs and the Marketplace, Store, Service Description Repository, Service Instance Registry... Does this make sense for you Matteo? Best regards, Javier 2012/7/25 Leidig, Torsten > Hi Javier,**** > > ** ** > > I agree, we should only put the specific enablers into the Catalog. So > the generic ?Compsition Editor? should be removed and ?Mashup Factory? and > ?Wirecloud? should be added.**** > > In some cases it is not possible to separate the Composition Editor and > Execution. In these cases I would argue that there is one specific enabler > in the catalog called for example ?Mashup Factory?, which comprises two GE > actually.**** > > ** ** > > Regards,**** > > Torsten**** > > ** ** > > *From:* Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] > *Sent:* Dienstag, 24. Juli 2012 16:01 > *To:* Leidig, Torsten > *Cc:* matteo.melideo at eng.it; 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 all,**** > > ** ** > > I fully agree with Torsten! Indeed, the first paragraph is a good summary > of what we have agreed/achieved in WP3.**** > > ** ** > > I got surprised when I surfed the catalogue and found a great level of > "freedom" in what is considered as a GE, that may confuse its users. **** > > ** ** > > Torsten, I still have a couple of doubts regarding WP3 GEs:**** > > ** ** > > When adding our Composition GEs to the Catalogue, I used the same > terminology as in: **** > > ** ** > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware*** > * > > ** ** > > This is why I added two separate GEs: "Composition Editor" and > "(Composition) Execution Engine" instead of a single "Composition GE". > Please note that in the catalogue "Execution Engine" appears out of context > and hence the prefix "Composition".**** > > ** ** > > Moreover, if you enter the "Composition Editor" directory:**** > > ** ** > > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware > **** > > ** ** > > You can find the current implementations of that GE made from assets of > the individual partners:**** > > - Mashup Factory ( > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware > )**** > - Wirecloud ( > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware > )**** > > Following the same idea, I added Wirecloud as an Instance of the > "Composition Editor" GE in the catalogue, but the other instance (the > "Mashup Factory") is still missing. I imagine that our colleagues from DT > will be responsible for providing the content, but I'm not sure if they > will have the rights to do so because for the time being I'm the owner of > the GE.**** > > ** ** > > Finally, if you enter the "Execution Engine" directory:**** > > ** ** > > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware > **** > > ** ** > > You will see that "Wirecloud" is replicated there. This is because > Wirecloud is an instance (OSS reference implementation) of both the > Composition Editor and the Execution Engine GEs. The same will occur in the > catalogue: Wirecloud will appear as an instance of both GEs. Am I right? > Does it make sense for you?**** > > ** ** > > Last, but not least: regarding the "ownership" of the GEs. I think I'm now > the "owner" of both the Composition Editor and the Composition Execution > Engine GEs just because I created the two entries in the catalogue :-( Of > course I will agree with any change in this respect. And of course I > volunteer to upload / copy&paste any information you provide (instances, > descriptions, documentation, etc.).**** > > ** ** > > Best regards,**** > > Javier**** > > ** ** > > 2012/7/24 Leidig, Torsten **** > > 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**** > > 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] *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; 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 **** > > 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] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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)**** > > 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)**** > > 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)**** > > 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)**** > > **** > > 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 | F +49 6227 78-26158 | M +49 151 16810936 > | mailto: uwe.riss at sap.com **** > > 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**** > > 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 > ************************************************ > --------------------- > 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Wed Jul 25 11:32:23 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Wed, 25 Jul 2012 11:32:23 +0200 Subject: [Fiware-apps] Fwd: IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: <500FB25F.6000409@eng.it> References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> <500EAD0E.8000605@eng.it> <500FB25F.6000409@eng.it> Message-ID: Hi all, I'm forwarding this email from Matteo explaining how to complete the entries in the catalogue and how to organize the information in each entry. I think it will be very useful for all of us. As I said in a previous email, the two entries for the Composition GEs I added a couple of days ago are now approved, but I will not make them public because we are going to add a separate entry for each Enabler (i.e. for each (partial) implementation of our GEs we plan to make available). I will add a new entry for the Wirecloud mashup platform: an open source, reference implementation of both the Composition Editor and the Execution Engine GEs that covers part of their APIs and open specifications. Hope this resolves the situation. Best regards, Javier ---------- Forwarded message ---------- From: Matteo Melideo Date: 2012/7/25 Subject: Re: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue To: "Javier Soriano (FI-UPM)" Cc: Dalle Carbonare Davide Dear Javier, I read the text of your GEs and I approved them. Now you can finalise these providing the missing info and then making your GE public. In particular, I kindly invite you to finalize the description of your GE following the guidelines reported here: - The instances page will list all instances where your GE is running. This is typically as a minimum a URL and you add the specific functionality ("SEs") that makes a specific instance unique (i.e. implementation of a GE plus the SEs). Your first instance is probably the testbed. To add a new enabler, go to the "Instances"-tab and select "Add new instance". You can add downloadable files to an instance of the Generic Enabler. This can be appropriate if the instance for example requires special documentation that does not apply to the entire GE. - The download page should contain 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 - Files which are only relevant for a specific instance should be attached directly to this instance. - In the documentation part you write the juicy technical details directed to the coder who should use it. 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 (see styling tips below). For any other info please look at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogueand do not hesitate to contact me. BR Matteo Il 24/07/2012 16:28, Javier Soriano (FI-UPM) ha scritto: Yes Matteo, I wrote my last email without reading your quite detailed response to Torsten's. Thank you very much because it will be extremely useful as a guide. You can be sure you haven't wasted your time ;-) and it is now much more clear for me what is expected in all the sections of the catalogue. Indeed, your email has confirmed many decisions I made by my own (risk ;-). Thanks again for your time. Best regards, Javier 2012/7/24 Matteo Melideo > Hi Javier, > I hope my mail clarified the point but the way the GEs are described is up > to the WP leaders not to us. We just need to be sure what written is well > done and in line with the catalogue expectations. > > > Regards > > M. > Il 24/07/2012 16:00, Javier Soriano (FI-UPM) ha scritto: > > Dear all, > > I fully agree with Torsten! Indeed, the first paragraph is a good > summary of what we have agreed/achieved in WP3. > > I got surprised when I surfed the catalogue and found a great level of > "freedom" in what is considered as a GE, that may confuse its users. > > Torsten, I still have a couple of doubts regarding WP3 GEs: > > When adding our Composition GEs to the Catalogue, I used the same > terminology as in: > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware > > This is why I added two separate GEs: "Composition Editor" and > "(Composition) Execution Engine" instead of a single "Composition GE". > Please note that in the catalogue "Execution Engine" appears out of context > and hence the prefix "Composition". > > Moreover, if you enter the "Composition Editor" directory: > > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware > > You can find the current implementations of that GE made from assets of > the individual partners: > > - Mashup Factory ( > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware > ) > - Wirecloud ( > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware > ) > > Following the same idea, I added Wirecloud as an Instance of the > "Composition Editor" GE in the catalogue, but the other instance (the > "Mashup Factory") is still missing. I imagine that our colleagues from DT > will be responsible for providing the content, but I'm not sure if they > will have the rights to do so because for the time being I'm the owner of > the GE. > > Finally, if you enter the "Execution Engine" directory: > > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware > > You will see that "Wirecloud" is replicated there. This is because > Wirecloud is an instance (OSS reference implementation) of both the > Composition Editor and the Execution Engine GEs. The same will occur in the > catalogue: Wirecloud will appear as an instance of both GEs. Am I right? > Does it make sense for you? > > Last, but not least: regarding the "ownership" of the GEs. I think I'm > now the "owner" of both the Composition Editor and the Composition > Execution Engine GEs just because I created the two entries in the > catalogue :-( Of course I will agree with any change in this respect. And > of course I volunteer to upload / copy&paste any information you provide > (instances, descriptions, documentation, etc.). > > Best regards, > Javier > > > 2012/7/24 Leidig, Torsten > >> 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 >> >> 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] *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; 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 >> >> 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] >> *Sent:* Dienstag, 24. Juli 2012 09:35 >> *To:* Leidig, Torsten; Riss, Uwe >> *Cc:* 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) >> >> 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) >> >> 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) >> >> 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) >> >> >> >> 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 | F +49 6227 78-26158 | M +49 151 16810936 >> | mailto: uwe.riss at sap.com >> >> 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 >> >> 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 > ************************************************ > --------------------- > 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From matteo.melideo at eng.it Wed Jul 25 11:45:54 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 25 Jul 2012 11:45:54 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue In-Reply-To: References: <1491C91A94302A448D73CD9C6B7A782046C02D0EDE@DEWDFECCR02.wdf.sap.corp> <500E6A9C.7070105@eng.it> Message-ID: <500FC052.4060905@eng.it> Dear Javier, as, at the right moment anything is publicly visible, I would suggest to not remove anything. As soon as you will have finished, we will do a recap deciding what to remove and what to publish. Ok? Best regards Matteo Il 25/07/2012 11:25, Javier Soriano (FI-UPM) ha scritto: > Hi Torsten, hi Horst, hi Matteo, hi all, > > Torsten, Matteo has just approved the two GEs I added to the > catalogue: Composition Editor and Execution Engine GEs. I will forward > the email Matteo has sent me to the WP3 list because it contains very > useful information about how to complete the entries in the catalogue > and how to organize the information. We should use it when adding new > entries. > > Torsten, following your instructions, I will not make the two GEs > public for the moment. Instead, I will create a new entry for the > Wirecloud mashup platform. This makes sense to me. I didn't take this > decision from the very beginning because, as you explained yesterday, > in WP3 we agreed a different definition for GEs. But it makes sense to > me to introduce the notion of "Enabler" to refer to a particular > implementation of a GE (or of part of it, as is the case for our > Composition GEs) which is to be offered through the catalogue. > > Horst has to do the same for the "Mashup Factory" Do you agree Horst? > > The entries from Ericsson can be considered already aligned with this > decision. Do you agree Calin? > > Later, we can ask Matteo to remove the entries for the GEs I created a > couple of days ago. In the meantime, we can reuse some content from > these entries. For example, when I highlighted the relationships among > different entries in the catalogue: the composition GEs and the > Marketplace, Store, Service Description Repository, Service Instance > Registry... Does this make sense for you Matteo? > > Best regards, > Javier > > 2012/7/25 Leidig, Torsten > > > Hi Javier, > > I agree, we should only put the specific enablers into the > Catalog. So the generic ?Compsition Editor? should be removed and > ?Mashup Factory? and ?Wirecloud? should be added. > > In some cases it is not possible to separate the Composition > Editor and Execution. In these cases I would argue that there is > one specific enabler in the catalog called for example ?Mashup > Factory?, which comprises two GE actually. > > Regards, > > Torsten > > *From:*Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es > ] > *Sent:* Dienstag, 24. Juli 2012 16:01 > *To:* Leidig, Torsten > *Cc:* matteo.melideo at eng.it ; > 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 all, > > I fully agree with Torsten! Indeed, the first paragraph is a good > summary of what we have agreed/achieved in WP3. > > I got surprised when I surfed the catalogue and found a great > level of "freedom" in what is considered as a GE, that may confuse > its users. > > Torsten, I still have a couple of doubts regarding WP3 GEs: > > When adding our Composition GEs to the Catalogue, I used the same > terminology as in: > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware > > This is why I added two separate GEs: "Composition Editor" and > "(Composition) Execution Engine" instead of a single "Composition > GE". Please note that in the catalogue "Execution Engine" appears > out of context and hence the prefix "Composition". > > Moreover, if you enter the "Composition Editor" directory: > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware > > You can find the current implementations of that GE made from > assets of the individual partners: > > * Mashup Factory > (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware) > * Wirecloud > (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware) > > Following the same idea, I added Wirecloud as an Instance of the > "Composition Editor" GE in the catalogue, but the other instance > (the "Mashup Factory") is still missing. I imagine that our > colleagues from DT will be responsible for providing the content, > but I'm not sure if they will have the rights to do so because for > the time being I'm the owner of the GE. > > Finally, if you enter the "Execution Engine" directory: > > https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware > > You will see that "Wirecloud" is replicated there. This is because > Wirecloud is an instance (OSS reference implementation) of both > the Composition Editor and the Execution Engine GEs. The same will > occur in the catalogue: Wirecloud will appear as an instance of > both GEs. Am I right? Does it make sense for you? > > Last, but not least: regarding the "ownership" of the GEs. I think > I'm now the "owner" of both the Composition Editor and the > Composition Execution Engine GEs just because I created the two > entries in the catalogue :-( Of course I will agree with any > change in this respect. And of course I volunteer to upload / > copy&paste any information you provide (instances, descriptions, > documentation, etc.). > > Best regards, > > Javier > > 2012/7/24 Leidig, Torsten > > > 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 > > 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 > ] *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 > ; 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 > > > 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 > ] > *Sent:* Dienstag, 24. Juli 2012 09:35 > *To:* Leidig, Torsten; Riss, Uwe > *Cc:* 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) > > 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) > > 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) > > 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) > > 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 | F +49 6227 > 78-26158 | M +49 151 16810936 > | mailto:uwe.riss at sap.com > > > 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 > > 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 > ************************************************ > --------------------- > 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From uwe.riss at sap.com Wed Jul 25 14:14:12 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 25 Jul 2012 14:14:12 +0200 Subject: [Fiware-apps] Comments on Features linked to GEs in the Apps Chapter Message-ID: <1491C91A94302A448D73CD9C6B7A782046C03489E2@DEWDFECCR02.wdf.sap.corp> Dear Colleagues, Please check Juanjo's email with respect to the sections that concern your GE and address the issues raised in there. Thank and best regards, Uwe From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Mittwoch, 25. Juli 2012 09:08 To: Leidig, Torsten; Riss, Uwe Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Comments on Features linked to GEs in the Apps Chapter Dear Uwe and Torsten, Please find my comments regarding revision/addition of Features linked to GEs in the Apps Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Please forward this to the people of your team involved so that they can start working on a revised version of the Features addressing the comments. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. I have left USDL apart because I do not consider it a GE itself. 2. Service Repository Taking a look at the User Stories derived from the single defined Feature that you provide ( FIWARE.FEATURE.Apps.USDL.BasicRepositoryService) , we would get an enough complete overview of the functionality that the GE supports. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. If you go for keeping the existing Feature, certainly the Goal description doesn't follow the guidelines we defined long time ago (see Project Handbook, https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki). Assuming that you have defined Features that are 1:1 linked to User Stories, I believe you have to review the description of FIWARE.STORY.Apps.Repository.RepositorySearch to clarify what do you mean by "OpenSearch" ("... The search functionality should be described by OpenSearch.") It is not clear what is the difference between FIWARE.STORY.Apps.Repository.ListServiceDescriptions and FIWARE.STORY.Apps.Repository.RepositorySearch looking at their description, which means that they probably should be refined. 3. Registry There are no Features linked to this GE. Most probably because we would be in a situation similar to Service Repository. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. 4. Marketplace Generally speaking, Goal description didn't follow the guidelines defined long time ago (again, see established guidelines) FIWARE.FEATURE.Apps.Marketplace.FulltextSearch Feature: It would be nice to describe how keywords are created/assigned/linked to services. Minor suggestion ... Shouldn't the feature be identified as "KeywordSearch" or "TextKeywordSearch" rather than "FulltextSearch" ? FIWARE.FEATURE.Apps.Marketplace.StoreManagement Feature: I would suggest to elaborate in the description how are Stores going to be registered ... Is it about registering the URL linked to a Store against which users/applications will be able to issue requests linked to the Store API ? FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature: Little is said about Offerings in the description as to be able to rightfully label this as a Feature. Are we providing enough level of detail as to understand this could be implemented in the course of a single minor Release (i.e., three months) ? One of the things I would expect to see is a high-level description of what an Offering would be ... what attributes it would have, etc FIWARE.FEATURE.Apps.Marketplace.UserManagement Feature: typo saying "rolse" instead of "role". Seems like the description was a copy&paste of the description of the FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature ... 5. Store I wonder then what we are going to deliver here for the first Release once it is clear that Ericsson won't deliver the eStore ... My understanding was that the gap was going to be covered by the UPM ... but I don't know what's the status and it seems you haven't updated the backlog in this respect ... Could you elaborate on the matter ? 6. Revenue Sharing FIWARE.FEATURE.Apps.RSSS.RSSModelManagement Feature: * On one hand it is said that "Revenue Sharing must support the management of revenue sharing models." but on the other hand, it is said that "Just percentage algorithm is supported." It is unclear what we mean when we say "just" ... Does it mean that we are ONLY going to support models defined based on percentage algorithms now and forever, or that we are going to support only percentage algorithms in the second major release (when this GE is planned to be delivered for the first time) but this may be extended in future releases ? If it is the first case, then I would avoid saying "just" and say something like "each revenue sharing model will map into an algorithm for calculating revenues among involved parties", for example. If it is the second case, then I would suggest defining an Epic that has to maps to the need to support the manage of multiple revenue sharing models in general (we can indeed identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement) and then use the current Feature to elaborate on the management of revenue sharing models using percentage algorithms, changing the Id accordingly (to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FixedPercentageRSSModels, for example) * Notwithstanding the above, I believe that the description of the this Feature should be enriched: * If each Revenue Sharing Model maps into an algorithm that establishes what is the % of the revenues that is assigned to each party, then I would clearly say so. * I would explain that the User will have means to provision/register the algorithm assigned to each model * I would elaborate on what kind of algorithms will be supported. Looking at the definition of the FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision User Story later on, it seems like the will be algorithms that will establish a % that gets fixed over time but there will be also algorithms that enable to change these % dynamically FIWARE.FEATURE.Apps.RSSS.CDRsReception Feature: It would be worth explaining (in the description) what short of mechanisms are going to be supported for CDRs Reception. Is it going to be through an API that enables to submit CDRs in real time on an individual basis ? Are we going to allow submission of CDRs using files ? We don't need to enter in the details of course (signature of operations, format of files) but give an overall description of what mechanisms are going to be supported. FIWARE.FEATURE.Apps.RSSS.RSSCalculation Feature: * It would be worth describing (in the description) whether calculation takes place in batches or recalculation is performed real-time in parallel to reception of CDRs. Also whether "hot" updates of algorithms definitions is going to be supported or not: are we going to have operations to "pause" calculation for a given number of commercialized services because we have changed the way revenue share is calculated or should we stop the complete system ? things like that. * I wonder whether this Features shouldn't be merged with the FIWARE.FEATURE.Apps.RSSS.RSSCalcAggrBased. I would keep them separate if we are going to support different methods of calculation (e.g., both based on batch calculation but also incremental). But if it is always incremental, why don't merging them. FIWARE.FEATURE.Apps.RSSS.FlexibleRSSAlgorithms Feature: I would try to elaborate here what is going to be possible or not. Maybe this depends on what the BM&BE GE will provide because that GE is the one that would provide tools to define the different algorithms based on, for example, defined templates. If so, it would be worth mentioning it. FIWARE.FEATURE.Apps.RSSS.CDRAggregations: It seems like the goal from the previous Feature has been copied&pasted here. The description seems to be appropriate but the goal doesn't. FIWARE.FEATURE.Apps.RSSS.Vouchers Feature: It had to read the description several times to get a relatively clear view of the Feature. I would suggest some editorial changes that maybe would improve the understanding: The RSS will calculate the RS taking usage of vouchers into account. There will be no RS generated when the user of an application/service acquires a voucher, only the uses of the voucher will generate incomes for the providers of the application/services. RSS will calculate a cost per usage by dividing the cost of the voucher by the total number of uses it contains. As the cost of the voucher might change every time it is renewed, the RSS will store each new acquisition price and establish a relationship between every voucher usage and the corresponding acquisition. (note: shouldn't 'a cost' marked in red be replaced by 'the total revenue (to be shared)' ?) Last but not least, if some User Stories were derived as a result of elaborating the Features, it would be nice to reflect that relationship in the Id as we have adopted as convention in many other GEs. If, for example, FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision is related to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement, then identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FlexibleRSSAlgorithmProvision. 7. Composition I will treat this in a separate email. 8. Mediator Description of the following Mediator features are rather poor. I wonder whether a minimal peer review by someone else (WP Leader ?) has been passed: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration One may think that a better clue of what is being described could be obtained after reading the description of the Architecture of the Mediator GE (part of FI-WARE Architecture and Open Specifications), however this is not the case. As an example, you simply try to search for the words 'semantic', 'BPMN' or 'BPEL' in the wiki page linked to description of the Architecture of the Mediator GE. Therefore, it is almost imposible to get a clue of what these features are about. Of course, the text provided as Goal or description doesn't help at all: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation: DataFlow Mediation based on semantic exact matching and subsuption (Goal) Data mapping of elements in the I/O that are similar (Description) * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation: DataFlow Mediation based on semantic plugin and intersection (Goal) Advanced data mapping of elements in the I/O that ara not exactly matched. (Description) * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling: DataFlow Mediation based on semantic plugin and interseaction (Goal, same as previous Feature but now with typo) Advanced data mapping of elements in the I/O that ara not exactly matched (Description, same as previous) * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration: Get a BPMN2.0 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration: Get a BPEL1.2 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) One misses Features that somehow may align with description of the Architecture of the GE ... e.g., ability to create and manage the lifecycle of Mediation Tasks, Dynamic Mediation Tasks ... the ability to create chains of mediation tasks ... the provision of proxies and endpoints ... but nothing is there. One can intuitively understand what kind of functionality may be supported by the Mediator GE when reviewing the following Features: * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2REST * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2POX * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.TCP2HTTP However, all kind of questions come to my mind when trying to understand how this may work. Is it a WSDL generated in the case of the SOAP2REST or SOAP2POX cases ? How is it generated ? Is there a tool that generates the code of a mediation task based on description of a particular REST API (i.e., a different mediation task is generated per REST interface) ? Or are we talking about some sort of generic mediation task that processes configuration data generated per particular REST API ? How is the description of a REST API provided ? (all of us know that there is nothing like a WSDL in REST) They should be answered somewhere ... if in the Architecture wiki page, then you should at least include a reference (link) in the description here. The owners of this GE responsible of the Features above have to seriously revise description of Features for this GE because it is a clear candidate for rejection. Regarding the FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.Security Feature, it is more or less clear what it does despite its usage will be rather limited, given the fact that most of the APIs provided by GEs in FI-WARE are REST. ________________________________ 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 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Wed Jul 25 23:43:05 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Wed, 25 Jul 2012 23:43:05 +0200 Subject: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue Message-ID: <84DE6B7638096349804AC8EC332FE1245920C4086C@ESESSCMS0361.eemea.ericsson.se> On a shallow read I tend to agree. But Mathieu is doing the editing. Mathieu, do you agree? BR, /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 25 juli 2012 11:26 To: Leidig, Torsten Cc: fiware-apps at lists.fi-ware.eu; Alvaro Arranz; Dalle Carbonare Davide Subject: Re: [Fiware-apps] IMPORTANT: About WP3 Composition GEs and the Catalogue Hi Torsten, hi Horst, hi Matteo, hi all, Torsten, Matteo has just approved the two GEs I added to the catalogue: Composition Editor and Execution Engine GEs. I will forward the email Matteo has sent me to the WP3 list because it contains very useful information about how to complete the entries in the catalogue and how to organize the information. We should use it when adding new entries. Torsten, following your instructions, I will not make the two GEs public for the moment. Instead, I will create a new entry for the Wirecloud mashup platform. This makes sense to me. I didn't take this decision from the very beginning because, as you explained yesterday, in WP3 we agreed a different definition for GEs. But it makes sense to me to introduce the notion of "Enabler" to refer to a particular implementation of a GE (or of part of it, as is the case for our Composition GEs) which is to be offered through the catalogue. Horst has to do the same for the "Mashup Factory" Do you agree Horst? The entries from Ericsson can be considered already aligned with this decision. Do you agree Calin? Later, we can ask Matteo to remove the entries for the GEs I created a couple of days ago. In the meantime, we can reuse some content from these entries. For example, when I highlighted the relationships among different entries in the catalogue: the composition GEs and the Marketplace, Store, Service Description Repository, Service Instance Registry... Does this make sense for you Matteo? Best regards, Javier 2012/7/25 Leidig, Torsten > Hi Javier, I agree, we should only put the specific enablers into the Catalog. So the generic "Compsition Editor" should be removed and "Mashup Factory" and "Wirecloud" should be added. In some cases it is not possible to separate the Composition Editor and Execution. In these cases I would argue that there is one specific enabler in the catalog called for example "Mashup Factory", which comprises two GE actually. Regards, Torsten From: Javier Soriano (FI-UPM) [mailto:jsoriano at fi.upm.es] Sent: Dienstag, 24. Juli 2012 16:01 To: Leidig, Torsten Cc: matteo.melideo at eng.it; 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 all, I fully agree with Torsten! Indeed, the first paragraph is a good summary of what we have agreed/achieved in WP3. I got surprised when I surfed the catalogue and found a great level of "freedom" in what is considered as a GE, that may confuse its users. Torsten, I still have a couple of doubts regarding WP3 GEs: When adding our Composition GEs to the Catalogue, I used the same terminology as in: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/?root=fiware This is why I added two separate GEs: "Composition Editor" and "(Composition) Execution Engine" instead of a single "Composition GE". Please note that in the catalogue "Execution Engine" appears out of context and hence the prefix "Composition". Moreover, if you enter the "Composition Editor" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/?root=fiware You can find the current implementations of that GE made from assets of the individual partners: * Mashup Factory (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/MashupFactory/?root=fiware) * Wirecloud (https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/CompositionEditor/Wirecloud/?root=fiware) Following the same idea, I added Wirecloud as an Instance of the "Composition Editor" GE in the catalogue, but the other instance (the "Mashup Factory") is still missing. I imagine that our colleagues from DT will be responsible for providing the content, but I'm not sure if they will have the rights to do so because for the time being I'm the owner of the GE. Finally, if you enter the "Execution Engine" directory: https://forge.fi-ware.eu/scm/viewvc.php/trunk/FI-WARE/Apps/ExecutionEngine/?root=fiware You will see that "Wirecloud" is replicated there. This is because Wirecloud is an instance (OSS reference implementation) of both the Composition Editor and the Execution Engine GEs. The same will occur in the catalogue: Wirecloud will appear as an instance of both GEs. Am I right? Does it make sense for you? Last, but not least: regarding the "ownership" of the GEs. I think I'm now the "owner" of both the Composition Editor and the Composition Execution Engine GEs just because I created the two entries in the catalogue :-( Of course I will agree with any change in this respect. And of course I volunteer to upload / copy&paste any information you provide (instances, descriptions, documentation, etc.). Best regards, Javier 2012/7/24 Leidig, Torsten > 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 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] 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; 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 > 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] Sent: Dienstag, 24. Juli 2012 09:35 To: Leidig, Torsten; Riss, Uwe Cc: 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) 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) 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) 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) 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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 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 ************************************************ --------------------- 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Thu Jul 26 00:33:01 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Thu, 26 Jul 2012 00:33:01 +0200 Subject: [Fiware-apps] Draft for a new DoW part for WP3 In-Reply-To: <1491C91A94302A448D73CD9C6B7A782046C034825A@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782046C034825A@DEWDFECCR02.wdf.sap.corp> Message-ID: <84DE6B7638096349804AC8EC332FE1245920C40870@ESESSCMS0361.eemea.ericsson.se> Hi Uwe, I have given the answers to your requests and also created some new comments - regarding everybody. Since the latter changes the comment number, I provide here 2 different files. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Riss, Uwe Sent: den 24 juli 2012 19:42 To: fiware-apps at lists.fi-ware.eu Subject: [Fiware-apps] Draft for a new DoW part for WP3 Dear Colleagues, as announced some time ago we have worked on a revision of the WP3 part of the DoW that takes all changes into account that are clear for the time being. I would now like to ask you to check the attached document whether the changes are reasonable from your perspective, in particular if they concern your own activities. Since I have already asked you to send me an update of your planned activities the changes that you have sent to me are already included. However, they might need some justification from your side. The next steps are as follows: ? Please read the draft carefully and respond to the TODOs specified at the end of the documents that relate to comments for the particular partners where justification for changes are required. ? If you want to make additional changes please provide a justification for each additional change and use the tracker to make the changes visible. ? After the consolidation by all involved partners it seems to be necessary to have a look at the assigned PMs since from the current perspective there seems to be a significant imbalance in some cases. Please provide your responses by the end of this week so that we can discuss it at the next conf call. Thanks and best regards, Uwe 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 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Draft_DoW_WP3_responses_EAB.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 186059 bytes Desc: Draft_DoW_WP3_responses_EAB.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Draft_DoW_WP3_newCommentsEAB.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 186265 bytes Desc: Draft_DoW_WP3_newCommentsEAB.docx URL: From calin.curescu at ericsson.com Thu Jul 26 08:49:37 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Thu, 26 Jul 2012 08:49:37 +0200 Subject: [Fiware-apps] Contact during holidays Message-ID: <84DE6B7638096349804AC8EC332FE1245920E727FA@ESESSCMS0361.eemea.ericsson.se> ?Dear all, During these last push days I would like to make you all aware that I am on holidays with limited access to mail, which I will still try to read when I can 1-3 days delay. Mathieu is still in the office though. On urgent matters please call me on my work phone: +46761153352. BR, Calin From torsten.leidig at sap.com Thu Jul 26 09:58:50 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 26 Jul 2012 09:58:50 +0200 Subject: [Fiware-apps] FW: Review of more deliverables In-Reply-To: <5010354B.6070103@tid.es> References: <5010354B.6070103@tid.es> Message-ID: Please find the reveiw report for the Installation and Adminstration guides. Your action is required. Best Torsten From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Mittwoch, 25. Juli 2012 20:05 To: Riss, Uwe; Leidig, Torsten Cc: JUAN JOSE HIERRO SUREDA Subject: Review of more deliverables Dear Uwe & Torsten, This is my review for the Instal & Admin l manual and also for the User and Programmer's manual. The problematic things are marked in light blue. Please be aware that you have a very short time to react so let your partners know ASAP. A few comments: * Things to be addressed are highlighted in blue. * Note that my review is "formal" (formats, structure, consistency, reasonable aspect) but the coordination (Juanjo) may add comments of a more technical nature afterwards. So an "ok" from me does not necessarily means a final approval by the project coordination. * General comment for all WPs: there are many GEs in some WP with an "Installation and Administration Guide" that is an installation manual only. Giving the need to deliver at once, we will not try to fix it immediately. After the delivery we will provide a deadline to address it and provide the administration part. Of course, the impact on the cost reporting could be affected by this. * This applies to part of the WPs only. The case of the Install and Admin Guides of GEs offered as a Service of nature PP the partner has to provide proper guides (what is needed by the administrator of the machine where it is running at your company ). This will given to the EC upon request and it will protected somehow (account/password, IP filtering, ...). In the deliverables at the end of the month we will provide simply a text stating that. We would give the manuals+binaries afterwards and only if they ask for it. I'd appreciate it if you could confirm what GEs are going to be provided as a Service (not to install on the testbed) in July. Theoretically this is in the testbed wiki but things change too fast and I prefer to ask you. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_1.0_b_WP3.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12292 bytes Desc: Audit_Release_1.0_b_WP3.xlsx URL: From calin.curescu at ericsson.com Fri Jul 27 01:35:39 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Fri, 27 Jul 2012 01:35:39 +0200 Subject: [Fiware-apps] Multiple GE implementation - new naming - Unit testing, install guides and user guides Message-ID: <84DE6B7638096349804AC8EC332FE1245920C40AC0@ESESSCMS0361.eemea.ericsson.se> For the ones involved in the Composition part, According to Miguel's rules I changed the all the Unit Test namings in the Wiki to correspond to the name scheme. Please check at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Applications/Services_Ecosystem_and_Delivery_Framework_in_FI-WARE#Unit_Testing_Plan_3 I also changed the Ericsson i.e. the ...ECE... entries in the install guides and user guides: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD3-8.4.1#Apps_Components https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.3.1_FIWARE_Installation_and_Administration_Guide%22_WP3_Apps_Contribution Maybe you want to do the same. BR, /Calin -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri Jul 27 09:31:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 09:31:42 +0200 Subject: [Fiware-apps] Installation on the Testbed and procedures Message-ID: <501243DE.3010807@tid.es> Dear all, As leader of the task D10.2 "FI-WARE Integration" and also from the coordination I'd like to make some clarifications of general interest. As you know, WP10 (Experimentation Support, Integrated Testing and Validation) has as main task the set-up and running of the FI-WARE Testbed. Given the importance of this goal, WP10 has a representative of each partner. This representative (not the WPL) should make sure that all people within his/her company are well informed of the situation and what we expect from them in the Testbed and the experimentation stage. Several partners are not doing this work (in same cases never attended the WP10 phc) and the project coordination is receiving complaints as many people don't seem to be well informed. We sometimes resort to the WPL to help here, but this is not the "official" channel. I will try to recap to give all the consortium an overview of the situation and what we need from you. GENERAL INFO * The Testbed Team is starting to send the details on how to install the testbed to the GE owners who declared that they are going to install their GE in July * Theoretically you should install your GE yourselves but we can give a hand deploying a KVM image for those who prefer this method (other hypervisors are not supported) * The GE owner is the one who administrates and maintains the GE, not the testbed team. If something goes wrong, he/she has to put it up and running again, the WP10 will only monitor the situation and will prompt about abnormal behaviour of the GE . * We have two tools to follow this up: * Implementation cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit * Integration Tracker : https://forge.fi-ware.eu/tracker/?atid=224&group_id=18&func=browse * Each release of each GE is represented by a ticket * The use of this is explained here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Integration_Plan#Integration_Process * If you do not have access to the testbed project and cannot reach this wiki and the tracker, request access following the standard procedure REQUESTS FOR GE OWNERS * We have an installation calendar. Please fill in the responsible person per GE and state the dates when you could install * http://www.doodle.com/bymgm9h9gnbfms8k * Fill the GE template in the Testbed Cockpit (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit ) declaring if the GE is multi-tenant or not (this deeply affects the GE usage by different Use case projects at the same time) * The access to the Testbed is limited per IP. Make sure that the IPs from which you are going to access the Testbed are listed here (if not, you will not be able to enter the testbed): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit (click on your enabler and see the wiki page with the details per enabler) * Alternatively, there is also a page that has company wide IPs (not particular to an enabler): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Operations_Cockpit * Make sure that when you install your GE, you update the corresponding ticket on the Integration tracker and also the Implementation cockpit. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Fri Jul 27 11:26:59 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Fri, 27 Jul 2012 11:26:59 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter (Part II) In-Reply-To: <50118918.8000505@tid.es> References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <50118918.8000505@tid.es> Message-ID: Dear Composition Partners, I got this mail from Juanjo and think that the issue is concerning the Composition GE and have to be discussed among the composition partners. From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 26. Juli 2012 20:15 To: Leidig, Torsten; Riss, Uwe Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Comments on Features linked to GEs in the Apps Chapter (Part II) Hi all, Please find bellow my comments on the remaining GEs of the chapter, namely the Composition GE. Not so difficult to deal with, definitively something feasible by EOB Monday. Let me share that I'm still a bit skeptical about still trying to merge all the different assets we are bringing here into a single GE, rather than simply declaring that we go for supporting different GEs per "composition paradigm" we want to support ... definitively this is something we are not going to achieve in the first release ... but let's keep trying ... (and still Think Big :-) Cheers, -- Juanjo 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: * FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured * FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation * FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions Feature: Is this still in place ? I'm not pretty sure so I preferred to ask :-) If still applies, I definitively would like to see a description of what those sort of extensions would be. Note that if we have classified this as a Feature, is because we bet it can be implemented in the course of 3 Sprints, so it should be already designed/discussed to enough level of detail as to be able to assume such estimation ... If not, then it should be an Epic (and even though in a higher level, it should still give some clue about what sort of extensions we are talking about) FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition Feature: I would rename this Feature so that the relationship with the previous FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenGadgetExecution feature becomes more evident. I have changed the Goal to enhance the fact that we target end users that can design mashups without programming skills. I would also enhance the existing description to highlight the relationship. My suggested description: End users can create new applications, also referred as mashups, by wiring UI components called widgets/gadgets searched and selected from a catalog. Those gadgets can communicate between themselves at runtime based on the Event-driven Gadget communication mechanism supported by the Execution Engine. End users can also import mashups defined by other users as whole, either from the catalog or from a mashup description file in MDL. Imported mashups can be enhanced by adding new gadgets from the catalog that may be wired together with the gadgets in the original mashup. Last but not least, the user can store the resulting composite app in the catalog for reuse. Note that this description is large enough so that we may have split this Feature into several, but I can live keeping just one, provided the description is complete. FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushDrivenWiring Feature: I may be wrong, but the description sounds very much like the description of the FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenGadgetExecution feature ... and it doesn't highlight so clearly what the Feature really is about: supporting push communication with gadgets running on a client browser from the server. My suggested id, goal and description. Id: FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushCommunicationToClientGadgetsFromServers Goal: Applications and Services running at the backend should be able to push data to gadgets running at browser clients Description: Certain applications may require that backend services be able to push data into Gadgets that are part of a mashup application running on a client browser. This requires both an html5 javascript pub/sub API in the client side, and the corresponding server side pub/sub API. It also requires a pub/sub middleware to be plugged in the Execution Engine (i.e. a plugin architecture in the Execution Engine) FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured Feature: The description of this features should be clearly enhanced. It should elaborate on why we believe it's useful to introduce semantics and, besides, what semantics are we going to typically exploit in an environment like the one proposed. FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation Feature: same as previous. Please provide more info. FIWARE.FEATURE.Apps.CompositionEditor.CreateComposition Feature: I would rename this as FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMComposition to distinguish it from the compositions based on the DT asset ... Regarding the following Features, I would label the kind of composition supported some way to make it clear that we are not talking about any sort of composition (kind of meta-feature applicable to all composition paradigms supported) but the kind of composition based on the DT asset, which is what they are as far as I understand. ? FIWARE.FEATURE.Apps.CompositionEditor.Compose ? FIWARE.FEATURE.Apps.CompositionEditor.Install ? FIWARE.FEATURE.Apps.CompositionEditor.Test FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the goal so that it says "Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format On 25/07/12 09:08, Juanjo Hierro wrote: Dear Uwe and Torsten, Please find my comments regarding revision/addition of Features linked to GEs in the Apps Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Please forward this to the people of your team involved so that they can start working on a revised version of the Features addressing the comments. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. I have left USDL apart because I do not consider it a GE itself. 2. Service Repository Taking a look at the User Stories derived from the single defined Feature that you provide ( FIWARE.FEATURE.Apps.USDL.BasicRepositoryService) , we would get an enough complete overview of the functionality that the GE supports. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. If you go for keeping the existing Feature, certainly the Goal description doesn't follow the guidelines we defined long time ago (see Project Handbook, https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki). Assuming that you have defined Features that are 1:1 linked to User Stories, I believe you have to review the description of FIWARE.STORY.Apps.Repository.RepositorySearch to clarify what do you mean by "OpenSearch" ("... The search functionality should be described by OpenSearch.") It is not clear what is the difference between FIWARE.STORY.Apps.Repository.ListServiceDescriptions and FIWARE.STORY.Apps.Repository.RepositorySearch looking at their description, which means that they probably should be refined. 3. Registry There are no Features linked to this GE. Most probably because we would be in a situation similar to Service Repository. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. 4. Marketplace Generally speaking, Goal description didn't follow the guidelines defined long time ago (again, see established guidelines) FIWARE.FEATURE.Apps.Marketplace.FulltextSearch Feature: It would be nice to describe how keywords are created/assigned/linked to services. Minor suggestion ... Shouldn't the feature be identified as "KeywordSearch" or "TextKeywordSearch" rather than "FulltextSearch" ? FIWARE.FEATURE.Apps.Marketplace.StoreManagement Feature: I would suggest to elaborate in the description how are Stores going to be registered ... Is it about registering the URL linked to a Store against which users/applications will be able to issue requests linked to the Store API ? FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature: Little is said about Offerings in the description as to be able to rightfully label this as a Feature. Are we providing enough level of detail as to understand this could be implemented in the course of a single minor Release (i.e., three months) ? One of the things I would expect to see is a high-level description of what an Offering would be ... what attributes it would have, etc FIWARE.FEATURE.Apps.Marketplace.UserManagement Feature: typo saying "rolse" instead of "role". Seems like the description was a copy&paste of the description of the FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature ... 5. Store I wonder then what we are going to deliver here for the first Release once it is clear that Ericsson won't deliver the eStore ... My understanding was that the gap was going to be covered by the UPM ... but I don't know what's the status and it seems you haven't updated the backlog in this respect ... Could you elaborate on the matter ? 6. Revenue Sharing FIWARE.FEATURE.Apps.RSSS.RSSModelManagement Feature: * On one hand it is said that "Revenue Sharing must support the management of revenue sharing models." but on the other hand, it is said that "Just percentage algorithm is supported." It is unclear what we mean when we say "just" ... Does it mean that we are ONLY going to support models defined based on percentage algorithms now and forever, or that we are going to support only percentage algorithms in the second major release (when this GE is planned to be delivered for the first time) but this may be extended in future releases ? If it is the first case, then I would avoid saying "just" and say something like "each revenue sharing model will map into an algorithm for calculating revenues among involved parties", for example. If it is the second case, then I would suggest defining an Epic that has to maps to the need to support the manage of multiple revenue sharing models in general (we can indeed identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement) and then use the current Feature to elaborate on the management of revenue sharing models using percentage algorithms, changing the Id accordingly (to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FixedPercentageRSSModels, for example) * Notwithstanding the above, I believe that the description of the this Feature should be enriched: * If each Revenue Sharing Model maps into an algorithm that establishes what is the % of the revenues that is assigned to each party, then I would clearly say so. * I would explain that the User will have means to provision/register the algorithm assigned to each model * I would elaborate on what kind of algorithms will be supported. Looking at the definition of the FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision User Story later on, it seems like the will be algorithms that will establish a % that gets fixed over time but there will be also algorithms that enable to change these % dynamically FIWARE.FEATURE.Apps.RSSS.CDRsReception Feature: It would be worth explaining (in the description) what short of mechanisms are going to be supported for CDRs Reception. Is it going to be through an API that enables to submit CDRs in real time on an individual basis ? Are we going to allow submission of CDRs using files ? We don't need to enter in the details of course (signature of operations, format of files) but give an overall description of what mechanisms are going to be supported. FIWARE.FEATURE.Apps.RSSS.RSSCalculation Feature: * It would be worth describing (in the description) whether calculation takes place in batches or recalculation is performed real-time in parallel to reception of CDRs. Also whether "hot" updates of algorithms definitions is going to be supported or not: are we going to have operations to "pause" calculation for a given number of commercialized services because we have changed the way revenue share is calculated or should we stop the complete system ? things like that. * I wonder whether this Features shouldn't be merged with the FIWARE.FEATURE.Apps.RSSS.RSSCalcAggrBased. I would keep them separate if we are going to support different methods of calculation (e.g., both based on batch calculation but also incremental). But if it is always incremental, why don't merging them. FIWARE.FEATURE.Apps.RSSS.FlexibleRSSAlgorithms Feature: I would try to elaborate here what is going to be possible or not. Maybe this depends on what the BM&BE GE will provide because that GE is the one that would provide tools to define the different algorithms based on, for example, defined templates. If so, it would be worth mentioning it. FIWARE.FEATURE.Apps.RSSS.CDRAggregations: It seems like the goal from the previous Feature has been copied&pasted here. The description seems to be appropriate but the goal doesn't. FIWARE.FEATURE.Apps.RSSS.Vouchers Feature: It had to read the description several times to get a relatively clear view of the Feature. I would suggest some editorial changes that maybe would improve the understanding: The RSS will calculate the RS taking usage of vouchers into account. There will be no RS generated when the user of an application/service acquires a voucher, only the uses of the voucher will generate incomes for the providers of the application/services. RSS will calculate a cost per usage by dividing the cost of the voucher by the total number of uses it contains. As the cost of the voucher might change every time it is renewed, the RSS will store each new acquisition price and establish a relationship between every voucher usage and the corresponding acquisition. (note: shouldn't 'a cost' marked in red be replaced by 'the total revenue (to be shared)' ?) Last but not least, if some User Stories were derived as a result of elaborating the Features, it would be nice to reflect that relationship in the Id as we have adopted as convention in many other GEs. If, for example, FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision is related to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement, then identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FlexibleRSSAlgorithmProvision. 7. Composition I will treat this in a separate email. 8. Mediator Description of the following Mediator features are rather poor. I wonder whether a minimal peer review by someone else (WP Leader ?) has been passed: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration One may think that a better clue of what is being described could be obtained after reading the description of the Architecture of the Mediator GE (part of FI-WARE Architecture and Open Specifications), however this is not the case. As an example, you simply try to search for the words 'semantic', 'BPMN' or 'BPEL' in the wiki page linked to description of the Architecture of the Mediator GE. Therefore, it is almost imposible to get a clue of what these features are about. Of course, the text provided as Goal or description doesn't help at all: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation: DataFlow Mediation based on semantic exact matching and subsuption (Goal) Data mapping of elements in the I/O that are similar (Description) * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation: DataFlow Mediation based on semantic plugin and intersection (Goal) Advanced data mapping of elements in the I/O that ara not exactly matched. (Description) * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling: DataFlow Mediation based on semantic plugin and interseaction (Goal, same as previous Feature but now with typo) Advanced data mapping of elements in the I/O that ara not exactly matched (Description, same as previous) * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration: Get a BPMN2.0 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration: Get a BPEL1.2 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) One misses Features that somehow may align with description of the Architecture of the GE ... e.g., ability to create and manage the lifecycle of Mediation Tasks, Dynamic Mediation Tasks ... the ability to create chains of mediation tasks ... the provision of proxies and endpoints ... but nothing is there. One can intuitively understand what kind of functionality may be supported by the Mediator GE when reviewing the following Features: * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2REST * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2POX * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.TCP2HTTP However, all kind of questions come to my mind when trying to understand how this may work. Is it a WSDL generated in the case of the SOAP2REST or SOAP2POX cases ? How is it generated ? Is there a tool that generates the code of a mediation task based on description of a particular REST API (i.e., a different mediation task is generated per REST interface) ? Or are we talking about some sort of generic mediation task that processes configuration data generated per particular REST API ? How is the description of a REST API provided ? (all of us know that there is nothing like a WSDL in REST) They should be answered somewhere ... if in the Architecture wiki page, then you should at least include a reference (link) in the description here. The owners of this GE responsible of the Features above have to seriously revise description of Features for this GE because it is a clear candidate for rejection. Regarding the FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.Security Feature, it is more or less clear what it does despite its usage will be rather limited, given the fact that most of the APIs provided by GEs in FI-WARE are REST. ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From chatelp at gmail.com Fri Jul 27 12:13:23 2012 From: chatelp at gmail.com (Pierre Chatel) Date: Fri, 27 Jul 2012 12:13:23 +0200 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782046C0348093@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> <1491C91A94302A448D73CD9C6B7A782046C0348093@DEWDFECCR02.wdf.sap.corp> Message-ID: Dear WP3 colleagues, I think there is an error in the deliverable tracking table, shared as a Google Doc. It is stated that THALES provides a "Mediation" Generic Enabler that is distinct from the "Mediator" GE. In fact, this is not the case. *We will provide, and are currently implementing "Dynamic Mediation Tasks" that will be integrated in the "Mediator GE", in fact we even participated to the redaction of the "Mediator GE Open RESTful API" document that defines those specific tasks*. THALES' asset, SETHA2, will be provided to FI-WARE* in the Mediator GE*, through these specific tasks, and *not as a separate GE*. I'm sorry if it was not clarified sooner since we didn't participate to last confcall, but we did ironed-out all these aspects with TI beforehand. So I made the assumption that TI would pass on the message on our behalf for this. So, in the end, when THALES will have implemented its dynamic mediation tasks, this will be integrated Mediation GE, probably via TI's own asset, that also complies to the Open Specification, but that will provide a more general framework for execution of the tasks. Please TI correct me if I'm wrong*. This is also the reason why Thales is not advanced on the Testbed aspect since we needed to have the Open Specification clarified before doing any actual glue code between our asset and what should be compliant to the Open Spec on Dynamic Mediation Tasks.* I also add 2 Thales collaborators in CC of this email, since I'm leaving for holidays, please include them in any further communications. Best regards, Pierre. On Tue, Jul 24, 2012 at 4:37 PM, Riss, Uwe wrote: > Dear WP3 Colleagues, > > Please find the access to the minutes of today?s conf call here: > > * > https://forge.fi-ware.eu/docman/view.php/12/1195/2012-07-24-FI-WARE_Minutes.doc > * > > The FI-WARE Apps wiki page for our planning can be found here: > > *https://forge.fi-ware.eu/plugins/mediawiki/wiki/apps/index.php/Main_Page* > > Please check whether you appear in the participant list and whether the > minutes are complete. > > Best regards, > Uwe > > > *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 | F +49 6227 78-26158 | M +49 151 16810936 > | mailto: *uwe.riss at sap.com* > *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. > > > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Fri Jul 27 12:33:34 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Fri, 27 Jul 2012 12:33:34 +0200 Subject: [Fiware-apps] Contact during holidays In-Reply-To: <84DE6B7638096349804AC8EC332FE1245920E727FA@ESESSCMS0361.eemea.ericsson.se> References: <84DE6B7638096349804AC8EC332FE1245920E727FA@ESESSCMS0361.eemea.ericsson.se> Message-ID: Hi all, Perhaps it would be useful to share our holidays. I'm on holidays for the next three weeks with limited access to mail. Best regards, Javier 2012/7/26 Calin Curescu > Dear all, > > During these last push days I would like to make you all aware that I am > on holidays with limited access to mail, which I will still try to read > when I can 1-3 days delay. Mathieu is still in the office though. On urgent > matters please call me on my work phone: +46761153352. > > BR, > Calin > _______________________________________________ > 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesus.gorronogoitia at atosresearch.eu Fri Jul 27 12:41:12 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Fri, 27 Jul 2012 12:41:12 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter (Part II) In-Reply-To: References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <50118918.8000505@tid.es> Message-ID: <1343385672.2925.2.camel@avalon.atos.net> Dear All, i have reacted to the comments related to our GE. Next week neither Miguel nor me will be available. Miguel will come from his holidays after next week and for sure he will react promptly to any pending issue. Regards. Yosu On Fri, 2012-07-27 at 11:26 +0200, Leidig, Torsten wrote: > FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured Feature: The > description of this features should be clearly enhanced. It should > elaborate on why we believe it's useful to introduce semantics and, > besides, what semantics are we going to typically exploit in an > environment like the one proposed. > > FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation > Feature: same as previous. Please provide more info. > > FIWARE.FEATURE.Apps.CompositionEditor.CreateComposition Feature: I > would rename this as > FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMComposition to > distinguish it from the compositions based on the DT asset ... ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ From torsten.leidig at sap.com Mon Jul 30 09:16:57 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 30 Jul 2012 09:16:57 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: <5015BB44.9060005@tid.es> References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> Message-ID: Dear WP3 Partners, There are still issues with the Chapter Backlog as outlined by Juanjo below. Please revisit the specific parts and make the changes if possible or answer to Juanjos questions/demand. Best regards, Torsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Monday, July 30, 2012 12:38 AM To: Leidig, Torsten; Riss, Uwe Cc: Juanjo Hierro; Miguel Carrillo Subject: Re: Comments on Features linked to GEs in the Apps Chapter Hi, Please find between lines my revision on how comments have been addressed. There are some comments regarding Features of some GEs that have not been addressed at all. I always believe that when someone takes some time to carry out a peer review of your stuff, you should at least provide a reaction to his comments. Ignoring peer reviews may well justify some rejection of person*months, at least those you should have devoted to respond to that peer review (either rejecting comments with some rationale or incorporating changes based on comments) ... despite they may be minor. I would like to hear your opinion. Best regards, -- Juanjo On 25/07/12 09:08, Juanjo Hierro wrote: Dear Uwe and Torsten, Please find my comments regarding revision/addition of Features linked to GEs in the Apps Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Please forward this to the people of your team involved so that they can start working on a revised version of the Features addressing the comments. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. I have left USDL apart because I do not consider it a GE itself. 2. Service Repository Taking a look at the User Stories derived from the single defined Feature that you provide ( FIWARE.FEATURE.Apps.USDL.BasicRepositoryService) , we would get an enough complete overview of the functionality that the GE supports. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. If you go for keeping the existing Feature, certainly the Goal description doesn't follow the guidelines we defined long time ago (see Project Handbook, https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki). I still believe that referring to a single feature in the Technical Roadmap deliverable will look awful but you apparently disagree ... Assuming that you have defined Features that are 1:1 linked to User Stories, I believe you have to review the description of FIWARE.STORY.Apps.Repository.RepositorySearch to clarify what do you mean by "OpenSearch" ("... The search functionality should be described by OpenSearch.") This comment has not been addressed. Still a stakeholder (e.g., a UC project) won't understand what you refer to when you talk about "OpenSearch" It is not clear what is the difference between FIWARE.STORY.Apps.Repository.ListServiceDescriptions and FIWARE.STORY.Apps.Repository.RepositorySearch looking at their description, which means that they probably should be refined. Not clear whether this comment was addressed looking at the history, but reading what is there, I believe the difference is more or less clear. 3. Registry There are no Features linked to this GE. Most probably because we would be in a situation similar to Service Repository. Please consider implementing any of the suggested solutions described in the email on General Comments sent to all chapter leaders (section 1.4), particularly that of cloning User Stories as Features. Not addressed. 4. Marketplace Generally speaking, Goal description didn't follow the guidelines defined long time ago (again, see established guidelines) FIWARE.FEATURE.Apps.Marketplace.FulltextSearch Feature: It would be nice to describe how keywords are created/assigned/linked to services. Minor suggestion ... Shouldn't the feature be identified as "KeywordSearch" or "TextKeywordSearch" rather than "FulltextSearch" ? Not addressed, though not critical. Did you disagree ? FIWARE.FEATURE.Apps.Marketplace.StoreManagement Feature: I would suggest to elaborate in the description how are Stores going to be registered ... Is it about registering the URL linked to a Store against which users/applications will be able to issue requests linked to the Store API ? Addressed. FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature: Little is said about Offerings in the description as to be able to rightfully label this as a Feature. Are we providing enough level of detail as to understand this could be implemented in the course of a single minor Release (i.e., three months) ? One of the things I would expect to see is a high-level description of what an Offering would be ... what attributes it would have, etc Addressed FIWARE.FEATURE.Apps.Marketplace.UserManagement Feature: typo saying "rolse" instead of "role". Seems like the description was a copy&paste of the description of the FIWARE.FEATURE.Apps.Marketplace.OfferingManagement Feature ... Addressed 5. Store I wonder then what we are going to deliver here for the first Release once it is clear that Ericsson won't deliver the eStore ... My understanding was that the gap was going to be covered by the UPM ... but I don't know what's the status and it seems you haven't updated the backlog in this respect ... Could you elaborate on the matter ? This is still not clear to me ... but let's handle that separately 6. Revenue Sharing FIWARE.FEATURE.Apps.RSSS.RSSModelManagement Feature: * On one hand it is said that "Revenue Sharing must support the management of revenue sharing models." but on the other hand, it is said that "Just percentage algorithm is supported." It is unclear what we mean when we say "just" ... Does it mean that we are ONLY going to support models defined based on percentage algorithms now and forever, or that we are going to support only percentage algorithms in the second major release (when this GE is planned to be delivered for the first time) but this may be extended in future releases ? If it is the first case, then I would avoid saying "just" and say something like "each revenue sharing model will map into an algorithm for calculating revenues among involved parties", for example. If it is the second case, then I would suggest defining an Epic that has to maps to the need to support the manage of multiple revenue sharing models in general (we can indeed identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement) and then use the current Feature to elaborate on the management of revenue sharing models using percentage algorithms, changing the Id accordingly (to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FixedPercentageRSSModels, for example) * Notwithstanding the above, I believe that the description of the this Feature should be enriched: * If each Revenue Sharing Model maps into an algorithm that establishes what is the % of the revenues that is assigned to each party, then I would clearly say so. * I would explain that the User will have means to provision/register the algorithm assigned to each model * I would elaborate on what kind of algorithms will be supported. Looking at the definition of the FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision User Story later on, it seems like the will be algorithms that will establish a % that gets fixed over time but there will be also algorithms that enable to change these % dynamically FIWARE.FEATURE.Apps.RSSS.CDRsReception Feature: It would be worth explaining (in the description) what short of mechanisms are going to be supported for CDRs Reception. Is it going to be through an API that enables to submit CDRs in real time on an individual basis ? Are we going to allow submission of CDRs using files ? We don't need to enter in the details of course (signature of operations, format of files) but give an overall description of what mechanisms are going to be supported. FIWARE.FEATURE.Apps.RSSS.RSSCalculation Feature: * It would be worth describing (in the description) whether calculation takes place in batches or recalculation is performed real-time in parallel to reception of CDRs. Also whether "hot" updates of algorithms definitions is going to be supported or not: are we going to have operations to "pause" calculation for a given number of commercialized services because we have changed the way revenue share is calculated or should we stop the complete system ? things like that. * I wonder whether this Features shouldn't be merged with the FIWARE.FEATURE.Apps.RSSS.RSSCalcAggrBased. I would keep them separate if we are going to support different methods of calculation (e.g., both based on batch calculation but also incremental). But if it is always incremental, why don't merging them. FIWARE.FEATURE.Apps.RSSS.FlexibleRSSAlgorithms Feature: I would try to elaborate here what is going to be possible or not. Maybe this depends on what the BM&BE GE will provide because that GE is the one that would provide tools to define the different algorithms based on, for example, defined templates. If so, it would be worth mentioning it. FIWARE.FEATURE.Apps.RSSS.CDRAggregations: It seems like the goal from the previous Feature has been copied&pasted here. The description seems to be appropriate but the goal doesn't. FIWARE.FEATURE.Apps.RSSS.Vouchers Feature: It had to read the description several times to get a relatively clear view of the Feature. I would suggest some editorial changes that maybe would improve the understanding: The RSS will calculate the RS taking usage of vouchers into account. There will be no RS generated when the user of an application/service acquires a voucher, only the uses of the voucher will generate incomes for the providers of the application/services. RSS will calculate a cost per usage by dividing the cost of the voucher by the total number of uses it contains. As the cost of the voucher might change every time it is renewed, the RSS will store each new acquisition price and establish a relationship between every voucher usage and the corresponding acquisition. (note: shouldn't 'a cost' marked in red be replaced by 'the total revenue (to be shared)' ?) Last but not least, if some User Stories were derived as a result of elaborating the Features, it would be nice to reflect that relationship in the Id as we have adopted as convention in many other GEs. If, for example, FIWARE.STORY.Apps.RSSS.FlexibleRSSAlgorithmProvision is related to FIWARE.FEATURE.Apps.RSSS.RSSModelManagement, then identify it as FIWARE.FEATURE.Apps.RSSS.RSSModelManagement.FlexibleRSSAlgorithmProvision. Pablo sent me a report on how the different comments were addressed, so I actually consider them addressed 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. Not addressed. FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions Feature: Is this still in place ? I'm not pretty sure so I preferred to ask :-) If still applies, I definitively would like to see a description of what those sort of extensions would be. Note that if we have classified this as a Feature, is because we bet it can be implemented in the course of 3 Sprints, so it should be already designed/discussed to enough level of detail as to be able to assume such estimation ... If not, then it should be an Epic (and even though in a higher level, it should still give some clue about what sort of extensions we are talking about) Not addressed. FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition Feature: I would rename this Feature so that the relationship with the previous FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenGadgetExecution feature becomes more evident. I have changed the Goal to enhance the fact that we target end users that can design mashups without programming skills. I would also enhance the existing description to highlight the relationship. My suggested description: End users can create new applications, also referred as mashups, by wiring UI components called widgets/gadgets searched and selected from a catalog. Those gadgets can communicate between themselves at runtime based on the Event-driven Gadget communication mechanism supported by the Execution Engine. End users can also import mashups defined by other users as whole, either from the catalog or from a mashup description file in MDL. Imported mashups can be enhanced by adding new gadgets from the catalog that may be wired together with the gadgets in the original mashup. Last but not least, the user can store the resulting composite app in the catalog for reuse. Note that this description is large enough so that we may have split this Feature into several, but I can live keeping just one, provided the description is complete. Addressed. FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushDrivenWiring Feature: I may be wrong, but the description sounds very much like the description of the FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenGadgetExecution feature ... and it doesn't highlight so clearly what the Feature really is about: supporting push communication with gadgets running on a client browser from the server. My suggested id, goal and description. Id: FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushCommunicationToClientGadgetsFromServers Goal: Applications and Services running at the backend should be able to push data to gadgets running at browser clients Description: Certain applications may require that backend services be able to push data into Gadgets that are part of a mashup application running on a client browser. This requires both an html5 javascript pub/sub API in the client side, and the corresponding server side pub/sub API. It also requires a pub/sub middleware to be plugged in the Execution Engine (i.e. a plugin architecture in the Execution Engine) Apparently not addressed. FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured Feature: The description of this features should be clearly enhanced. It should elaborate on why we believe it's useful to introduce semantics and, besides, what semantics are we going to typically exploit in an environment like the one proposed. Addressed. FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation Feature: same as previous. Please provide more info. Addressed FIWARE.FEATURE.Apps.CompositionEditor.CreateComposition Feature: I would rename this as FIWARE.FEATURE.Apps.CompositionEditor.CreateBPMComposition to distinguish it from the compositions based on the DT asset ... Regarding the following Features, I would label the kind of composition supported some way to make it clear that we are not talking about any sort of composition (kind of meta-feature applicable to all composition paradigms supported) but the kind of composition based on the DT asset, which is what they are as far as I understand. FIWARE.FEATURE.Apps.CompositionEditor.Compose FIWARE.FEATURE.Apps.CompositionEditor.Install FIWARE.FEATURE.Apps.CompositionEditor.Test Not addressed. FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the goal so that it says "Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format Not addressed 8. Mediator Description of the following Mediator features are rather poor. I wonder whether a minimal peer review by someone else (WP Leader ?) has been passed: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration One may think that a better clue of what is being described could be obtained after reading the description of the Architecture of the Mediator GE (part of FI-WARE Architecture and Open Specifications), however this is not the case. As an example, you simply try to search for the words 'semantic', 'BPMN' or 'BPEL' in the wiki page linked to description of the Architecture of the Mediator GE. Therefore, it is almost imposible to get a clue of what these features are about. Of course, the text provided as Goal or description doesn't help at all: * FIWARE.FEATURE.Apps.Mediation.SemanticDataMediation: DataFlow Mediation based on semantic exact matching and subsuption (Goal) Data mapping of elements in the I/O that are similar (Description) * FIWARE.FEATURE.Apps.Mediation.AdvancedSemanticDataMediation: DataFlow Mediation based on semantic plugin and intersection (Goal) Advanced data mapping of elements in the I/O that ara not exactly matched. (Description) * FIWARE.FEATURE.Apps.Mediation.RunTimeProcessModelling: DataFlow Mediation based on semantic plugin and interseaction (Goal, same as previous Feature but now with typo) Advanced data mapping of elements in the I/O that ara not exactly matched (Description, same as previous) * FIWARE.FEATURE.Apps.Mediation.BPMN20CompliantFileGeneration: Get a BPMN2.0 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) * FIWARE.FEATURE.Apps.Mediation.BPEL1.2CompliantFileGeneration: Get a BPEL1.2 fully compliant file (Goal, one quickly ask himself 'for what ?') Completing BPMN2.0 file (Description) One misses Features that somehow may align with description of the Architecture of the GE ... e.g., ability to create and manage the lifecycle of Mediation Tasks, Dynamic Mediation Tasks ... the ability to create chains of mediation tasks ... the provision of proxies and endpoints ... but nothing is there. One can intuitively understand what kind of functionality may be supported by the Mediator GE when reviewing the following Features: * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2REST * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.SOAP2POX * FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.TCP2HTTP However, all kind of questions come to my mind when trying to understand how this may work. Is it a WSDL generated in the case of the SOAP2REST or SOAP2POX cases ? How is it generated ? Is there a tool that generates the code of a mediation task based on description of a particular REST API (i.e., a different mediation task is generated per REST interface) ? Or are we talking about some sort of generic mediation task that processes configuration data generated per particular REST API ? How is the description of a REST API provided ? (all of us know that there is nothing like a WSDL in REST) They should be answered somewhere ... if in the Architecture wiki page, then you should at least include a reference (link) in the description here. The owners of this GE responsible of the Features above have to seriously revise description of Features for this GE because it is a clear candidate for rejection. Regarding the FIWARE.FEATURE.Apps.Mediation.ProtocolMediation.Security Feature, it is more or less clear what it does despite its usage will be rather limited, given the fact that most of the APIs provided by GEs in FI-WARE are REST. As far as I understand, none of the comments have been addressed ... I would like to understand what your position is on this, overall taking into accout that this was a clear candidate for rejection ... ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfernandez at fi.upm.es Mon Jul 30 10:19:01 2012 From: rfernandez at fi.upm.es (=?ISO-8859-1?Q?Rafael_Fern=E1ndez?=) Date: Mon, 30 Jul 2012 10:19:01 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> Message-ID: Dear Torsten, We (UPM) fully agree with Juanjo's comments regarding the following features: - FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition, - FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenWidgetExecution, and - FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushCommunicationToClientWidgetsFromServers So we have addressed them. Best regards, Rafa. -- *Dr. Rafael Fern?ndez* Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Mon Jul 30 11:25:20 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Mon, 30 Jul 2012 11:25:20 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> Message-ID: Dear all, Apart from this, I want to stress that we fully agree with Juanjo in that it would be easier to declare that we go for supporting different GEs per "composition paradigm" we want to support. Easier from the viewpoint of APIs, Open Specs and Catalogue. But I don't want to open this discussion again, unless Ericsson or SAP do. I give you all my opinion (UPM's) just in case you find it useful. Best regards, Javier 2012/7/30 Rafael Fern?ndez > Dear Torsten, > > We (UPM) fully agree with Juanjo's comments regarding the following > features: > > - > FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition, > - FIWARE.FEATURE.Apps.ExecutionEngine.SupportEventDrivenWidgetExecution, > and > - > FIWARE.FEATURE.Apps.ExecutionEngine.SupportPushCommunicationToClientWidgetsFromServers > > So we have addressed them. > > Best regards, > Rafa. > > -- > *Dr. Rafael Fern?ndez* > Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software > Facultad de Inform?tica - Universidad Polit?cnica de Madrid > Campus Internacional de Excelencia Montegancedo > 28660 - Boadilla del Monte, Madrid > Spain > > > _______________________________________________ > 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 ************************************************ --------------------- 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.hutschemaekers at ericsson.com Mon Jul 30 14:00:15 2012 From: mathieu.hutschemaekers at ericsson.com (Mathieu Hutschemaekers) Date: Mon, 30 Jul 2012 14:00:15 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> Message-ID: <666A6B6D38439F49A7FB8E0FE839CA06355682C8CD@ESESSCMS0365.eemea.ericsson.se> Dear all, In Calin's absence I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far reaching as expected. 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: * FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured * FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation * FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure I know that the original intention of 'C3' was to indicate Ericsson specific items. So I changed them to indicate 'ECE' now. Since I am not sure whether all partners want to support all the items in your list we have to consider that separately. FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. At the moment the idea is that the composition editor works against the marketplace who could cover a number of stores and, in that way, a number of repositories. I do not see the need to include a separate item to work against multiple repositories. FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the goal so that it says "Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.hutschemaekers at ericsson.com Mon Jul 30 14:09:04 2012 From: mathieu.hutschemaekers at ericsson.com (Mathieu Hutschemaekers) Date: Mon, 30 Jul 2012 14:09:04 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> Message-ID: <666A6B6D38439F49A7FB8E0FE839CA06355682C8D6@ESESSCMS0365.eemea.ericsson.se> Dear all, (apologies for the premature, incomplete first mail. Please ignore.) In Calin's absence I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far-reaching as expected. If the suggested changes are not (fully) implemented, I provide in-lined comments. I now see that all items are covered, one way or other, with the exception of FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: * FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured * FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation * FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure I know that the original intention of 'C3' was to indicate Ericsson specific items. So I changed them to indicate 'ECE' now. Since I am not sure whether all partners want to support all the items in your list we have to consider that separately. FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. At the moment the idea is that the composition editor works against the marketplace who could cover a number of stores and, in that way, a number of repositories. I do not see the need to include a separate item to work against multiple repositories. FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product I changed the goal, but will consider the suggestion about the document (no such document readily available). FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the goal so that it says "Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format I changed the goal, but will consider the suggestion about the document (no such document readily available). -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Mon Jul 30 19:19:15 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 30 Jul 2012 19:19:15 +0200 Subject: [Fiware-apps] FW: Review prior to delivery In-Reply-To: <5016983E.8040706@tid.es> References: <5016983E.8040706@tid.es> Message-ID: We are converging... Seems to be one blocker for the Light Semantic Composition Regards, Torsten PS: tomorrow I would like to have a complete final overview of the software status: a) Where is the software uploaded for the reviewers or users (depending whether it is PP or not) b) Is the software installed in the testbed? c) Do you have a virtual host for the enabler, assigned by the testbed people? d) Is the software installed on the owners premise? e) Is the enabler described in the catalog including the information according to the instance endpoint (service address)? If you are for some hard to understand reasons not in the call tomorrow, please answer the questions via email right away. From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Monday, July 30, 2012 4:21 PM To: Leidig, Torsten; Riss, Uwe Cc: JUAN JOSE HIERRO SUREDA Subject: Review prior to delivery Dear Torsten and Uwe, My review was more targeted this time. I just scanned through the wiki and how changes requested have been made there. Mostly satisfactory with one single rejection that stands but it looks not too difficult to address * Features - this is Juanjo's :) * Unit testing - ok, you can generate the pdf (or not, depends on the situation of the Features ... read on) * I had to edit a few things as they were not 100% compliant - nothing particularly radical * I wonder if the changes in the features requested by Juanjo could imply the addition of new Features and therefore new unit tests ... * Install guide - rejected * a previous comment was ignored (see attached file) - it looks like it is easy to fix * User guide - ok, you can generate the pdf * Torsten, can you briefly comment on the status of the code? (a brief comment per GE - stating also the ones that will be offered as PP) Once this is done, you can start moving stuff to the public wiki. B.R. Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_1.0_b_WP3.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12000 bytes Desc: Audit_Release_1.0_b_WP3.xlsx URL: From calin.curescu at ericsson.com Mon Jul 30 23:16:21 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Mon, 30 Jul 2012 23:16:21 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: <666A6B6D38439F49A7FB8E0FE839CA06355682C8D6@ESESSCMS0365.eemea.ericsson.se> References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> <666A6B6D38439F49A7FB8E0FE839CA06355682C8D6@ESESSCMS0365.eemea.ericsson.se> Message-ID: <84DE6B7638096349804AC8EC332FE1245920F3C28C@ESESSCMS0361.eemea.ericsson.se> Dear Juanjo, Torsten, Please find some answers to several Features regarding Composition that we took care of. Mathieu did some changes and I added some too. Please find my additions with green below. As a generic comment I think it's a relevant proposal to have different GEs for the compositions flavors, but this we will discuss only after the 1st year review is finished, it would not be good to rush it. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Mathieu Hutschemaekers Sent: den 30 juli 2012 14:09 To: 'fiware-apps at lists.fi-ware.eu' Subject: Re: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter Dear all, (apologies for the premature, incomplete first mail. Please ignore.) In Calin's absence I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far-reaching as expected. If the suggested changes are not (fully) implemented, I provide in-lined comments. I now see that all items are covered, one way or other, with the exception of FIWARE.FEATURE.Apps.CompositionEditor.IoTBPMNExtensions 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: * FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured * FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation * FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure I know that the original intention of 'C3' was to indicate Ericsson specific items. So I changed them to indicate 'ECE' now. Since I am not sure whether all partners want to support all the items in your list we have to consider that separately. Regarding the "semantic" features above: Only Atos work deals with special semantic task transformation, thus the 2 fatures cannot be transferred to the other Composition Editors. Regarding "common" features, I agree they exist and we should uniformize them, but we can more formally on this after this review. For the time being, there are two Features that all the editors need to do: Import/Export to/from USDL repository, and search services from the Marketplace. The "USDL" feature above I have change to represent both import/export. The feature below I created to represent the search in the Marketplace. This answers also your concern on federation, the Marketplace is federating several USDL repositories. To show this I put the name "common" in the 2 features. Thus: FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonRepositoryImportExport and FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonSearchInMarketplace FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. At the moment the idea is that the composition editor works against the marketplace who could cover a number of stores and, in that way, a number of repositories. I do not see the need to include a separate item to work against multiple repositories. A marketplace is federating service from several USDL repositories, thus a composition editor will compose services from several repositories and/or several business entities. See change of name in answer above. FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product I changed the goal, but will consider the suggestion about the document (no such document readily available). A pointer to such a document (ECE user guide) has been added. FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the goal so that it says "Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format I changed the goal, but will consider the suggestion about the document (no such document readily available). This is considered internally for future addition. -------------- next part -------------- An HTML attachment was scrubbed... URL: From calin.curescu at ericsson.com Mon Jul 30 23:19:43 2012 From: calin.curescu at ericsson.com (Calin Curescu) Date: Mon, 30 Jul 2012 23:19:43 +0200 Subject: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter In-Reply-To: <84DE6B7638096349804AC8EC332FE1245920F3C28C@ESESSCMS0361.eemea.ericsson.se> References: <500F2187.6090907@tid.es> <500F9B6C.8080202@tid.es> <5015BB44.9060005@tid.es> <666A6B6D38439F49A7FB8E0FE839CA06355682C8D6@ESESSCMS0365.eemea.ericsson.se> <84DE6B7638096349804AC8EC332FE1245920F3C28C@ESESSCMS0361.eemea.ericsson.se> Message-ID: <84DE6B7638096349804AC8EC332FE1245920F3C28D@ESESSCMS0361.eemea.ericsson.se> Dear Horst, Andreas I have changed: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository with: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.FEATURE.Apps.CompositionEditor.CommonRepositoryImportExport See reasons below, /C From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Calin Curescu Sent: den 30 juli 2012 23:16 To: 'fiware-apps at lists.fi-ware.eu'; Juanjo Hierro (jhierro at tid.es); torsten.leidig at sap.com Subject: Re: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter Dear Juanjo, Torsten, Please find some answers to several Features regarding Composition that we took care of. Mathieu did some changes and I added some too. Please find my additions with green below. As a generic comment I think it's a relevant proposal to have different GEs for the compositions flavors, but this we will discuss only after the 1st year review is finished, it would not be good to rush it. BR, /Calin From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Mathieu Hutschemaekers Sent: den 30 juli 2012 14:09 To: 'fiware-apps at lists.fi-ware.eu' Subject: Re: [Fiware-apps] FW: Comments on Features linked to GEs in the Apps Chapter Dear all, (apologies for the premature, incomplete first mail. Please ignore.) I looked at the comments and applied any changes I saw fit. I apologize if the changes are not as far-reaching as expected. If the suggested changes are not (fully) implemented, I provide in-lined comments. I now see that all items are covered, one way or other, with the exception of FIWARE.FEATURE.Apps.CompositionEditor.IoTB 7. Composition First of all, I wanted to clarify whether we are using some sort of convention for ids ... In a first approach it seems like the id of any Feature that applies to the Composition Editor, no matter whether it applies to masup of UI gadgets, composition of backend services using BPM standards or composition of backend services using the ECE platform, is preceded by a 'C3' prefix ... This to distinguish them from Features like FIWARE.FEATURE.Apps.CompositionEditor.CreateUIOrientedServiceComposition which are specific of UI gadgets mashups. However, later I read some features that I would say are also common to all three paradigms ... shouldn't their ids be preceded by a 'C3' ? I'm talking about: * FIWARE.FEATURE.Apps.CompositionEditor.SemanticFeatured * FIWARE.FEATURE.Apps.CompositionEditor.TaskSemanticAnnotation * FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository (this one I'm not pretty sure I know that the original intention of 'C3' was to indicate Ericsson specific items. So I changed them to indicate 'ECE' now. Since I am not sure whether all partners want to support all the items in your list we have to consider that separately. rmal style='margin-bottom:12.0pt'>Regarding the "semantic" features above: Only Atos work deals with special semantic task transformation, thus the 2 fatures cannot be transferred to the other Composition Editors. Regarding "common" features, I agree they exist and we should uniformize them, but we can more formally on this after this review. For the time being, there are two Features that all the editors need to do: Import/Export to/from USDL repository, and search services from the Marketplace. The "USDL" feature above I have change to represent both import/export. The feature below I created to represent the search in the Marketplace. This answers also your concern on federation, the Marketplace is feder tories. To show this I put the name "common" in the 2 features. Thus: FIWARE.FEATURE.Apps.CompositionEditor.PublishCompositionToUSDLRepository is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonRepositoryImportExport and FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService is replaced by: FIWARE.FEATURE.Apps.CompositionEditor.CommonSearchInMarketplace FIWARE.FEATURE.Apps.CompositionEditor.C3BasicSearchUSDLService Feature: I guess it would be worth mentioning whether a given Composition Editor will be able to federate the services in multiple distributed USDL Repositories. I guess it would be nice to support it. Since I guess this will not be supported for the first release, I would go for splitting it into two Features or one Feature and an Epic, the former referring to access to a concrete USDL Repository (i.e., ability to connect to a single one) and the later linked to an extension of future releases to support federation. At the moment the idea is that the composition editor works against the marketplace who could cover a number of stores and, in that way, a number of repositories. I do not see the need to include a separate item to work against multiple repositories.A marketplace is federating service from several USDL repositories, thus a composition editor will compose services from several repositories and/or several business entities. See change of name in answer above. FIWARE.FEATURE.Apps.CompositionEditor.ECE-CreateComposition Feature: I would change the goal so that it says "Creation of an ECE-based Service Composition" for the same reasons I gave with my last comment regarding DT's service composition technology. In the description, I would bind an URL to "... The tool is using Ericsson Composition Editor constructs ..." which points to descriptive documentation of that components of Ericsson's product I changed the goal, but will consider the suggestion about the document (no such document readil style='font-family:"Arial","sans-serif";color:#1F497D'> A pointer to such a document (ECE user guide) has been added. FIWARE.FEATURE.Apps.ExecutionEngine.ECE-ExecuteComposition Feature: I would change the t;Execution of an ECE-based Service Composition" for the same reasons. In the description, I would bind an URL to "...Given a composition description in the Ericsson Composition Format, provide ..." which points to descriptive documentation of the format I changed the goal, but will consider the suggestion about the document (no such document readily available). This is considered internally for future addition. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfernandez at fi.upm.es Mon Jul 30 23:42:54 2012 From: rfernandez at fi.upm.es (=?ISO-8859-1?Q?Rafael_Fern=E1ndez?=) Date: Mon, 30 Jul 2012 23:42:54 +0200 Subject: [Fiware-apps] FW: Review prior to delivery In-Reply-To: References: <5016983E.8040706@tid.es> Message-ID: Dear Torsten, I'm afraid that probably I won't be able to attend our weekly confcall tomorrow due to a sick leave (and Javier is enjoying his holidays) so I prefer to answer this email now, just in case... Please find my answers below: a) **Where is the software uploaded for the reviewers or users > (depending whether it is PP or not) > Our software (Wirecloud Mashup Platform) is stored in the FiWare subversion repository. It can be found both in the /trunk//FI-WARE/Apps/CompositionEditor/Wirecloud and /trunk/FI-WARE/Apps/ExecutionEngine/Wirecloud directories. > **** > > **b) **Is the software installed in the testbed? > Not yet. Hopefully for next week. > **** > > **c) **Do you have a virtual host for the enabler, assigned by the > testbed people? > Yes, 130.206.178.207 > > **** > > **d) **Is the software installed on the owners premise? > N/A > **** > > **e) **Is the enabler described in the catalog including the > information according to the instance endpoint (service address)?**** > > ** > At this moment, our enabler in the catalog links to our own platform deployed in http://wirecloud.conwet.fi.upm.es. However, my understanding is that this URL should be changed to the IP address of our testbed VM. Am I right? Best regards, Rafa -- *Dr. Rafael Fern?ndez* Dept. Lenguajes y Sistemas Inform?ticos e Ingenier?a de Software Facultad de Inform?tica - Universidad Polit?cnica de Madrid Campus Internacional de Excelencia Montegancedo 28660 - Boadilla del Monte, Madrid Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: