From torsten.leidig at sap.com Wed Feb 1 09:16:25 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 1 Feb 2012 09:16:25 +0100 Subject: [Fiware-apps] FW: [Fiware-opencall-bm] Open Call published, list of current Epics listed In-Reply-To: <4F28ED48.90700@tid.es> References: <4F28ED48.90700@tid.es> Message-ID: FYI: Please send comments and contributions from the perspective of your GE on the fiware-opencall-bm and fiware-opencall-middleware mailing list. From: fiware-opencall-bm-bounces at lists.fi-ware.eu [mailto:fiware-opencall-bm-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 1. Februar 2012 08:44 To: fiware-opencall-bm at lists.fi-ware.eu; fiware-opencall-middleware at lists.fi-ware.eu Subject: [Fiware-opencall-bm] Open Call published, list of current Epics listed Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ There are pointers to the dedicated spaces on the Wiki where Epics per topic are published: * Middleware topic: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Common_base_technologies#FI-WARE_Advanced_Middleware * BM&BE topic: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Applications/Services_Ecosystem_and_Delivery_Framework_in_FI-WARE#Business_Elements_.26_Business_Models We have announced that a refined version of these Epics may be available on February 21st. You may take this 20 days to elaborate them further, though I believe that the middleware topic is pretty well covered. The BM&BE may require some more additional work. From February 21st on, no further changes should be implemented. I have filled the "Owner contact" field of each Epic with the email address of the dedicated mailing list we created for the corresponding topic. Thus, some external input and even questions may come from the outside. 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 pabloa at tid.es Thu Feb 2 10:29:25 2012 From: pabloa at tid.es (Pablo Arozarena) Date: Thu, 02 Feb 2012 10:29:25 +0100 Subject: [Fiware-apps] Specify contributions to testbed In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D80268E1@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D80268E1@DEWDFECCR02.wdf.sap.corp> Message-ID: <4F2A5775.1000107@tid.es> Hi Uwe, Please, find attached TID's input to the testbed requirements sheet. Best regards, Pablo El 30/01/2012 16:36, Riss, Uwe escribi?: Dear colleagues, Could you please specify your requirements regarding the testbed in the attached Excel sheet and send it back to me for consolidation by tomorrow (Tuesday) EOB. The effort should actually be bearable so that I suppose the deadline to be realistic. 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. -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of stefano de panfilis Sent: Sonntag, 29. Januar 2012 17:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: [Fiware-wpl] Contributions to testbed dear all, first of all let me thank you those who promptly provided the needed info for setting-up the testbed and participated in very interesting and constructive discussions giving us, wp10 team, important feedback for our work. as also said during various meetings the last days in madrid, the questions we put forward to all of you have been fine tuned, so even for those who already provided the info, please check them again. but certainly this email is mostly addressed to whom as Apps, IoT, and Data provided very little info even if any!!! i really ask you to fill promptly, and certainly within this week (3 feb 2012), the required info. i kindly ask the help of wp10 team members to check for their colleagues in other wps to provide the info. in order to provide the info please go to the wp10 wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Testbed_Fact_Finding_Investigation) where you have the questions and the already provided answers. what is red is what is missing!!! for your convenience you can send me your inputs also in text form or with the attached excel file, but please send it! anyway, on 10 feb the testbed design deliverable v1 will be released to the ec with the info i'll have at the moment. please consider that the deliverable is a matching between yours ges and the testbed components (both hw and sw), so without your inputs it is impossible to do such matching. i'm sure of your understanding. ciao, stefano -- Pablo Arozarena Product Development and Innovation Telef?nica Digital Distrito Telef?nica, Edificio Oeste 1 - Planta 5 Ronda de la Comunicaci?n, s/n 28050 Madrid Spain Tlf: +34 91 4832866 ________________________________ 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: GE_HW_req_20120126_Atos_THALES-TID.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 82094 bytes Desc: not available URL: From miguel.huerta at atos.net Thu Feb 2 17:06:02 2012 From: miguel.huerta at atos.net (=?ISO-8859-1?Q?Miguel_=C1ngel_Huerta?=) Date: Thu, 02 Feb 2012 17:06:02 +0100 Subject: [Fiware-apps] FW: [Fiware-wpa] Actions Points to be Done In-Reply-To: References: <4F27C0D6.4080301@tid.es> Message-ID: <4F2AB46A.3090803@atos.net> Hi Torsten, This mail is just to inform you that we (Yosu and me) have finished backlog entries upto Release 2.2. All the tickets in the tracker (Use Cases, Features and Epics) has been created, assigned and planned as open, closed or under execution. If i am right, the only activity relating backlog entries pending for us is the creation of Workintems, as it was said in some of the meetings these are created just to inform in which part is working each partner. We also have start working in our open specs, keep waiting instructions from T3.1 Leader since we will have to put in common all composition editor, mediation and execution engine specifications. PD: i dont know why any ticket created in Apps.Mediation is not well assigned to this, since if you filter the tracker by Apps-Mediation you don't get any result, you must filter by "Default" to get the tickets assigned to Mediation... B.R. *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 01/31/2012 11:26 AM, Leidig, Torsten wrote: > > 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, 31. Januar 2012 11:22 > *To:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > *Subject:* [Fiware-wpa] Actions Points to be Done > > Dear WPLs/WPAs, > > I plan to deliver more precise guidelines, including some templates > sometime today but probably very late in the evening, effectively to > be ready tomorrow morning because I'm currently very busy finalization > of the publication of the first Open Call which was due by today. > > Apologize for any problem this may cause, but I hope you will > understand. In the meantime, please try to deal with the couple of > urgent points that we revised during last week WPL/WPA meeting (some > of them commented during our joint confcall yesterday). We should > not forget to address them: > > * Provide complete and accurate minutes of the f2f meeting last > week. As announced, Miguel sent detailed instructions to follow > regarding this (based on feedback by some partners, we will change > the place where you should upload them, Miguel will send an email > updating on this). PLEASE don't forget to transform Actions > Points you identified into WorkItems in the corresponding tracker > (your chapter tracker or the FI-WARE-Private tracker). Miguel > will setup a Backlog Management tracker on the "FI-WARE Private" > project so that you will be able to create WorkItems you believe > that need to be addressed and followed-up at FI-WARE global level. > * Complete response to questionnaire distributed by the Testbed > team. This is urgent in order to complete the Testbed design. > * SAP: complete revision of Epics linked to BM&BE GE being > considered in the first Open Call. > * Planning of sprint 4 (this requires the first point regarding > identification of WorkItems to be done) > * Address APs identified during Security plenary session: > o Each Chapter to provide their answers to the questions raised > by the Security team for each of the Security GEs (the sooner, > the better and no later than by end of this week so 3/02/2012) > o Each Chapters to consider integration of Security GEs within > their Chapter architecture and whenever those are needed and > at appropriate level (i.e. architecture level, GE level). As > a first step, this should lead to definition of at least one > Epic by chapter and GEs to reflect this as ongoing work > o Each Chapter to analyze the interaction (sequence) diagram > with the Security Monitoring GE to check, amend/complete and > validate them (there is one for each of the Chapters that was > elaborated by the Security team). This is needed prior > delivery of the information requested by the Security Chapter > (i.e. log, security events, countermeasures, ....) by Security > Monitoring GE (also gets the architecture of the chapter ready > to have this information delivered). The Security chapter will > provide other chapters with information needed by Security > Monitoring GE (also format under which this information has to > be provided) > * Review status of UC project tickets to update them or make some > progress. Don't forget to change the assignee of a ticket to be > the issuer whenever you change the state to "Needs revision by the > issuer". > * Standardization Plan: please check latest requests on the matter > ... there is info pending ! > > 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-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: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: atos_logotype.gif Type: image/gif Size: 816 bytes Desc: not available URL: From uwe.riss at sap.com Mon Feb 6 13:42:09 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 6 Feb 2012 13:42:09 +0100 Subject: [Fiware-apps] FW: [Fiware-wpa] [Fiware-wpl] Actions Points to be Done Message-ID: <1491C91A94302A448D73CD9C6B7A782045D89CE270@DEWDFECCR02.wdf.sap.corp> Dear WP3 Partners, As you all known the Security Chapter has asked us to provide some input. Torsten has compiled an initial list to answer these questions. I'd like to ask you to check this list and to bring up missing issues in out call tomorrow morning. If you cannot attend please send them per email to Torsten or me. The current version reads: Regarding Identity Managment: ? Authentication will be needed on the service level. ? Service will authenticate user (client), a service will authenticate another service who is calling the service on behalf of a user. ? A user will be authenticated against an authentication provider or against a certificate. ? A service will be authenticated by an API key. ? Things will not be handled different from services. ? The IDM should support all relevant protocols used widely in the internet. ? The example services will be implemented by the GE providers and the use case project members. ? Network security is expected to be provided by the testbed provider and/or the Cloud provider. Apps GE are relying mostly on HTTPS protocol. PKI must be provided for the testbed. Privacy and Data Handling ? We don't know. We assume that privacy threats are considered within the assets of the individual partners. ? There are no general approaches to store personal data securely. This is the responsibility of the individual asset provider. We assume there will be trust relationship between components, which share personal data such as forwarding a buy request from the store to the provider. No personal data are exchanged otherwise. ? Disclosure of personal data is not intended. ? Unkown ? A service needs to know information that is necessary to execute the business transaction only. There are no known specific attributes or predicates yet. ? Maybe. ? Revocation is not a requirement but are a common practice that might be used for some security reasons, so it should be supported. Security Monitoring ? Must be analysed in more detail by then individual asset owners. Generally, it should be possible to at least support a subset of the requested events. I most cases this require deep changes in the asset code. ? No specific indicators are supported. We are curious what the team can provide. ? We don't know. ? Probably yes. ? That needs to be shown. ? That needs to be shown. 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-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: Montag, 6. Februar 2012 12:14 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: BISSON Pascal; LELEU Philippe Subject: Re: [Fiware-wpa] [Fiware-wpl] Actions Points to be Done Importance: High Dear Colleagues, I'm just forwarding you this email from Juanjo to remind you the Action Points Daniel and I on behalf of Security team were requesting from each of you. Counting on you to work on those actions points and report to us asap. Reading you soon. Pascal / Daniel * Address APs identified during Security plenary session: * Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012) * Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level). As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work * Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team). This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided) De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 31 janvier 2012 11:22 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Actions Points to be Done Dear WPLs/WPAs, I plan to deliver more precise guidelines, including some templates sometime today but probably very late in the evening, effectively to be ready tomorrow morning because I'm currently very busy finalization of the publication of the first Open Call which was due by today. Apologize for any problem this may cause, but I hope you will understand. In the meantime, please try to deal with the couple of urgent points that we revised during last week WPL/WPA meeting (some of them commented during our joint confcall yesterday). We should not forget to address them: * Provide complete and accurate minutes of the f2f meeting last week. As announced, Miguel sent detailed instructions to follow regarding this (based on feedback by some partners, we will change the place where you should upload them, Miguel will send an email updating on this). PLEASE don't forget to transform Actions Points you identified into WorkItems in the corresponding tracker (your chapter tracker or the FI-WARE-Private tracker). Miguel will setup a Backlog Management tracker on the "FI-WARE Private" project so that you will be able to create WorkItems you believe that need to be addressed and followed-up at FI-WARE global level. * Complete response to questionnaire distributed by the Testbed team. This is urgent in order to complete the Testbed design. * SAP: complete revision of Epics linked to BM&BE GE being considered in the first Open Call. * Planning of sprint 4 (this requires the first point regarding identification of WorkItems to be done) * Address APs identified during Security plenary session: * Each Chapter to provide their answers to the questions raised by the Security team for each of the Security GEs (the sooner, the better and no later than by end of this week so 3/02/2012) * Each Chapters to consider integration of Security GEs within their Chapter architecture and whenever those are needed and at appropriate level (i.e. architecture level, GE level). As a first step, this should lead to definition of at least one Epic by chapter and GEs to reflect this as ongoing work * Each Chapter to analyze the interaction (sequence) diagram with the Security Monitoring GE to check, amend/complete and validate them (there is one for each of the Chapters that was elaborated by the Security team). This is needed prior delivery of the information requested by the Security Chapter (i.e. log, security events, countermeasures, ....) by Security Monitoring GE (also gets the architecture of the chapter ready to have this information delivered). The Security chapter will provide other chapters with information needed by Security Monitoring GE (also format under which this information has to be provided) * Review status of UC project tickets to update them or make some progress. Don't forget to change the assignee of a ticket to be the issuer whenever you change the state to "Needs revision by the issuer". * Standardization Plan: please check latest requests on the matter ... there is info pending ! 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 -------------- A non-text attachment was scrubbed... Name: WP8 Session at FI-WARE GA 25012012 [Mode de compatibilit?].pdf Type: application/pdf Size: 2943776 bytes Desc: WP8 Session at FI-WARE GA 25012012 [Mode de compatibilit?].pdf URL: From marco.ughetti at telecomitalia.it Mon Feb 6 16:02:17 2012 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Mon, 6 Feb 2012 16:02:17 +0100 Subject: [Fiware-apps] Action points status Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5383B22C2E08A@GRFMBX707BA020.griffon.local> Hi Torsten, This email is just to update you on what we have done about mediation staff. Currently we have: 1. Added backlogs entries (Epics, Feature, UserStories) regarding the API implementations and the first mediation task (SOAP2REST) we discussed in Madrid 2. Added Workitems on what we are doing (API definition, testbed requirement, some check about how to address the delivery of the first instance of the mediator for internal tests) 3. Added a first draft of the OPenSpec for MediatorAPI As Miguel pointed out, all the tickets created in Apps.Mediation are associated only with the "Default" filter. I don't know why and how to fix it Concerning with the Security questions, I think that the only relationship between the mediator and the security stuff are related to Identity Server and currently I don't have any other question. Probably I first need to understand what kind of API the Identity Server will provide in order to evaluate the impact on mediator As I will be on business trip, I will not attend the call tomorrow morning. For TI, Enrico will attend it Best Marco 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. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From torsten.leidig at sap.com Mon Feb 6 17:06:22 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 6 Feb 2012 17:06:22 +0100 Subject: [Fiware-apps] Joint Apps-i2nd MEETING IN mADRID In-Reply-To: References: Message-ID: Dear Pier, Thanks for preparing the minutes document. I just added one statement about the use of USDL for GE, which want to expose their services for the Business Framework. According to the participants I don't remember exactly who from Apps was in the meeting. So I kindly ask the people to add themselves to the attendee list. Best regards, Torsten From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Montag, 6. Februar 2012 10:06 To: Leidig, Torsten Cc: Hans Einsiedler (Hans.Einsiedler at telekom.de) Subject: Joint Apps-i2nd MEETING IN mADRID Dear Torsten, during the Madrid meeting we had a joint session between Apps and I2ND chapters, during which I wrote a short summary of the discussions, you can find it at the following link: https://docs.google.com/document/d/1Sr9CVo4aw1KMz5lfqrlSS7vE0TrR7z11PUW07WwNBDE/edit Could you please check that it's ok for you (list of Apps attendants should be added), and make possible modifications if something is erroneously reported, so that we can later upload the minutes on the project Forge site? Many thanks and Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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. [cid:image001.gif at 01CCE4F1.A6DC2BC0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From uwe.riss at sap.com Mon Feb 6 17:31:43 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 6 Feb 2012 17:31:43 +0100 Subject: [Fiware-apps] FI-WARE WP3 Call Message-ID: <1491C91A94302A448D73CD9C6B7A782045D89CE63E@DEWDFECCR02.wdf.sap.corp> When: Dienstag, 7. Februar 2012 10:00-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 call. The agenda contains the following issues: ? Short presentation of the Architecture (Torsten) ? Status of the Open Specifications ? Status of Security requirements specification ? Status of Testbed requirements specification Best regards, Uwe To join the meeting: https://sap.emea.pgiconnect.com/D026158 Participant Passcode: 656 085 0596 Adobe Connectivity Test: https://admin.acrobat.com/common/help/en/support/meeting_test.htm 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# 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5889 bytes Desc: not available URL: From torsten.leidig at sap.com Tue Feb 7 09:37:46 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 7 Feb 2012 09:37:46 +0100 Subject: [Fiware-apps] FW: [Fiware-wpa] Reviewers have requested access to FusionForge In-Reply-To: <4F302304.9050400@tid.es> References: <942FD2F004D742BAA1C638BDEB2354B4@ManSzePC> <4F302304.9050400@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: Montag, 6. Februar 2012 19:59 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Reviewers have requested access to FusionForge Hi all, Prior giving access to FusionForge to our reviewer, Man-Sze Li, I want you to be aware. I will give her access from tomorrow morning 11:00am on, unless I hear about any objection. A good reason for you to take care about the status of your stuff :-) particularly the tracker. 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 -------- Original Message -------- Subject: RE: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Date: Mon, 6 Feb 2012 11:52:16 +0100 From: Man-Sze Li To: JUAN JOSE HIERRO SUREDA Dear Dr Hierro I would wish to take up the offer to be able to access the FI-WARE backlogs live. Thank you in advance for arranging for a user account on FusionForge for me. Best regards Man-Sze Li -----Original Message----- From: Arian.ZWEGERS at ec.europa.eu [mailto:Arian.ZWEGERS at ec.europa.eu] Sent: 26 January 2012 10:35 To: msli at icfocus.co.uk; dgr at whitestein.com; rdifrancesco at ymail.com; bel.piet1 at gmail.com Subject: FW: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog fyi -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Thursday, January 26, 2012 11:11 AM To: ZWEGERS Arian (INFSO); INFSO-ICT-285248 Cc: Jose Jimenez; Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Submission of deliverable D.2.1.a FI-WARE Requirements Backlog Dear Arian, This is the official submission of deliverable D.2.1.a "FI-WARE Requirements Backlog" of the FI-WARE project. As you know, the FI-WARE Backlog is managed through several trackers (each FI-WARE chapter managing its own tracker), in combination with the public Wiki. Contents of the FI-WARE Backlog are constantly updated through the subsequent FI-WARE sprints, following an Agile approach. Therefore, versions of deliverable D.2.1 correspond to snapshots of these trackers. It took some time to find the way we could generate such a snapshot and adjust the format. On the other hand, the exercise allowed us to identify some missalignments regarding formatting conventions across FI-WARE chapters (e.g., notation for release or sprint ids, ids for entries, etc.) we have fixed. There should not be that much delay in subsequent submissions of the deliverable. Given the nature of the deliverable, we found that an spreadsheet format was the most useful and convenient format. Note that the deliverable corresponded to a snapshot we took early in December. Therefore, the backlog has evolved since then. If you or the reviewers wish to access the FI-WARE Backlogs "live" it would be as easy to create a user account for you on the different FI-WARE chapter projects in FusionForge. I remind you that this was something we already offered in September 2011. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx . ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jesus.gorronogoitia at atosresearch.eu Tue Feb 7 11:32:37 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 07 Feb 2012 11:32:37 +0100 Subject: [Fiware-apps] Open Specifications Message-ID: <1328610757.2451.15.camel@avalon.atos.net> Dear Marco Ughetti, Rafael Fern?ndez we are interested in participating in the specification of open specifications for Mediator, CompositionEditor and CompositionExecution. ?Could you explain us how do you think we should participate? ?Editing directly the text in the WIKI? ?Should we have some preliminar discussion by email? ?How can we manage versioning if different contributors are working in parallel? ?How do we get consensus? Particular questions: - Current CompositionEditor is very mash-up oriented, which does not fit with our requirements for composition, basically a BPMN 2.0 editor, such as Oryx. Can we add our methods/features in the interaction protocol for service composition? I am planning just to add very generic service composition interactions from the typical task composition using work and data flow (i.e. BPMN/BPEL, etc) - Mediation: current specification is a bit generic, based on proxy. Can we add our methods/features in the interaction protocol for data mediation? Kind regards Yosu ------------------------------------------------------------------ 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 jesus.gorronogoitia at atosresearch.eu Tue Feb 7 14:15:26 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 07 Feb 2012 14:15:26 +0100 Subject: [Fiware-apps] Open Specifications Message-ID: <1328620526.2451.50.camel@avalon.atos.net> Dear Marco Ughetti, Rafael Fern?ndez we are interested in participating in the specification of open specifications for Mediator, CompositionEditor and CompositionExecution. ?Could you explain us how do you think we should participate? ?Editing directly the text in the WIKI? ?Should we have some preliminar discussion by email? ?How can we manage versioning if different contributors are working in parallel? ?How do we get consensus? Particular questions: - Current CompositionEditor is very mash-up oriented, which does not fit with our requirements for composition, basically a BPMN 2.0 editor, such as Oryx. Can we add our methods/features in the interaction protocol for service composition? I am planning just to add very generic service composition interactions from the typical task composition using work and data flow (i.e. BPMN/BPEL, etc) - Mediation: current specification is a bit generic, based on proxy. Can we add our methods/features in the interaction protocol for data mediation? Kind regards Yosu ------------------------------------------------------------------ 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 miguel.huerta at atos.net Tue Feb 7 16:00:12 2012 From: miguel.huerta at atos.net (=?UTF-8?B?TWlndWVsIMOBbmdlbCBIdWVydGE=?=) Date: Tue, 07 Feb 2012 16:00:12 +0100 Subject: [Fiware-apps] Open Specifications In-Reply-To: <1328620526.2451.50.camel@avalon.atos.net> References: <1328620526.2451.50.camel@avalon.atos.net> Message-ID: <4F313C7C.3090708@atos.net> On 02/07/2012 02:15 PM, Yosu Gorro?ogoitia wrote: > Dear Marco Ughetti, Rafael Fern?ndez > > we are interested in participating in the specification of open > specifications for Mediator, CompositionEditor and CompositionExecution. > ?Could you explain us how do you think we should participate? ?Editing > directly the text in the WIKI? ?Should we have some preliminar > discussion by email? ?How can we manage versioning if different > contributors are working in parallel? ?How do we get consensus? > > Particular questions: > - Current CompositionEditor is very mash-up oriented, which does not fit > with our requirements for composition, basically a BPMN 2.0 editor, such > as Oryx. Can we add our methods/features in the interaction protocol for > service composition? I am planning just to add very generic service > composition interactions from the typical task composition using work > and data flow (i.e. BPMN/BPEL, etc) > > - Mediation: current specification is a bit generic, based on proxy. Can > we add our methods/features in the interaction protocol for data > mediation? > > Kind regards > Yosu > > > ------------------------------------------------------------------ > 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. > ------------------------------------------------------------------ > ------------------------------------------------------------------ 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 uwe.riss at sap.com Tue Feb 7 16:01:12 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 7 Feb 2012 16:01:12 +0100 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782045D8A81BF5@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/794/FI-WARE+WP3+Minutes+07-02-2012.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 It contains links to meeting minutes and well as to the Open Spec page. Please update the status of your Open Spec, respectively. 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 jesus.gorronogoitia at atosresearch.eu Tue Feb 7 16:09:50 2012 From: jesus.gorronogoitia at atosresearch.eu (Yosu =?ISO-8859-1?Q?Gorro=F1ogoitia?=) Date: Tue, 07 Feb 2012 16:09:50 +0100 Subject: [Fiware-apps] Open Specifications In-Reply-To: <4F313C7C.3090708@atos.net> References: <1328620526.2451.50.camel@avalon.atos.net> <4F313C7C.3090708@atos.net> Message-ID: <1328627390.2451.64.camel@avalon.atos.net> Dear Torsten, it seems the messages we sent to the FIWARE WP3 mailing list don't reach the recipient. Did you receive below message sent to this list? Kind regards Yosu > > Dear Marco Ughetti, Rafael Fern?ndez > > > > we are interested in participating in the specification of open > > specifications for Mediator, CompositionEditor and > CompositionExecution. > > ?Could you explain us how do you think we should participate? > ?Editing > > directly the text in the WIKI? ?Should we have some preliminar > > discussion by email? ?How can we manage versioning if different > > contributors are working in parallel? ?How do we get consensus? > > > > Particular questions: > > - Current CompositionEditor is very mash-up oriented, which does not > fit > > with our requirements for composition, basically a BPMN 2.0 editor, > such > > as Oryx. Can we add our methods/features in the interaction protocol > for > > service composition? I am planning just to add very generic service > > composition interactions from the typical task composition using > work > > and data flow (i.e. BPMN/BPEL, etc) > > > > - Mediation: current specification is a bit generic, based on proxy. > Can > > we add our methods/features in the interaction protocol for data > > mediation? > > > > Kind regards > > Yosu ------------------------------------------------------------------ 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 rfernandez at fi.upm.es Tue Feb 7 19:09:33 2012 From: rfernandez at fi.upm.es (=?ISO-8859-1?Q?Rafael_Fern=E1ndez?=) Date: Tue, 7 Feb 2012 19:09:33 +0100 Subject: [Fiware-apps] Open Specifications In-Reply-To: <1328610757.2451.15.camel@avalon.atos.net> References: <1328610757.2451.15.camel@avalon.atos.net> Message-ID: Dear Yosu, It seems the message took about 7 hours to get our mailbox, but it finally reached it! :-) We (UPM) are currently writing the Open Specs of both the Composition Editor and Composition Execution enablers, but our "interactions" are taking into account only our focus on application mashup, so it would be great if you can participate on it. We think editing the text in the wiki is ok, but you should try to avoid clicking on the main "edit" link (located in the upper tabs section) since it edits the whole page and two simultaneous edits will result in a conflict. Instead, use the other edit links next to every section headers... Best regards, Rafa On Tue, Feb 7, 2012 at 11:32 AM, Yosu Gorro?ogoitia < jesus.gorronogoitia at atosresearch.eu> wrote: > Dear Marco Ughetti, Rafael Fern?ndez > > we are interested in participating in the specification of open > specifications for Mediator, CompositionEditor and CompositionExecution. > ?Could you explain us how do you think we should participate? ?Editing > directly the text in the WIKI? ?Should we have some preliminar > discussion by email? ?How can we manage versioning if different > contributors are working in parallel? ?How do we get consensus? > > Particular questions: > - Current CompositionEditor is very mash-up oriented, which does not fit > with our requirements for composition, basically a BPMN 2.0 editor, such > as Oryx. Can we add our methods/features in the interaction protocol for > service composition? I am planning just to add very generic service > composition interactions from the typical task composition using work > and data flow (i.e. BPMN/BPEL, etc) > > - Mediation: current specification is a bit generic, based on proxy. Can > we add our methods/features in the interaction protocol for data > mediation? > > Kind regards > Yosu > > ------------------------------------------------------------------ > 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. > ------------------------------------------------------------------ > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps > -- *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 torsten.leidig at sap.com Wed Feb 8 09:30:46 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 8 Feb 2012 09:30:46 +0100 Subject: [Fiware-apps] Open Specifications In-Reply-To: <1328610757.2451.15.camel@avalon.atos.net> Message-ID: Dear Compositioners and Mediators, We said in the GA workshops and also yesterday, that we will have multiple GE Open Specifications for Composition Editor and Execution in the first place. I think the same situation is with the Mediators. So I suggest to every partner adds his own Open Specification pages. E.g. FIWARE.OpenSpecification.Apps.CompositionEditor.Mashup (DTAG) FIWARE.OpenSpecification.Apps.CompositionEditor.Widget (UPM) We will see later whether it's possible to derive a generic specification if necessary. Regards, Torsten On 07.02.12 11:32, "Yosu Gorro?ogoitia" wrote: >Dear Marco Ughetti, Rafael Fern?ndez > >we are interested in participating in the specification of open >specifications for Mediator, CompositionEditor and CompositionExecution. >?Could you explain us how do you think we should participate? ?Editing >directly the text in the WIKI? ?Should we have some preliminar >discussion by email? ?How can we manage versioning if different >contributors are working in parallel? ?How do we get consensus? > >Particular questions: >- Current CompositionEditor is very mash-up oriented, which does not fit >with our requirements for composition, basically a BPMN 2.0 editor, such >as Oryx. Can we add our methods/features in the interaction protocol for >service composition? I am planning just to add very generic service >composition interactions from the typical task composition using work >and data flow (i.e. BPMN/BPEL, etc) > >- Mediation: current specification is a bit generic, based on proxy. Can >we add our methods/features in the interaction protocol for data >mediation? > >Kind regards >Yosu > >------------------------------------------------------------------ >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. >------------------------------------------------------------------ > >_______________________________________________ >Fiware-apps mailing list >Fiware-apps at lists.fi-ware.eu >http://lists.fi-ware.eu/listinfo/fiware-apps From torsten.leidig at sap.com Thu Feb 9 07:54:41 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 9 Feb 2012 07:54:41 +0100 Subject: [Fiware-apps] FW: [Fiware-wpa] Tutorial: Creation of deliverables with wiki pages In-Reply-To: <4F32FE09.6070307@tid.es> References: <4F32FE09.6070307@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 Miguel Carrillo Sent: Mittwoch, 8. Februar 2012 23:58 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Tutorial: Creation of deliverables with wiki pages Dear WPLs/WPAs, Please note that there is a new tutorial to teach everyone to create pdf documents with the wiki. All public deliverables should use this method as all public deliverables will be worked and deposited on the wiki. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_pdf_deliverables_from_wiki_pages Important: as leaders of your WPs, you have to make sure that all the editors of the documents are aware of this. Do not forget this, if not they get lost. 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 -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From marco.ughetti at telecomitalia.it Thu Feb 9 15:01:03 2012 From: marco.ughetti at telecomitalia.it (Ughetti Marco) Date: Thu, 9 Feb 2012 15:01:03 +0100 Subject: [Fiware-apps] R: Open Specifications In-Reply-To: <1328610757.2451.15.camel@avalon.atos.net> References: <1328610757.2451.15.camel@avalon.atos.net> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5383B22C2EDA1@GRFMBX707BA020.griffon.local> Dear Yosu, I apologize for the delayed reply but I experienced some problems with some emails (this one went to the spam folder) Obviously it would be great if you can participate to the OpenSpecs. Consider that current version of the spec is generic because we decided to balance various aspects: - to provide an api not strictly related to our asset; - to provide an api that allows to add generic mediation task (most of them unknown so far) - to provide an api that we will be able to implement in the reference implementation :) I'd like to keep the APIs quite generic (i.e. to avoid to have a specific API method for every specific mediation task available) but I'm open to discuss about it If you are thinking to specific data mediation tasks please feel free to add to the wiki (maybe in a specific "live" section) so we can think about them and how to expose them through APIs If you think that a specific call or webex can be useful we can arrange it Best Marco -----Messaggio originale----- Da: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] Per conto di Yosu Gorro?ogoitia Inviato: marted? 7 febbraio 2012 11:33 A: 'fiware-apps at lists.fi-ware.eu' Oggetto: [Fiware-apps] Open Specifications Dear Marco Ughetti, Rafael Fern?ndez we are interested in participating in the specification of open specifications for Mediator, CompositionEditor and CompositionExecution. ?Could you explain us how do you think we should participate? ?Editing directly the text in the WIKI? ?Should we have some preliminar discussion by email? ?How can we manage versioning if different contributors are working in parallel? ?How do we get consensus? Particular questions: - Current CompositionEditor is very mash-up oriented, which does not fit with our requirements for composition, basically a BPMN 2.0 editor, such as Oryx. Can we add our methods/features in the interaction protocol for service composition? I am planning just to add very generic service composition interactions from the typical task composition using work and data flow (i.e. BPMN/BPEL, etc) - Mediation: current specification is a bit generic, based on proxy. Can we add our methods/features in the interaction protocol for data mediation? Kind regards Yosu ------------------------------------------------------------------ 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. ------------------------------------------------------------------ _______________________________________________ Fiware-apps mailing list Fiware-apps at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-apps 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 uwe.riss at sap.com Mon Feb 13 16:32:23 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 13 Feb 2012 16:32:23 +0100 Subject: [Fiware-apps] FI-WARE WP3 Call Message-ID: <1491C91A94302A448D73CD9C6B7A782045D8C8BF27@DEWDFECCR02.wdf.sap.corp> When: Occurs every Dienstag effective 14.02.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. Best regards, Uwe To join the meeting: https://sap.emea.pgiconnect.com/D026158 Participant Passcode: 656 085 0596 Adobe Connectivity Test: https://admin.acrobat.com/common/help/en/support/meeting_test.htm 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# 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6159 bytes Desc: not available URL: From uwe.riss at sap.com Tue Feb 14 13:23:00 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Tue, 14 Feb 2012 13:23:00 +0100 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782045D8D20192@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/806/FI-WARE_WP3_Minutes_14-02-12.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 It contains links to the meeting minutes and others. Please update the status of your Open Spec, respectively. 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 torsten.leidig at sap.com Wed Feb 15 12:02:13 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 15 Feb 2012 12:02:13 +0100 Subject: [Fiware-apps] FW: [Fiware-wpa] IMPORTANT: Reference example on Main Interactions section to be followed In-Reply-To: <4F3B8055.1050703@tid.es> References: <4F3B8055.1050703@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: Mittwoch, 15. Februar 2012 10:52 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: Reference example on Main Interactions section to be followed Hi, While reviewing the different drafts of the "Architecture Description" chapters, I have found that many of the descriptions of "Main Interactions" is quite poor. We have developed a good reference example for this kind of sections. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 If you have followed the reference example provided initially based on the CORBA specifications as well as the guidelines already provided, you should not have anything too far from this, but unfortunately, I'm discovering that this is not the case in many of the GE Architecture Descriptions. The guidelines for editing the "Architecture Description" deliverable have been updated accordingly. I encourage you to review them carefully and add any question on teh FAQ section you may have. You may find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions 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 uwe.riss at sap.com Wed Feb 22 11:22:43 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 22 Feb 2012 11:22:43 +0100 Subject: [Fiware-apps] FIWARE WP3 Call - Minutes In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782045D90C1CFB@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/820/FI-WARE_WP3_Minutes_21-02-12.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 It contains links to the meeting minutes and others. It also contains links to the use cases mentioned in the call. 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 Mon Feb 27 17:19:38 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 27 Feb 2012 17:19:38 +0100 Subject: [Fiware-apps] FIWARE WP3 Call - Preparation In-Reply-To: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782045D61ADA81@DEWDFECCR02.wdf.sap.corp> Message-ID: <1491C91A94302A448D73CD9C6B7A782045D91EDE52@DEWDFECCR02.wdf.sap.corp> Dear WP3 Colleagues, As preparation for the conf call tomorrow I send you the suggested release plan from Madrid: Release Planning The following stories will be addressed in the first major release 1. CE calls Marketplace 2. CE publish offering to store (alternatively: publish offering into the store via Store UI) 3. CE puts composite service USDL into the Repository. 4. Mediator Proxy generator is used via Web UI 5. Manual mapping REST service to SOAP which can be used in DT Mashup platform 6. Newly created SOAP service is used in CE 7. Store is registered on the Marketplace (manually) 8. Marketplace asks for offerings on the store 9. CE can discover services on the Marketplace 10. User goes to Store and buys service 11. Order is fed back to provider. Please review these items so that we can discuss open questions regarding their realization tomorrow. Besides, I will give an update of today's WPL/WPA conf call. 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 torsten.leidig at sap.com Mon Feb 27 17:51:13 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 27 Feb 2012 17:51:13 +0100 Subject: [Fiware-apps] Meeting minutes Message-ID: And the pw ;-) Regards, Torsten 1234abcD -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Mon Feb 27 17:53:11 2012 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Mon, 27 Feb 2012 17:53:11 +0100 Subject: [Fiware-apps] Joint WPLs/WPAs follow-up confcall (February 27th) - Google Docs Message-ID: https://docs.google.com/document/d/1gkEUTMfUizrYxt9y24jOWdT3fvFpv5nKQJch1_3sVAc/edit?pli=1 FYI: the meeting minutes of today's WPL/WPA call (readable/writeable for everyone with the link and the pass...) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsoriano at fi.upm.es Tue Feb 28 11:36:05 2012 From: jsoriano at fi.upm.es (Javier Soriano (FI-UPM)) Date: Tue, 28 Feb 2012 11:36:05 +0100 Subject: [Fiware-apps] About considering widgets and app mashups for the next release Message-ID: Dear Uwe, dear all, We apologize we haven't raised this during the confcal, but we wanted to further elaborate on it before presenting our proposal. We were ok with the release (April) planning discussed today during our weekly telco (i.e. the one included in the minutes of our workshops in Madrid), which is focused on services and ignores widgets and application mashups, because we (UPM) aren't sure we have enough effort assigned to WP3 so as to guarantee we can achieve the integration of our asset with the marketplace, store, etc. in this release. But, nevertheless, we want to keep on working on the integration of our asset (WireCloud Widget Platform: an application mashup CE and execution engine) because, bearing in mind the following requirement coming from the UC Projects: [#1095] Finest.Epic.IoS.WidgetPlatformInfrastructuresubmitted by Stephan Heyne (from FINEST project): " A visual portal website is needed where each user can add, remove and use widgets. Therefore, also a widget repository is needed where a user can select widgets from. An infrastructure should be provided to deploy new widgets to the portal. It should be easy to use by an end-user." it urges to be able to publish a mashup (i.e. an offering??) into the store, put its USDL description into the Repository, discover widgets and/or mashups on the Marketplace, and go to store and "buy"/"pick" widget or app mashup. We could try to have it done for this release (by April 30) if you agree to include it in the release planning. For example: 1. CE calls Marketplace 2. CE CAN DISCOVER WIDGETS AND APPLICATION MASHUPS ON THE MARKETPLACE 3. USER GOES TO STORE AND PICKS WIDGETS / APP MASHUPS 4. Order is fed back to provider??? 5. WIDGETS AND APP MASHUPS ARE USED IN CE TO PRODUCE A NEW APP MASHUP 6. CE PUBLISH NEW APP MASHUP OFFERING TO STORE (ALTERNATIVELY: PUBLISH APP MASHUP OFFERING INTO THE STORE VIA STORE UI) 7. CE PUTS NEW APP MASHUP USDL INTO THE REPOSITORY 8. Store is registered on the Marketplace (manually) 9. Marketplace asks for offerings on the store 10. CE CAN DISCOVER THE NEW APP MASHUP ON THE MARKETPLACE 11. USER GOES TO STORE AND PICKS APP MASHUP 12. Order is fed back to provider??? 13. APP MASHUP ARE USED IN CE Does it make sense to you to include it in the release planning? BTW, we are working on addressing Juanjo's comments on open specs. Rafael told you about it. 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: