From jhierro at tid.es Thu Dec 1 09:04:01 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 01 Dec 2011 09:04:01 +0100 Subject: [Fiware-wpa] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting Message-ID: <4ED734F1.1030905@tid.es> Hi, Based on the inputs from some of you and other project members, I feel like it would not be a bad idea to have a General Assembly meeting the whole week of January 16th. My idea is that it would be mostly an opportunity for each WP to have bi-lateral meetings or tri-lateral meetings with other WPs, and fill the gaps of the agenda of the week to meet within the WP for their own benefit. Please, each of you, confirm whether there is any objection or not, so that I can announce it tomorrow. I believe that we would be able to make the necessary arrangements to host the meeting here in Madrid but, of course, any other proposal is welcome. On the other hand, I would like to arrange first a virtual meeting of the WPAs the week of December 19 and then a two-days face2face meeting the week of January 9th to work on cross-chapter architectural aspects and design the architectural vision about how all chapters can fit together into an uniform platform. Regarding the face2face meeting, we again volunteer to host it in Madrid but any other proposal is welcome. One possibility would be to have it on January 12-13 in the same place as the General Assembly meeting so that those who travel from far away can stay over the weekend ... For both the virtual and face2face meeting, I will setup a doodle. I take this opportunity to remind you that we will have a joint WPL/WPA confcall next Monday December 5, starting at 11:00am. What thing I would like to address in that confcall is the Open Call, so I would kindly ask you to bring a prioritized list of topics for the Open Call so that we can discuss. Bear in mind that we will have a meeting of the FI-PPP AB on December 15 where we will try to agree on a list of topics for the first Open Call, so it would nice that we can agree on what to bring there. I will send a more detailed agenda of topics for our joint WPL/WPA confcall along this morning. Looking forward your feedback regarding the GA meeting, -- 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 From torsten.leidig at sap.com Thu Dec 1 09:29:22 2011 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Thu, 1 Dec 2011 09:29:22 +0100 Subject: [Fiware-wpa] IMPORTANT: Approach for Architecture Specification Deliverable In-Reply-To: <4ED63FF2.6020400@tid.es> References: <4ED63FF2.6020400@tid.es> Message-ID: Dear Juanjo, thanks for the information. However, I think it's of only limited value. Please provide a concrete template for the specification documents! How about using the Wiki for documentation again? FI-Ware is not a standards organization. Please be aware that some of the specifications that where developed in conjunction with FI-Ware will probably be published in a standardization community using their formats. The FI-Ware spec will probably be not much more than a commented reference. 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. 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, 30. November 2011 15:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: Approach for Architecture Specification Deliverable Hi all, As you know, we have to start working on the Architecture Specifications, which is one of the deliverables that is due in month 9, that is, end of January. My intention is to adopt a pragmatic approach, trying to generate something that can be integrated as part of the GE Open Specifications that we have to produce by month 12. My vision is that all GE Open Specifications should start with a chapter where an overview of the envisioned Architecture for the GE is described. While style would be narrative, the description should be enough concrete, i.e., formulated over actual data type, interface and operation names and elaborating on the base interaction scenarios involving the different entities exporting the defined interfaces. Then, after that chapter, the detailed specification of all data types and interfaces with their operations, are provided (this including signature of operations and accurate description of expected behaviour linked to operations) Then, the Architecture Specification deliverable would be just the result of developing this overview chapter. But nothing better than an example, so let me use one taken from OMG's set of CORBA Services Specifications. Along my many years involved in different standardization efforts, I have found that OMG CORBA Service specs are rather comprehensive and close to what programmers (our ultimate customers!) love to see. Please find enclosed the CORBA Event Service Specifications. What I would then select as the Architecture description are the contents of the following sections: * The whole chapter 1 * Section 2.2 and 2.4 (which some people may have argued should have been included in chapter 1 :-) Note that anyone who reads the mentioned sections would get a CLEAR picture of what is the Architecture of the service and what are going to be the entities and interfaces/operations that will be supported in a compliant implementation. The conceptual and programming model would be also rather clear from a programmer's perspective. Therefore, rather valuable information for an application developer perspective which is what really should matter to us. A side benefit is that what will remain as pending regarding GE Open Specifications will be less, that is, the detailed specification of data types and interfaces/operations. One thing that we will have to define is the set of conventions that we should all follow whenever we need to draw any figure, like figures 1-x or 2-x. For this, Thomas and me will come soon to you with a proposal in short time. Please take your time to analyze this carefully and formulate any question you may have. From now on, I assume that you will start planning activities in Sprint 2 and 3 dealing with development of these specifications within each of your chapters. This may well take the form of Work Items in the tracker. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Thu Dec 1 09:42:32 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Thu, 1 Dec 2011 10:42:32 +0200 Subject: [Fiware-wpa] [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting In-Reply-To: <4ED734F1.1030905@tid.es> References: <4ED734F1.1030905@tid.es> Message-ID: Dear Juanjo, all, I think it is a good idea to have F2F meetings within each WP during January, to boost the work on the M9 deliverable, as well as to make sure we are on track with actual implementation and initial integration (within the WP) towards M12. In fact, I was thinking to arrange such a meeting for WP4 myself. Also, it might be good to have a F2F meeting between WPAs. What I would suggest is to hold both during the same week at the same place (could be in Madrid), to relieve travel constraints which I'm sure many of us have. We can start with a full-day WPAs meeting (e.g., 8:30am to 6:30pm), followed by 3- or 4-day of plenary (majority of which would be dedicated to parallel sessions in each WP). The week of January 16th sounds like a good candidate (and I don't think that spreading this across a weekend is necessary). Regards, Alex fiware-wpl-bounces at lists.fi-ware.eu wrote on 01/12/2011 10:04:01 AM: > From: Juanjo Hierro > To: "fiware-wpl at lists.fi-ware.eu" , > "fiware-wpa at lists.fi-ware.eu" > Date: 01/12/2011 10:04 AM > Subject: [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly > (Plenary) meeting > Sent by: fiware-wpl-bounces at lists.fi-ware.eu > > Hi, > > Based on the inputs from some of you and other project members, I > feel like it would not be a bad idea to have a General Assembly meeting > the whole week of January 16th. > > My idea is that it would be mostly an opportunity for each WP to have > bi-lateral meetings or tri-lateral meetings with other WPs, and fill the > gaps of the agenda of the week to meet within the WP for their own benefit. > > Please, each of you, confirm whether there is any objection or not, > so that I can announce it tomorrow. > > I believe that we would be able to make the necessary arrangements to > host the meeting here in Madrid but, of course, any other proposal is > welcome. > > On the other hand, I would like to arrange first a virtual meeting of > the WPAs the week of December 19 and then a two-days face2face meeting > the week of January 9th to work on cross-chapter architectural aspects > and design the architectural vision about how all chapters can fit > together into an uniform platform. Regarding the face2face meeting, we > again volunteer to host it in Madrid but any other proposal is > welcome. One possibility would be to have it on January 12-13 in the > same place as the General Assembly meeting so that those who travel from > far away can stay over the weekend ... For both the virtual and > face2face meeting, I will setup a doodle. > > I take this opportunity to remind you that we will have a joint > WPL/WPA confcall next Monday December 5, starting at 11:00am. What > thing I would like to address in that confcall is the Open Call, so I > would kindly ask you to bring a prioritized list of topics for the Open > Call so that we can discuss. Bear in mind that we will have a meeting > of the FI-PPP AB on December 15 where we will try to agree on a list of > topics for the first Open Call, so it would nice that we can agree on > what to bring there. I will send a more detailed agenda of topics for > our joint WPL/WPA confcall along this morning. > > Looking forward your feedback regarding the GA meeting, > > -- 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Dec 1 09:52:00 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 01 Dec 2011 09:52:00 +0100 Subject: [Fiware-wpa] IMPORTANT: Approach for Architecture Specification Deliverable In-Reply-To: References: <4ED63FF2.6020400@tid.es> Message-ID: <4ED74030.9080302@tid.es> Of course the deliverables will be developed on the Wiki ! I thought it was clear that we won't longer generate word documents for any of the Public Deliverables ... What I haven't made my mind yet is where on the Wiki we will place the contents ... this might be a topic we discuss in our joint WPLs/WPAs confcall next Monday. I agree that in those cases where the specifications of APIs and Interfaces we are implementing match specifications already published by some standardization body, the contents of the Wiki will probably be not much more than a commented reference ... But note that typically there is a divergence between what is actually implemented in the product and the public standard specifications (mostly when we are talking about standard specifications that are "in progress" or yet preliminary). In those cases, we need to comment on what are the differences. May you elaborate on any particular case you have in mind ? Then we may agree on how to handle it ... Best regards, -- Juanjo On 01/12/11 09:29, Leidig, Torsten wrote: Dear Juanjo, thanks for the information. However, I think it?s of only limited value. Please provide a concrete template for the specification documents! How about using the Wiki for documentation again? FI-Ware is not a standards organization. Please be aware that some of the specifications that where developed in conjunction with FI-Ware will probably be published in a standardization community using their formats. The FI-Ware spec will probably be not much more than a commented reference. 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. 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, 30. November 2011 15:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: Approach for Architecture Specification Deliverable Hi all, As you know, we have to start working on the Architecture Specifications, which is one of the deliverables that is due in month 9, that is, end of January. My intention is to adopt a pragmatic approach, trying to generate something that can be integrated as part of the GE Open Specifications that we have to produce by month 12. My vision is that all GE Open Specifications should start with a chapter where an overview of the envisioned Architecture for the GE is described. While style would be narrative, the description should be enough concrete, i.e., formulated over actual data type, interface and operation names and elaborating on the base interaction scenarios involving the different entities exporting the defined interfaces. Then, after that chapter, the detailed specification of all data types and interfaces with their operations, are provided (this including signature of operations and accurate description of expected behaviour linked to operations) Then, the Architecture Specification deliverable would be just the result of developing this overview chapter. But nothing better than an example, so let me use one taken from OMG's set of CORBA Services Specifications. Along my many years involved in different standardization efforts, I have found that OMG CORBA Service specs are rather comprehensive and close to what programmers (our ultimate customers!) love to see. Please find enclosed the CORBA Event Service Specifications. What I would then select as the Architecture description are the contents of the following sections: * The whole chapter 1 * Section 2.2 and 2.4 (which some people may have argued should have been included in chapter 1 :-) Note that anyone who reads the mentioned sections would get a CLEAR picture of what is the Architecture of the service and what are going to be the entities and interfaces/operations that will be supported in a compliant implementation. The conceptual and programming model would be also rather clear from a programmer's perspective. Therefore, rather valuable information for an application developer perspective which is what really should matter to us. A side benefit is that what will remain as pending regarding GE Open Specifications will be less, that is, the detailed specification of data types and interfaces/operations. One thing that we will have to define is the set of conventions that we should all follow whenever we need to draw any figure, like figures 1-x or 2-x. For this, Thomas and me will come soon to you with a proposal in short time. Please take your time to analyze this carefully and formulate any question you may have. From now on, I assume that you will start planning activities in Sprint 2 and 3 dealing with development of these specifications within each of your chapters. This may well take the form of Work Items in the tracker. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Thu Dec 1 09:53:32 2011 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 1 Dec 2011 09:53:32 +0100 Subject: [Fiware-wpa] [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary)meeting In-Reply-To: <4ED734F1.1030905@tid.es> References: <4ED734F1.1030905@tid.es> Message-ID: Hi Juanjo, We have an Architecture on the 18th & 19th of January (in Sophia Antipolis) so we have to change the dates of the AB or find another week for the FI-Ware GM. Just for information, as Sophia is a small place for Orange Labs, I do not have meeting rooms (and only small rooms) to host both meetings (AB and FI-Ware GM) :-( BR Thierry -----Message d'origine----- 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??: jeudi 1 d?cembre 2011 09:04 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary)meeting Hi, Based on the inputs from some of you and other project members, I feel like it would not be a bad idea to have a General Assembly meeting the whole week of January 16th. My idea is that it would be mostly an opportunity for each WP to have bi-lateral meetings or tri-lateral meetings with other WPs, and fill the gaps of the agenda of the week to meet within the WP for their own benefit. Please, each of you, confirm whether there is any objection or not, so that I can announce it tomorrow. I believe that we would be able to make the necessary arrangements to host the meeting here in Madrid but, of course, any other proposal is welcome. On the other hand, I would like to arrange first a virtual meeting of the WPAs the week of December 19 and then a two-days face2face meeting the week of January 9th to work on cross-chapter architectural aspects and design the architectural vision about how all chapters can fit together into an uniform platform. Regarding the face2face meeting, we again volunteer to host it in Madrid but any other proposal is welcome. One possibility would be to have it on January 12-13 in the same place as the General Assembly meeting so that those who travel from far away can stay over the weekend ... For both the virtual and face2face meeting, I will setup a doodle. I take this opportunity to remind you that we will have a joint WPL/WPA confcall next Monday December 5, starting at 11:00am. What thing I would like to address in that confcall is the Open Call, so I would kindly ask you to bring a prioritized list of topics for the Open Call so that we can discuss. Bear in mind that we will have a meeting of the FI-PPP AB on December 15 where we will try to agree on a list of topics for the first Open Call, so it would nice that we can agree on what to bring there. I will send a more detailed agenda of topics for our joint WPL/WPA confcall along this morning. Looking forward your feedback regarding the GA meeting, -- 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From matteo.melideo at eng.it Thu Dec 1 10:36:17 2011 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 01 Dec 2011 10:36:17 +0100 Subject: [Fiware-wpa] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting In-Reply-To: <4ED734F1.1030905@tid.es> References: <4ED734F1.1030905@tid.es> Message-ID: <4ED74A91.9070308@eng.it> Juanjo hi, provided that I fully second the idea to have a plenary meeting in January I suspect that week as quite chaotic: on the 17th of January 17:00 there is the call 8 deadline. Did you considered this? M. Il 01/12/2011 09:04, Juanjo Hierro ha scritto: > Hi, > > Based on the inputs from some of you and other project members, I > feel like it would not be a bad idea to have a General Assembly meeting > the whole week of January 16th. > > My idea is that it would be mostly an opportunity for each WP to have > bi-lateral meetings or tri-lateral meetings with other WPs, and fill the > gaps of the agenda of the week to meet within the WP for their own > benefit. > > Please, each of you, confirm whether there is any objection or not, > so that I can announce it tomorrow. > > I believe that we would be able to make the necessary arrangements to > host the meeting here in Madrid but, of course, any other proposal is > welcome. > > On the other hand, I would like to arrange first a virtual meeting of > the WPAs the week of December 19 and then a two-days face2face meeting > the week of January 9th to work on cross-chapter architectural aspects > and design the architectural vision about how all chapters can fit > together into an uniform platform. Regarding the face2face meeting, we > again volunteer to host it in Madrid but any other proposal is > welcome. One possibility would be to have it on January 12-13 in the > same place as the General Assembly meeting so that those who travel from > far away can stay over the weekend ... For both the virtual and > face2face meeting, I will setup a doodle. > > I take this opportunity to remind you that we will have a joint > WPL/WPA confcall next Monday December 5, starting at 11:00am. What > thing I would like to address in that confcall is the Open Call, so I > would kindly ask you to bring a prioritized list of topics for the Open > Call so that we can discuss. Bear in mind that we will have a meeting > of the FI-PPP AB on December 15 where we will try to agree on a list of > topics for the first Open Call, so it would nice that we can agree on > what to bring there. I will send a more detailed agenda of topics for > our joint WPL/WPA confcall along this morning. > > Looking forward your feedback regarding the GA meeting, > > -- 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-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa > > > -------------- 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 pierangelo.garino at telecomitalia.it Thu Dec 1 15:41:12 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 1 Dec 2011 15:41:12 +0100 Subject: [Fiware-wpa] R: [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting In-Reply-To: <4ED734F1.1030905@tid.es> References: <4ED734F1.1030905@tid.es> Message-ID: Hi Juanjo, I share the opinion of other partners that the week of 16th Jan is the deadline for proposal submission of 8th FP7 Call (Jan 17th), so it might be an issue at least for a whole week meeting. A better week would be probably on Jan 30th or next one. Independent of the meeting date, I would propose to structure the agenda in such a way that two-three days are sufficient for most of the attendants, rather than involving all the people the whole week. BR Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 1 dicembre 2011 09:04 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting Hi, Based on the inputs from some of you and other project members, I feel like it would not be a bad idea to have a General Assembly meeting the whole week of January 16th. My idea is that it would be mostly an opportunity for each WP to have bi-lateral meetings or tri-lateral meetings with other WPs, and fill the gaps of the agenda of the week to meet within the WP for their own benefit. Please, each of you, confirm whether there is any objection or not, so that I can announce it tomorrow. I believe that we would be able to make the necessary arrangements to host the meeting here in Madrid but, of course, any other proposal is welcome. On the other hand, I would like to arrange first a virtual meeting of the WPAs the week of December 19 and then a two-days face2face meeting the week of January 9th to work on cross-chapter architectural aspects and design the architectural vision about how all chapters can fit together into an uniform platform. Regarding the face2face meeting, we again volunteer to host it in Madrid but any other proposal is welcome. One possibility would be to have it on January 12-13 in the same place as the General Assembly meeting so that those who travel from far away can stay over the weekend ... For both the virtual and face2face meeting, I will setup a doodle. I take this opportunity to remind you that we will have a joint WPL/WPA confcall next Monday December 5, starting at 11:00am. What thing I would like to address in that confcall is the Open Call, so I would kindly ask you to bring a prioritized list of topics for the Open Call so that we can discuss. Bear in mind that we will have a meeting of the FI-PPP AB on December 15 where we will try to agree on a list of topics for the first Open Call, so it would nice that we can agree on what to bring there. I will send a more detailed agenda of topics for our joint WPL/WPA confcall along this morning. Looking forward your feedback regarding the GA meeting, -- 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl 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 jhierro at tid.es Thu Dec 1 19:14:39 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 01 Dec 2011 19:14:39 +0100 Subject: [Fiware-wpa] Virtual WPA meeting to deal with cross-chapter architectural chapter In-Reply-To: <4ED734F1.1030905@tid.es> References: <4ED734F1.1030905@tid.es> Message-ID: <4ED7C40F.7010204@tid.es> Hi all, Regarding the virtual meeting of the WPAs that I suggested to plan for the week of December 19th, I suggest that we use the slot for the joint WPL/WPA meeting initially scheduled for that week. I would suggest that we all book at least 2h:30min in our agendas as duration for this virtual meeting. This way, we can use aprox. 2h for the part dealing with cross-chapter architectural discussion and 30 mins for any other matter which may be relevant to tackle from a project management perspective. PLEASE PENCIL THIS in your agendas. Thanks and best regards, -- Juanjo -------- Original Message -------- Subject: [Fiware-wpl] URGENT RESPONSE: FI-WARE General Assembly (Plenary) meeting Date: Thu, 1 Dec 2011 09:04:01 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi, Based on the inputs from some of you and other project members, I feel like it would not be a bad idea to have a General Assembly meeting the whole week of January 16th. My idea is that it would be mostly an opportunity for each WP to have bi-lateral meetings or tri-lateral meetings with other WPs, and fill the gaps of the agenda of the week to meet within the WP for their own benefit. Please, each of you, confirm whether there is any objection or not, so that I can announce it tomorrow. I believe that we would be able to make the necessary arrangements to host the meeting here in Madrid but, of course, any other proposal is welcome. On the other hand, I would like to arrange first a virtual meeting of the WPAs the week of December 19 and then a two-days face2face meeting the week of January 9th to work on cross-chapter architectural aspects and design the architectural vision about how all chapters can fit together into an uniform platform. Regarding the face2face meeting, we again volunteer to host it in Madrid but any other proposal is welcome. One possibility would be to have it on January 12-13 in the same place as the General Assembly meeting so that those who travel from far away can stay over the weekend ... For both the virtual and face2face meeting, I will setup a doodle. I take this opportunity to remind you that we will have a joint WPL/WPA confcall next Monday December 5, starting at 11:00am. What thing I would like to address in that confcall is the Open Call, so I would kindly ask you to bring a prioritized list of topics for the Open Call so that we can discuss. Bear in mind that we will have a meeting of the FI-PPP AB on December 15 where we will try to agree on a list of topics for the first Open Call, so it would nice that we can agree on what to bring there. I will send a more detailed agenda of topics for our joint WPL/WPA confcall along this morning. Looking forward your feedback regarding the GA meeting, -- 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl . ________________________________ 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 mcp at tid.es Fri Dec 2 14:49:43 2011 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 02 Dec 2011 14:49:43 +0100 Subject: [Fiware-wpa] Administration of FI-WARE mailing lists Message-ID: <4ED8D777.80604@tid.es> Dear all, As you are aware, we are using a number of lists that is becoming increasingly high. We are changing the way in which this is handled. I have set up a page with the list of mailing lists on the wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_join_the_mailing_lists (It is not very explicit because I do not want to give names of concrete people on the public wiki and I should not provide the list addresses publicly either. "WorkPackage" is a term not allowed on the wiki, this is why I write "activity" instead. Anyway, I believe that any project member understands this list) >From now on, each WPL will handle his own list, this basically means that the requests will be addresed to them directly. I assume that you have all the info, but if any of you need the passwords and administrative addresses, I am at your disposal. The legal and administrative lists will be handled drectly by our colleagues in the admin section at TID (Javier de Pedro) IMPORTANT: this is for FIWARE members only. I have detected two intruders so far and they were immediately removed from the lists. No one know better that the WPL who is in his WP and who is not! So I have to trust you here and that you will not grant access to anyone external to the project (Use Cases are external, obviously). Have a nice weekend Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 davide.dallecarbonare at eng.it Fri Dec 2 18:02:40 2011 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Fri, 02 Dec 2011 18:02:40 +0100 Subject: [Fiware-wpa] Tools questionnaire v2 Message-ID: <4ED904B0.6030905@eng.it> Dear leaders and architects, The WP9 needs few minutes of your time to fill the attached questionnaire. We strongly ask you take care of it in order to provide us your requirements for the development, deploy, test and validation infrastructure. Thanks to your information we can avoid to waste time towards wrong directions that can also be read by the reviewers as a communication problems inside the consortium. I ask you to send it back to me by Friday 9th EOB and, in the case you will not be able to meet this deadline, please, write me a message with the new date. Kind Regards, Davide ps: the final, v2, of the document will be published into the official FI-WARE wiki within next week with some possible minor updates, nevertheless, you can use the attached version to fill the questionnaire without any problem. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Questionnaire v2.doc Type: application/msword Size: 34304 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Questionnaire v2.odt Type: application/vnd.oasis.opendocument.text Size: 18044 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE DevComE Technical Description v2.pdf Type: application/pdf Size: 712390 bytes Desc: not available URL: From jhierro at tid.es Mon Dec 5 10:49:21 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 05 Dec 2011 10:49:21 +0100 Subject: [Fiware-wpa] Dial-in and Webex details In-Reply-To: <7C982425-95B9-4063-85DE-965335ECF25E@tid.es> References: <7C982425-95B9-4063-85DE-965335ECF25E@tid.es> Message-ID: <4EDC93A1.6020906@tid.es> Hi, Regarding means to dial-in, we will use powwownow: PIN: 050662. Local dial-in phone numbers at: * http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf In addition, here you are the webex link we may use during the confcall. Please join by Webex, not just phone, so that we can track who is connected: https://telefonica.webex.com/telefonica/j.php?ED=188728562&UID=0&PW=NOWFmMzlkZDFj&RT=MTQjMjM%3D Cheers, -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Dec 6 22:54:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 06 Dec 2011 22:54:32 +0100 Subject: [Fiware-wpa] Fwd: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call In-Reply-To: <4EDE8CCE.7080901@tid.es> References: <4EDE8CCE.7080901@tid.es> Message-ID: <4EDE8F18.8070602@tid.es> Hi all, As I already mentioned to you, the FI-PPP AB will meet on December 15th and this meeting will be focused on trying to select a number of topics for the first Open Call to be issued by FI-WARE by the end of January. Following there are a couple of emails I have sent to members of the FI-PPP AB as preparation for this meeting (please read them bottom up) . Note that there is not just homework for UC projects but also for us regarding identification of topics for the Open Call. Therefore, those chapters that had identified some topics for the first Open Call are requested to provide their input following the proposed schedule. As I have already mentioned to the UC projects, please try to be pragmatic and include only those things that are rather clear to you. Don't hesitate to ask any question you may have. Best regards, -- Juanjo -------- Original Message -------- Subject: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:44:46 +0100 From: Juanjo Hierro To: ab at fi-ppp.eu Hi, Note that I have created a separate sheet per project within the spreadsheet. Columns are for voting. You should create the entries in the corresponding sheet. IMPORTANT: Please try to concentrate on what is the highest priority for you and be selective. It's not just a matter of copying all your requests in the FI-WARE tracker. We are going to use this tool in order to find the first list of topics that will go to the first Open Call. But there will be others as you know (at least one, I'm looking for more). Selecting a topic also implies a commitment on behalf of both FI-WARE and the supporting UC projects to work on the related Themes/Epic (*) up to refine them into Features that a) would become part of FI-WARE backlog and b) would be part of the documentation available to submitters of the Open Call. Best regards, -- Juanjo (*) - In general, entries in the "Unclassified Themes/Epics/Features backlog" should have been labeled as either Themes or Epics. Labeling an entry as a Feature or a Story means that there is a development team that can commit to deliver a product that implements the described functionality within the duration of a FI-WARE Release (three consecutive Sprints long) or the duration of a Sprint (one month long), respectively. UC projects should be careful labeling entries in the Unclassified Themes/Epics/Features backlog as Features or Stories because it would be interpreted as the UC project can actually deliver a product in a Release/Sprint timeframe, even if FI-WARE partners were not able to do so. On 06/12/11 20:54, Juanjo Hierro wrote: Hi all, As you know, the next FI-PPP AB (virtual) meeting is scheduled for Dec 15th. It was scheduled to start at 09:00am CET but I belive that duration was not established. I believe that, due to the relevance of the topics, we should spent 4 hours, with a programmed break of about 20 mins in between. So please plan it to take place from 09:00am CET until 13:20pm CET. I believe we should just focus on agreeing on a list of topics for the first Open Call, leaving other potential topics aside. Therefore, my proposal for the agenda is that we cover one proposed topic after another, in a similar way we made it for some of the topics during our last face2face meeting, trying to make a decision on whether we should include each topic in this first Open Call or not. In order to be effective, I would suggest that we place the topics to discuss in a shared Google docs spreasheet prior to the meeting. I have created one inspired in the excel spreadsheet we used during our face2face meeting in Munich: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE (note: anyone who gets access to this URL link will be able to edit the contents, so please bear this in mind when sharing it !) Following are the ACTION POINTs we have to complete prior to the meeting: * UC projects and FI-WARE: * to create entries in this spreadsheet linked to proposed topics * sharp deadline: Monday Dec 12, 09:00am CET (better if earlier, so that rest can evaluate, note that FI-WARE is already evaluating several of your requests) * UC projects and FI-WARE: * to cast their positioning in the spreadsheet regarding updloaded topics (must-, should-, would-, won't- use) * sharp deadline: Wednesday Dec 14, 19:00pm CET Please complete the info about each row in the spreadsheet so that we can easily navigate to the more detailed info from there. One IMPORTANT remark: I believe we should be rather strict and just select those topics for which we can actually formulate a complete and detailed request for proposal. I mean topics for which we can provide a detailed description, in terms of list of well-described Feature entries in the FI-WARE backlog, before the call is issued, that is, end of January 2012. Note that not including a topic in this first Open Call doesn't mean that we refuse to include it in FI-WARE. We may go for postponing a given topic to the next call, thus devoting enough time to refine the features. I have formally asked to our PO whether it would be feasible to split the first Open Call into two subsequents subcalls, the first still planned by end of January and the second by end of February or mid-March. This would be, IMHO, the most pragmatic way to go. Cheers, -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Dec 7 08:55:25 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 08:55:25 +0100 Subject: [Fiware-wpa] GUIDELINE: FI-WARE Architecture Specifications: proposed solution for some of the pending questions Message-ID: <4EDF1BED.7060805@tid.es> Hi all, On Nov 30th, I sent a detailed email describing how I think we should approach development of the next major deliverable, i.e., the deliverable on FI-WARE Architecture Specifications. I hope that all of you had already read carefully its contents so that we all are on the same page. There were two questions that were pending to solve before starting the actual writing of the deliverable on the Wiki. I elaborate on the proposed approach for both of them here. 1. Conventions for figures to include in Architecture Specifications In order to get an harmonized set of specifications a convention for figures describing aspects of the Functional Architecture linked to a GE has to be adopted. After some analysis, Thomas and me have decided to propose following FMC conventions for "Block Diagrams - Compositional Structures" defined in [1]. Note that the adoption of FMC conventions is limited to these Block Diagrams. Rest is not mandatory at all (nor indeed needed for this deliverable). Unless we hear about any objection, this will be the adopted recommendation you should forward to your teams. The gallery of basic elements used in FMC Block Diagrams is pretty simple, so I'm sure you could use any of your favorite editing tools for creating Architecture Description Diagrams, even powerpoint. For those who may not want to use powerpoint but a drawing tool that is better tailored to draw Diagrams, we may recommend yED (see [2]) 2. Uploading contents on the Wiki As already explained in one of my previous mails in response to a question made by Torsten, we will definitively go for developing contents of this deliverable on the Wiki. Therefore, one of the questions we should answer first is where on the Wiki. Here you are a list of points that describe the approach I suggest we should follow: * A new entry on the main home page of the FI-WARE Wiki will be created titled "FI-WARE Architecture". This will lead to a Wiki page were we will provide: * a short introduction of the goal of the Architecture Specifications * links to specific Wiki pages, one per chapter of FI-WARE. Each of these Wiki pages will be structured so that it includes an Introduction section (we will decide what comes here later) and a section per GE who should follow the structure we described in the email I sent on Nov 30 (note that the CORBA Event Service example I provided would map to the concept of a single GE in FI-WARE like the Pub/Sub Broker GE) * a link to a Wiki page to be titled "Bringing all pieces together", were we will elaborate on the description of how the different chapters will connect together from an architectural point of view, serving example (but generic) use case scenarios. * We should include a section titled "Open Specifications" at each of the GE sections we have under the "Materializing the FI-WARE Vision" part of the Wiki. This section will contain a bullet list of two items, each one linking to a Wiki page. The first one will be titled "Architecture Specification" and the second one will be titled "Detailed Interface Specifications". The first one will be a direct link to the section dedicated to the GE under the "FI-WARE Architecture" part of the Wiki described in the point above (note this will allow to navigate to concrete GE Architecture Specifications from the "Materializing the FI-WARE Vision" part of the Wiki, but that is precisely something we want to achieve). The second one will be where the detailed description of what remains regarding the complete set of Open Specifications linked to a GE, that is, the detailed description (signature and behaviour description of provided APIs, definition of protocols, non-functional mandatory features, etc) of interfaces introduced in the Architecture Specification. A draft of the guidelines, based on the above descriptive text, will be made soon available on the FI-WARE Project Handbook available on the Wiki. Please don't hesitate to make any question or formulate any doubt so that answers can help to enrich the guidelines. Please share this email with members of your team. Cheers, -- Juanjo References: [1] - http://www.fmc-modeling.org/notation_reference [2] - http://www.yworks.com/en/products_yed_about.html ________________________________ 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 jhierro at tid.es Wed Dec 7 09:11:03 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 09:11:03 +0100 Subject: [Fiware-wpa] REMINDER: Fwd: IMPORTANT: Handling of UC project tickets In-Reply-To: <4ED64FA4.2050509@tid.es> References: <4ED64FA4.2050509@tid.es> Message-ID: <4EDF1F97.8020009@tid.es> Hi, Based on the question one of you made to me recently, I have derived that he (and eventually someone else) may have missed the email below that launched the task force for handling tickets issued by the UC projects. It is expected that you have started to handle tickets only linked to your chapter. Tickets linked to several chapters are being handled by Thomas and myself. Cheers, -- Juanjo -------- Original Message -------- Subject: IMPORTANT: Handling of UC project tickets Date: Wed, 30 Nov 2011 16:45:40 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, We should try to accelerate as much as possible the handling of tickets coming from the UC projects. But first we had to agreed with UC projects about the concrete workflow to follow. Based on lessons learned so far, we also didn't want to start this activity without a detailed tutorial explaining how to proceed. Now that we have this settled, let's start with the stuff, handling tickets as much in parallel as possible. For this, we have assigned to you, as Chapter Leads, the rights to assign yourself (or to another member of your team) any of the existing tickets. We suggest then that we work as follows: * You should take care of tickets that are only assigned to your chapter. Start transitioning them to the "Under Evaluation by FI-WARE" state in a first step (try also to assign them to either you or someone from your team at that moment) * There are several tickets that are not linked to any chapter or linked to more than one: Thomas and me will take care of them and figure out how to handle them (may be deriving new tickets per chapter, or we'll see) It will be nice that you try to accompany the transition to the initial "Under Evaluation by FI-WARE" state with some message that provides an early feedback to the UC projects on whether the requested functionality most probably is already in the roadmap or not (of course, subject to a more detailed and careful evaluation). Again, please don't hesitate to ask any question you may have. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Dec 7 18:08:40 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 18:08:40 +0100 Subject: [Fiware-wpa] Fwd: Re: URGENT response: about 1st Open Call In-Reply-To: <4EDF9CEB.1050509@tid.es> References: <4EDF9CEB.1050509@tid.es> Message-ID: <4EDF9D98.9080606@tid.es> Hi all, Please find bellow a relevant exchange of emails with our PO. Bottom line: we will have three Open Calls instead of two, leaving the biggest share for the second. This gives us a little bit more of time for doing things the proper way. Just focus on a very concrete list of rather clear and urgent topics for the first Open Call which would be kept scheduled by the end of January. Cheers, -- Juanjo -------- Original Message -------- Subject: Re: URGENT response: about 1st Open Call Date: Wed, 07 Dec 2011 18:05:47 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Annalisa.Bogliolo at ec.europa.eu , Peter.Fatelnig at ec.europa.eu , INFSO-ICT-285248 at ec.europa.eu , jhierro >> "Juan J. Hierro" Hi Arian, Thanks for your response. I fully agree with your proposed schema, both in terms of dates and funding distribution. Also with the spirit linked to each call. This is definitively much more realistic ! Regarding structure of tasks, our idea is that the functionality to be supported by products submitted as proposal to the call should be document as a set of related Features listed in the FI-WARE Backlog. Therefore, a "task" would map to a set of Features (all of them trying to describe features of the target product/development) rather than a single Feature. Best regards, -- Juanjo On 07/12/11 16:14, Arian.ZWEGERS at ec.europa.eu wrote: Hi Juanjo, In principle, any modification to the open call set-up is possible, but requires an amendment (and therefore my agreement). Given that there is so much at stake, I would indeed prefer to split the first open call, and redistribute the funding, and therefore have something like: 1) Jan 2012, 2-3 M? 2) Apr 2012, 7-8 M? 3) Jan 2012, 2-3 M? The first one is to make sure things are in place, to learn the process and to do it right. You would only ask the things that you are sure of. Also, this date has been announced a few times now and should be kept (as much as possible). The second one is the "big one". Putting it later than the first one should allow you to learn from the experience with the first call, and should give you enough time to define exactly what you need. The third call is then to fill in the missing parts. By the way, you should think well about how you want to structure the "tasks" (as mentioned in the Guidance Notes for Project Coordinators) you call for. Features are too low a level for that. Best regards, Arian. ________________________________ From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Tuesday, December 06, 2011 4:29 PM To: ZWEGERS Arian (INFSO) Cc: jhierro >> "Juan J. Hierro" Subject: URGENT response: about 1st Open Call Hi Arian, Among the several things going in parallel, we are now dealing (as you may guess :-) with the list of topics for the first Open Call. As you commented during the first offical review of the project, it is rather important that we address the Open Call in a proper manner, since there will be many eyes looking how we are going to handle it. On the other hand, we must get the most from the money devoted to the Open Call, therefore, I believe we should be rather strict and just select those topics for which we can actually formulate a complete and detailed request for proposal. I mean topics for which we can provide a detailed description, in terms of list of well-described Feature entries in the FI-WARE backlog, before the call is issued, that is, end of January 2012. I'm a bit concerned that we go for including topics in the first Open Call while they would definitively require more careful analysis. Therefore, my question is: would it be feasible to split the first Open Call into two subsequent Open Calls, one still there to be published by end of January 2012 and then leaving a second one in, let's say end of February or mid-March ? Could we assign more than the 7 M? initially assigned to the first Open Call to these two first Open Calls? My understanding is that the number of Open Calls, as well as the grant assigned to each Open Call were just indicative, but nothing that was written in stone. Your feedback is rather appreciated. Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Dec 12 13:44:11 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 12 Dec 2011 13:44:11 +0100 Subject: [Fiware-wpa] VERY URGENT: Discussion on topics for the first Open Call In-Reply-To: <4EDE8F18.8070602@tid.es> References: <4EDE8F18.8070602@tid.es> Message-ID: <4EE5F71B.8010801@tid.es> Hi all, As I already announced last week, we will have a rather important confcoall this Thursday which deals with selection of topics for the first Open Call. If we want any topic to be discussed there, we should go for providing the necessary info on the google docs spreadsheet that we shared. I haven't seen any contribution. Maybe this is just because there were no topics you have identified in your chapters for this first Open Call, which might be well the case because there is now less pressure once we will have three Open Calls and the second one will be in April (may be early April). I'm happy with that (indeed, I would go only for topics we are 100% sure we will be able to precisely define by end January) but wanted to confirm. If there is anyone of you who wishes to add something, please let me know. I have sent an email to UC project representatives extending the deadline up to tomorrow 09:00am CET. Cheers, -- Juanjo -------- Original Message -------- Subject: Fwd: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:54:32 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, As I already mentioned to you, the FI-PPP AB will meet on December 15th and this meeting will be focused on trying to select a number of topics for the first Open Call to be issued by FI-WARE by the end of January. Following there are a couple of emails I have sent to members of the FI-PPP AB as preparation for this meeting (please read them bottom up) . Note that there is not just homework for UC projects but also for us regarding identification of topics for the Open Call. Therefore, those chapters that had identified some topics for the first Open Call are requested to provide their input following the proposed schedule. As I have already mentioned to the UC projects, please try to be pragmatic and include only those things that are rather clear to you. Don't hesitate to ask any question you may have. Best regards, -- Juanjo -------- Original Message -------- Subject: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:44:46 +0100 From: Juanjo Hierro To: ab at fi-ppp.eu Hi, Note that I have created a separate sheet per project within the spreadsheet. Columns are for voting. You should create the entries in the corresponding sheet. IMPORTANT: Please try to concentrate on what is the highest priority for you and be selective. It's not just a matter of copying all your requests in the FI-WARE tracker. We are going to use this tool in order to find the first list of topics that will go to the first Open Call. But there will be others as you know (at least one, I'm looking for more). Selecting a topic also implies a commitment on behalf of both FI-WARE and the supporting UC projects to work on the related Themes/Epic (*) up to refine them into Features that a) would become part of FI-WARE backlog and b) would be part of the documentation available to submitters of the Open Call. Best regards, -- Juanjo (*) - In general, entries in the "Unclassified Themes/Epics/Features backlog" should have been labeled as either Themes or Epics. Labeling an entry as a Feature or a Story means that there is a development team that can commit to deliver a product that implements the described functionality within the duration of a FI-WARE Release (three consecutive Sprints long) or the duration of a Sprint (one month long), respectively. UC projects should be careful labeling entries in the Unclassified Themes/Epics/Features backlog as Features or Stories because it would be interpreted as the UC project can actually deliver a product in a Release/Sprint timeframe, even if FI-WARE partners were not able to do so. On 06/12/11 20:54, Juanjo Hierro wrote: Hi all, As you know, the next FI-PPP AB (virtual) meeting is scheduled for Dec 15th. It was scheduled to start at 09:00am CET but I belive that duration was not established. I believe that, due to the relevance of the topics, we should spent 4 hours, with a programmed break of about 20 mins in between. So please plan it to take place from 09:00am CET until 13:20pm CET. I believe we should just focus on agreeing on a list of topics for the first Open Call, leaving other potential topics aside. Therefore, my proposal for the agenda is that we cover one proposed topic after another, in a similar way we made it for some of the topics during our last face2face meeting, trying to make a decision on whether we should include each topic in this first Open Call or not. In order to be effective, I would suggest that we place the topics to discuss in a shared Google docs spreasheet prior to the meeting. I have created one inspired in the excel spreadsheet we used during our face2face meeting in Munich: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE (note: anyone who gets access to this URL link will be able to edit the contents, so please bear this in mind when sharing it !) Following are the ACTION POINTs we have to complete prior to the meeting: * UC projects and FI-WARE: * to create entries in this spreadsheet linked to proposed topics * sharp deadline: Monday Dec 12, 09:00am CET (better if earlier, so that rest can evaluate, note that FI-WARE is already evaluating several of your requests) * UC projects and FI-WARE: * to cast their positioning in the spreadsheet regarding updloaded topics (must-, should-, would-, won't- use) * sharp deadline: Wednesday Dec 14, 19:00pm CET Please complete the info about each row in the spreadsheet so that we can easily navigate to the more detailed info from there. One IMPORTANT remark: I believe we should be rather strict and just select those topics for which we can actually formulate a complete and detailed request for proposal. I mean topics for which we can provide a detailed description, in terms of list of well-described Feature entries in the FI-WARE backlog, before the call is issued, that is, end of January 2012. Note that not including a topic in this first Open Call doesn't mean that we refuse to include it in FI-WARE. We may go for postponing a given topic to the next call, thus devoting enough time to refine the features. I have formally asked to our PO whether it would be feasible to split the first Open Call into two subsequents subcalls, the first still planned by end of January and the second by end of February or mid-March. This would be, IMHO, the most pragmatic way to go. Cheers, -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Dec 12 13:08:09 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 12 Dec 2011 13:08:09 +0100 Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A2B@EXCLU2K7.hi.inet> When: Monday, December 19, 2011 11:00 AM-2:00 PM. Central European Standard Time *~*~*~*~*~*~*~*~*~* ________________________________ 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: not available Type: text/calendar Size: 3328 bytes Desc: not available URL: From daniel.gidoin at thalesgroup.com Tue Dec 13 10:11:01 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Tue, 13 Dec 2011 10:11:01 +0100 Subject: [Fiware-wpa] VERY URGENT: Discussion on topics for the first Open Call In-Reply-To: <4EE5F71B.8010801@tid.es> References: <4EDE8F18.8070602@tid.es> <4EE5F71B.8010801@tid.es> Message-ID: <19338_1323767459_4EE716A3_19338_9087_1_32d24187-4132-4c84-b24f-6e138770e095@THSONEA01HUB03P.one.grp> Dear Juanjo, I send a contribution in the day. I apologize but I cannot do it faster. Best regard Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 12 d?cembre 2011 13:44 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] VERY URGENT: Discussion on topics for the first Open Call Hi all, As I already announced last week, we will have a rather important confcoall this Thursday which deals with selection of topics for the first Open Call. If we want any topic to be discussed there, we should go for providing the necessary info on the google docs spreadsheet that we shared. I haven't seen any contribution. Maybe this is just because there were no topics you have identified in your chapters for this first Open Call, which might be well the case because there is now less pressure once we will have three Open Calls and the second one will be in April (may be early April). I'm happy with that (indeed, I would go only for topics we are 100% sure we will be able to precisely define by end January) but wanted to confirm. If there is anyone of you who wishes to add something, please let me know. I have sent an email to UC project representatives extending the deadline up to tomorrow 09:00am CET. Cheers, -- Juanjo -------- Original Message -------- Subject: Fwd: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:54:32 +0100 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, As I already mentioned to you, the FI-PPP AB will meet on December 15th and this meeting will be focused on trying to select a number of topics for the first Open Call to be issued by FI-WARE by the end of January. Following there are a couple of emails I have sent to members of the FI-PPP AB as preparation for this meeting (please read them bottom up) . Note that there is not just homework for UC projects but also for us regarding identification of topics for the Open Call. Therefore, those chapters that had identified some topics for the first Open Call are requested to provide their input following the proposed schedule. As I have already mentioned to the UC projects, please try to be pragmatic and include only those things that are rather clear to you. Don't hesitate to ask any question you may have. Best regards, -- Juanjo -------- Original Message -------- Subject: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:44:46 +0100 From: Juanjo Hierro To: ab at fi-ppp.eu Hi, Note that I have created a separate sheet per project within the spreadsheet. Columns are for voting. You should create the entries in the corresponding sheet. IMPORTANT: Please try to concentrate on what is the highest priority for you and be selective. It's not just a matter of copying all your requests in the FI-WARE tracker. We are going to use this tool in order to find the first list of topics that will go to the first Open Call. But there will be others as you know (at least one, I'm looking for more). Selecting a topic also implies a commitment on behalf of both FI-WARE and the supporting UC projects to work on the related Themes/Epic (*) up to refine them into Features that a) would become part of FI-WARE backlog and b) would be part of the documentation available to submitters of the Open Call. Best regards, -- Juanjo (*) - In general, entries in the "Unclassified Themes/Epics/Features backlog" should have been labeled as either Themes or Epics. Labeling an entry as a Feature or a Story means that there is a development team that can commit to deliver a product that implements the described functionality within the duration of a FI-WARE Release (three consecutive Sprints long) or the duration of a Sprint (one month long), respectively. UC projects should be careful labeling entries in the Unclassified Themes/Epics/Features backlog as Features or Stories because it would be interpreted as the UC project can actually deliver a product in a Release/Sprint timeframe, even if FI-WARE partners were not able to do so. On 06/12/11 20:54, Juanjo Hierro wrote: Hi all, As you know, the next FI-PPP AB (virtual) meeting is scheduled for Dec 15th. It was scheduled to start at 09:00am CET but I belive that duration was not established. I believe that, due to the relevance of the topics, we should spent 4 hours, with a programmed break of about 20 mins in between. So please plan it to take place from 09:00am CET until 13:20pm CET. I believe we should just focus on agreeing on a list of topics for the first Open Call, leaving other potential topics aside. Therefore, my proposal for the agenda is that we cover one proposed topic after another, in a similar way we made it for some of the topics during our last face2face meeting, trying to make a decision on whether we should include each topic in this first Open Call or not. In order to be effective, I would suggest that we place the topics to discuss in a shared Google docs spreasheet prior to the meeting. I have created one inspired in the excel spreadsheet we used during our face2face meeting in Munich: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE (note: anyone who gets access to this URL link will be able to edit the contents, so please bear this in mind when sharing it !) Following are the ACTION POINTs we have to complete prior to the meeting: * UC projects and FI-WARE: * to create entries in this spreadsheet linked to proposed topics * sharp deadline: Monday Dec 12, 09:00am CET (better if earlier, so that rest can evaluate, note that FI-WARE is already evaluating several of your requests) * UC projects and FI-WARE: * to cast their positioning in the spreadsheet regarding updloaded topics (must-, should-, would-, won't- use) * sharp deadline: Wednesday Dec 14, 19:00pm CET Please complete the info about each row in the spreadsheet so that we can easily navigate to the more detailed info from there. One IMPORTANT remark: I believe we should be rather strict and just select those topics for which we can actually formulate a complete and detailed request for proposal. I mean topics for which we can provide a detailed description, in terms of list of well-described Feature entries in the FI-WARE backlog, before the call is issued, that is, end of January 2012. Note that not including a topic in this first Open Call doesn't mean that we refuse to include it in FI-WARE. We may go for postponing a given topic to the next call, thus devoting enough time to refine the features. I have formally asked to our PO whether it would be feasible to split the first Open Call into two subsequents subcalls, the first still planned by end of January and the second by end of February or mid-March. This would be, IMHO, the most pragmatic way to go. Cheers, -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Dec 13 10:43:17 2011 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 13 Dec 2011 10:43:17 +0100 Subject: [Fiware-wpa] Minutes of meeting Message-ID: <4EE71E35.2090302@tid.es> Dear all, I have been telling part of the WPLs in private but this keeps happening, I believe this has not been communicated properly. Please follow these guidelines for minutes of meeting: * Take the template from https://forge.fi-ware.eu/docman/view.php/7/41/FI-WARE+Minutes+template+11-11-11.doc * Do not forget to upload each instance of minutes of meeting to the documentation repository to a dedicated folder I understand this could be cumbersome to fill in completely and maybe not very useful. Feel free to prune it a bit when/where needed or alternatively to leave blank fields but respect the general style. We do not want to burden anyone with useless work but we have to follow a common format. Regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 jhierro at tid.es Tue Dec 13 17:30:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 13 Dec 2011 17:30:37 +0100 Subject: [Fiware-wpa] Aspects about workflow defined for handing UC project requests Message-ID: <4EE77DAD.3070702@tid.es> Hi, I have change the privileges linked to FI-WARE Project members in the FI-WARE project so that they can assign tickets to any sort of user. This way, in the event you decide that a ticket should transition to the "Needs revision by the Issuer" (don't forget to add comments guiding the issuer about what they have to review or provide more info about) ... you should assign it to the original issuer (you can see it described at the top of the page linked to a particular ticket. Cheers, -- ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Dec 16 12:44:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 16 Dec 2011 12:44:37 +0100 Subject: [Fiware-wpa] IMPORTANT: FI-WARE General Assembly (Plenary) meeting in January Message-ID: <4EEB2F25.80708@tid.es> Hi all, This is to let you know that the next FI-WARE General Assembly (Plenary) meeting will take place in Madrid in Telefonica's facilities, from January 23rd until January 27th. Focus will be given in that the different chapter (WP) teams meet together face2face. Also to arrange joint meetings involving several chapters at convenience, in order to address cross-chapter issues. Thus, we will take advantage that we are meeting in the same venue. We may have a short plenary meeting of about 2-3 hours but not more than that. We have booked 9 rooms from January 23 starting at 14:30 until January 27th 14:00. We believe it should be enough to run all the parallel meetings that are needed. We will setup a google docs spreadsheet to help closing the concrete dates and times at which a) each chapter (WP) will meet alone and b) joint chapter meetings will take place (this, of course means they agree among themselves). Soon we will send you an email with more info about logistics but we wanted to share already this basic information so that you can start booking flights and accomodations. We couldn't make it before we got sure that we could book all the necessary rooms. WPLs and WPAs will meet from January 23 starting at 09:00am. Cheers, -- ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Fri Dec 16 12:53:39 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 16 Dec 2011 12:53:39 +0100 Subject: [Fiware-wpa] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours Message-ID: <4EEB3143.2040602@tid.es> Hi all, This is a reminder that we will have our regular joint WPL/WPA follow-up confcall on Monday starting at 11:00 and expected to last 3 hours. Main focus of the confcall will be to start discussion on cross/global architectural issues. All WPLs/WPAs are welcome to bring presentations elaborating on both their views (please, enough detailed, not just vague/abstract ideas) and the questions they believe require launching dedicated Task Forces for further discussion. From shared material and the discussion that may follow, we should derive a number of Action Points and we should agree what concrete Task Forces have to be launched. We may devote also some time to agree on preparation of the next FI-WARE General Assembly. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From stefano.depanfilis at eng.it Sun Dec 18 01:41:47 2011 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Sun, 18 Dec 2011 01:41:47 +0100 Subject: [Fiware-wpa] [Fiware] IMPORTANT: FI-WARE General Assembly (Plenary) meeting in January In-Reply-To: <4EEB2F25.80708@tid.es> References: <4EEB2F25.80708@tid.es> Message-ID: dear juanjo, happy with the meeting but having the wpl wpa on 23rd at 9:00 means we have to travel on sunday. i definitively kind ask you to move this on the afternoon or on another day. ciao, stefano 2011/12/16 Juanjo Hierro : > Hi all, > > ?This is to let you know that the next FI-WARE General Assembly > (Plenary) meeting will take place in Madrid in Telefonica's facilities, > from January 23rd until January 27th. > > ?Focus will be given in that the different chapter (WP) teams meet > together face2face. ? Also to arrange joint meetings involving several > chapters at convenience, in order to address cross-chapter issues. > Thus, we will take advantage that we are meeting in the same venue. ? We > may have a short plenary meeting of about 2-3 hours but not more than that. > > ?We have booked 9 rooms from January 23 starting at 14:30 until > January 27th 14:00. ? We believe it should be enough to run all the > parallel meetings that are needed. > > ?We will setup a google docs spreadsheet to help closing the concrete > dates and times at which a) each chapter (WP) will meet alone and b) > joint chapter meetings will take place (this, of course means they agree > among themselves). > > ?Soon we will send you an email with more info about logistics but we > wanted to share already this basic information so that you can start > booking flights and accomodations. ?We couldn't make it before we got > sure that we could book all the necessary rooms. > > ?WPLs and WPAs will meet from January 23 starting at 09:00am. > > ?Cheers, > > -- > ------------- > Juanjo Hierro > > Product Development and Innovation (PDI) - Telefonica Digital > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > > 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 mailing list > Fiware at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 From pascal.bisson at thalesgroup.com Mon Dec 19 09:25:16 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 19 Dec 2011 09:25:16 +0100 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours In-Reply-To: <4EEB3143.2040602@tid.es> References: <4EEB3143.2040602@tid.es> Message-ID: <29396_1324283122_4EEEF4F2_29396_6377_1_a94baad4-09d4-474f-8e09-a80435b5a342@THSONEA01HUB06P.one.grp> Dear Juanjo, Dear Colleagues, Due to a management meeting Daniel and I have to attend this morning we would not be able to attend the audio conf of today. Apologize for the inconvenience. Regarding topical architectural issues we'd like to discuss across WPs there are a number of them which were already stated and reported on the Wiki (also discussed through bilateral meeting we had with other WPs at previous GA in Torino - one of them being overall monitoring). In any case I and especially Daniel as WP8 architect will come back to you with more details through couple of slides you requested. As for the rest I do sill think we need to go for a physical meeting with all WPAs addressing those architectural issues in order to converge on how to integrate the various partial (view-oriented) architectures we came up with. Best Regards, Pascal PS: Daniel and I will in any case catch up on the minutes of this audio. Once more apologize not being in a position to attend today's audio. -----Message d'origine----- 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??: vendredi 16 d?cembre 2011 12:54 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours Hi all, This is a reminder that we will have our regular joint WPL/WPA follow-up confcall on Monday starting at 11:00 and expected to last 3 hours. Main focus of the confcall will be to start discussion on cross/global architectural issues. All WPLs/WPAs are welcome to bring presentations elaborating on both their views (please, enough detailed, not just vague/abstract ideas) and the questions they believe require launching dedicated Task Forces for further discussion. From shared material and the discussion that may follow, we should derive a number of Action Points and we should agree what concrete Task Forces have to be launched. We may devote also some time to agree on preparation of the next FI-WARE General Assembly. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From jhierro at tid.es Mon Dec 19 10:51:13 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 19 Dec 2011 10:51:13 +0100 Subject: [Fiware-wpa] Webex info In-Reply-To: <195143571.1324281841332.JavaMail.nobody@jsj2wl012.webex.com> References: <195143571.1324281841332.JavaMail.nobody@jsj2wl012.webex.com> Message-ID: <4EEF0911.9020107@tid.es> Hi all, Please find below the details for the Webex bridge that we will use during our confcall in a few minutes ... Cheers, -- Juanjo -------- Original Message -------- Subject: Meeting invitation: FI-WARE joint WPLs/WPAs confcall Date: Mon, 19 Dec 2011 09:04:01 +0100 From: Gestor i-Reunion webex6100 Reply-To: Webex6100 at tid.es To: JUAN JOSE HIERRO SUREDA Hello , Gestor i-Reunion webex6100 invites you to attend this online meeting. Topic: FI-WARE joint WPLs/WPAs confcall Date: Monday, December 19, 2011 Time: 11:00 am, Europe Time (Paris, GMT+01:00) Meeting Number: 963 682 409 Meeting Password: 1234abcD ------------------------------------------------------- To join the online meeting (Now from iPhones too!) ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/j.php?ED=189195347&UID=1265142462&PW=NY2Q0MTNhNmVk&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: 1234abcD 4. Click "Join Now". To view in other time zones or languages, please click the link: https://telefonica.webex.com/telefonica-en/j.php?ED=189195347&UID=1265142462&PW=NY2Q0MTNhNmVk&ORT=MiMyMw%3D%3D ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://telefonica.webex.com/telefonica-en/mc 2. On the left navigation bar, click "Support". You can contact me at: Webex6100 at tid.es To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://telefonica.webex.com/telefonica-en/j.php?ED=189195347&UID=1265142462&ICS=MI&LD=1&RD=2&ST=1&SHA2=/5xunVx1NyJpGsu6HLpRPacCOWETW31BZgvNs/uK8sQ=&RT=MiMyMw%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://telefonica.webex.com/telefonica-en/systemdiagnosis.php Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session. ________________________________ 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 jhierro at tid.es Mon Dec 19 10:52:21 2011 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 19 Dec 2011 10:52:21 +0100 Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A30@EXCLU2K7.hi.inet> When: Monday, December 19, 2011 11:00 AM-2:00 PM. Central European Standard Time *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ 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: not available Type: text/calendar Size: 3468 bytes Desc: not available URL: From mcp at tid.es Mon Dec 19 11:50:16 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 19 Dec 2011 11:50:16 +0100 Subject: [Fiware-wpa] Bug in Trackers Message-ID: <4EEF16E8.80509@tid.es> Dear all, As most of you may be aware, we have a bug in the bug tracker (it sounds a bit like a joke!). While the origin of the problem is identified and the bug corrected, we can supply a workaround to be able to work. The bug is that when a user creates a filter that selects tickets by asignee, the SQL query crashes and the user gets blocked (the last query is always loaded by default so logging back on again will not help). The way to get out of this situation is to delete the cookies, if you not want to delete them all then just get rid of those in the domain " "forge.fi-ware.eu". Hope it helps Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 jhierro at tid.es Mon Dec 19 16:18:55 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 19 Dec 2011 16:18:55 +0100 Subject: [Fiware-wpa] Fwd: FI-WARE: excerpts from the draft review report In-Reply-To: <7BACCBA4EE7D3946BF23FB79D9FD2E610124680D@S-DC-EXM11.net1.cec.eu.int> References: <7BACCBA4EE7D3946BF23FB79D9FD2E610124680D@S-DC-EXM11.net1.cec.eu.int> Message-ID: <4EEF55DF.6010809@tid.es> Hi all, A first take on the review report sent by Arian. I pass it to you without further analysis but in general I feel it is positive. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro -------- Original Message -------- Subject: FI-WARE: excerpts from the draft review report Date: Fri, 16 Dec 2011 12:25:08 +0100 From: Arian.ZWEGERS at ec.europa.eu To: JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA CC: INFSO-ICT-285248 at ec.europa.eu Dear Jose, Juanjo, Today is my last day in the office this year. Attached are some excerpts from the draft review report. I don't think the review report is ready yet to be sent to you, but I don't want to delay some of the comments. Merry Xmas and Happy New Year, Best regards, Arian. ________________________________ 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: Excerpt FI-WARE Review 1 report.doc Type: application/msword Size: 494080 bytes Desc: not available URL: From mcp at tid.es Mon Dec 19 17:08:10 2011 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 19 Dec 2011 17:08:10 +0100 Subject: [Fiware-wpa] We are on Facebook now! Message-ID: <4EEF616A.9000307@tid.es> Dear all, We have our Facebook page now. You can reach it on: WPL, can you please disseminate this within your respective WPs? http://www.facebook.com/pages/FI-WARE/251366491587242 Please tick on the "I like it" button to help us grow a reasonable number of votes on Facebook. Thanks Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue Dec 20 10:17:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 20 Dec 2011 10:17:32 +0100 Subject: [Fiware-wpa] Notes from last joint WPLs/WPAs confcall Message-ID: <4EF052AC.5090901@tid.es> Hi all, Please find below my notes from our confcall today. Please share with your respective teams. As you see, there will be a number of APs to setup a number of Task Forces, each concentrated in a particular cross-chapter topic (see point on goals and agenda). A mailing list for discussion on the topic will be setup. In addition, a ticket will be created in a Task Force Management tracker we will setup in the "FI-WARE Private" project in FusionForge that has been created. The ticket will point to the archive of the mailing list being created and will help us to follow up progress. Cheers, -- Juanjo 1. Attendees * Cloud Chapter: Alex (IBM) * Data Chapter: Carlos (TID) * IoT Chapter: Denes (NSN) * Apps Chapter: Torsten (SAP), Axel (SAP) * Security Chapter: None * I2ND: Pier (TI), Hans (DT) * Dev Tools: Davide (Engineering) * Exploitation (Juan) 2. Goals and agenda: The main goal of the confcall is to identify architectural topics that will require further discussion involving more than one chapter. An Architecture Task Force will be created for each relevant topic. Concretely, this will mean that: * TID will set up a dedicated mailing list and create a ticket on the Task Force tracker in the FI-WARE private project in FusionForge * Each WPL/WPA will designate who should join from their chapters * The partner who proposed the Task Force (owner of the Task Force) will kick-off the discussion on the mailing list by sending an email which helps as terms of reference * The owner of the Task Force should present conclusions at the joint WPL/WPA meeting that will take place on January 23rd Each WPL/WPA was requested to bring any cross-chapter topic for which he wish to create a Task Force. The following partners brought some views: * Juanjo (TID) * Davide (Engineering) * Torsten (SAP) * Pier (Telecom Italia) 3. Presentation by Juanjo 3.1 Generalize Event Management model being proposed at the level of Things in IoT chapter, applying it to Cloud Monitoring and Security Events Monitoring Despite it is still under discussion, the Event Management Model being proposed at the level of Things in the IoT chapter is rather generic and has been defined so it is consistent with the Event Management model defined within the Data/Context Management Model. This Event Management Model is based on the OMA (Open Mobile Alliance) specs for NGSI Context-Management. In such model, an event leads to generation of a Context Element data structure which includes info about updated values of properties linked to entities defined in the system. An entity maps to the concept of "Thing" in the IoT chapter but there may be other entities in the system (e.g., another application). In FI-WARE, values assigned to properties describing Things will be derived from data gathered from IoT resources, referred as sensors, which run on IoT devices. Associations between Things and IoT resources as well as formulas for mapping values of IoT resources into properties of entities are handled through an IoT Configuration Management GE at the Things Management Layer. However, this concept may be further generalized so that we talk about "Monitoring Agents" or "Monitored Resources". The model would then be able to work for both Cloud Monitoring and Security Events Monitoring. The advantage for this approach would be reuse of components, as well as exhibiting higher coherence. AP: Setup task force to check whether the Events Management Model defined at the level of Things within IoT chapter can be adopted for both Cloud monitoring and Security events monitoring. Mailing list to be created: fiware-monitoring 3.2 Glue middleware There are a number of issues that are related to how interfaces exported by GEs are actually specified and implemented: * first, we have to agree on a common way to specify interfaces exported by GEs ... Should we adopt REST as a minimum common denominator ? Can we define a technology-neutral approach that would allow an interface to be accessible using multiple technologies (REST, WS, optimized binary protocols, ...) and would allow us to overcome that a given technology becomes deprecated ? * second, the most suitable technical solution for some Security issues may need to implement some functions at middleware level * third, APIs usage accountability may require that also some functions be implemented at middleware level if we want to achieve a suitable level of transparency Alex: not sure if we can decide on one API paradigm but he agrees we should support just a limited set Juanjo: is not about choosing one API paradigm but probably define an interface definition language that may abstract us from the limited set of API paradigms we will support (which could then be extended over time). Denes: any decision on middleware should take into account that middleware may need to fit with restrictions about computing resources in IoT devices AP: Setup task force on the matter. Mailing list to be created: fiware-middleware 3.3 Network-aware Cloud Some UC projects have declared the need to be able to declare what SLO (Service Level Objectives) they want to see fulfilled for certain end-to-end scenarios, typically requiring communication between applications running on the Cloud and IoT gateways (cloud proxies) or end users. It would then be up to the Cloud Hosting capabilities in FI-WARE to cope with those SLOs relying on capacities of the underlying network. Despite we will see whether this functionality would easily fit in the roadmap based on available resources, all declare to agree with creation of a Task Force on the matter. It will typically involve partners from the I2ND chapter, Cloud chapter and Apps chapter (since we need to resolve how this sort of SLOs become part of the SLA definition linked to an application) We agree to leave P2P scenarios aside for the time being unless UC projects raise the need to analyze them. AP: Start with a single Task Force involving I2ND, Cloud and Apps chapter members. Mailing list to be created: fiware-network-cloud-SLOs Eventually split into two task forces if needed which may be: - a task force involving Apps (Business Framework) and Cloud chapters, dealing with how to declare SLAs at USDL related to end-to-end SLOs - a task force involving Cloud and I2ND chapter dealing with how to implement SLOs relying on QoS management functions exported by networks 3.4 Semantic Web Infrastructure: Several chapters addressing development of GEs whose implementation relies on Semantic Web technologies. We should go for the selection of a single technology for this (mostly RDF storage and SPARQL support) AP: Setup a Task Force that takes a decision for all the project. Mailing list to be created: fiware-semantic-platform Torsten: Shouldn't we also go for a common decision regarding linked-data GE ? AP: Apps chapter to share info about linked-data technologies being defined in their chapter so that rest of WPAs can evaluate whether it can be used elsewhere (info to be sent to fiware-wpa mailing list for the time being) 3.5 Common Look&Feel in FI-WARE portals AP: Juanjo to launch a thread of discussion on the matter so that we can start discussion on the matter 4. Development Tools by Davide Davide reinforce the need to link some of the developments to be made within the Dev&Tools and those in other chapters. Particularly those that have to do with deployment tools where we need to explore how they integrate (or matches) the development of part of the Cloud portal. He also reinforce the need to make a decision on how interfaces will be specified and what protocols will be supported. Davide take the opportunity to reinforce that other chapter leaders should answer the questionnaire that was distributed by WP9 to all WPLs/WPAs. 5. Presentation by Torsten Despite Torsten didn't have time to present all cross-chapter topics, he made emphasis on the need to push for making services provided by FI-WARE GEs available in the marketplace. This means that they should be defined in USDL. Juanjo: this should allow that a FI-WARE Instance Provider operating a FI-WARE Instance defined around the Marketplace GEs offer third parties the ability to publish their implementation of FI-WARE GEs in other chapters and get paid for their usage by applications. It would also help a FI-WARE Instance Provider operating a FI-WARE Instance that deploys all FI-WARE GEs to establish how it plans to charge for usage of their services by applications. AP: To setup Task Force on discussion about USDL. Mailing list to be created: fiware-usdl As a second major point in his presentation, Torsten put emphasis on the need to close the definition of the GEs supporting Identity Management. We should soon have the APIs of these GEs defined as soon as possible. Juanjo and Pier highlighted this is rather relevant. Juanjo expects that the Security chapter has been able to further refine the vision that they presented in the workshop which took place in November and now could present a detailed Reference Architecture with well-defined APIs. AP: To setup Task Force on discussion about Security Identity Management, Access Control and Data Handling. Mailing list to be created fiware-security-core Unfortunately, there was not time to address other topics to be brought by Torsten. He will distribute his presentation among WPLs/WPAs. 6. Short comments by Pier Pier mentioned that they are already working on how to ensure that cloud-edge proxy supports all capabilities that are needed to host IoT software. AP: We may consider that a Task Force is already in place. We just need to create a dedicated mailing list to discuss on the matter: ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Tue Dec 20 11:16:41 2011 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Tue, 20 Dec 2011 11:16:41 +0100 Subject: [Fiware-wpa] Notes from last joint WPLs/WPAs confcall In-Reply-To: <4EF052AC.5090901@tid.es> References: <4EF052AC.5090901@tid.es> Message-ID: Here my slides from Monday... Regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 20. Dezember 2011 10:18 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Notes from last joint WPLs/WPAs confcall Hi all, Please find below my notes from our confcall today. Please share with your respective teams. As you see, there will be a number of APs to setup a number of Task Forces, each concentrated in a particular cross-chapter topic (see point on goals and agenda). A mailing list for discussion on the topic will be setup. In addition, a ticket will be created in a Task Force Management tracker we will setup in the "FI-WARE Private" project in FusionForge that has been created. The ticket will point to the archive of the mailing list being created and will help us to follow up progress. Cheers, -- Juanjo 1. Attendees * Cloud Chapter: Alex (IBM) * Data Chapter: Carlos (TID) * IoT Chapter: Denes (NSN) * Apps Chapter: Torsten (SAP), Axel (SAP) * Security Chapter: None * I2ND: Pier (TI), Hans (DT) * Dev Tools: Davide (Engineering) * Exploitation (Juan) 2. Goals and agenda: The main goal of the confcall is to identify architectural topics that will require further discussion involving more than one chapter. An Architecture Task Force will be created for each relevant topic. Concretely, this will mean that: * TID will set up a dedicated mailing list and create a ticket on the Task Force tracker in the FI-WARE private project in FusionForge * Each WPL/WPA will designate who should join from their chapters * The partner who proposed the Task Force (owner of the Task Force) will kick-off the discussion on the mailing list by sending an email which helps as terms of reference * The owner of the Task Force should present conclusions at the joint WPL/WPA meeting that will take place on January 23rd Each WPL/WPA was requested to bring any cross-chapter topic for which he wish to create a Task Force. The following partners brought some views: * Juanjo (TID) * Davide (Engineering) * Torsten (SAP) * Pier (Telecom Italia) 3. Presentation by Juanjo 3.1 Generalize Event Management model being proposed at the level of Things in IoT chapter, applying it to Cloud Monitoring and Security Events Monitoring Despite it is still under discussion, the Event Management Model being proposed at the level of Things in the IoT chapter is rather generic and has been defined so it is consistent with the Event Management model defined within the Data/Context Management Model. This Event Management Model is based on the OMA (Open Mobile Alliance) specs for NGSI Context-Management. In such model, an event leads to generation of a Context Element data structure which includes info about updated values of properties linked to entities defined in the system. An entity maps to the concept of "Thing" in the IoT chapter but there may be other entities in the system (e.g., another application). In FI-WARE, values assigned to properties describing Things will be derived from data gathered from IoT resources, referred as sensors, which run on IoT devices. Associations between Things and IoT resources as well as formulas for mapping values of IoT resources into properties of entities are handled through an IoT Configuration Management GE at the Things Management Layer. However, this concept may be further generalized so that we talk about "Monitoring Agents" or "Monitored Resources". The model would then be able to work for both Cloud Monitoring and Security Events Monitoring. The advantage for this approach would be reuse of components, as well as exhibiting higher coherence. AP: Setup task force to check whether the Events Management Model defined at the level of Things within IoT chapter can be adopted for both Cloud monitoring and Security events monitoring. Mailing list to be created: fiware-monitoring 3.2 Glue middleware There are a number of issues that are related to how interfaces exported by GEs are actually specified and implemented: * first, we have to agree on a common way to specify interfaces exported by GEs ... Should we adopt REST as a minimum common denominator ? Can we define a technology-neutral approach that would allow an interface to be accessible using multiple technologies (REST, WS, optimized binary protocols, ...) and would allow us to overcome that a given technology becomes deprecated ? * second, the most suitable technical solution for some Security issues may need to implement some functions at middleware level * third, APIs usage accountability may require that also some functions be implemented at middleware level if we want to achieve a suitable level of transparency Alex: not sure if we can decide on one API paradigm but he agrees we should support just a limited set Juanjo: is not about choosing one API paradigm but probably define an interface definition language that may abstract us from the limited set of API paradigms we will support (which could then be extended over time). Denes: any decision on middleware should take into account that middleware may need to fit with restrictions about computing resources in IoT devices AP: Setup task force on the matter. Mailing list to be created: fiware-middleware 3.3 Network-aware Cloud Some UC projects have declared the need to be able to declare what SLO (Service Level Objectives) they want to see fulfilled for certain end-to-end scenarios, typically requiring communication between applications running on the Cloud and IoT gateways (cloud proxies) or end users. It would then be up to the Cloud Hosting capabilities in FI-WARE to cope with those SLOs relying on capacities of the underlying network. Despite we will see whether this functionality would easily fit in the roadmap based on available resources, all declare to agree with creation of a Task Force on the matter. It will typically involve partners from the I2ND chapter, Cloud chapter and Apps chapter (since we need to resolve how this sort of SLOs become part of the SLA definition linked to an application) We agree to leave P2P scenarios aside for the time being unless UC projects raise the need to analyze them. AP: Start with a single Task Force involving I2ND, Cloud and Apps chapter members. Mailing list to be created: fiware-network-cloud-SLOs Eventually split into two task forces if needed which may be: - a task force involving Apps (Business Framework) and Cloud chapters, dealing with how to declare SLAs at USDL related to end-to-end SLOs - a task force involving Cloud and I2ND chapter dealing with how to implement SLOs relying on QoS management functions exported by networks 3.4 Semantic Web Infrastructure: Several chapters addressing development of GEs whose implementation relies on Semantic Web technologies. We should go for the selection of a single technology for this (mostly RDF storage and SPARQL support) AP: Setup a Task Force that takes a decision for all the project. Mailing list to be created: fiware-semantic-platform Torsten: Shouldn't we also go for a common decision regarding linked-data GE ? AP: Apps chapter to share info about linked-data technologies being defined in their chapter so that rest of WPAs can evaluate whether it can be used elsewhere (info to be sent to fiware-wpa mailing list for the time being) 3.5 Common Look&Feel in FI-WARE portals AP: Juanjo to launch a thread of discussion on the matter so that we can start discussion on the matter 4. Development Tools by Davide Davide reinforce the need to link some of the developments to be made within the Dev&Tools and those in other chapters. Particularly those that have to do with deployment tools where we need to explore how they integrate (or matches) the development of part of the Cloud portal. He also reinforce the need to make a decision on how interfaces will be specified and what protocols will be supported. Davide take the opportunity to reinforce that other chapter leaders should answer the questionnaire that was distributed by WP9 to all WPLs/WPAs. 5. Presentation by Torsten Despite Torsten didn't have time to present all cross-chapter topics, he made emphasis on the need to push for making services provided by FI-WARE GEs available in the marketplace. This means that they should be defined in USDL. Juanjo: this should allow that a FI-WARE Instance Provider operating a FI-WARE Instance defined around the Marketplace GEs offer third parties the ability to publish their implementation of FI-WARE GEs in other chapters and get paid for their usage by applications. It would also help a FI-WARE Instance Provider operating a FI-WARE Instance that deploys all FI-WARE GEs to establish how it plans to charge for usage of their services by applications. AP: To setup Task Force on discussion about USDL. Mailing list to be created: fiware-usdl As a second major point in his presentation, Torsten put emphasis on the need to close the definition of the GEs supporting Identity Management. We should soon have the APIs of these GEs defined as soon as possible. Juanjo and Pier highlighted this is rather relevant. Juanjo expects that the Security chapter has been able to further refine the vision that they presented in the workshop which took place in November and now could present a detailed Reference Architecture with well-defined APIs. AP: To setup Task Force on discussion about Security Identity Management, Access Control and Data Handling. Mailing list to be created fiware-security-core Unfortunately, there was not time to address other topics to be brought by Torsten. He will distribute his presentation among WPLs/WPAs. 6. Short comments by Pier Pier mentioned that they are already working on how to ensure that cloud-edge proxy supports all capabilities that are needed to host IoT software. AP: We may consider that a Task Force is already in place. We just need to create a dedicated mailing list to discuss on the matter: ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ 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: FI-WARE WP3 Architecture 15-12-11.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 451128 bytes Desc: FI-WARE WP3 Architecture 15-12-11.pptx URL: From jhierro at tid.es Tue Dec 20 11:32:19 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 20 Dec 2011 11:32:19 +0100 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours In-Reply-To: <29396_1324283122_4EEEF4F2_29396_6377_1_a94baad4-09d4-474f-8e09-a80435b5a342@THSONEA01HUB06P.one.grp> References: <4EEB3143.2040602@tid.es> <29396_1324283122_4EEEF4F2_29396_6377_1_a94baad4-09d4-474f-8e09-a80435b5a342@THSONEA01HUB06P.one.grp> Message-ID: <4EF06433.8070209@tid.es> Dear Pascal, I'm sorry that you couldn't make the call. One of the points that were raised (already mentioned in the minutes), and indeed one about which many people is seeking for an aswer, has to do with definition of the Reference Architecture that we are going to adopt for Identity Management and Access Control. Identity Management and Access Control is a key core GE on which many GEs and final applications will rely. Therefore, we need to know ASAP what is the target solution for this very basic functionality as well as details about what APIs will be used by the programmers of GEs/Applications. I rather hope you have been able to progress on the matter since the workshop that took place in November. There, the Architecture for identity Management and Access Control that was sketched was rather high-level. We need more detail and, if possible, reference to the APIs that will be used. This is a demand not just from me but many of the other WPLs/WPAs. I copy the fiware-security mailing list in this response to make them aware about the critical importance of this point. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro On 19/12/11 09:25, BISSON Pascal wrote: > Dear Juanjo, > Dear Colleagues, > > Due to a management meeting Daniel and I have to attend this morning we would not be able to attend the audio conf of today. > > Apologize for the inconvenience. > > Regarding topical architectural issues we'd like to discuss across WPs there are a number of them which were already stated and reported on the Wiki (also discussed through bilateral meeting we had with other WPs at previous GA in Torino - one of them being overall monitoring). In any case I and especially Daniel as WP8 architect will come back to you with more details through couple of slides you requested. > > As for the rest I do sill think we need to go for a physical meeting with all WPAs addressing those architectural issues in order to converge on how to integrate the various partial (view-oriented) architectures we came up with. > > Best Regards, > > Pascal > > PS: Daniel and I will in any case catch up on the minutes of this audio. Once more apologize not being in a position to attend today's audio. > > -----Message d'origine----- > 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? : vendredi 16 d?cembre 2011 12:54 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours > > Hi all, > > This is a reminder that we will have our regular joint WPL/WPA > follow-up confcall on Monday starting at 11:00 and expected to last 3 hours. > > Main focus of the confcall will be to start discussion on > cross/global architectural issues. > > All WPLs/WPAs are welcome to bring presentations elaborating on both > their views (please, enough detailed, not just vague/abstract ideas) and > the questions they believe require launching dedicated Task Forces for > further discussion. From shared material and the discussion that may > follow, we should derive a number of Action Points and we should agree > what concrete Task Forces have to be launched. > > We may devote also some time to agree on preparation of the next > FI-WARE General Assembly. > > Cheers, > > ------------- > Juanjo Hierro > > Product Development and Innovation (PDI) - Telefonica Digital > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > . > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From pascal.bisson at thalesgroup.com Tue Dec 20 15:04:07 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 20 Dec 2011 15:04:07 +0100 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours In-Reply-To: <4EF06433.8070209@tid.es> References: <4EEB3143.2040602@tid.es> <29396_1324283122_4EEEF4F2_29396_6377_1_a94baad4-09d4-474f-8e09-a80435b5a342@THSONEA01HUB06P.one.grp> <4EF06433.8070209@tid.es> Message-ID: <4778_1324389854_4EF095DE_4778_12999_1_85827611-77d6-4b0b-b42e-acd02d155368@THSONEA01HUB01P.one.grp> Dear Juanjo, Dear ALL, First once more my apologize not having been able to join the audio conf of Monday as expected. Second no problem to have this email copied to the Security team being said I already forwarded them also with the minutes of the WPL/WPA audio conf of Monday. This for their information but also to discuss with them the so far outcomes Regarding APIs attached to Security GEs I have an audio conference on Friday where I will review progress on this being said I already stressed each Security GE owner to come up with provisional description of the API(s) accompanying the GE. This obviously apply to the core GEs and so Identity Management. In the meantime I can only regret that the bilateral audio conferences (WP8-WP6, WP8-WP5 and WP8-WP4) on Security GEs (and more specifically Core GEs) as direct follow-up of the WP8-ALL other WPs were not followed (honored) as it could have helped us to make faster progress on this (understanding of GEs and how they could be accessed). But ok this is ongoing work and we will report progress on what we achieved so far. Best Regards, Pascal -----Message d'origine----- De?: Juanjo Hierro [mailto:jhierro at tid.es] Envoy??: mardi 20 d?cembre 2011 11:32 ??: BISSON Pascal Cc?: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; SIEUX Corinne; GIDOIN Daniel; fiware-security at lists.fi-ware.eu Objet?: Re: [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours Dear Pascal, I'm sorry that you couldn't make the call. One of the points that were raised (already mentioned in the minutes), and indeed one about which many people is seeking for an aswer, has to do with definition of the Reference Architecture that we are going to adopt for Identity Management and Access Control. Identity Management and Access Control is a key core GE on which many GEs and final applications will rely. Therefore, we need to know ASAP what is the target solution for this very basic functionality as well as details about what APIs will be used by the programmers of GEs/Applications. I rather hope you have been able to progress on the matter since the workshop that took place in November. There, the Architecture for identity Management and Access Control that was sketched was rather high-level. We need more detail and, if possible, reference to the APIs that will be used. This is a demand not just from me but many of the other WPLs/WPAs. I copy the fiware-security mailing list in this response to make them aware about the critical importance of this point. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro On 19/12/11 09:25, BISSON Pascal wrote: > Dear Juanjo, > Dear Colleagues, > > Due to a management meeting Daniel and I have to attend this morning we would not be able to attend the audio conf of today. > > Apologize for the inconvenience. > > Regarding topical architectural issues we'd like to discuss across WPs there are a number of them which were already stated and reported on the Wiki (also discussed through bilateral meeting we had with other WPs at previous GA in Torino - one of them being overall monitoring). In any case I and especially Daniel as WP8 architect will come back to you with more details through couple of slides you requested. > > As for the rest I do sill think we need to go for a physical meeting with all WPAs addressing those architectural issues in order to converge on how to integrate the various partial (view-oriented) architectures we came up with. > > Best Regards, > > Pascal > > PS: Daniel and I will in any case catch up on the minutes of this audio. Once more apologize not being in a position to attend today's audio. > > -----Message d'origine----- > 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? : vendredi 16 d?cembre 2011 12:54 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours > > Hi all, > > This is a reminder that we will have our regular joint WPL/WPA > follow-up confcall on Monday starting at 11:00 and expected to last 3 hours. > > Main focus of the confcall will be to start discussion on > cross/global architectural issues. > > All WPLs/WPAs are welcome to bring presentations elaborating on both > their views (please, enough detailed, not just vague/abstract ideas) and > the questions they believe require launching dedicated Task Forces for > further discussion. From shared material and the discussion that may > follow, we should derive a number of Action Points and we should agree > what concrete Task Forces have to be launched. > > We may devote also some time to agree on preparation of the next > FI-WARE General Assembly. > > Cheers, > > ------------- > Juanjo Hierro > > Product Development and Innovation (PDI) - Telefonica Digital > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl > . > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Tue Dec 20 16:11:32 2011 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 20 Dec 2011 16:11:32 +0100 Subject: [Fiware-wpa] Final report to send to the PO Message-ID: <4EF0A5A4.1080902@tid.es> Dear all, We have finally produced a (hopefully) final edition of the report for the first 6 months. Please take a look at it, particularly at the numbers (effort) and send your approval if you agree. Regardless of you internal records, or previous communications to the coordination of the project, it is strongly recommended to adapt your declaration of effort to avoid rejection of costs from the PO. According to the evaluation of the Project Leader (Juanjo) this is aligned with the technical results presented in the review. You can reach it here: https://forge.fi-ware.eu/docman/view.php/7/701/D121-FI-WARE_Project+Report_v2.doc The deadline is Thursday, 22. At the end of this date day we will officially send it to the PO so you have until then to contact us. Regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 jhierro at tid.es Wed Dec 21 02:02:00 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 21 Dec 2011 02:02:00 +0100 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER: Joint WPL/WPA Follow-up confcall on Monday starting at 11:00 - 3 hours In-Reply-To: <4778_1324389854_4EF095DE_4778_12999_1_85827611-77d6-4b0b-b42e-acd02d155368@THSONEA01HUB01P.one.grp> References: <4EEB3143.2040602@tid.es> <29396_1324283122_4EEEF4F2_29396_6377_1_a94baad4-09d4-474f-8e09-a80435b5a342@THSONEA01HUB06P.one.grp> <4EF06433.8070209@tid.es> <4778_1324389854_4EF095DE_4778_12999_1_85827611-77d6-4b0b-b42e-acd02d155368@THSONEA01HUB01P.one.grp> Message-ID: <4EF13008.1090909@tid.es> On 20/12/11 15:04, BISSON Pascal wrote: > Dear Juanjo, > Dear ALL, > > First once more my apologize not having been able to join the audio conf of Monday as expected. > > Second no problem to have this email copied to the Security team being said I already forwarded them also with the minutes of the WPL/WPA audio conf of Monday. This for their information but also to discuss with them the so far outcomes I knew ... that's why I assumed there was no issue in doing so. > > Regarding APIs attached to Security GEs I have an audio conference on Friday where I will review progress on this being said I already stressed each Security GE owner to come up with provisional description of the API(s) accompanying the GE. This obviously apply to the core GEs and so Identity Management. Great ! > > In the meantime I can only regret that the bilateral audio conferences (WP8-WP6, WP8-WP5 and WP8-WP4) on Security GEs (and more specifically Core GEs) as direct follow-up of the WP8-ALL other WPs were not followed (honored) as it could have helped us to make faster progress on this (understanding of GEs and how they could be accessed). > > But ok this is ongoing work and we will report progress on what we achieved so far. I guess we may be facing some sort of "chicken & egg" problem ... I believe it is hard for some of the WPs you mention (WP5, WP6 and WP4) trying to sketch how they would integrate with security core GEs if they don't see first how the architecture for Identity Management and Access Control will look like and what are the concrete technologies/APIs that we will use for that ... so I rather suggest that you continue on such effort and hopefully when the a proposed architecture for Identity Management and Access Control gets detailed enough, a more concrete feedback from those other WPs may come naturally ... Besides, I believe part of the answer to the question about how Identity Management and Access Control GEs can integrate with WP4-WP6 relates to the issue I have brought about the "glue middleware" ... please take a look at the attached slides that I used on Monday. Regards, -- Juanjo > > Best Regards, > Pascal > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Cross-chapter Architectural topics.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 141442 bytes Desc: not available URL: From mcp at tid.es Wed Dec 21 18:29:42 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 21 Dec 2011 18:29:42 +0100 Subject: [Fiware-wpa] Private wiki Message-ID: <4EF21786.3010500@tid.es> Dear all, We have created a private project with a private wiki. It is so private that it is not listed on the list of projects on the forge. The only way to reach it is via a direct link! All the WPLs and WPAs should be already administrators of this wiki. * Admin link: https://forge.fi-ware.eu/projects/fi-ware-private * Private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Main_Page @WPLs & WPAs: Please add the users of your respective WPs to the user list. Choose the profile "Senior Developer" for them. To do it, you can go to the 1st link (admin link), click on "Admin" -> "Users" -> "Add Users From List". You will get to a list will all the users from the forge. You can do a multiple selection and add them one by one. Regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ 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 jhierro at tid.es Fri Dec 23 08:25:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 23 Dec 2011 08:25:30 +0100 Subject: [Fiware-wpa] IMPORTANT TO SYNC: FI-WARE First Open Call Message-ID: <4EF42CEA.6030009@tid.es> Hi all, This is to report to you about the decisions taken regarding topics for the first Open Call in FI-WARE. Please share this info with your respective teams. Going through a sequence of three intensive dedicated confcalls, the FI-PPP AB has came to an agreement on how to handle the higher priority topics raised by the UC projects as well as what will be the topics to be addressed in the first Open Call (a number of topics proposed by FI-WARE have been incorporated in the analysis in respect to this last point). You can get a wrap-up of this exercise summarizing the agreements reached looking at the sheet titled "Wrapup" in the following shared Google docs spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE&hl=en_US#gid=1 As you will see, only two topics will be addressed in the first Open Call. Following the advice of our PO, Arian Zwegers, we have decided to split the original first Open Call into two Open Calls, therefore having a total of three Open Calls overall. We have also decided to go for a very short list of topics in this first Open Call. This is because: * Again, following our PO advice, we have to take the opportunity of this Open Call to learn about how to manage the Open Call process so it's better to make it a "small trial" * We had to face the challenge of describing in detail and in collaboration with the UC projects what we will ask for in the description of this first Open Call, which has to be issued by end of January 2012. We have little time/resources to do this for too many topics, overall taking into account that we need to face a number of deliverables by end of January. In addition, many of the high-priority topics that both UC projects and ourselves have in our list (some of them shared) are still described in a too high-level so clearly there is a need to work on further refining them as to distill the actual features we want to support in FI-WARE. This is something that makes sense to afford during Q1 of 2012. Regarding the two particular topics selected for the first Open Call, let me elaborate a bit on them: * Middleware for efficient and QoS/Security-aware invocation of services as well as exchange of messages. There were several UC projects that were asking for this, not just for implementing communication between different parts of the application but for invoking services exposed to applications by the FI-WARE GEs. Therefore, we will have to go for it definitively. However, I see here the opportunity to drive what has to be developed in a way it can become useful in FI-WARE to help a) solving some of the issues we had identified during our Security workshop on November that have to do with managing access control through credentials when handling requests to services, b) dealing with several accountability and traceability issues and c) enabling a technology-neutral definition of GE interfaces. I will elaborate more on what I believe we may push into the definition of requirements for such middleware in the "Glue Middleware" Task Force we agreed to launch in our last joint WPLs/WPAs follow-up confcall. * Business Models and Business Elements (BM & BE) Definition and Simulation This is leveraged in a request made by UC projects to have means for simulating how costs of deploying a given application on top of FI-WARE (not only hosting service costs but costs derived from using other FI-WARE GE services or even third-party application services) could be simulated. Here, I found the opportunity to map this to our critical need to address the development of a BM & BE definition support component in the context of the first Open Call since this will be a base component of the Business Framework Reference Architecture for which an asset hadn't been identified. On the other hand, from my point of view, merging the two things together makes a lot of sense because any party that is able to contribute a product that implements this sort of simulation (which is the ultimate need expressed by the UC projects) may have probably implemented its own tools for defining the basic BM & BE on which simulation is based. Therefore, it makes sense to me to go and adapt our basic BM & BE Model to the one such potential new partner may bring. Regarding the rest of topics some of you had proposed, they where discussed and we agreed that they may go for the second call after their functional description is further defined, which is something that should happen during Q1 2012. Regarding the rest of topics raised by the UC projects, I would like to highlight the following: * Augmented Reality and 3D User Interfaces were brought to the table. Fair enough, these topics are clearly something we were not covering but have to do a lot with the kind of User Experiences someone would expect to see supported in Future Internet Applications. Therefore, I find it rather suitable to cover them through Open Calls which may attract rather specialized partners on the topics. In my view, this may probably lead to definition of a Working Package on User Interface support where, BTW, we may explore whether multi-device and multi-channel access to applications (currently in WP3 and somehow lacking of support) may be collocated. * Many UC projects are looking for means in the platform that will enable them to assure certain QoS at infrastructure level not just at centralized Data Centers but end-to-end. This had been mapped into a number of requests assigned to the I2ND chapter. UC projects do not expect to manage QoS at communication level from the application themselves (other than through the basic middleware targeted in the 1st Open Call). What they expect is to be able to select, configure and contract the SLA linked to an application at configuration&deployment time. SLAs that I see would be expressed in terms of a number of SLOs (Service Level Objectives). In words of one UC project: What would be very nice to have is a service which I can ask: "I need connectivity from A to B", and the service will answer "OK, you have 10 possible paths, price is such, characteristics of connection are such". If this is done properly, my application can then choose the "most reliable", "least expensive", or "most secure" path (and this will be seutp automatically). Next thing would be monitoring to see if the promised characteristics were really delivered (otherwise I don't pay...) I agree this has to be a functionality that has to be provided by FI-WARE but will require a close coordination between the Cloud, I2ND and Apps (Business Framework) chapter, so let's really assign this a high priority in our discussions. BTW, this clearly matches one of the cross-chapter Task Forces we identified during our last joint WPLs/WPAs confcall (Network-aware Cloud Task Force) * Many UC projects also have requirements for distributing their applications partly in the centralized Data Centers and partly in cloud proxies at the network-edge. Many of them wish to see the concept of cloud-proxy generalized as to cover smartphones and other smart but small devices. This comes along the need to be able to describe this distributed taxonomy at the time applications are configured and deployed on FI-WARE as well as the need to define means for handling failures in communication between the Data Center clouds and cloud proxies (periodic synchronizations and the like). This doesn't come as something new to us, but confirms the need to afford the definition of the necessary components at the Cloud chapter that can deal with this and prepare this as a subject for the second Open Call. * Another common requirements have to do with a) being able to assign a level of certainty/trust to data being managed by the application and b) being able to manage access and views to data depending on credentials of the user on behalf of whom an application is trying to get access to data. Both requirements are clearly generic and probably useful for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Several UC projects also expressed the need for several kind of "data-stream-oriented" GEs. For instance, the notion of Publish/Subscribe but linked to streams rather than to atomic data units. Again, this seems to be something generic and useful enough for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Rest of requirements were about topics I believe most probably are already in our roadmap or should not be a big issue to include in our roadmap. We agreed to follow them during Q1 2012 as to confirm this or not. Hope this long summary gives you a clear picture. Next steps will mean working on the detailed development of Epics that will be published as part of the first Open Call and will provide an enough detailed description of what we are looking for there. In addition, setting up a number of Task Forces on the topics above, involving UC projects, where we will address identification of Features. Such features will either enrich our current FI-WARE backlog (because we find they would fit within the roadmap of already identified GEs) or will be used for describing what will be requested in the second Open Call. More details will follow in the first weeks of January. I take advantage of this email to wish you all a very nice Christmas and a Happy New Year. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ 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 ralli at tid.es Fri Dec 23 13:24:22 2011 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 23 Dec 2011 13:24:22 +0100 Subject: [Fiware-wpa] [Fiware-wpl] Notes from last joint WPLs/WPAs confcall In-Reply-To: <4EF052AC.5090901@tid.es> References: <4EF052AC.5090901@tid.es> Message-ID: Hi all, Actually we are uploading these PhC minutes to the forge: https://forge.fi-ware.eu/docman/view.php/7/708/20111219-WPL_minutes.docx Please, note that you need to be logged in the forge prior to access through the above mentioned link. The overall template for the project minutes is available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Useful_document_templates Best regards, -- ------------------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------- El 20/12/2011, a las 10:17, Juanjo Hierro escribi?: Hi all, Please find below my notes from our confcall today. Please share with your respective teams. As you see, there will be a number of APs to setup a number of Task Forces, each concentrated in a particular cross-chapter topic (see point on goals and agenda). A mailing list for discussion on the topic will be setup. In addition, a ticket will be created in a Task Force Management tracker we will setup in the "FI-WARE Private" project in FusionForge that has been created. The ticket will point to the archive of the mailing list being created and will help us to follow up progress. Cheers, -- Juanjo 1. Attendees * Cloud Chapter: Alex (IBM) * Data Chapter: Carlos (TID) * IoT Chapter: Denes (NSN) * Apps Chapter: Torsten (SAP), Axel (SAP) * Security Chapter: None * I2ND: Pier (TI), Hans (DT) * Dev Tools: Davide (Engineering) * Exploitation (Juan) 2. Goals and agenda: The main goal of the confcall is to identify architectural topics that will require further discussion involving more than one chapter. An Architecture Task Force will be created for each relevant topic. Concretely, this will mean that: * TID will set up a dedicated mailing list and create a ticket on the Task Force tracker in the FI-WARE private project in FusionForge * Each WPL/WPA will designate who should join from their chapters * The partner who proposed the Task Force (owner of the Task Force) will kick-off the discussion on the mailing list by sending an email which helps as terms of reference * The owner of the Task Force should present conclusions at the joint WPL/WPA meeting that will take place on January 23rd Each WPL/WPA was requested to bring any cross-chapter topic for which he wish to create a Task Force. The following partners brought some views: * Juanjo (TID) * Davide (Engineering) * Torsten (SAP) * Pier (Telecom Italia) 3. Presentation by Juanjo 3.1 Generalize Event Management model being proposed at the level of Things in IoT chapter, applying it to Cloud Monitoring and Security Events Monitoring Despite it is still under discussion, the Event Management Model being proposed at the level of Things in the IoT chapter is rather generic and has been defined so it is consistent with the Event Management model defined within the Data/Context Management Model. This Event Management Model is based on the OMA (Open Mobile Alliance) specs for NGSI Context-Management. In such model, an event leads to generation of a Context Element data structure which includes info about updated values of properties linked to entities defined in the system. An entity maps to the concept of "Thing" in the IoT chapter but there may be other entities in the system (e.g., another application). In FI-WARE, values assigned to properties describing Things will be derived from data gathered from IoT resources, referred as sensors, which run on IoT devices. Associations between Things and IoT resources as well as formulas for mapping values of IoT resources into properties of entities are handled through an IoT Configuration Management GE at the Things Management Layer. However, this concept may be further generalized so that we talk about "Monitoring Agents" or "Monitored Resources". The model would then be able to work for both Cloud Monitoring and Security Events Monitoring. The advantage for this approach would be reuse of components, as well as exhibiting higher coherence. AP: Setup task force to check whether the Events Management Model defined at the level of Things within IoT chapter can be adopted for both Cloud monitoring and Security events monitoring. Mailing list to be created: fiware-monitoring 3.2 Glue middleware There are a number of issues that are related to how interfaces exported by GEs are actually specified and implemented: * first, we have to agree on a common way to specify interfaces exported by GEs ... Should we adopt REST as a minimum common denominator ? Can we define a technology-neutral approach that would allow an interface to be accessible using multiple technologies (REST, WS, optimized binary protocols, ...) and would allow us to overcome that a given technology becomes deprecated ? * second, the most suitable technical solution for some Security issues may need to implement some functions at middleware level * third, APIs usage accountability may require that also some functions be implemented at middleware level if we want to achieve a suitable level of transparency Alex: not sure if we can decide on one API paradigm but he agrees we should support just a limited set Juanjo: is not about choosing one API paradigm but probably define an interface definition language that may abstract us from the limited set of API paradigms we will support (which could then be extended over time). Denes: any decision on middleware should take into account that middleware may need to fit with restrictions about computing resources in IoT devices AP: Setup task force on the matter. Mailing list to be created: fiware-middleware 3.3 Network-aware Cloud Some UC projects have declared the need to be able to declare what SLO (Service Level Objectives) they want to see fulfilled for certain end-to-end scenarios, typically requiring communication between applications running on the Cloud and IoT gateways (cloud proxies) or end users. It would then be up to the Cloud Hosting capabilities in FI-WARE to cope with those SLOs relying on capacities of the underlying network. Despite we will see whether this functionality would easily fit in the roadmap based on available resources, all declare to agree with creation of a Task Force on the matter. It will typically involve partners from the I2ND chapter, Cloud chapter and Apps chapter (since we need to resolve how this sort of SLOs become part of the SLA definition linked to an application) We agree to leave P2P scenarios aside for the time being unless UC projects raise the need to analyze them. AP: Start with a single Task Force involving I2ND, Cloud and Apps chapter members. Mailing list to be created: fiware-network-cloud-SLOs Eventually split into two task forces if needed which may be: - a task force involving Apps (Business Framework) and Cloud chapters, dealing with how to declare SLAs at USDL related to end-to-end SLOs - a task force involving Cloud and I2ND chapter dealing with how to implement SLOs relying on QoS management functions exported by networks 3.4 Semantic Web Infrastructure: Several chapters addressing development of GEs whose implementation relies on Semantic Web technologies. We should go for the selection of a single technology for this (mostly RDF storage and SPARQL support) AP: Setup a Task Force that takes a decision for all the project. Mailing list to be created: fiware-semantic-platform Torsten: Shouldn't we also go for a common decision regarding linked-data GE ? AP: Apps chapter to share info about linked-data technologies being defined in their chapter so that rest of WPAs can evaluate whether it can be used elsewhere (info to be sent to fiware-wpa mailing list for the time being) 3.5 Common Look&Feel in FI-WARE portals AP: Juanjo to launch a thread of discussion on the matter so that we can start discussion on the matter 4. Development Tools by Davide Davide reinforce the need to link some of the developments to be made within the Dev&Tools and those in other chapters. Particularly those that have to do with deployment tools where we need to explore how they integrate (or matches) the development of part of the Cloud portal. He also reinforce the need to make a decision on how interfaces will be specified and what protocols will be supported. Davide take the opportunity to reinforce that other chapter leaders should answer the questionnaire that was distributed by WP9 to all WPLs/WPAs. 5. Presentation by Torsten Despite Torsten didn't have time to present all cross-chapter topics, he made emphasis on the need to push for making services provided by FI-WARE GEs available in the marketplace. This means that they should be defined in USDL. Juanjo: this should allow that a FI-WARE Instance Provider operating a FI-WARE Instance defined around the Marketplace GEs offer third parties the ability to publish their implementation of FI-WARE GEs in other chapters and get paid for their usage by applications. It would also help a FI-WARE Instance Provider operating a FI-WARE Instance that deploys all FI-WARE GEs to establish how it plans to charge for usage of their services by applications. AP: To setup Task Force on discussion about USDL. Mailing list to be created: fiware-usdl As a second major point in his presentation, Torsten put emphasis on the need to close the definition of the GEs supporting Identity Management. We should soon have the APIs of these GEs defined as soon as possible. Juanjo and Pier highlighted this is rather relevant. Juanjo expects that the Security chapter has been able to further refine the vision that they presented in the workshop which took place in November and now could present a detailed Reference Architecture with well-defined APIs. AP: To setup Task Force on discussion about Security Identity Management, Access Control and Data Handling. Mailing list to be created fiware-security-core Unfortunately, there was not time to address other topics to be brought by Torsten. He will distribute his presentation among WPLs/WPAs. 6. Short comments by Pier Pier mentioned that they are already working on how to ensure that cloud-edge proxy supports all capabilities that are needed to host IoT software. AP: We may consider that a Task Force is already in place. We just need to create a dedicated mailing list to discuss on the matter: ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ 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: From jhierro at tid.es Tue Dec 27 08:00:48 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 27 Dec 2011 08:00:48 +0100 Subject: [Fiware-wpa] Fwd: Draft of the FI-WARE First Open Call announcement In-Reply-To: <4EF96C11.6070605@tid.es> References: <4EF96C11.6070605@tid.es> Message-ID: <4EF96D20.80400@tid.es> Hi all, Please find enclosed the draft version of the first FI-WARE Open Call announcement that we have submitted to our PO, Arian Zwegers. This document is just a draft. Suggestions on how to further improve it are welcomed prior to its publication planned on January 31, 2012. Note that we have selected a closing date for the Open Call that would allow submitters to specify whether their proposal would be based on integration of results coming from a potentially funded project under FP7 ICT Call 8. Best regards, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro -------- Original Message -------- Subject: Draft of the FI-WARE First Open Call announcement Date: Tue, 27 Dec 2011 07:56:17 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: FI-WARE project EC mailbox , Jose Jimenez , Miguel Carrillo , "subsidies at tid.es" , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find enclosed the draft that we have developed for the FI-WARE First Open Call announcement. We look forward your comments. Best regards, ------------- Juanjo Hierro FI-WARE Chief Architect and Technical Manager 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE - Announcement of first competitive Open Call for additional partners.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 22326 bytes Desc: not available URL: