From andreas.friesen at sap.com Wed Jun 1 17:12:27 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Wed, 1 Jun 2011 17:12:27 +0200 Subject: [Fiware-apps] Canceled: FI-WARE WP3 weekly call Message-ID: <92E1E76787317A4E876E7A444ABC3902130C305269@DEWDFECCR08.wdf.sap.corp> When: Freitag, 3. Juni 2011 11:00-12:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: telco (via SAP connect) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, as decided in the last telco, we cancel the wekly WP3 telco this Friday, 3.6 Best Andreas Dear All, this is a meeting request to weekly WP3 call starting this Fr. until end of September (M5). You have been invited to join a Web Conference using SAP CONNECT. Invited By: Andreas Friesen To join the meeting, click here: https://sap.emea.pgiconnect.com/d043567/ Participant Passcode:233 065 7669 France, Paris: +33 1 70 99 43 40 tel:+33170994340x2330657669# Germany, Berlin: +49 30 5900 24908 tel:+4930590024908x2330657669# Germany, Frankfurt: +49 69 71044 5497 tel:+4969710445497x2330657669# Italy, Milan: +39 02 3041 0328 tel:+390230410328x2330657669# Netherlands, Amsterdam: +31 20 794 8448 tel:+31207948448x2330657669# Spain, Barcelona: +34 93 545 2564 tel:+34935452564x2330657669# Spain, Madrid: +34 91 790 9567 tel:+34917909567x2330657669# Switzerland, Zurich: +41 43 456 9604 tel:+41434569604x2330657669# 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 Regards, Andreas -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4647 bytes Desc: not available URL: From jesus.gorronogoitia at atosresearch.eu Thu Jun 2 12:02:44 2011 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Thu, 02 Jun 2011 12:02:44 +0200 Subject: [Fiware-apps] Canceled: FI-WARE WP3 weekly call In-Reply-To: <92E1E76787317A4E876E7A444ABC3902130C305269@DEWDFECCR08.wdf.sap.corp> References: <92E1E76787317A4E876E7A444ABC3902130C305269@DEWDFECCR08.wdf.sap.corp> Message-ID: <1307008964.12693.12.camel@linux-gzvm.site> Dear Andreas, So far we have not been contacted by T3.1 Lead, Ericsson, whereby we have not been able to contribute to WP3 T3.1 current tasks. For us it is important to know what is the current work plan in T3.1, including tasks, assigned responsibilities, deadlines, etc. As i assume this work plan has not been defined yet, we want to participate in further discussions to concrete it. This lack of leadership is T3.1 is our particular concern, that should be amended asap. I am a bit concerned that the current specification of generic enablers for M2, in particular what refers to T3.1 (Composition) could not be compatible (or aligned) with Atos expected contributions in FIWARE, in particular what refers to Semi-Automatic Design Time Service Composition, since we have not been requested to contribute to this T3.1 specification. Kind regards Yosu On Wed, 2011-06-01 at 17:12 +0200, Friesen, Andreas wrote: > When: Freitag, 3. Juni 2011 11:00-12:00 (UTC+01:00) Amsterdam, Berlin, > Bern, Rome, Stockholm, Vienna. > Where: telco (via SAP connect) > > Note: The GMT offset above does not reflect daylight saving time > adjustments. > > *~*~*~*~*~*~*~*~*~* > > Dear All, > > as decided in the last telco, we cancel the wekly WP3 telco this > Friday, 3.6 > > Best > Andreas > > Dear All, > > this is a meeting request to weekly WP3 call starting this Fr. until > end of September (M5). > > You have been invited to join a Web Conference using SAP CONNECT. > Invited By: Andreas Friesen > To join the meeting, click here: > https://sap.emea.pgiconnect.com/d043567/ > > Participant Passcode:233 065 7669 > > France, Paris: +33 1 70 99 43 40 tel:+33170994340x2330657669# > Germany, Berlin: +49 30 5900 24908 tel:+4930590024908x2330657669# > Germany, Frankfurt: +49 69 71044 5497 tel: > +4969710445497x2330657669# > Italy, Milan: +39 02 3041 0328 tel:+390230410328x2330657669# > Netherlands, Amsterdam: +31 20 794 8448 tel: > +31207948448x2330657669# > Spain, Barcelona: +34 93 545 2564 tel:+34935452564x2330657669# > Spain, Madrid: +34 91 790 9567 tel:+34917909567x2330657669# > Switzerland, Zurich: +41 43 456 9604 tel:+41434569604x2330657669# > > 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 > > Regards, > Andreas > > > _______________________________________________ > 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 Origin 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 Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, 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 calin.curescu at ericsson.com Thu Jun 2 22:03:10 2011 From: calin.curescu at ericsson.com (Calin Curescu) Date: Thu, 2 Jun 2011 22:03:10 +0200 Subject: [Fiware-apps] Canceled: FI-WARE WP3 weekly call In-Reply-To: <1307008964.12693.12.camel@linux-gzvm.site> References: <92E1E76787317A4E876E7A444ABC3902130C305269@DEWDFECCR08.wdf.sap.corp>, <1307008964.12693.12.camel@linux-gzvm.site> Message-ID: <84DE6B7638096349804AC8EC332FE1241002B5DA06@ESESSCMS0361.eemea.ericsson.se> Dear Yosu, I have recently taken over Ericsson responsibilities in task 3.1, and working my way in. I'll come back on the Atos Composition alignment. Best regards, /Calin ________________________________________ From: Yosu Gorro?ogoitia [jesus.gorronogoitia at atosresearch.eu] Sent: Thursday, June 02, 2011 12:02 PM To: Friesen, Andreas Cc: 'fiware-apps at lists.fi-ware.eu'; Froese, Andreas; Heller, Markus; Bohnert, Thomas Michael; Calin Curescu; Novelli, Francesco; Nuria De-Lama Sanchez; Clara M Pezuela Robles Subject: Re: [Fiware-apps] Canceled: FI-WARE WP3 weekly call Dear Andreas, So far we have not been contacted by T3.1 Lead, Ericsson, whereby we have not been able to contribute to WP3 T3.1 current tasks. For us it is important to know what is the current work plan in T3.1, including tasks, assigned responsibilities, deadlines, etc. As i assume this work plan has not been defined yet, we want to participate in further discussions to concrete it. This lack of leadership is T3.1 is our particular concern, that should be amended asap. I am a bit concerned that the current specification of generic enablers for M2, in particular what refers to T3.1 (Composition) could not be compatible (or aligned) with Atos expected contributions in FIWARE, in particular what refers to Semi-Automatic Design Time Service Composition, since we have not been requested to contribute to this T3.1 specification. Kind regards Yosu On Wed, 2011-06-01 at 17:12 +0200, Friesen, Andreas wrote: > When: Freitag, 3. Juni 2011 11:00-12:00 (UTC+01:00) Amsterdam, Berlin, > Bern, Rome, Stockholm, Vienna. > Where: telco (via SAP connect) > > Note: The GMT offset above does not reflect daylight saving time > adjustments. > > *~*~*~*~*~*~*~*~*~* > > Dear All, > > as decided in the last telco, we cancel the wekly WP3 telco this > Friday, 3.6 > > Best > Andreas > > Dear All, > > this is a meeting request to weekly WP3 call starting this Fr. until > end of September (M5). > > You have been invited to join a Web Conference using SAP CONNECT. > Invited By: Andreas Friesen > To join the meeting, click here: > https://sap.emea.pgiconnect.com/d043567/ > > Participant Passcode:233 065 7669 > > France, Paris: +33 1 70 99 43 40 tel:+33170994340x2330657669# > Germany, Berlin: +49 30 5900 24908 tel:+4930590024908x2330657669# > Germany, Frankfurt: +49 69 71044 5497 tel: > +4969710445497x2330657669# > Italy, Milan: +39 02 3041 0328 tel:+390230410328x2330657669# > Netherlands, Amsterdam: +31 20 794 8448 tel: > +31207948448x2330657669# > Spain, Barcelona: +34 93 545 2564 tel:+34935452564x2330657669# > Spain, Madrid: +34 91 790 9567 tel:+34917909567x2330657669# > Switzerland, Zurich: +41 43 456 9604 tel:+41434569604x2330657669# > > 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 > > Regards, > Andreas > > > _______________________________________________ > 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 Origin 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 Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, 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 andreas.friesen at sap.com Thu Jun 9 13:55:38 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Thu, 9 Jun 2011 13:55:38 +0200 Subject: [Fiware-apps] Agenda for WP3 telco tomorrow Message-ID: <92E1E76787317A4E876E7A444ABC3902130C5FC826@DEWDFECCR08.wdf.sap.corp> Dear All, this week we made significant steps forward in T3.1 and T3.3 so I propose that we discuss the architectures of T3.1 and T3.3 with all partners in WP3 and then make a planning how to complete WP3 M2 contributions until Fr, next week. Introduction T3.1 (Calin Curescu or a representative of T3.1) Introduction T3.3 (Andreas Friesen) Deadlines and responsibilities for M2 contributions Other urgent issues Best regards Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.friesen at sap.com Fri Jun 10 15:23:29 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Fri, 10 Jun 2011 15:23:29 +0200 Subject: [Fiware-apps] An advice how to proceed with T3.1 Message-ID: <92E1E76787317A4E876E7A444ABC3902130C681E40@DEWDFECCR08.wdf.sap.corp> Dear T3.1 partners, we discussed today in the WP3 call the question: "What are generic enablers in T3.1?". I had now a very intensive discussion with Juanjo about this issue and hope that you will perceive the outcome of this discussion as (hopefully) good news. WP3 will provide the business framework infrastructure as a generic enabler to monetize different types of apps/services and their compositions. We believe that it cannot be a responsibility or obligation of FI-WARE (or any other entity) to say what is the best technology for a certain type of composition or mashup so that it would be a major mistake to specify a set of generic enablers prescribing to the outside world an interface or infrastructure to implement a certain composition or mashup capability. Hence, the aim of T3.1 is to develop a rich set of technologies exemplary implementing different types of service and apps compositions and mashups and demonstrating their integration with the business framework. Now the practical advice :): Start the description of T3.1 with a high-level architecture showing the main building blocks of the Aggregator and Mediator and the relationships to other roles within and outside WP3 and describe them. Provide a classification of composition and mashup technologies you collectively intend to contribute to T3.1 (front-end, back-end, WS-based, data/process mashups, event-based, workflow-based, etc. try to find a meaningful classification scheme, the description in DoW could be a good starting point). Make the following statement: "It is not the intention of FI-WARE neither to prescribe nor to prevent use of specific techniques, technologies, standards, engines or development environments. We intend to provide to the user of the FI-WARE platform a choice from a rich set of different composition and mashup technologies demonstrating integration with the business framework. We are open to new technologies and will offer a guideline if a company wishes to integrate its technology with the FI-WARE business framework. The architectures and functional capabilities of the services and apps composition technologies we aim to contribute as part of the platform are described in the following subsections Describe the architectures and purpose of your systems (the already available example from DT is perhaps a good starting point)... I hope this helps to generate the first drafts until next Wednesday. Best regards, Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.friesen at sap.com Fri Jun 17 09:20:03 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Fri, 17 Jun 2011 09:20:03 +0200 Subject: [Fiware-apps] Agenda for WP3 telco today Message-ID: <92E1E76787317A4E876E7A444ABC3902135B8B6F68@DEWDFECCR08.wdf.sap.corp> Dear All, Today the main scope should be to review the progress of T3.1. We will also shortly talk about T3.3. T3.1 (Calin Curescu) T3.3 (Juan Lambea, Andreas Friesen) Deadlines and responsibilities for M2 contributions Other urgent issues Best regards Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Fri Jun 17 10:13:31 2011 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 17 Jun 2011 10:13:31 +0200 Subject: [Fiware-apps] Agenda for WP3 telco today In-Reply-To: <92E1E76787317A4E876E7A444ABC3902135B8B6F68@DEWDFECCR08.wdf.sap.corp> References: <92E1E76787317A4E876E7A444ABC3902135B8B6F68@DEWDFECCR08.wdf.sap.corp> Message-ID: <4DFB0CAB.6090408@eng.it> Dear Andreas, I am currently in another PhC for the SLA at SOI project and I do not know if it will finish on time. In case, I will try to join later. Regards, Matteo On 17/06/2011 09:20, Friesen, Andreas wrote: > > Dear All, > > Today the main scope should be to review the progress of T3.1. We will > also shortly talk about T3.3. > > T3.1 (Calin Curescu) > > T3.3 (Juan Lambea, Andreas Friesen) > > Deadlines and responsibilities for M2 contributions > > Other urgent issues > > Best regards > > Andreas > > *Dr. Andreas Friesen* > Research Program Manager Service Science > *SAP Research Center Karlsruhe* > *SAP AG* > Vincenz-Priessnitz-Strasse 1 > 76131 Karlsruhe, Germany > T + 49 6227 752 586 > F + 49 6227 78-43567 > M +49 171 8674630 > mailto:andreas.friesen at sap.com > http://www.sap.com > > Pflichtangaben/Mandatory Disclosure Statements: > http://www.sap.com/company/legal/impressum.epx > > Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige > vertrauliche Informationen enthalten. Sollten Sie diese E-Mail > irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, > eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich > untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die > empfangene E-Mail. Vielen Dank. > > This e-mail may contain trade secrets or privileged, undisclosed, or > otherwise confidential information. If you have received this e-mail > in error, you are hereby notified that any review, copying, or > distribution of it is strictly prohibited. Please inform us > immediately and destroy the original transmittal. Thank you for your > cooperation. > > > _______________________________________________ > 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 juanlr at tid.es Fri Jun 17 10:45:50 2011 From: juanlr at tid.es (JUAN LAMBEA RUEDA) Date: Fri, 17 Jun 2011 10:45:50 +0200 Subject: [Fiware-apps] Agenda for WP3 telco today In-Reply-To: <4DFB0CAB.6090408@eng.it> References: <92E1E76787317A4E876E7A444ABC3902135B8B6F68@DEWDFECCR08.wdf.sap.corp> <4DFB0CAB.6090408@eng.it> Message-ID: <400B1E0D509AB14C95FFDC1DE303B9A881E0F7FF63@EXCLU2K7.hi.inet> Dear all, I'm in the same phone conference with Matteo I'm not sure if I will be on time... best regards Juan De: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] En nombre de Matteo Melideo Enviado el: viernes, 17 de junio de 2011 10:14 Para: Friesen, Andreas CC: 'fiware-apps at lists.fi-ware.eu' Asunto: Re: [Fiware-apps] Agenda for WP3 telco today Dear Andreas, I am currently in another PhC for the SLA at SOI project and I do not know if it will finish on time. In case, I will try to join later. Regards, Matteo On 17/06/2011 09:20, Friesen, Andreas wrote: Dear All, Today the main scope should be to review the progress of T3.1. We will also shortly talk about T3.3. T3.1 (Calin Curescu) T3.3 (Juan Lambea, Andreas Friesen) Deadlines and responsibilities for M2 contributions Other urgent issues Best regards Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps ________________________________ 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 andreas.friesen at sap.com Mon Jun 20 16:30:16 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Mon, 20 Jun 2011 16:30:16 +0200 Subject: [Fiware-apps] WP3 M2 Deliverable Message-ID: <92E1E76787317A4E876E7A444ABC3902135B9F4CF6@DEWDFECCR08.wdf.sap.corp> Dear ALL, please find attached the current version of the WP3 M2 contribution. The overview section 1.1.1has been significantly revised and updated (ALL: please send your feedback) Section 1.1.2 has been introduced to consolidate the Generic Enablers of the Business Framework (Broker) - Section 1.1.2.1 is new and shows the high-level architecture of the business framework. - A short description for SLA Management is missing (ENG would it be possible to you to provide 1-2 paragraphs on that? - The rest of the subsections in 1.1.2 have been taken over from the older version. - I propose to move the description of SLA Management to the question marks section Action: All T3.3 partners please provide your feedback/updates on section 1.1.2 and corresponding subsections to me. Section 1.1.3 covers Composition and Mashup - This is the latest version provided by Calin today morning Action: All T3.1 partners please send your feedback and updates to Calin. Please also check if something needs to be moved to question marks section due to uncertainties. Section 1.1.4 Covers the Multi-channel Multi-device Access - The content has been taken over from an older version. Action: All partners please send your feedback and comments to Javier Soriano/Rafael Fernandez (UPM) Action: UDE/UPM please try to identify terms where provision of definitions is required. Please also try to identify inconsistencies in using the terms in the document. Since I missed the 12:00 deadline today (sorry for that), please send your feedback until tomorrow 12:00. I will upload the current version to FusionForge and indicate that the next version will be available by tomorrow EOB. Thanks to all for timely feedback and contributions. Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE-WP3-HL-Description-A-v0.9.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1045893 bytes Desc: FI-WARE-WP3-HL-Description-A-v0.9.docx URL: From calin.curescu at ericsson.com Tue Jun 21 10:30:39 2011 From: calin.curescu at ericsson.com (Calin Curescu) Date: Tue, 21 Jun 2011 10:30:39 +0200 Subject: [Fiware-apps] No T3 meeting today 10-12 References: <84DE6B7638096349804AC8EC332FE1241002B5DA10@ESESSCMS0361.eemea.ericsson.se> Message-ID: <84DE6B7638096349804AC8EC332FE124142C78A8F5@ESESSCMS0361.eemea.ericsson.se> Dear all, There will be no meeting today 10-12. Andreas talked about the possibility to have one last Friday, but in the end it was not possible to schedule one (I just talked to him). (I sent also to FI-WARE APPS list. Who can tell me the composition of the list?) BR, /Calin From: Calin Curescu Sent: den 20 juni 2011 11:34 To: Calin Curescu; 'Horst.Stein at telekom.de'; 'jsoriano at fi.upm.es'; 'jesus.gorronogoitia at atosresearch.eu'; 'chatelp at gmail.com'; 'andreas.friesen at sap.com'; 'Tim.Jonischkat at paluno.uni-due.de'; 'marco.ughetti at telecomitalia.it'; 'stephan.haller at sap.com'; 'rfernandez at fi.upm.es'; 'carsten.magerkurth at sap.com'; ':'; 'Andreas.Grothe at telekom.de'; Ioannis Fikouras Subject: T3.1 & Generic enablers Dear all, I think we should also have a discussion on the generic enabler relevance. I was thinking about it and I want to pick it up since: a) Creating compositions/mashups are a central part of the FI-WARE influencing all the other parts. b) Out of the definition if GE in the DOW: ????.the chapter linked to Data/Context Management Services. This chapter may comprise some sort of GE that allows compilation and storage of massive data from disparate sources. Note that this GE may in turn be based on a number of GEs, each specialized in gathering data from a specific source (e.g., data from connected ?Dthings??, data obtained from user devices, data provided by the user, data exported by applications, etc.)??. I really don??t see any difference between this and how our aggregation/mediation technologies are structured. BR, /Calin From: Calin Curescu Sent: den 20 juni 2011 08:44 To: Horst.Stein at telekom.de; jsoriano at fi.upm.es; jesus.gorronogoitia at atosresearch.eu; chatelp at gmail.com; andreas.friesen at sap.com; Tim.Jonischkat at paluno.uni-due.de; marco.ughetti at telecomitalia.it; stephan.haller at sap.com; rfernandez at fi.upm.es; carsten.magerkurth at sap.com; :; Andreas.Grothe at telekom.de; Ioannis Fikouras Subject: RE: T3.1 Architecture document Dear all, Please find attached the architecture description document. Please send me your comments by 15.00 today to be merged back in the version I send to Andreas to submit. Best regards, /Calin From: Calin Curescu Sent: den 10 juni 2011 02:22 To: Horst.Stein at telekom.de; jsoriano at fi.upm.es; jesus.gorronogoitia at atosresearch.eu; chatelp at gmail.com; andreas.friesen at sap.com; Tim.Jonischkat at paluno.uni-due.de; marco.ughetti at telecomitalia.it; stephan.haller at sap.com; rfernandez at fi.upm.es; carsten.magerkurth at sap.com; :; Andreas.Grothe at telekom.de; Ioannis Fikouras Subject: T3.1 Architecture meeting summary Dear all, Please find next the summary from today's meeting. I have also updated the architecture image. I also include hare the latest version of the M2 document that we need to edit. All the description up to USDL are part of task 3.1. Since the Sections and subsections were structured only the early input from DT, UPM I made a some new sections from scratch, and the idea is that everybody is editing in the sections that are relevant to them / their assets by mid next week (you might want to decide the deadline with Andreas tomorrow). Obs: the rest of the document is somehow formatted in the description, so we could use a similar approach. Best regards, /Calin T3.1 Architecture meeting summary: FI-WARE task 3.1 Architecture meeting. Participants: Calin Curescu (Ericsson) Horst Stein (DT) Bettina Lehmann (DT) Andreas Grothe (DT) Pierre Chatel (THALES) Andreas Friesen (SAP) Tim Jonischkat (DU) Marco Ughetti (TI) Stephan Haller (SAP) Rafael Fernandez (UPM) Yosu Gorronogoitia (ATOS) - Yosu could not participate in the meeting, but we had a discussion later during the day. - Calin Curescu started to present the architecture for the high components (GEs) in task 3.1, which are the "Aggregator" and the "Mediator" and also the "Channel Maker" from task 3.4. The slides started from the idea that the Channel maker was relevant to the Mashup/Composition theme since important components used in the creation of user-side application gadgets (by mashing up UIs with data transformation and backend service connection) are part of the "Channel Maker" architecture. UPM (the main interested in application creation and mashup) soon made it clear that gadget creation is out of scope, and their main focus is on the application mashup (EzWeb). The "Channel Maker" might become part of an open call. As result of this Calin Will update the slides accordingly. - It was also discussed that while the USDL Registry and Repository can hold and provide the business aspects of services, there is the need for another registry component inside the Aggregator GE to hold the the technical descriptions of the services together with the composition description (i.e. the BPEL process, or the application mashup described in the MDL, or the Ericsson composition skeletons). - The main compontents of the Aggregator are the "Composition Editor" and the "Execution Engine". As already presented in the DoW there are two types of aggregation we address: the composition of backend services and the mashup of front-end applications (gadgets), however both need an editor for the aggregation and a runtime to instatiate it. This also means that these GEs will comprise a number of different complementary components (e.g. like the Compsition Studio (DT), mashup engine (UPM), Composition IDE (Ericsson) or Onyx editor (Atos)). The same is valid for the execution engines (e.g. BPEL orchestraton (DT), mashup container platform (UPM), event-driven orchestration (Ericsson), BPMN/BPEL orchestration (Atos)). - Finally there are three types of mediation functions that can be part of a mediator GE - data mediation (where compatible forms of data can be translated to each oter, e.g. mainly EDI functonality), protocol mediation (that helps service components with APIs exposed by different protocols to communicate, and process mediation - that translates or refines processes to be run in the execution engine). - A discussion started if it is needed to have the mediator as an explicit generic enabler. Pierre Chatel (THALES) explained that their work on the 3 functionality types presented above will result in a lower level library to be used by other enablers (e.g. by an execution engine) for high dynamicity cases, and not in a mediator (or gateway) component. Marco (TI) suggested tha part of the TI enterprise service bus (ESB) could play the mediator role. However it was not clear what functionality the TI mediator could provide and Marco agreed to pepare 1-2 slides detailing their contribution in task 3.1. ATOS is providing a component for the adaptive parametric automation of common modelling tasks at design time, i.e BPMN -> BPEL processes. This seems to fit very much in the process mediator functionality. Ericsson is providing the WebCommunication component that will help compose front end gadgets also across different device/browser boundaries. This amounts to a protocol mediation component. Also Ericsson as part of their composition/orchestration engine provides a multitude of protocol adaptations (REST, SOAP, SIP, RMI, JS, etc.) - SAP works on a Process Modelling and Language Extensions for IoT. This has a lot to do with the Execution/orchestration engine and they will provide a description in that section. - DT in their asset achitecture have a "user management" component however this service fits better the enablers in WP9: Security, privacy, Trust. Other components in DT arch. such as Deployment UI and Dialog Creator represent more generic services that do not have a direct enabler correspondence. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.friesen at sap.com Tue Jun 21 13:57:12 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Tue, 21 Jun 2011 13:57:12 +0200 Subject: [Fiware-apps] No T3 meeting today 10-12 In-Reply-To: <84DE6B7638096349804AC8EC332FE124142C78A8F5@ESESSCMS0361.eemea.ericsson.se> References: <84DE6B7638096349804AC8EC332FE1241002B5DA10@ESESSCMS0361.eemea.ericsson.se> <84DE6B7638096349804AC8EC332FE124142C78A8F5@ESESSCMS0361.eemea.ericsson.se> Message-ID: <92E1E76787317A4E876E7A444ABC3902135BAB88E9@DEWDFECCR08.wdf.sap.corp> Dear Calin, All, please take my apologies for not scheduling the meeting today. I forgot to send the MR in the due time and I was not online today morning to do it on short term. Let??s consolidate the inputs first and discuss next actions in the regular call on Friday. With respect to the GEs in T3.1 (see Calin??s mail below), of course, you can specify GEs where appropriate, but you do not need to do so for each and every component and technology. If you identify a functional component that has the quality to become GE specify it as GE. All the other functional components representing a specific solution (i.e., one of many alternatives with similar functionality but different interfaces, languages, etc.) should be described as examples of composition and mashup technologies integrated into the FI-WARE platform. BR, Andreas From: Calin Curescu [mailto:calin.curescu at ericsson.com] Sent: Dienstag, 21. Juni 2011 10:31 To: Horst.Stein at telekom.de; jsoriano at fi.upm.es; jesus.gorronogoitia at atosresearch.eu; chatelp at gmail.com; Friesen, Andreas; Tim.Jonischkat at paluno.uni-due.de; marco.ughetti at telecomitalia.it; Haller, Stephan; rfernandez at fi.upm.es; Magerkurth, Carsten; :; Andreas.Grothe at telekom.de; 'fiware-apps at lists.fi-ware.eu' Subject: No T3 meeting today 10-12 Dear all, There will be no meeting today 10-12. Andreas talked about the possibility to have one last Friday, but in the end it was not possible to schedule one (I just talked to him). (I sent also to FI-WARE APPS list. Who can tell me the composition of the list?) BR, /Calin From: Calin Curescu Sent: den 20 juni 2011 11:34 To: Calin Curescu; 'Horst.Stein at telekom.de'; 'jsoriano at fi.upm.es'; 'jesus.gorronogoitia at atosresearch.eu'; 'chatelp at gmail.com'; 'andreas.friesen at sap.com'; 'Tim.Jonischkat at paluno.uni-due.de'; 'marco.ughetti at telecomitalia.it'; 'stephan.haller at sap.com'; 'rfernandez at fi.upm.es'; 'carsten.magerkurth at sap.com'; ':'; 'Andreas.Grothe at telekom.de'; Ioannis Fikouras Subject: T3.1 & Generic enablers Dear all, I think we should also have a discussion on the generic enabler relevance. I was thinking about it and I want to pick it up since: a) Creating compositions/mashups are a central part of the FI-WARE influencing all the other parts. b) Out of the definition if GE in the DOW: ????.the chapter linked to Data/Context Management Services. This chapter may comprise some sort of GE that allows compilation and storage of massive data from disparate sources. Note that this GE may in turn be based on a number of GEs, each specialized in gathering data from a specific source (e.g., data from connected ?Dthings??, data obtained from user devices, data provided by the user, data exported by applications, etc.)??. I really don??t see any difference between this and how our aggregation/mediation technologies are structured. BR, /Calin From: Calin Curescu Sent: den 20 juni 2011 08:44 To: Horst.Stein at telekom.de; jsoriano at fi.upm.es; jesus.gorronogoitia at atosresearch.eu; chatelp at gmail.com; andreas.friesen at sap.com; Tim.Jonischkat at paluno.uni-due.de; marco.ughetti at telecomitalia.it; stephan.haller at sap.com; rfernandez at fi.upm.es; carsten.magerkurth at sap.com; :; Andreas.Grothe at telekom.de; Ioannis Fikouras Subject: RE: T3.1 Architecture document Dear all, Please find attached the architecture description document. Please send me your comments by 15.00 today to be merged back in the version I send to Andreas to submit. Best regards, /Calin From: Calin Curescu Sent: den 10 juni 2011 02:22 To: Horst.Stein at telekom.de; jsoriano at fi.upm.es; jesus.gorronogoitia at atosresearch.eu; chatelp at gmail.com; andreas.friesen at sap.com; Tim.Jonischkat at paluno.uni-due.de; marco.ughetti at telecomitalia.it; stephan.haller at sap.com; rfernandez at fi.upm.es; carsten.magerkurth at sap.com; :; Andreas.Grothe at telekom.de; Ioannis Fikouras Subject: T3.1 Architecture meeting summary Dear all, Please find next the summary from today's meeting. I have also updated the architecture image. I also include hare the latest version of the M2 document that we need to edit. All the description up to USDL are part of task 3.1. Since the Sections and subsections were structured only the early input from DT, UPM I made a some new sections from scratch, and the idea is that everybody is editing in the sections that are relevant to them / their assets by mid next week (you might want to decide the deadline with Andreas tomorrow). Obs: the rest of the document is somehow formatted in the description, so we could use a similar approach. Best regards, /Calin T3.1 Architecture meeting summary: FI-WARE task 3.1 Architecture meeting. Participants: Calin Curescu (Ericsson) Horst Stein (DT) Bettina Lehmann (DT) Andreas Grothe (DT) Pierre Chatel (THALES) Andreas Friesen (SAP) Tim Jonischkat (DU) Marco Ughetti (TI) Stephan Haller (SAP) Rafael Fernandez (UPM) Yosu Gorronogoitia (ATOS) - Yosu could not participate in the meeting, but we had a discussion later during the day. - Calin Curescu started to present the architecture for the high components (GEs) in task 3.1, which are the "Aggregator" and the "Mediator" and also the "Channel Maker" from task 3.4. The slides started from the idea that the Channel maker was relevant to the Mashup/Composition theme since important components used in the creation of user-side application gadgets (by mashing up UIs with data transformation and backend service connection) are part of the "Channel Maker" architecture. UPM (the main interested in application creation and mashup) soon made it clear that gadget creation is out of scope, and their main focus is on the application mashup (EzWeb). The "Channel Maker" might become part of an open call. As result of this Calin Will update the slides accordingly. - It was also discussed that while the USDL Registry and Repository can hold and provide the business aspects of services, there is the need for another registry component inside the Aggregator GE to hold the the technical descriptions of the services together with the composition description (i.e. the BPEL process, or the application mashup described in the MDL, or the Ericsson composition skeletons). - The main compontents of the Aggregator are the "Composition Editor" and the "Execution Engine". As already presented in the DoW there are two types of aggregation we address: the composition of backend services and the mashup of front-end applications (gadgets), however both need an editor for the aggregation and a runtime to instatiate it. This also means that these GEs will comprise a number of different complementary components (e.g. like the Compsition Studio (DT), mashup engine (UPM), Composition IDE (Ericsson) or Onyx editor (Atos)). The same is valid for the execution engines (e.g. BPEL orchestraton (DT), mashup container platform (UPM), event-driven orchestration (Ericsson), BPMN/BPEL orchestration (Atos)). - Finally there are three types of mediation functions that can be part of a mediator GE - data mediation (where compatible forms of data can be translated to each oter, e.g. mainly EDI functonality), protocol mediation (that helps service components with APIs exposed by different protocols to communicate, and process mediation - that translates or refines processes to be run in the execution engine). - A discussion started if it is needed to have the mediator as an explicit generic enabler. Pierre Chatel (THALES) explained that their work on the 3 functionality types presented above will result in a lower level library to be used by other enablers (e.g. by an execution engine) for high dynamicity cases, and not in a mediator (or gateway) component. Marco (TI) suggested tha part of the TI enterprise service bus (ESB) could play the mediator role. However it was not clear what functionality the TI mediator could provide and Marco agreed to pepare 1-2 slides detailing their contribution in task 3.1. ATOS is providing a component for the adaptive parametric automation of common modelling tasks at design time, i.e BPMN -> BPEL processes. This seems to fit very much in the process mediator functionality. Ericsson is providing the WebCommunication component that will help compose front end gadgets also across different device/browser boundaries. This amounts to a protocol mediation component. Also Ericsson as part of their composition/orchestration engine provides a multitude of protocol adaptations (REST, SOAP, SIP, RMI, JS, etc.) - SAP works on a Process Modelling and Language Extensions for IoT. This has a lot to do with the Execution/orchestration engine and they will provide a description in that section. - DT in their asset achitecture have a "user management" component however this service fits better the enablers in WP9: Security, privacy, Trust. Other components in DT arch. such as Deployment UI and Dialog Creator represent more generic services that do not have a direct enabler correspondence. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.friesen at sap.com Tue Jun 21 14:04:29 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Tue, 21 Jun 2011 14:04:29 +0200 Subject: [Fiware-apps] WP3 M2 Deliverable In-Reply-To: References: <92E1E76787317A4E876E7A444ABC3902135B9F4CF6@DEWDFECCR08.wdf.sap.corp> Message-ID: <92E1E76787317A4E876E7A444ABC3902135BAB8906@DEWDFECCR08.wdf.sap.corp> Hi Keven, All, please find attached the document compatible with Word 2003. Andreas From: Keven Kearney [mailto:keven.kearney at eng.it] Sent: Dienstag, 21. Juni 2011 13:51 To: Friesen, Andreas Subject: Re: [Fiware-apps] WP3 M2 Deliverable Hi Andreas, Would it be possible for you to publish documents compatible with older versions of Word (my version is 2003) ? PDF renderings would be ideal :) Keven ----- Original Message ----- From: Friesen, Andreas To: 'fiware-apps at lists.fi-ware.eu' Sent: Monday, June 20, 2011 4:30 PM Subject: [Fiware-apps] WP3 M2 Deliverable Dear ALL, please find attached the current version of the WP3 M2 contribution. The overview section 1.1.1has been significantly revised and updated (ALL: please send your feedback) Section 1.1.2 has been introduced to consolidate the Generic Enablers of the Business Framework (Broker) - Section 1.1.2.1 is new and shows the high-level architecture of the business framework. - A short description for SLA Management is missing (ENG would it be possible to you to provide 1-2 paragraphs on that? - The rest of the subsections in 1.1.2 have been taken over from the older version. - I propose to move the description of SLA Management to the question marks section Action: All T3.3 partners please provide your feedback/updates on section 1.1.2 and corresponding subsections to me. Section 1.1.3 covers Composition and Mashup - This is the latest version provided by Calin today morning Action: All T3.1 partners please send your feedback and updates to Calin. Please also check if something needs to be moved to question marks section due to uncertainties. Section 1.1.4 Covers the Multi-channel Multi-device Access - The content has been taken over from an older version. Action: All partners please send your feedback and comments to Javier Soriano/Rafael Fernandez (UPM) Action: UDE/UPM please try to identify terms where provision of definitions is required. Please also try to identify inconsistencies in using the terms in the document. Since I missed the 12:00 deadline today (sorry for that), please send your feedback until tomorrow 12:00. I will upload the current version to FusionForge and indicate that the next version will be available by tomorrow EOB. Thanks to all for timely feedback and contributions. Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. ________________________________ _______________________________________________ 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: FI-WARE-WP3-HL-Description-A-v0.10.doc Type: application/msword Size: 1261056 bytes Desc: FI-WARE-WP3-HL-Description-A-v0.10.doc URL: From andreas.friesen at sap.com Tue Jun 21 19:09:26 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Tue, 21 Jun 2011 19:09:26 +0200 Subject: [Fiware-apps] The first complete draft of WP3 contribution to M2 submitted to FusionForge Message-ID: <92E1E76787317A4E876E7A444ABC3902135BAB8E36@DEWDFECCR08.wdf.sap.corp> Dear All, please find attached the document I just submitted to FusionForge. All inputs received so far are integrated. Please review terms and conditions (I just copied into the document the definitions from DoW). They are for sure neither complete nor consistent with the text. Please send the terms you believe have to be defined to the list. Tim (UDE) will consolidate them and try to provide some example definitions until Friday so that we can discuss in the WP telco how to tackle this section in a consistent way. Please send improvements to your TL. Best Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE High-level Desc Apps v1.0 11-06-21 valid until 11-06-22.doc Type: application/msword Size: 1276416 bytes Desc: FI-WARE High-level Desc Apps v1.0 11-06-21 valid until 11-06-22.doc URL: From calin.curescu at ericsson.com Fri Jun 24 10:29:58 2011 From: calin.curescu at ericsson.com (Calin Curescu) Date: Fri, 24 Jun 2011 10:29:58 +0200 Subject: [Fiware-apps] The first complete draft of WP3 contribution to M2 submitted to FusionForge In-Reply-To: <92E1E76787317A4E876E7A444ABC3902135BAB8E36@DEWDFECCR08.wdf.sap.corp> References: <92E1E76787317A4E876E7A444ABC3902135BAB8E36@DEWDFECCR08.wdf.sap.corp> Message-ID: <84DE6B7638096349804AC8EC332FE124142CA2BAD8@ESESSCMS0361.eemea.ericsson.se> Dear all, According to the work in T3.1 I propose some changes to the ?overview? section. I also removed Ericsson association with the Charging Service. We also need a short discussions on generic enablers in T3.1 during Friday. Best regards, /Calin ________________________________________ From: fiware-apps-bounces at lists.fi-ware.eu [fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Friesen, Andreas [andreas.friesen at sap.com] Sent: Tuesday, June 21, 2011 7:09 PM To: 'fiware-apps at lists.fi-ware.eu' Subject: [Fiware-apps] The first complete draft of WP3 contribution to M2 submitted to FusionForge Dear All, please find attached the document I just submitted to FusionForge. All inputs received so far are integrated. Please review terms and conditions (I just copied into the document the definitions from DoW). They are for sure neither complete nor consistent with the text. Please send the terms you believe have to be defined to the list. Tim (UDE) will consolidate them and try to provide some example definitions until Friday so that we can discuss in the WP telco how to tackle this section in a consistent way. Please send improvements to your TL. Best Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE High-level Desc Apps v1 0 11-06-21 valid until 11-06-22-Calin.doc Type: application/binary Size: 1261056 bytes Desc: FI-WARE High-level Desc Apps v1 0 11-06-21 valid until 11-06-22-Calin.doc URL: From andreas.friesen at sap.com Fri Jun 24 12:22:16 2011 From: andreas.friesen at sap.com (Friesen, Andreas) Date: Fri, 24 Jun 2011 12:22:16 +0200 Subject: [Fiware-apps] Summary of today's WP3 call Message-ID: <92E1E76787317A4E876E7A444ABC3902135BBF5390@DEWDFECCR08.wdf.sap.corp> Dear All, here the summary of today's WP3 call: Participants Andreas Friesen (SAP) Calin Curescu (EAB) Horst Stein (DT) Keven Kearney (ENG) Andreas: Reported on the current status of the WP3 contribution to the M2 deliverable (the first complete draft submitted to FusionForge at 21st of June). The feedback from WP2 about the integration into M2 deliverable expected on Monday, 27th of June (EOB). The next actions are to improve the "terms and definitions" section and the "question marks" section. Calin: Distributed an improved version of T3.1 contribution Keven: Submitted the first version of SLA Management description Andreas: We continue to collect partner updates for the M2 deliverable. The next consolidated version of WP3 contribution will be created next week after we received feedback from WP2. After the M2 deliverable has been finalized we should start talking to other WPs, first of all to the security WP. Please start thinking about potential security requirements and threats. We will have to nominate 2-3 experts to talk with security architects about security issues in the WP3 architecture. Please find attached the email from Juanjo explaining the next actions expected from us in more detail. Best regards, Andreas Dr. Andreas Friesen Research Program Manager Service Science SAP Research Center Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T + 49 6227 752 586 F + 49 6227 78-43567 M +49 171 8674630 mailto:andreas.friesen at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: [Fiware-wpl] IMPORTANT - Start of integration of FI-WARE High-level Description deliverable: next steps Date: Thu, 23 Jun 2011 09:04:32 +0200 Size: 19937 URL: From jesus.gorronogoitia at atosresearch.eu Fri Jun 24 13:50:18 2011 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Fri, 24 Jun 2011 13:50:18 +0200 Subject: [Fiware-apps] Summary of today's WP3 call In-Reply-To: <92E1E76787317A4E876E7A444ABC3902135BBF5390@DEWDFECCR08.wdf.sap.corp> References: <92E1E76787317A4E876E7A444ABC3902135BBF5390@DEWDFECCR08.wdf.sap.corp> Message-ID: <1308916218.11594.1.camel@linux-gzvm.site> Dear all, I am sorry for not attending the telco, i am afraid i misunderstood the last email and i thought no telco was scheduled today. Regards Yosu On Fri, 2011-06-24 at 12:22 +0200, Friesen, Andreas wrote: > Dear All, > > > > here the summary of today?s WP3 call: > > > > Participants > > > > Andreas Friesen (SAP) > > Calin Curescu (EAB) > > Horst Stein (DT) > > Keven Kearney (ENG) > > > > Andreas: Reported on the current status of the WP3 contribution to the > M2 deliverable (the first complete draft submitted to FusionForge at > 21st of June). The feedback from WP2 about the integration into M2 > deliverable expected on Monday, 27th of June (EOB). The next actions > are to improve the ?terms and definitions? section and the ?question > marks? section. > > Calin: Distributed an improved version of T3.1 contribution > > Keven: Submitted the first version of SLA Management description > > Andreas: We continue to collect partner updates for the M2 > deliverable. The next consolidated version of WP3 contribution will be > created next week after we received feedback from WP2. After the M2 > deliverable has been finalized we should start talking to other WPs, > first of all to the security WP. Please start thinking about potential > security requirements and threats. We will have to nominate 2-3 > experts to talk with security architects about security issues in the > WP3 architecture. Please find attached the email from Juanjo > explaining the next actions expected from us in more detail. > > > > Best regards, > > Andreas > > > > > > > > Dr. Andreas Friesen > Research Program Manager Service Science > SAP Research Center Karlsruhe > SAP AG > Vincenz-Priessnitz-Strasse 1 > 76131 Karlsruhe, Germany > T + 49 6227 752 586 > F + 49 6227 78-43567 > M +49 171 8674630 > mailto:andreas.friesen at sap.com > http://www.sap.com > > Pflichtangaben/Mandatory Disclosure Statements: > http://www.sap.com/company/legal/impressum.epx > > Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige > vertrauliche Informationen enthalten. Sollten Sie diese E-Mail > irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, > eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich > untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die > empfangene E-Mail. Vielen Dank. > > This e-mail may contain trade secrets or privileged, undisclosed, or > otherwise confidential information. If you have received this e-mail > in error, you are hereby notified that any review, copying, or > distribution of it is strictly prohibited. Please inform us > immediately and destroy the original transmittal. Thank you for your > cooperation. > > > > > > > email message attachment > > -------- Forwarded Message -------- > > From: Juanjo Hierro > > To: fiware-wpl at lists.fi-ware.eu , > > fiware-wpa at lists.fi-ware.eu > > Subject: [Fiware-wpl] IMPORTANT - Start of integration of FI-WARE > > High-level Description deliverable: next steps > > Date: Thu, 23 Jun 2011 09:04:32 +0200 > > > > Hi all, > > > > I believe that all the Architecture Chapter teams have uploaded > > their contribution to the docman system. Thanks for your > > commitment and effort !! > > > > Now, I will start to integrate the different chapters into a > > single document and perform and overall review all the chapters > > while making the integration. My plan is to finish this process by > > monday June 27, EOB. > > > > What can teams do in the meantime ? My suggestion is that you > > work in the "Question Marks" section and give also a final review to > > the "terms and definitions" section if you had generated it in the > > last minute (I know it is the case for some teams :-) These two > > sections can be easily replaced in the integrated document. > > > > Regarding the "Question Marks" section, I would suggest to > > structure it into a subsection titled "Security aspects" and a > > subsection titled "Other topics still under discussion". > > * On "Security aspects": I suggest that you nominate one-two > > people in your team that work with the WP8 team to analyze > > contents of your chapter and identify Security questions. > > Please contact Pascal Bisson > > (pascal.bisson at thalesgroup.com), leader of WP8, to > > coordinate with him how to carry out this task. It is > > about identifying at least 3-5 issues, and describing each > > with one-two paragraphs. You can download the > > contribution linked to the Data/Context Management chapter > > and check the "Security aspects" subsection where you may > > find some reference examples (particularly the one on > > Privacy Management) > > * On "Other topics still under discussion": The idea is just > > formulate 3-5 topics for which discussion has not yet been > > finalized within the team. Try to elaborate on the > > different alternatives you are considering/discussing with > > respect to the topic as well as any consideration that is > > relevant. Each topic should be described similarly to how > > topics in the "Security aspects" subsection were described > > in the Data/Context Management chapter (again, the > > description of the Privacy Management issue is a good > > reference example). It is up to the WPL how to organize > > this task. > > Regarding the "terms and definitions" section, there isn't > > anything special to remark. But try to provide precise > > definitions. Also try to make this section something that can > > "work" relatively standalone. > > > > I expect your contributions to both sections by Tuesday June 29, > > 19:00 CET. > > > > IN ADDITION: I know that some of you still wish to work on the > > content of sections linked to the overview and description of GEs. > > How can you work in parallel to integration ? I would suggest the > > following: > > * In the placeholder under the contrib folder linked to your > > document you will always be able to find the last version of > > your chapter already integrated in the final document. > > * Whenever I start to work with a given chapter, I will change > > its status to "pending" (this is one of the valid status > > -like "private"- you can assign to a document in the form > > linked to an entry in the Admin section of the docman > > system). This will mean I have blocked it. You will > > detect that your contribution is pending because you > > wouldn't be able to see it in the folders/document tree that > > is displayed when you click on "View Documentation". You > > should then wait until I upload a new version (already > > integrated in the master document). Of course, you may > > still be working on some changes but then you should > > implement them individually over the file that I will > > finally upload to the docman system (that file may have > > comments or even changes and, for sure, some fixes in > > formatting I don't want to loose, so it won't be as simple > > as replace the file with the one you were working on in > > parallel to me). Whenever I upload a new version of the > > file, I will change its status to "private" and you will be > > able to see it in the folders/document tree. > > * If a document is not "pending", this mean that you can > > download it and work on it. But, PLEASE, whenever you plan > > to do so, please mark it also as "pending" before > > downloading, so that I can realize you will download it and > > start working on it. You only have the right to keep a > > document "pending" from 09:00am to 19:00pm. After 19:00 > > and until 09:00am the next day, I can change its status and > > replace the attached file without notice. In the event I > > need that you release the document -changing its state to > > "private" again- before 19:00, I'll let you know. > > * PLEASE, DON'T CREATE NEW ENTRIES: It should work with the > > already existing ones, changing the status and replacing the > > attached file when needed. > > > > I know that we would probably do it better using SVN but SVN got > > installed recently and many people don't have the time to get used > > to it. Despite it took some time, all WPLs already know how to > > manage the docman, so we should keep using docman for this release > > of the deliverable. > > > > For a number of reasons, I won't be able to start integration > > until 19:00 today (it's holiday in Spain) so you will find that all > > the contributions to each chapter are marked as "private", > > therefore, not blocked. > > > > Let's work hard to finish the document !! > > > > Best regards, > > > > -- Juanjo > > > > > > > > > > ____________________________________________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > > consultar nuestra pol?tica de env?o y recepci?n de correo > > electr?nico en el enlace situado m?s abajo. > > This message is intended exclusively for its addressee. We only send > > and receive email on the basis of the terms set out at. > > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > 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 Origin 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 Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, 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 Wed Jun 29 13:11:13 2011 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 29 Jun 2011 13:11:13 +0200 Subject: [Fiware-apps] FW: FI-Ware: Terms & Definitions Message-ID: Dear FI-Ware WP3 colleagues, Please find a list of terms enclosed that I believe to be part of the "Terms and Definitions" sections of the M2 deliverable. Please find further suggestions (optimally along with a description) to Tim until end of week latest. He will come back to you if he needs more input. 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. 1. Business Framework 2. Business Element 3. Business Model 4. Business Process 5. Business Role 6. Provider (Role) 7. Consumer (Role) 8. Aggregator (Role) 9. Prosumer (Role) 10. Gateway (Role) 11. Broker (Role) 12. Premise (Role) 13. Hoster (Role) 14. Channel Maker (Role) 15. Monetization 16. Delivery Framework 17. Multi-channel 18. Multi-device 19. USDL - Service Description 20. Service Delivery Framework 21. Mashable Application Component 22. Composite Service 23. Service Composition 24. Service Orchestration 25. Event-driven Composition 26. Mashup 27. Front-end/Back-end Composition 28. Mediator 29. Revenue Sharing 30. Revenue Settlement 31. Revenue Sources 32. Service Value Network (optional) 33. Service Level Agreement (SLA) 34. Registry 35. Repository 36. Marketplace 37. Store F?llt dir noch was ein? Sonst schicke ich es an Tim und die Liste weiter. -------------- next part -------------- An HTML attachment was scrubbed... URL: