From jhierro at tid.es Wed Jun 1 20:13:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Jun 2011 20:13:32 +0200 Subject: [Fiware-wpl] NEXT STEPS and Updated template of FI-WARE High-level Description deliverable with reference example of GE description Message-ID: <4DE6814C.6020508@tid.es> Hi all, I hope you are making good progress in the development of your respective chapters in the FI-WARE High-Level Description deliverable. Trying to give you some hints regarding how the sections on GE description should look like, please find an updated version of the deliverable template at: http://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc There, I have included the description of a GE which I particularly consider a good reference example of a GE description in terms of clarity, style of writing and level of detail provided. Sometimes, taking a look to a concrete example, you get a better clue of what is expected. I will try to provide some additional ones in the coming days. I believe this might be more practical prior sending specific comments on the drafts you have produced so far. Regarding revision of your drafts and trying to put in place a method that may help to avoid any collision while editing, I suggest that we adopt the following approach: * You should upload in FusionForge the latest draft you have consolidated every day, no later than 19:00 CET. Please send an email to this two lists (fiware-wpl and fiware-wpa) announcing you have done so and where we can find it (URL) * Me or Thomas will select some of the drafts you have uploaded and review them, uploading an updated version with comments prior the next day, no later than 08:00 CET. If you don't see a change in your chapter at that time, that means we haven't reviewed it the previous night, nor plan to do so before 19:00 CET. This means you can edit it without risk. If you realize there is a new version, please download it and adopt it as your working document. It should contain comments you are asked to review. Some of these comments may refer to sections that requires discussion and analysis. Such comments will be considered as a request to you for blocking the edition of a given fragment of your chapter until such discussion takes place (we will contact you separately to schedule some phone call, for example). We will specify what concrete fragment of the document we wish you to block, so that you can work in the rest. The above applies also to weekends. This is not that I'm meaning you should work during weekends, but some people do so and that's fine for us. You simply will be required to follow the above rules also those days. This method of working will be effective starting tomorrow. Based on the above, I expect that you will upload the latest consolidated draft of your chapter by tomorrow, 19:00 CET. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 2 15:33:14 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 Jun 2011 15:33:14 +0200 Subject: [Fiware-wpl] [Fiware-wpa] NEXT STEPS and Updated template of FI-WARE High-level Description deliverable with reference example of GE description In-Reply-To: <4DE6814C.6020508@tid.es> References: <4DE6814C.6020508@tid.es> Message-ID: <4DE7911A.4080702@tid.es> Hi, You should upload your contributions to the group named as "D.2.2 contribs" under "D.2.2 FI-WARE High-level Description" which in turn is under "FI-WARE deliverables" in the docman system linked to the FI-WARE project at FusionForge. [cid:part1.08010807.04060202 at tid.es] Best regards, -- Juanjo On 01/06/11 20:13, Juanjo Hierro wrote: Hi all, I hope you are making good progress in the development of your respective chapters in the FI-WARE High-Level Description deliverable. Trying to give you some hints regarding how the sections on GE description should look like, please find an updated version of the deliverable template at: http://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc There, I have included the description of a GE which I particularly consider a good reference example of a GE description in terms of clarity, style of writing and level of detail provided. Sometimes, taking a look to a concrete example, you get a better clue of what is expected. I will try to provide some additional ones in the coming days. I believe this might be more practical prior sending specific comments on the drafts you have produced so far. Regarding revision of your drafts and trying to put in place a method that may help to avoid any collision while editing, I suggest that we adopt the following approach: * You should upload in FusionForge the latest draft you have consolidated every day, no later than 19:00 CET. Please send an email to this two lists (fiware-wpl and fiware-wpa) announcing you have done so and where we can find it (URL) * Me or Thomas will select some of the drafts you have uploaded and review them, uploading an updated version with comments prior the next day, no later than 08:00 CET. If you don't see a change in your chapter at that time, that means we haven't reviewed it the previous night, nor plan to do so before 19:00 CET. This means you can edit it without risk. If you realize there is a new version, please download it and adopt it as your working document. It should contain comments you are asked to review. Some of these comments may refer to sections that requires discussion and analysis. Such comments will be considered as a request to you for blocking the edition of a given fragment of your chapter until such discussion takes place (we will contact you separately to schedule some phone call, for example). We will specify what concrete fragment of the document we wish you to block, so that you can work in the rest. The above applies also to weekends. This is not that I'm meaning you should work during weekends, but some people do so and that's fine for us. You simply will be required to follow the above rules also those days. This method of working will be effective starting tomorrow. Based on the above, I expect that you will upload the latest consolidated draft of your chapter by tomorrow, 19:00 CET. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: moz-screenshot-26.png Type: image/png Size: 60961 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 3 15:17:52 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 Jun 2011 15:17:52 +0200 Subject: [Fiware-wpl] IMPORTANT: [Fiware-wpa] NEXT STEPS and Updated template of FI-WARE High-level Description deliverable with reference example of GE description In-Reply-To: <4DE7911A.4080702@tid.es> References: <4DE6814C.6020508@tid.es> <4DE7911A.4080702@tid.es> Message-ID: <4DE8DF00.5070004@tid.es> Hi, This is a reminder on this matter. So far, only the Context/Data Management WP and the IoT Service Enablement WP have follow the instructions. You should do the same in the rest of WPs. So far I'm not that dissapointed because I know that yesterday was bank holidays in most of Europe and probably you have also taken today. But there will not be any excuse if you don't upload a draft every evening starting on monday (read emails attached bottom up). Of course, if you upload something before monday, it would be nice. Best regards, -- Juanjo On 02/06/11 15:33, Juanjo Hierro wrote: Hi, You should upload your contributions to the group named as "D.2.2 contribs" under "D.2.2 FI-WARE High-level Description" which in turn is under "FI-WARE deliverables" in the docman system linked to the FI-WARE project at FusionForge. [cid:part1.00030604.05020508 at tid.es] Best regards, -- Juanjo On 01/06/11 20:13, Juanjo Hierro wrote: Hi all, I hope you are making good progress in the development of your respective chapters in the FI-WARE High-Level Description deliverable. Trying to give you some hints regarding how the sections on GE description should look like, please find an updated version of the deliverable template at: http://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc There, I have included the description of a GE which I particularly consider a good reference example of a GE description in terms of clarity, style of writing and level of detail provided. Sometimes, taking a look to a concrete example, you get a better clue of what is expected. I will try to provide some additional ones in the coming days. I believe this might be more practical prior sending specific comments on the drafts you have produced so far. Regarding revision of your drafts and trying to put in place a method that may help to avoid any collision while editing, I suggest that we adopt the following approach: * You should upload in FusionForge the latest draft you have consolidated every day, no later than 19:00 CET. Please send an email to this two lists (fiware-wpl and fiware-wpa) announcing you have done so and where we can find it (URL) * Me or Thomas will select some of the drafts you have uploaded and review them, uploading an updated version with comments prior the next day, no later than 08:00 CET. If you don't see a change in your chapter at that time, that means we haven't reviewed it the previous night, nor plan to do so before 19:00 CET. This means you can edit it without risk. If you realize there is a new version, please download it and adopt it as your working document. It should contain comments you are asked to review. Some of these comments may refer to sections that requires discussion and analysis. Such comments will be considered as a request to you for blocking the edition of a given fragment of your chapter until such discussion takes place (we will contact you separately to schedule some phone call, for example). We will specify what concrete fragment of the document we wish you to block, so that you can work in the rest. The above applies also to weekends. This is not that I'm meaning you should work during weekends, but some people do so and that's fine for us. You simply will be required to follow the above rules also those days. This method of working will be effective starting tomorrow. Based on the above, I expect that you will upload the latest consolidated draft of your chapter by tomorrow, 19:00 CET. 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 ________________________________ 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: image/png Size: 60961 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From GLIKSON at il.ibm.com Fri Jun 3 18:23:24 2011 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 3 Jun 2011 19:23:24 +0300 Subject: [Fiware-wpl] NEXT STEPS and Updated template of FI-WARE High-level Description deliverable with reference example of GE description In-Reply-To: <4DE8DF00.5070004@tid.es> References: <4DE6814C.6020508@tid.es> <4DE7911A.4080702@tid.es> <4DE8DF00.5070004@tid.es> Message-ID: I've uploaded the draft for Cloud Hosting. Regards, Alex From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Date: 03/06/2011 04:18 PM Subject: [Fiware-wpa] IMPORTANT: [Fiware-wpl] NEXT STEPS and Updated template of FI-WARE High-level Description deliverable with reference example of GE description Sent by: fiware-wpa-bounces at lists.fi-ware.eu Hi, This is a reminder on this matter. So far, only the Context/Data Management WP and the IoT Service Enablement WP have follow the instructions. You should do the same in the rest of WPs. So far I'm not that dissapointed because I know that yesterday was bank holidays in most of Europe and probably you have also taken today. But there will not be any excuse if you don't upload a draft every evening starting on monday (read emails attached bottom up). Of course, if you upload something before monday, it would be nice. Best regards, -- Juanjo On 02/06/11 15:33, Juanjo Hierro wrote: Hi, You should upload your contributions to the group named as "D.2.2 contribs" under "D.2.2 FI-WARE High-level Description" which in turn is under "FI-WARE deliverables" in the docman system linked to the FI-WARE project at FusionForge. Best regards, -- Juanjo On 01/06/11 20:13, Juanjo Hierro wrote: Hi all, I hope you are making good progress in the development of your respective chapters in the FI-WARE High-Level Description deliverable. Trying to give you some hints regarding how the sections on GE description should look like, please find an updated version of the deliverable template at: http://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc There, I have included the description of a GE which I particularly consider a good reference example of a GE description in terms of clarity, style of writing and level of detail provided. Sometimes, taking a look to a concrete example, you get a better clue of what is expected. I will try to provide some additional ones in the coming days. I believe this might be more practical prior sending specific comments on the drafts you have produced so far. Regarding revision of your drafts and trying to put in place a method that may help to avoid any collision while editing, I suggest that we adopt the following approach: You should upload in FusionForge the latest draft you have consolidated every day, no later than 19:00 CET. Please send an email to this two lists (fiware-wpl and fiware-wpa) announcing you have done so and where we can find it (URL) Me or Thomas will select some of the drafts you have uploaded and review them, uploading an updated version with comments prior the next day, no later than 08:00 CET. If you don't see a change in your chapter at that time, that means we haven't reviewed it the previous night, nor plan to do so before 19:00 CET. This means you can edit it without risk. If you realize there is a new version, please download it and adopt it as your working document. It should contain comments you are asked to review. Some of these comments may refer to sections that requires discussion and analysis. Such comments will be considered as a request to you for blocking the edition of a given fragment of your chapter until such discussion takes place (we will contact you separately to schedule some phone call, for example). We will specify what concrete fragment of the document we wish you to block, so that you can work in the rest. The above applies also to weekends. This is not that I'm meaning you should work during weekends, but some people do so and that's fine for us. You simply will be required to follow the above rules also those days. This method of working will be effective starting tomorrow. Based on the above, I expect that you will upload the latest consolidated draft of your chapter by tomorrow, 19:00 CET. 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 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[attachment "jhierro.vcf" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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: not available Type: image/png Size: 60961 bytes Desc: not available URL: From jhierro at tid.es Mon Jun 13 19:16:47 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Jun 2011 19:16:47 +0200 Subject: [Fiware-wpl] IMPORTANT: Update on status and planning for coming weeks Message-ID: <4DF645FF.30905@tid.es> Hi all, This is a message where I would like to inform you about overall status of the project and propose an update on our short-term planning. I hope it will also be helpful in bringing a shared view of where we are and what we are doing that we can communicate consistently inside and outside our consortia. It's a long mail, but please read it carefully. As always, comments and feedback is welcome. Cheers, -- Juanjo 1. Introduction. Some basic considerations. As you all know, we are currently focused in delivery of the FI-WARE High-level Description document. This would be a sort of "Product vision" document in line with what the Agile methodology proposes. Notice that the true consolidated "Product Vision" document is the one we expect to deliver by end of month 5, i.e., end of September. Once we get that "Product Vision" ready, we should start materializing our vision in subsequent Sprints (duration of our Sprints should be two months). By end of month 5 we should also have a first release of our FI-WARE features backlog, made up of the features we have identified ourselves and plan to implement for each and every GE in FI-WARE. We should be able to develop that backlog independently of the input by UC projects, I mean, we should have a plan/roadmap ready for each and every GE by end of month 5. What we are going to deliver in month 2 should be considered an early draft of this "Product Vision". It's something that is helpful for starting the dialogue with the UC projects. Kind of: "you know, this is an early description of what we are planning to deliver, your feedback is welcome". But doesn't need to be a) complete, i.e., meaning there might be things we will declare "work under progress and expected to be finished by end of month 5" nor b) as exhaustive as it will be by end of month 5. Indeed, I want only to provide the description of GEs we are rather confident about in our release in month 2. Anything that we don't considered yet closed should go to the "Question Marks" section (which I'm considering to retitle as "Question marks and work still under progress" or simply "Work still under progress"). From month 2 until month 5, UC projects will be entitled to generate "request for inclusion" of features to our backlog. We will see how many of these feature request will finally be accepted and how accepted features will be prioritized against the features we have already identified on our own. Analysis and management of feature requests coming from UC projects is something we will carry out from month 5 to month 7. 2. Status of FI-WARE High-level Description ("Product Vision") deliverable in month 2. Our initial plan was to have a consolidated draft of each of the Architecture Chapters in the FI-WARE High-level Description document by mid June. Then spend the two last weeks of June to perform some peer reviews and carry out final integration of the deliverable. I guess you agree we have to face that it would be rather tough to reach this milestone. On the other hand, I feel like we have had very fruitful discussions in several of the WPs and we are getting more and more closer to a nice description of the GEs in each chapter. So I see the bottle more "half full" than "half empty" :-) Overall because definitively we have to spend the necessary time to agree in a "Product Vision" without feeling so much stressed (to certain extend :-) to milestones that were very tight and hard to achieve since the very beginning. Given said this, my proposal would be to delay this first internal integration milestone until June 22 (mid next week) unless I hear any objection from some of you. Of course, we will have to make all what is in our hands to reach this new date. I trust on you and I feel that if we keep things going the way they are going, we can meet the new deadline. Note that this delay is something I'm just sharing with you. Feel free to manage this info the way you want with partners in your WP :-) You can disclose it or not at your own criteria. May be you wish to keep some pressure on some internal milestone you had setup, for example :-) From June 22 until June 30 we will try to make a complete integration of all contributions as to deliver a first consolidated draft of the document. On June 22 I will come with a proposal on what precise tasks we will carry out during that period and how we are going to manage things, but I can anticipate that the following tasks will be included in the plan: * We will plan peer reviews of those chapters we may consider closer to a final version. Concrete partners will be assigned this task. * We will setup a number of task forces, typically one per WP, to analyze security issues with regard to each WP. The task force corresponding to a given WP would involve people from that WP and people from the Security WP. By June 30 we will perform an assessment about where we are. If we have something final, that would be great and we will officially deliver it to both the UC projects and the EC. If we have something that is still a draft but might be worth disclosing to the UC projects under a notice that it is still a draft, we will announce an official delay to the EC for July 18 but we will disclose the existing draft (with the mentioned notice) to both the UC projects and the EC. 3. Some administrative/management details. We will keep the docman system as the way to share versions of the different contributions as well as consolidated releases of the final deliverable at least until June 22. I want to let you know that we already have SVN (Subversion) available in FusionForge, but I guess it doesn't make sense to migrate right now but keep going until we get this first deliverable finished. Later, we may migrate to SVN. We will keep sharing the contributions in the contribs folder linked to deliverable D.2.2 in the docman system under the FI-WARE project in FusionForge. However, I will today change the name of the entries in that folder to get something harmonized. From then on, I expect that all new releases of a given contrib will be uploaded under the assigned entry. This should be done by going to the Admin interface, then navigating to the entry in question and updating the file assigned to the entry. You should then assign a name to your contributed file which follows the following name convention: "FI-WARE High-level Desc v. valid until .doc" where: * is a name from the following list: * "Apps" (WP3) * "Cloud" (WP4) * "IoT" (WP5) * "Data" (WP6) * "I2ND" (WP7) * "Security" (WP8) * v. is the numbering of the version you assign to your contribution (e.g., v1.0 or v5.3) * is the date in which you have closed the edition of the file: (e.g., June 20, 2011 would be "11-06-20"). * is the date at which you plan to download the document again and you plan to start editing it again. If not specified, we will assume you expect to download a new release for editing "the next day (tomorrow) at 09:00am". (note: major and minor numbers are not reset when you change the date of a release. They should be absolute.) As an example, you may upload "FI-WARE High-level Desc Cloud v3.2 11-06-18 valid until 11-06-20.doc" That file would mean that it is v3.2 of your chapter, released on June 18, 2011. It will also mean that you don't plan to resume editing of it until June 20, 2011. As explained in a previous mail, you should upload new releases of the document (if you have some) no later than 19:00 and, PLEASE, if you have introduced some change in the document, no matter how minor they are, you should update the document in the server at 19:00 and do not touch it until 09:00am the following day. Besides, you should always download the version that is on the server whenever you plan to start editing your chapter. Please declare a if you rather don't plan to edit the document the day after. This would allow Thomas and me to have more time to review it, not just during nights :-) ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Tue Jun 14 13:58:41 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 14 Jun 2011 13:58:41 +0200 Subject: [Fiware-wpl] IMPORTANT: Update on status and planning for coming weeks In-Reply-To: <4DF645FF.30905@tid.es> References: <4DF645FF.30905@tid.es> Message-ID: <4DF74CF1.7080304@tid.es> Following my email yesterday, just let you know that I have changed the name of the entries/placeholders in the contribs folders linked to your contribution. I would kindly ask you to go there and update the corresponding file linked to each entry so that it now follows the naming conventions that I explained in my email. Please, whenever you upload a new file, do so by going to the Admin menu, then navigating to your entry and then uploading the file in the field titled "OPTIONAL: upload new file" in the form. So, please, don't create new entries, just upload a new file linked to the existing entry. Thanks and best regards, -- Juanjo On 13/06/11 19:16, Juanjo Hierro wrote: Hi all, This is a message where I would like to inform you about overall status of the project and propose an update on our short-term planning. I hope it will also be helpful in bringing a shared view of where we are and what we are doing that we can communicate consistently inside and outside our consortia. It's a long mail, but please read it carefully. As always, comments and feedback is welcome. Cheers, -- Juanjo 1. Introduction. Some basic considerations. As you all know, we are currently focused in delivery of the FI-WARE High-level Description document. This would be a sort of "Product vision" document in line with what the Agile methodology proposes. Notice that the true consolidated "Product Vision" document is the one we expect to deliver by end of month 5, i.e., end of September. Once we get that "Product Vision" ready, we should start materializing our vision in subsequent Sprints (duration of our Sprints should be two months). By end of month 5 we should also have a first release of our FI-WARE features backlog, made up of the features we have identified ourselves and plan to implement for each and every GE in FI-WARE. We should be able to develop that backlog independently of the input by UC projects, I mean, we should have a plan/roadmap ready for each and every GE by end of month 5. What we are going to deliver in month 2 should be considered an early draft of this "Product Vision". It's something that is helpful for starting the dialogue with the UC projects. Kind of: "you know, this is an early description of what we are planning to deliver, your feedback is welcome". But doesn't need to be a) complete, i.e., meaning there might be things we will declare "work under progress and expected to be finished by end of month 5" nor b) as exhaustive as it will be by end of month 5. Indeed, I want only to provide the description of GEs we are rather confident about in our release in month 2. Anything that we don't considered yet closed should go to the "Question Marks" section (which I'm considering to retitle as "Question marks and work still under progress" or simply "Work still under progress"). From month 2 until month 5, UC projects will be entitled to generate "request for inclusion" of features to our backlog. We will see how many of these feature request will finally be accepted and how accepted features will be prioritized against the features we have already identified on our own. Analysis and management of feature requests coming from UC projects is something we will carry out from month 5 to month 7. 2. Status of FI-WARE High-level Description ("Product Vision") deliverable in month 2. Our initial plan was to have a consolidated draft of each of the Architecture Chapters in the FI-WARE High-level Description document by mid June. Then spend the two last weeks of June to perform some peer reviews and carry out final integration of the deliverable. I guess you agree we have to face that it would be rather tough to reach this milestone. On the other hand, I feel like we have had very fruitful discussions in several of the WPs and we are getting more and more closer to a nice description of the GEs in each chapter. So I see the bottle more "half full" than "half empty" :-) Overall because definitively we have to spend the necessary time to agree in a "Product Vision" without feeling so much stressed (to certain extend :-) to milestones that were very tight and hard to achieve since the very beginning. Given said this, my proposal would be to delay this first internal integration milestone until June 22 (mid next week) unless I hear any objection from some of you. Of course, we will have to make all what is in our hands to reach this new date. I trust on you and I feel that if we keep things going the way they are going, we can meet the new deadline. Note that this delay is something I'm just sharing with you. Feel free to manage this info the way you want with partners in your WP :-) You can disclose it or not at your own criteria. May be you wish to keep some pressure on some internal milestone you had setup, for example :-) From June 22 until June 30 we will try to make a complete integration of all contributions as to deliver a first consolidated draft of the document. On June 22 I will come with a proposal on what precise tasks we will carry out during that period and how we are going to manage things, but I can anticipate that the following tasks will be included in the plan: * We will plan peer reviews of those chapters we may consider closer to a final version. Concrete partners will be assigned this task. * We will setup a number of task forces, typically one per WP, to analyze security issues with regard to each WP. The task force corresponding to a given WP would involve people from that WP and people from the Security WP. By June 30 we will perform an assessment about where we are. If we have something final, that would be great and we will officially deliver it to both the UC projects and the EC. If we have something that is still a draft but might be worth disclosing to the UC projects under a notice that it is still a draft, we will announce an official delay to the EC for July 18 but we will disclose the existing draft (with the mentioned notice) to both the UC projects and the EC. 3. Some administrative/management details. We will keep the docman system as the way to share versions of the different contributions as well as consolidated releases of the final deliverable at least until June 22. I want to let you know that we already have SVN (Subversion) available in FusionForge, but I guess it doesn't make sense to migrate right now but keep going until we get this first deliverable finished. Later, we may migrate to SVN. We will keep sharing the contributions in the contribs folder linked to deliverable D.2.2 in the docman system under the FI-WARE project in FusionForge. However, I will today change the name of the entries in that folder to get something harmonized. From then on, I expect that all new releases of a given contrib will be uploaded under the assigned entry. This should be done by going to the Admin interface, then navigating to the entry in question and updating the file assigned to the entry. You should then assign a name to your contributed file which follows the following name convention: "FI-WARE High-level Desc v. valid until .doc" where: * is a name from the following list: * "Apps" (WP3) * "Cloud" (WP4) * "IoT" (WP5) * "Data" (WP6) * "I2ND" (WP7) * "Security" (WP8) * v. is the numbering of the version you assign to your contribution (e.g., v1.0 or v5.3) * is the date in which you have closed the edition of the file: (e.g., June 20, 2011 would be "11-06-20"). * is the date at which you plan to download the document again and you plan to start editing it again. If not specified, we will assume you expect to download a new release for editing "the next day (tomorrow) at 09:00am". (note: major and minor numbers are not reset when you change the date of a release. They should be absolute.) As an example, you may upload "FI-WARE High-level Desc Cloud v3.2 11-06-18 valid until 11-06-20.doc" That file would mean that it is v3.2 of your chapter, released on June 18, 2011. It will also mean that you don't plan to resume editing of it until June 20, 2011. As explained in a previous mail, you should upload new releases of the document (if you have some) no later than 19:00 and, PLEASE, if you have introduced some change in the document, no matter how minor they are, you should update the document in the server at 19:00 and do not touch it until 09:00am the following day. Besides, you should always download the version that is on the server whenever you plan to start editing your chapter. Please declare a if you rather don't plan to edit the document the day after. This would allow Thomas and me to have more time to review it, not just during nights :-) ________________________________ 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: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Sun Jun 19 19:27:58 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Sun, 19 Jun 2011 19:27:58 +0200 Subject: [Fiware-wpl] New version of IoT Architecture Message-ID: Dear all, I've just uploaded the last version (v013) of IoT contribution to D2.2. BR Thierry Nagellen Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 20 13:17:42 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 20 Jun 2011 13:17:42 +0200 Subject: [Fiware-wpl] Minutes of the second meeting of the FI-PPP Architecture Board Message-ID: <4DFF2C56.1070505@tid.es> Dear all, Please find enclosed the minutes of the second meeting of the FI-PPP Architecture Board that took place on June 16th. Next meeting of the FI-PPP AB will be f2f in Madrid on July 11-12. As you would see in the minutes, I already announced that the official release of the FI-WARE High-level Description deliverable will be delayed to mid July (indeed to be presented to members of the AB in our f2f meeting in July). However, we committed to share with them a draft by end of June. This draft is intended to be stable and with all target contents ready (the two first weeks of July would be devoted to final review after official release). This would help UC projects to start reading the FI-WARE High-level Description in order to understand what we plan to deliver. Please push work in your respective WPs to make it happen. 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 -------------- A non-text attachment was scrubbed... Name: FI-PPP-AB-Meeting-Minutes 11-06-16 v1.0.doc Type: application/msword Size: 591360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Wed Jun 22 17:12:42 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 Jun 2011 17:12:42 +0200 Subject: [Fiware-wpl] Submission of chapters for the first complete integration of FI-WARE High-level description deliverable Message-ID: <4E02066A.3020501@tid.es> Hi all, I would kindly ask you to follow the conventions I explained in my email on June 13 ... * Don't create additional entries to the one that already exist ... you should locate your entry navigating across the Admin pages of the docman system. When you are at your entry, you should find something like: [cid:part1.08080305.05030602 at tid.es] Then, you should upload the new version of your file (which should follow the naming conventions defined) by filling the field "OPTIONAL: Upload new file". PLEASE, DON'T CHANGE THE OTHER FIELDS. The field name convention should not be used to change the fields in the "Document Title" and the "Description" fields of the form. * I will delete those entries that I believe are out of date. Thanks and best regards, -- Juanjo 3. Some administrative/management details. We will keep the docman system as the way to share versions of the different contributions as well as consolidated releases of the final deliverable at least until June 22. I want to let you know that we already have SVN (Subversion) available in FusionForge, but I guess it doesn't make sense to migrate right now but keep going until we get this first deliverable finished. Later, we may migrate to SVN. We will keep sharing the contributions in the contribs folder linked to deliverable D.2.2 in the docman system under the FI-WARE project in FusionForge. However, I will today change the name of the entries in that folder to get something harmonized. From then on, I expect that all new releases of a given contrib will be uploaded under the assigned entry. This should be done by going to the Admin interface, then navigating to the entry in question and updating the file assigned to the entry. You should then assign a name to your contributed file which follows the following name convention: "FI-WARE High-level Desc v. valid until .doc" where: * is a name from the following list: * "Apps" (WP3) * "Cloud" (WP4) * "IoT" (WP5) * "Data" (WP6) * "I2ND" (WP7) * "Security" (WP8) * v. is the numbering of the version you assign to your contribution (e.g., v1.0 or v5.3) * is the date in which you have closed the edition of the file: (e.g., June 20, 2011 would be "11-06-20"). * is the date at which you plan to download the document again and you plan to start editing it again. If not specified, we will assume you expect to download a new release for editing "the next day (tomorrow) at 09:00am". (note: major and minor numbers are not reset when you change the date of a release. They should be absolute.) As an example, you may upload "FI-WARE High-level Desc Cloud v3.2 11-06-18 valid until 11-06-20.doc" That file would mean that it is v3.2 of your chapter, released on June 18, 2011. It will also mean that you don't plan to resume editing of it until June 20, 2011. As explained in a previous mail, you should upload new releases of the document (if you have some) no later than 19:00 and, PLEASE, if you have introduced some change in the document, no matter how minor they are, you should update the document in the server at 19:00 and do not touch it until 09:00am the following day. Besides, you should always download the version that is on the server whenever you plan to start editing your chapter. Please declare a if you rather don't plan to edit the document the day after. This would allow Thomas and me to have more time to review it, not just during nights :-) ________________________________ 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: image/png Size: 74761 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 23 09:04:32 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 23 Jun 2011 09:04:32 +0200 Subject: [Fiware-wpl] IMPORTANT - Start of integration of FI-WARE High-level Description deliverable: next steps Message-ID: <4E02E580.7030401@tid.es> Hi all, I believe that all the Architecture Chapter teams have uploaded their contribution to the docman system. Thanks for your commitment and effort !! Now, I will start to integrate the different chapters into a single document and perform and overall review all the chapters while making the integration. My plan is to finish this process by monday June 27, EOB. What can teams do in the meantime ? My suggestion is that you work in the "Question Marks" section and give also a final review to the "terms and definitions" section if you had generated it in the last minute (I know it is the case for some teams :-) These two sections can be easily replaced in the integrated document. Regarding the "Question Marks" section, I would suggest to structure it into a subsection titled "Security aspects" and a subsection titled "Other topics still under discussion". * On "Security aspects": I suggest that you nominate one-two people in your team that work with the WP8 team to analyze contents of your chapter and identify Security questions. Please contact Pascal Bisson (pascal.bisson at thalesgroup.com), leader of WP8, to coordinate with him how to carry out this task. It is about identifying at least 3-5 issues, and describing each with one-two paragraphs. You can download the contribution linked to the Data/Context Management chapter and check the "Security aspects" subsection where you may find some reference examples (particularly the one on Privacy Management) * On "Other topics still under discussion": The idea is just formulate 3-5 topics for which discussion has not yet been finalized within the team. Try to elaborate on the different alternatives you are considering/discussing with respect to the topic as well as any consideration that is relevant. Each topic should be described similarly to how topics in the "Security aspects" subsection were described in the Data/Context Management chapter (again, the description of the Privacy Management issue is a good reference example). It is up to the WPL how to organize this task. Regarding the "terms and definitions" section, there isn't anything special to remark. But try to provide precise definitions. Also try to make this section something that can "work" relatively standalone. I expect your contributions to both sections by Tuesday June 29, 19:00 CET. IN ADDITION: I know that some of you still wish to work on the content of sections linked to the overview and description of GEs. How can you work in parallel to integration ? I would suggest the following: * In the placeholder under the contrib folder linked to your document you will always be able to find the last version of your chapter already integrated in the final document. * Whenever I start to work with a given chapter, I will change its status to "pending" (this is one of the valid status -like "private"- you can assign to a document in the form linked to an entry in the Admin section of the docman system). This will mean I have blocked it. You will detect that your contribution is pending because you wouldn't be able to see it in the folders/document tree that is displayed when you click on "View Documentation". You should then wait until I upload a new version (already integrated in the master document). Of course, you may still be working on some changes but then you should implement them individually over the file that I will finally upload to the docman system (that file may have comments or even changes and, for sure, some fixes in formatting I don't want to loose, so it won't be as simple as replace the file with the one you were working on in parallel to me). Whenever I upload a new version of the file, I will change its status to "private" and you will be able to see it in the folders/document tree. * If a document is not "pending", this mean that you can download it and work on it. But, PLEASE, whenever you plan to do so, please mark it also as "pending" before downloading, so that I can realize you will download it and start working on it. You only have the right to keep a document "pending" from 09:00am to 19:00pm. After 19:00 and until 09:00am the next day, I can change its status and replace the attached file without notice. In the event I need that you release the document -changing its state to "private" again- before 19:00, I'll let you know. * PLEASE, DON'T CREATE NEW ENTRIES: It should work with the already existing ones, changing the status and replacing the attached file when needed. I know that we would probably do it better using SVN but SVN got installed recently and many people don't have the time to get used to it. Despite it took some time, all WPLs already know how to manage the docman, so we should keep using docman for this release of the deliverable. For a number of reasons, I won't be able to start integration until 19:00 today (it's holiday in Spain) so you will find that all the contributions to each chapter are marked as "private", therefore, not blocked. Let's work hard to finish the document !! Best regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Fri Jun 24 10:40:26 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 24 Jun 2011 10:40:26 +0200 Subject: [Fiware-wpl] Clarification on Question Marks section Message-ID: <4E044D7A.6050904@tid.es> Dear all, In response to comments from some of the WPLs, I just want to comment that the "Question Marks" sections is not about describing the dependencies with other WPs. It's about declaring points that are still under discussion and therefore subject to change or refine. Of course, it may happen that some of those topics still under discussion may happen to be in relationship with areas of interdependencies with other WPs. You indeed may use "check for interdependencies with other WPs" as an "heuristic" to find out some topics you want to claim that are still under discussion or, simply, yet not addressed. But the section should not be targeted to describe interdependencies with other WPs. Besides, please check the style/extension of Security-related topics that I provided as an example in the Data-Context Management chapter. We shouldn't go for a long description or elaboration of topics, just a formulation of them. 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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Fri Jun 24 13:08:28 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 24 Jun 2011 13:08:28 +0200 Subject: [Fiware-wpl] FI-WARE - Security aspects in each Chaper Message-ID: <19296_1308913799_4E047087_19296_1485_1_f5cffd0d-a7af-47ea-9b1d-bf30f0b2886f@THSONEA01HUB05P.one.grp> Dear Colleagues and WP leads, I'm contacting you following the email which was sent to you by Juanjo on the topic (23/06/2011 09:05am) >From our WP8 side we were requested to start reviewing the input document of each other AT chapter to identify security issues. Being said (as announced at KO meeting in Madrid) we appointed people at the level of our team to monitor activities of other teams for what concerns Security we started to do so. Starting first by identifying Security issues from WP6 input document to D2.1a. This led Juanjo as WP6L to use our WP8 input to produce a first draft of the section about "Security aspects" in the "Question Marks" section of the Context/Data Management chapter. Being said we will from our side continue on WP6 and engage the work on other Technical WPs I would appreciate if WP3, WP4, WP5, WP7 and WP9 Leads (so each of you) could let me know the (one-two) people they appointed to be counterparts of the people I appointed from my WP8 side on the topic. This in order to engage the discussion once identified security issues at the level of your WP in order to come up with agreement on final text to propose /insert. Hearing from each of you on your "nominees" for these joint task forces on security issues. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 27 10:19:39 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Jun 2011 10:19:39 +0200 Subject: [Fiware-wpl] IMPORTANT REMINDER - Security Aspects In-Reply-To: <4E02E580.7030401@tid.es> References: <4E02E580.7030401@tid.es> Message-ID: <4E083D1B.8020103@tid.es> On 23/06/11 09:04, Juanjo Hierro wrote: Regarding the "Question Marks" section, I would suggest to structure it into a subsection titled "Security aspects" and a subsection titled "Other topics still under discussion". * On "Security aspects": I suggest that you nominate one-two people in your team that work with the WP8 team to analyze contents of your chapter and identify Security questions. Please contact Pascal Bisson (pascal.bisson at thalesgroup.com), leader of WP8, to coordinate with him how to carry out this task. It is about identifying at least 3-5 issues, and describing each with one-two paragraphs. You can download the contribution linked to the Data/Context Management chapter and check the "Security aspects" subsection where you may find some reference examples (particularly the one on Privacy Management) So far Leaders of WP3, WP4, WP5, WP6 and WP7 haven't yet received sent to Pascal the names of the (1-2) people appointed to discuss things with the Security team. This would be important to enter the necessary discussion with them and, therefore, be able to finalize the contents of the "Security aspects" subsection. I would suggest to provide these names today and contact Pascal as how to organize the work to be done. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Mon Jun 27 14:39:50 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Mon, 27 Jun 2011 14:39:50 +0200 Subject: [Fiware-wpl] FI-WARE - Security aspects in each Chaper In-Reply-To: <19296_1308913799_4E047087_19296_1485_1_f5cffd0d-a7af-47ea-9b1d-bf30f0b2886f@THSONEA01HUB05P.one.grp> References: <19296_1308913799_4E047087_19296_1485_1_f5cffd0d-a7af-47ea-9b1d-bf30f0b2886f@THSONEA01HUB05P.one.grp> Message-ID: Hi Pascal As the Security appointed person for IoT is Xavier from orange, I will interact with him directly. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : vendredi 24 juin 2011 13:08 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Robert Seidl; Corinne.SIEUX at fr.thalesgroup.com; Slim TRABELSI; LELEU Philippe; Michael Osborne; GIDOIN Daniel Objet : [Fiware-wpl] FI-WARE - Security aspects in each Chaper Dear Colleagues and WP leads, I'm contacting you following the email which was sent to you by Juanjo on the topic (23/06/2011 09:05am) >From our WP8 side we were requested to start reviewing the input document of each other AT chapter to identify security issues. Being said (as announced at KO meeting in Madrid) we appointed people at the level of our team to monitor activities of other teams for what concerns Security we started to do so. Starting first by identifying Security issues from WP6 input document to D2.1a. This led Juanjo as WP6L to use our WP8 input to produce a first draft of the section about "Security aspects" in the "Question Marks" section of the Context/Data Management chapter. Being said we will from our side continue on WP6 and engage the work on other Technical WPs I would appreciate if WP3, WP4, WP5, WP7 and WP9 Leads (so each of you) could let me know the (one-two) people they appointed to be counterparts of the people I appointed from my WP8 side on the topic. This in order to engage the discussion once identified security issues at the level of your WP in order to come up with agreement on final text to propose /insert. Hearing from each of you on your "nominees" for these joint task forces on security issues. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Jun 27 15:10:23 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 27 Jun 2011 15:10:23 +0200 Subject: [Fiware-wpl] FI-WARE - Security aspects in each Chaper In-Reply-To: References: <19296_1308913799_4E047087_19296_1485_1_f5cffd0d-a7af-47ea-9b1d-bf30f0b2886f@THSONEA01HUB05P.one.grp> Message-ID: <14234_1309180305_4E088191_14234_8272_4_62c21584-83ba-4827-9d0f-0e2ff2118f91@THSONEA01HUB01P.one.grp> Fine with me Thierry and thanks for the notice. Regards, Pascal De : thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Envoy? : lundi 27 juin 2011 14:40 ? : BISSON Pascal; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : robert.seidl at nsn.com; SIEUX Corinne; slim.trabelsi at sap.com; LELEU Philippe; osb at zurich.ibm.com; GIDOIN Daniel Objet : RE: [Fiware-wpl] FI-WARE - Security aspects in each Chaper Hi Pascal As the Security appointed person for IoT is Xavier from orange, I will interact with him directly. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : vendredi 24 juin 2011 13:08 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Robert Seidl; Corinne.SIEUX at fr.thalesgroup.com; Slim TRABELSI; LELEU Philippe; Michael Osborne; GIDOIN Daniel Objet : [Fiware-wpl] FI-WARE - Security aspects in each Chaper Dear Colleagues and WP leads, I'm contacting you following the email which was sent to you by Juanjo on the topic (23/06/2011 09:05am) >From our WP8 side we were requested to start reviewing the input document of each other AT chapter to identify security issues. Being said (as announced at KO meeting in Madrid) we appointed people at the level of our team to monitor activities of other teams for what concerns Security we started to do so. Starting first by identifying Security issues from WP6 input document to D2.1a. This led Juanjo as WP6L to use our WP8 input to produce a first draft of the section about "Security aspects" in the "Question Marks" section of the Context/Data Management chapter. Being said we will from our side continue on WP6 and engage the work on other Technical WPs I would appreciate if WP3, WP4, WP5, WP7 and WP9 Leads (so each of you) could let me know the (one-two) people they appointed to be counterparts of the people I appointed from my WP8 side on the topic. This in order to engage the discussion once identified security issues at the level of your WP in order to come up with agreement on final text to propose /insert. Hearing from each of you on your "nominees" for these joint task forces on security issues. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 28 07:13:01 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Jun 2011 07:13:01 +0200 Subject: [Fiware-wpl] Fwd: Status of FI-WARE High-level Description deliverable due in month 2 Message-ID: <4E0962DD.5040501@tid.es> FYI, -- Juanjo -------- Original Message -------- Subject: Status of FI-WARE High-level Description deliverable due in month 2 Date: Tue, 28 Jun 2011 07:11:31 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Annalisa.Bogliolo at ec.europa.eu CC: Jose Jimenez , "jhierro >> \"Juan J. Hierro\"" Dear Arian and Annalisa, As you already know, the FI-WARE project has a first deliverable (FI-WARE High-level Description) due in month 2, that is June 30 2011. As you can imagine, we are working hard to get this deliverable finalized and a lot of stuff has been produced already. These two first months have indeed very intensive and productive trying to distill the product vision for each and every FI-WARE Architecture Chapter. Unfortunately, we have recently started the integration of the different chapters (one per Architecture chapter of FI-WARE) and the peer review of each chapter contents. Therefore, we are afraid that we will have to delay the official release of the FI-WARE High-level Description deliverable to mid July. To avoid any impact on progress of the program, we plan to deliver an integrated close-to-stable draft (early release) to the UC projects and the EC by July 4th. Such draft should already have all the necessary content (we are going to produce probably more than 200 pages) as to start the interaction process with the UC projects in order to collect their requirements. We will mostly devote the period between that date and the official release of the deliverable to polish the official version of the deliverable so there will not be so much changes in terms of contents between the early and final releases of the deliverable. During July, we plan to populate several places of the website based on the contents of the FI-WARE High-level Description deliverable. This delay has already been announced to members of the FI-PPP Architecture Board so they are prepared to receive this draft instead of the official release. On July 11-12 we have planned a face2face meeting of the FI-PPP AB in Madrid where a detailed presentation of the FI-WARE High-level Description will be given. At that date we also expect to close an agreement with UC projects on the format of entries to the FI-PPP AB backlog (part of which will be the FI-WARE features backlog). Find enclosed the minutes of our last FI-PPP AB virtual meeting that took place on June 16th. Don't hesitate to contact us if you have any further question. Best regards, Juanjo Hierro P.S.: Please let me know if I have to send this message to any formal mailbox of the EC. ________________________________ 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-PPP-AB-Meeting-Minutes 11-06-16 v1.0.doc Type: application/msword Size: 591360 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 30 01:36:50 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 Jun 2011 01:36:50 +0200 Subject: [Fiware-wpl] Presentation of FI-WARE High-level Description at FI-PPP Architecture Board meeting in Madrid on July 11-12 Message-ID: <4E0BB712.1040107@tid.es> Hi all, As you already know, since I forwarded to you the minutes of the last FI-PPP Architecture Board meeting, we plan to present the first deliverable of the FI-WARE High-level Description deliverable during the next FI-WARE Architecture Board (AB) meeting that will take place in Madrid, July 11-12. The meeting will start at 13:00 CET on July 11. Despite the number of representatives of each FI-PPP project present at the meeting is limited to two, other attendees might be invited when a topic in the agenda justifies their presence. In this case, I would like to tell you that if any of you wish to attend and present the results of the WP he leads, you are more than welcome to attend and do so. I believe that I can manage explaining all chapters (probably the I2ND and Security chapters may be the ones that I may feel less comfortable with because I have less expertise but could still manage presenting them) but maybe you want to take the opportunity to present the results of the work of your team. Of course, I perfectly understand that making a trip just for this may be too much, so don't feel pressured at all. In the event you wish to attend, please let me know asap. The agenda of the meeting as well as logistic info is provided in the emails attached below. As you see, the presentation of FI-WARE will take place the first day. Best regards, -- Juanjo -------- Original Message -------- Subject: Fwd: AB agenda Date: Tue, 28 Jun 2011 07:38:46 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu Dear colleagues, Please find enclosed below the scheduled agenda for the second face2face meeting of the FI-PPP Architecture Board, to take place in Madrid on July 11-12. If you have any comment, please don't hesitate to comment. Note that we plan, as already announced in our last virtual meeting, to deliver a draft version of the FI-WARE High-level Description by end of June (although we may have a little bit of delay on this and indeed deliver it by July 4th after the weekend). Point 5 of the agenda is booked for you to provide a first impression/feedback on this description. Best regards, -- Juanjo Madrid AB agenda DAY 1 starting at 13.00 1. Welcome and opening - Juanjo (13:00 - 13:15) 2. FI-WARE High-level Description (HLD) presentation Part I - Juanjo (13:15 - 14:00) coffe break (14:00 - 14:30) 4. FI-WARE High-level Description (HLD) presentation Part II - Juanjo (14:30 - 15:15) 5. Each project's comments on FIWARE HLD - 15 mins each, 15 mins break in between (15:15 - 17:30) - ENVIROFI - Denis H - FI-CONTENT - Denis M - FINEST - Andreas - FINSENY - Kolja - Instant Mobility - Thierry - OUTSMART - Benoit - SAFECITY - Roberto - SmartAgriFood - Adrie/Bosco/Nicolas 6. Review on the Common Glossary including definition of GE and SCE - Juanjo (17:30 - 18:00) DAY 2 starting at 9.00 5. Definition of the FI-PPP AB backlog (09:00 - 11:00) - definition of fields for entries in the FI-PPP AB backlog - definition of process to create entries and manage changes in the FI-PPP AB backlog Coffee break 6. Collaborative tools (11:00 - 13:00) - Repositories - work vs. dissemination - Agile possibilities - concrete AgileFant demonstration and discussion (tbc) - Access rights to the portal Lunch 7. UC and FI-WARE project interactions during next 3 months for capturing input to the FI-PPP AB backlog (14:00 - 15:00) 8. Other businesses (15:00 - 17:00) - Invitation rules of external experts to AB meetings - Agenda for the virtual meeting in August - Contribution to the proposal timetable for AB meetings in 2012 - Conflict resolution framework - Standardisation Working Group 9. AOB and closure at 17.00 -------- Original Message -------- Subject: Venue of the face2face FI-PPP AB meeting in Madrid Date: Mon, 27 Jun 2011 20:44:42 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu Hi all, Just to mention that our face2face FI-PPP AB meeting will take place in Madrid at the "Telefonica City" also named as "Distrito C". A link on google maps would help you to find where it is placed: http://maps.google.es/maps?q=distrito+C,+ronda+de+la+comunicaci%C3%B3n,+Madrid&hl=es&ie=UTF8&ll=40.517241,-3.661838&spn=0.009918,0.022724&sll=40.597271,-3.713379&sspn=9.722366,23.269043&z=16 Note that it is not located near to downtown but relatively close to the Airport. Note also that THIS IS NOT the place at which Telefonica I+D facilities where traditionally located. We moved to Distrito C almost one year ago. There is no particular recomendation I believe I can make regarding hotel accommodation. You may go for finding a hotel close to Telefonica buildings but then you would be relatively far from downtown. On the other hand, you may go for finding a hotel close to downtown (e.g., close to C/ Gran V?a) but then you should plan going to Telefonica ahead of time the morning of July 12 in order to avoid arriving late, overall if you plan to take a taxi. There is a metro station adjacent to Telefonica Buildings (Ronda de la Comunicacion station, line 10). I attached a Metro Map for your convenience. Any hotel close to this metro line at downtown could be a good choice. Hope it helps. Don't hesitate to ask if you have any doubt, -- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: MadridMetroMap.pdf Type: application/pdf Size: 3179145 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From matteo.melideo at eng.it Thu Jun 30 11:55:10 2011 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 30 Jun 2011 11:55:10 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Minutes of the second meeting of the FI-PPP Architecture Board In-Reply-To: <4DFF2C56.1070505@tid.es> References: <4DFF2C56.1070505@tid.es> Message-ID: <4E0C47FE.1080608@eng.it> Dear Juanjo, for Engineering Davide Dalle Carbonare will attend this meeting as representative of the Wp9. Please, keep him informed on all the details about this meeting. Thanks a lot and regards, Matteo On 20/06/2011 13:17, Juanjo Hierro wrote: > Dear all, > > Please find enclosed the minutes of the second meeting of the FI-PPP > Architecture Board that took place on June 16th. > > Next meeting of the FI-PPP AB will be f2f in Madrid on July 11-12. > > As you would see in the minutes, I already announced that the > official release of the FI-WARE High-level Description deliverable will > be delayed to mid July (indeed to be presented to members of the AB in > our f2f meeting in July). However, we committed to share with them a > draft by end of June. This draft is intended to be stable and with all > target contents ready (the two first weeks of July would be devoted to > final review after official release). This would help UC projects to > start reading the FI-WARE High-level Description in order to understand > what we plan to deliver. > > Please push work in your respective WPs to make it happen. > > Best regards, > > -- Juanjo > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-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: