From lorant.farkas at nsn.com Mon Jul 2 11:07:22 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 2 Jul 2012 12:07:22 +0300 Subject: [Fiware-iot] FI-WARE look&feel Message-ID: <93D28BDF64839C468B848D14227151A203A9AF18@FIESEXC014.nsn-intra.net> Dear All, FYI, please take a look and comment. My understanding is that we need to utilize this when we publicize our GE-s (features, downloadable from etc). Thanks & Br, Lorant The UPM has produced a first set of guidelines for FI-WARE webs and portals: https://forge.fi-ware.eu/docman/view.php/27/1125/Look%26Feel.zip Teams to try adapting to this as much as possible for the Testbed by end of July. FI-WARE Webs and Portals should definitively align by the upgrade of the FI-WARE Testbed planned by end of September. AP on WPLs to start sharing this with their teams for consideration. Again, no strong requirement to follow the guidelines for the FI-WARE Testbed available by end of July but for the upgrade of it by end of September. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Jul 2 15:23:30 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 2 Jul 2012 16:23:30 +0300 Subject: [Fiware-iot] educational material of the IoT section in the wiki Message-ID: <93D28BDF64839C468B848D14227151A203AE0082@FIESEXC014.nsn-intra.net> Dear All, I tried to make some order in the wiki collecting material of the educational sessions. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-PPP_ Software_Architects_Week_Presentations_and_References#FI-WARE_IoT.2BDATA But as I was not there myself, so could you please help me out with the following? Thierry & Laurent: there were 2 versions of the IoT Gateway Data Handling GE, I used Thierry's because the other one had outdated architecture figures, OK? Should we use both? Then please make changes or let me know. Jan & Jakob: there were 2 versions of the Gateway Device Management GE, I used the one from Fusion Forge, should we use both? Then please make changes or let me know. Tarek & Payam: there were 2 versions of the UoS presentation, a shorter one and a longer one, I took the shorter one which was in the Forge, if these two are different and you would like to make them both available, please put it there, or let me know. Tobias & Salvatore: I renamed your stuff's title in wiki, please let me know if these new titles are OK & whether I missed some material, or are these the only ones All: there was a bullet point "Demos", was there anything like this in the IoT chapter? Please let me know. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 3 08:09:37 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 3 Jul 2012 09:09:37 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203AE022C@FIESEXC014.nsn-intra.net> When: Occurs every szerda effective 2011.09.28. until 2014.03.26. from 10:00 to 11:30 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: telco/webex (phone number: in the pdf, conference code: 38665541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 67286 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From lorant.farkas at nsn.com Tue Jul 3 08:10:36 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 3 Jul 2012 09:10:36 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203AE022E@FIESEXC014.nsn-intra.net> When: Occurs every szerda effective 2011.09.28. until 2014.03.26. from 10:00 to 11:30 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 67259 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From lorant.farkas at nsn.com Tue Jul 3 10:04:46 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 3 Jul 2012 11:04:46 +0300 Subject: [Fiware-iot] Gantt tool investigations Message-ID: <93D28BDF64839C468B848D14227151A203AE02F7@FIESEXC014.nsn-intra.net> Dear All, Wrt my action item IoT03_27.06.2012 I did a number of investigations and would like to come up with a proposal. The proposal is at the end of the e-mail, so if not interested you can skip the following parts until the 3. Proposal section. 1. Investigations on the existing toolset 1.1 Fusion Forge -Fusion forge has built-in task management, available in the "Tasks" -This would be very good if a graphic library php-jpgraph was installed, because then we could visualize tasks, dependencies, deadlines etc in a Gantt diagram -I issued a ticket to have this library installed (most probably takes no more than 5 minutes), this has never been solved. But since out of 21 tickets in the support tracker only 1 has been solved, and assuming tickets coming from the coordinator are prioritized higher, I don't expect this to be solved any time soon (even though I tried to convince the guy in charge ... in Spanish in a personalized e-mail :-)) 1.2 MediaWiki -The Mediawiki also has an extension called JSWikiGantt that - if installed - would give us the possibility to visualize Gantt charts -I requested also this as a second alternative, there was no action at all -Data for Gantt is taken either from Javascript (one puts the data in the code) or an XML file uploaded to the server -MediaWiki does not allow to upload XML files. So I would need to change the Javascript code every time we change the list of tasks (example: tasks stored in FusionForge -> export to CSV -> script to update Javascript code -> script to upload Javascript code to MediaWiki). This is cumbersome, but feasible, but still we face the problem the extension is (and will not be in the foreseeable future) installed 2. Possible solutions -Here I looked for alternatives that are hosted (I don't need to set up a web server in NSN), free (up to the number of members of the IoT work package, possibly unlimited number of projects - we might need more than one, in the number of handled tasks - because this might grow as complex as we want), interoperable with "well-known" Gantt tools (Microsoft Project and Fusion Forge CSV task exporter), has an output very Gantt-like (looks like a Microsoft Project, can insert dependencies, resources, deadlines, can set up notifications etc) -I looked at a number of tools, as listed below: -Tom's planner: free only for 1 project, cannot invite others -ACE: free for up to 50 tasks and up to 2 projects -OPProject: free, but needs hosting -ZOHO: not free, basically -Project2manage: does not look too good, website does not even display all graphical elements -Activecollab: needs hosting -Dotproject: needs hosting -Gantter: doesn't need hosting, unlimited usage, can export to MSProject, looks very Gantt-like, no direct interface to forge CSV exporter -Redmine: needs hosting -Asana: doesn't need hosting, unlimited hosting, doesn't look very Gantt-like, cannot export, no direct interface to forge CSV exporter 3. Proposal -I would propose to start experimenting with Gantter -The lack of interface to fusion forge is not a big problem, since we have not used too frequently the tasks feature of fusion forge -What this would mean in the beginning: -I will create a FI-WARE IoT project -I would invite all IoT members that I see from the mailing list/fusion forge -I would start transferring action items from the minutes to this project Please let me know if you have any comments/concerns etc. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Tue Jul 3 16:16:05 2012 From: stephan.haller at sap.com (Haller, Stephan) Date: Tue, 3 Jul 2012 16:16:05 +0200 Subject: [Fiware-iot] Template Handler GE Message-ID: <0D2446AEB6CAED48BB046223733964A54E394510E7@DEWDFECCR01.wdf.sap.corp> All, Here is the initial response for 2 of our action items from last week's call. I have added two pages to the (private) wiki describing architecture as well as how to materialize it, see: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/FIWARE.ArchitectureDescription.IoT.Backend.TemplateHandler * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Template_Handler_GE - first draft, but should and will be extended in the coming weeks There are a few open issues that need to be resolved before putting it on the public wiki. Talk to you tomorrow! Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Althardstrasse 80, CH-8105 Regensdorf, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 3 16:19:15 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 3 Jul 2012 17:19:15 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203AE0634@FIESEXC014.nsn-intra.net> When: 2012. j?lius 4. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's discuss tomorrow about the following topics: 1. Status on action items 2. Additions to the review meeting from Thierry 3. Update on the upcoming deliveries, who should do what 4. AoB As Thierry is out of office and D?nes is on holiday, I will be in 1 person the hoster and minutes taker. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 3731 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From Ernoe.Kovacs at neclab.eu Tue Jul 3 17:13:16 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Tue, 3 Jul 2012 15:13:16 +0000 Subject: [Fiware-iot] IoT weekly meeting [Standardisation Plan Update] Message-ID: <8152E2132B13FB488CFD1947E2DEF19C25142AA5@PALLENE.office.hd> Lorant, Thierry, all, I assume this would be under handled under topic 3 (Update on the upcoming deliveries, who should do what) but please be aware of the following: The deliverable 11.4a on the standardization plan was rejected and requested for full update in D11.4b (due End July). So there will be action items - on project level (TM; PCC, others to handle) - WP level (this is where you actions are needed and that is what we need to discuss to morrow - partner level (individual request and general updates) An action list was sent in May to WPL-list and PCC, but I fear it was never further discussed (mainly due to the May review) nor further distributed. /* Or am I wrong ??? */ Please have a slot tomorrow in which WP5 should discuss its standardization strategy and what needs to be done for the deliverable. Thanks for adding that to the agenda. - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Dienstag, 3. Juli 2012 16:19 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. j?lius 4. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's discuss tomorrow about the following topics: 1. Status on action items 2. Additions to the review meeting from Thierry 3. Update on the upcoming deliveries, who should do what 4. AoB As Thierry is out of office and D?nes is on holiday, I will be in 1 person the hoster and minutes taker. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jul 4 08:18:39 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 4 Jul 2012 09:18:39 +0300 Subject: [Fiware-iot] IoT weekly meeting [Standardisation Plan Update] In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C25142AA5@PALLENE.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C25142AA5@PALLENE.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A203AE0730@FIESEXC014.nsn-intra.net> Dear All, Of course, we can take this point. However in the WPA/WPL meetings between mid-May and 2 days ago this was not discussed. The last e-mail I received from Juan Bareno on the topic was 14th of May, I attach it hereby. So I hope you or Lindsay know more about this, otherwise this will be a short discussion with the only potential outcome that we will find out more/raise it in the next WPA/WPL call. Thanks & Br, Lorant From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Sent: Tuesday, July 03, 2012 5:13 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: Lindsay Frost Subject: RE: IoT weekly meeting [Standardisation Plan Update] Lorant, Thierry, all, I assume this would be under handled under topic 3 (Update on the upcoming deliveries, who should do what) but please be aware of the following: The deliverable 11.4a on the standardization plan was rejected and requested for full update in D11.4b (due End July). So there will be action items - on project level (TM; PCC, others to handle) - WP level (this is where you actions are needed and that is what we need to discuss to morrow - partner level (individual request and general updates) An action list was sent in May to WPL-list and PCC, but I fear it was never further discussed (mainly due to the May review) nor further distributed. /* Or am I wrong ??? */ Please have a slot tomorrow in which WP5 should discuss its standardization strategy and what needs to be done for the deliverable. Thanks for adding that to the agenda. - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Dienstag, 3. Juli 2012 16:19 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. j?lius 4. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's discuss tomorrow about the following topics: 1. Status on action items 2. Additions to the review meeting from Thierry 3. Update on the upcoming deliveries, who should do what 4. AoB As Thierry is out of office and D?nes is on holiday, I will be in 1 person the hoster and minutes taker. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: =?iso-8859-1?Q?ext_Juan_Bare=F1o_Guerenabarrena?= Subject: [Fiware-exploitation] FW: [Fiware-wpl] Draft shared minutes fortoday's joint WPL/WPAfollow-up confcall EXPLOITATION ACTIVITIES!! Date: Mon, 14 May 2012 18:56:05 +0300 Size: 191220 URL: From maarten.los at atosresearch.eu Wed Jul 4 12:33:53 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Wed, 4 Jul 2012 12:33:53 +0200 Subject: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting Message-ID: <461EDDC0FEB25648B2FE8B0145848AA5F40AB7@INTMAIL02.es.int.atosorigin.com> Dear partners, As discussed in today's IoT Weekly Meeting, we would like to call a telco to discuss the interfaces of the CEP Component (both that of Orange and of Atos) within the IoT Architecture (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.p hp/FiwareDeliverableD2.3IoT). Broadcasting this to the IoT list at large, just in case we miss anyone, but the main partners involved in the telco would be Orange, Ericsson and the WPA/WPL. We would kindly like to ask if you could state your availability by Friday COB on the following Doodle. Bridge details will be provided afterwards. http://www.doodle.com/rvcf843axt53pyru Here's a tentative agenda, please feel free to add anything you think is missing: Agenda - General interaction with Backend o Registering o NGSI9/NGSI10 interactions - General interaction within Gateway and/or other components, if any - Reception of Incoming events o Source(s) (currently understood to be Gateway Device Management GE - Data Handling API) o Data format + delivery method - Emission of Outgoing events o Destination(s) o Data format + delivery method Thanks and best regards, Maarten ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jul 4 15:13:09 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 4 Jul 2012 16:13:09 +0300 Subject: [Fiware-iot] IoT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A203AE0A7D@FIESEXC014.nsn-intra.net> Dear All, The meeting minutes are stored under https://forge.fi-ware.eu/docman/view.php/11/1150/IoT-Minutes-Telco-04072 012.docx I've been informed by one of the colleagues that you are spammed whenever I make any change in Gantter, he received already 8 notifications. I also lost some 2 hours of work because of not saving frequently. I propose that for the meantime I unshare the project and make some experiments how not to spam you/spam you only with topics where you are listed as task owners. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Jul 5 08:16:08 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 5 Jul 2012 09:16:08 +0300 Subject: [Fiware-iot] Gantter tool - will be abandoned for now Message-ID: <93D28BDF64839C468B848D14227151A203AE0C0A@FIESEXC014.nsn-intra.net> Dear All, Because of the notification issue which is a showstopper from the collaboration perspective I am cancelling this experiment for now. The problem is that all changes I make to the project are sent out to all resources when I click "save"; one can unsubscribe from receiving the notifications, but this means cancelling all notifications forever, and the unsubscription cannot be cancelled. They did not solve the problem in the last 3 months. It's a pity, because otherwise the tool looks really nice. So for the moment I will enter the todo-s in forge either as tasks or as work items as we did in the past (you will receive personalized notifications about them from forge) and hope that the support will sort out the graphical dependencies in order to have the nice Gantt with the timelines. Thanks & Br, Lorant _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Wednesday, July 04, 2012 3:13 PM To: fiware-iot at lists.fi-ware.eu Subject: IoT weekly minutes Dear All, The meeting minutes are stored under https://forge.fi-ware.eu/docman/view.php/11/1150/IoT-Minutes-Telco-04072 012.docx I've been informed by one of the colleagues that you are spammed whenever I make any change in Gantter, he received already 8 notifications. I also lost some 2 hours of work because of not saving frequently. I propose that for the meantime I unshare the project and make some experiments how not to spam you/spam you only with topics where you are listed as task owners. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianpiero.fici at telecomitalia.it Thu Jul 5 11:07:58 2012 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Thu, 5 Jul 2012 11:07:58 +0200 Subject: [Fiware-iot] ZigBee Gateway Device specification uploaded to Forge Message-ID: Hi all, I checked and the ZigBee specification "Network Device: Gateway Specification" is public (if you want you can also download it directly from the ZigBee portal http://www.zigbee.org/). This is the specification on which the TI asset is based (Protocol Adapter GE). I uploaded the last version of this specification to the DocManager area of the FI-WARE Iot project under the "Partner assets" section (direct link: https://forge.fi-ware.eu/docman/view.php/11/1155/115552r00ZB_BoD-ZigBee_Network_Device_-_ZigBee_Gateway_standard_version_1.pdf). I put also a copy of this specification under the "Standardization" section, in order to have all the reference standards in one place. Ciao, Gian Piero Fici Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From lorant.farkas at nsn.com Sat Jul 7 14:45:03 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Sat, 7 Jul 2012 15:45:03 +0300 Subject: [Fiware-iot] M15 deliverables Message-ID: <93D28BDF64839C468B848D14227151A2C531C4@FIESEXC014.nsn-intra.net> Dear All, As we need to deliver a large number of deliverables quite soon, we need to get better organized. The minimum we need to do now is 8 items, as you find below. I tried to schedule 2 items/week, so that we manage to finish everything by the last week of July/first week of August. I tried to schedule on high level what we produce and by when. Accordingly I tried to break down all this to personalized tasks, I did not manage to map yet everything, but it?s on its way. As a result you might have already received e-mails from the fusion forge ?Task? component, but there will be more created in the next days. I captured these in the ?tasks? and not in the tracker as ?work items?, because there was once a recommendation that deliverables are something that should not be captured as work items. I would like to get your opinion on the scheduling and I would like you to act when triggered by the tasks. Whenever you make progress on one of the tasks assigned to you, please record it in the respective task or just drop an e-mail to me. If you finish something before the deadlines proposed below, please do not hesitate to take the next item on your list, because these deadlines are already delayed with 1 month from the original planning. Thanks & Br, Lorant Partner contribution high level plan: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W30 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W31 From maarten.los at atosresearch.eu Mon Jul 9 09:17:45 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Mon, 9 Jul 2012 09:17:45 +0200 Subject: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting In-Reply-To: <461EDDC0FEB25648B2FE8B0145848AA5F40AB7@INTMAIL02.es.int.atosorigin.com> References: <461EDDC0FEB25648B2FE8B0145848AA5F40AB7@INTMAIL02.es.int.atosorigin.com> Message-ID: <461EDDC0FEB25648B2FE8B0145848AA5F97393@INTMAIL02.es.int.atosorigin.com> Dear partners, As per the Doodle results, I would like to fix the meeting for Monday July 16, 1300h Madrid time. Bridge details will follow. Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Maarten Los Sent: mi?rcoles, 04 de julio de 2012 12:34 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting Dear partners, As discussed in today's IoT Weekly Meeting, we would like to call a telco to discuss the interfaces of the CEP Component (both that of Orange and of Atos) within the IoT Architecture (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3IoT). Broadcasting this to the IoT list at large, just in case we miss anyone, but the main partners involved in the telco would be Orange, Ericsson and the WPA/WPL. We would kindly like to ask if you could state your availability by Friday COB on the following Doodle. Bridge details will be provided afterwards. http://www.doodle.com/rvcf843axt53pyru Here's a tentative agenda, please feel free to add anything you think is missing: Agenda - General interaction with Backend o Registering o NGSI9/NGSI10 interactions - General interaction within Gateway and/or other components, if any - Reception of Incoming events o Source(s) (currently understood to be Gateway Device Management GE - Data Handling API) o Data format + delivery method - Emission of Outgoing events o Destination(s) o Data format + delivery method Thanks and best regards, Maarten ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Tue Jul 10 13:13:27 2012 From: stephan.haller at sap.com (Haller, Stephan) Date: Tue, 10 Jul 2012 13:13:27 +0200 Subject: [Fiware-iot] Template Handler: Southbound interface(s) Message-ID: <0D2446AEB6CAED48BB046223733964A54E397E9047@DEWDFECCR01.wdf.sap.corp> All, As one of the action items from last call, I have consolidated the functionality needed for this interface, see: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/FIWARE.ArchitectureDescription.IoT.Backend.TemplateHandler#Resolution_of_Open_Issues_.28work_in_progress.29 I am afraid the Things Management GE as it stands (i.e., the functionality provided via NGSI-9/10) cannot fully cover this. So we would need to extend it or find some other GE within FI-WARE that has this functionality. Does anyone have an idea what that could be? Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Althardstrasse 80, CH-8105 Regensdorf, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Tue Jul 10 14:03:33 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 10 Jul 2012 14:03:33 +0200 Subject: [Fiware-iot] IoT Weekly Meeting Message-ID: <3F4C11BC54A36642BFB5875D599F47BD061EF30D@DEMUEXC013.nsn-intra.net> Dear All, The meeting starts as usual at 10:00am but the NSN conferencing service is changed, please check the details at the end of this mail. Agenda for this week: 1. Status update of partners on the following deliverables: - WP2 deliverables where we need to contribute: o D2.3 Architecture specifications end of W30 o D2.4 Technical roadmap end of W31 - WP5 deliverables (fully ours): o D5.1 Open Specifications end of W28 o D5.2 Software release end of W29 o D5.3 Installation and Administration guide end of W28 o D5.4 Users and Programmers guide end of W29 o D5.5 Unit Testing Plan & Report end of W30 - WP11 deliverables where we need to contribute: o D11.4 Standardization plan and Report end of W31 2. Discussion on Template Handler GE IMPORTANT: Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=M TgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT= MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 87082 bytes Desc: Local_access_numbers.pdf URL: From thierry.nagellen at orange.com Tue Jul 10 16:11:28 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 10 Jul 2012 14:11:28 +0000 Subject: [Fiware-iot] Commitment for the next deadlines Message-ID: <2038_1341929499_4FFC381B_2038_371_1_976A65C5A08ADF49B9A8523F7F81925C01F573@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As you know we are late providing deliverables due for M12 and some previous deliverables expected at M9 were rejected. Based on the review discussion and previous emails with our Project Officer we must provide deliverable for end of July. Telefonica, as project coordinator, will be able to reject some costs that partners will claim if partners' contributions are not at the expected level. For the deliverables we have to achieve, they are dedicated to the work we achieved regarding Generic Enablers and existing assets. So, if some part are missing , I could easily check, as WP Leader, who has not fulfilled his commitment and I must provide this picture to Telefonica. We need a strong commitment from everybody to achieve this part of the work including a strong revision of the Technical Roadmap to explain what the next steps are. Of course for global deliverables (WP2 and WP11), I will manage this issue with the support of Lorant and Denes but each of you has to provide in the next 10 days his own part of WP5 deliverables. (Check the list at the end of this email) If some contributions are missing, especially for the Technical Roadmap, as it was the case for the previous version, we (WP Leader and WP Architect) are going to provide the content which will be the rules for the next releases (minor and major). In fact, nobody will be able to claim that he has no information and no commitment to develop some features for the next releases. To avoid any trouble for the next steps, provide your vision following what we have discussed till now and what we have described in the DoW. Our main objective is to deliver the right versions of middleware to support the IoT architecture and to be able to show the first demos after M18 (July is M15). We have now a critical path and we expect your commitment to deliver what we promised to the FI PPP community and of course to the Commission. Thanks for your support. BR Thierry List of deliverables for July, 23rd WP5 deliverables (everybody and more specifically GE's owners): D5.1 Open Specifications D5.2 Software release D5.3 Installation and Administration guide D5.4 Users and Programmers guide D5.5 Unit Testing Plan & Report WP2 deliverables where we need to contribute: (leaders: Thierry, Lorant, Denes) D2.3 Architecture specifications D2.4 Technical roadmap WP11 deliverables where we need to contribute: (leader: Thierry with contributions of other partners) D11.4 Standardization plan and Report _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Jul 11 09:57:27 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 11 Jul 2012 09:57:27 +0200 Subject: [Fiware-iot] IoT Weekly Webex Message-ID: <3F4C11BC54A36642BFB5875D599F47BD061EF5CC@DEMUEXC013.nsn-intra.net> Please use the following webex link for today's meeting: ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/e.php?AT=MI&EventID=217167612&UID=0&PW=NMGMzOW MzYTJh&RT=MiMyNQ%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: cool 4. Click "Join Now". 5. Follow the instructions that appear on your screen. -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Jul 11 10:03:09 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 11 Jul 2012 10:03:09 +0200 Subject: [Fiware-iot] IoT Weekly Conference Call Message-ID: <3F4C11BC54A36642BFB5875D599F47BD061EF5E1@DEMUEXC013.nsn-intra.net> Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: Enter the conference code: 3865541959# -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 87082 bytes Desc: Local_access_numbers.pdf URL: From denes.bisztray at nsn.com Wed Jul 11 12:50:03 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 11 Jul 2012 12:50:03 +0200 Subject: [Fiware-iot] FW: [Fiware-wpa] Instructions to give the deliverables Message-ID: <3F4C11BC54A36642BFB5875D599F47BD061EF732@DEMUEXC013.nsn-intra.net> FYI, Here is the mail that gives link to the Private Wiki and contains the instructions on the deliverables as well. Best, D?nes From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Miguel Carrillo Sent: Tuesday, July 03, 2012 1:05 PM To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Instructions to give the deliverables Dear all, I apologise for the long email but I prefer to put all the info in one single message and provide detailed instructions. After discussing things in the weekly confcall with the WPLs and the WPAs we saw the need to reorganize the delivery of our commitments with the EC. We apologize again for all the trouble. It is the first release, the next one will be smoother as we all will know how to do things. Please note that the common reference is still valid: * [REF 1] - https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables We have 5 basic blocks that will be explained separately. To make clear that we share the same interpretation of the terms I will first clarify this: * Public = open to the whole world * Private = open to the PPP (Use Case Projects, EC ...) but not to the outside world BLOCK 1 - Source code ====================================================== Publicly available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE" Privately available - do not bother to deliver, it is not mandatory in this case. If some one for whatever reason wants to deliver it anyway keeping it private, he can use the SVN of his chapter (FI-WARE Data, FI-WARE IoT ,etc.) , it will be fully private. Please follow this naming convention and structure on SVN: * A directory called FI-WARE will be the first level * The second level will be named after the chapter. Take the same names as used in the Features names under "Materializing...". To be more precise use these: "Apps", "Cloud", "IoT", "Data","I2ND" and "Security". * The third level will be named after the GE, using the same name as in "Materializing...". For instance, in the following example the GE must be called "PublishSubscribe" * In the 4th level you upload the different releases of your software. In summary, something like this: BLOCK 2 - Binaries, packages, configuration ====================================================== After discussing this with a few people, we will do it on SVN now (it appears as "SCM" in the forge) - the "Files" part of the forge will no longer be used. Here is a big change, actually. Two cases: * Publicly available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE" * Privately available - upload it to the SVN (it appears as "SCM" in the forge) of the project "FI-WARE PPP Restricted" In this case there is one more naming rule. The files (binaries, packages, properties), whatever their original name is, must be appended with a string that identifies the release. For instance, the file: * openstack-tcloud would turn into * openstack-tcloud-1.1.19-SNAPSHOT (major release 1, minor release1, version 19) - the version is internal to each company, what you put here is your business!. The "SNAPSHOT" string is compulsory. All the files here will be tagged with "Release_1_1" BLOCK 3 - Installation and administration guide ====================================================== * If the GE is Public - to be edited on [REF1] and then moved to the public wiki, following the instructions in [REF 1] * If the GE is Private (accessible to PPP members only) - to be edited on [REF1] and then moved to the wiki of the project "FI-WARE PPP Restricted" BLOCK 4 - User and programmer's guide ====================================================== This is fully public and will be edited on the private wiki on the link on [REF 1]. Then, once matured, it will be ported to the public wiki BLOCK 5 - Unit Testing Plan and Report ====================================================== Two parts: * Unit Testing Plan is public and it will be created as explained in [REF 1] * The report will be will be a private document only accessible to the PPP members and the CE. It will be created by filling in a template that I will provide to the WPLs/WPAs. I have added a template, an example and instructions in the private wiki. Those with no access to the project FI-WARE or the project FI-WARE PPP Restricted can apply following the procedure explained in this tutorial: * https://wiki.fi-ware.eu/How_to_join_a_FI-WARE_project_in_FusionForge Ask your WPLs/WPAs to approve your request. They have the permissions to do it. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: abeebffj.png Type: image/png Size: 14179 bytes Desc: abeebffj.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT1779287.png Type: image/png Size: 6226 bytes Desc: ATT1779287.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ffhgfhjj.png Type: image/png Size: 6198 bytes Desc: ffhgfhjj.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT1779288.txt URL: From denes.bisztray at nsn.com Wed Jul 11 13:28:46 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 11 Jul 2012 13:28:46 +0200 Subject: [Fiware-iot] Meeting Minutes Message-ID: <3F4C11BC54A36642BFB5875D599F47BD061EF788@DEMUEXC013.nsn-intra.net> Dear All, The minutes from the weekly call is under the following link: https://forge.fi-ware.eu/docman/view.php/11/1169/IoT-Minutes-Telco-11062012.docx Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jul 11 14:06:22 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 11 Jul 2012 15:06:22 +0300 Subject: [Fiware-iot] list of actions for the partners Message-ID: <93D28BDF64839C468B848D14227151A203B2186F@FIESEXC014.nsn-intra.net> Dear All, Sorry for missing our weekly call. Let's stay pragmatic and try to plan our activities according to my originally proposed planning, despite what has been discussed in the weekly call or disclosed in earlier e-mails. Partner contribution high level plan: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W30 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W31 -For the W28 and W29 deliverables I already captured every needed action partner by partner/person by person, it should already be in your inboxes. Tasks incorporate detailed information on what you should do and how. If something is not clear, please ask. -For the W30 and W31 activities I still need to create the tasks in forge, you will receive notifications about them. -If you need to delegate tasks (example: Tobias delegates something to Salvatore), please do it within the Fusion Forge task assigned to you, or let me know by e-mail. -If your task progresses in some way, please write an e-mail or make a comment in the task I assigned to you. We will in parallel monitor the outcomes and make comments if we see progress, but it would be nice if you do his proactively. -Please also mark in the task the number of hours it took you/your colleagues to finalize it, -I put an early estimate when the task was created. It will help us to better plan in the future and to monitor/assess the amount of work you spent on the respective task. -If you finish something belonging to W28, please start working on tasks belonging to W29, and so on. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Jul 11 11:33:30 2012 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 11 Jul 2012 11:33:30 +0200 Subject: [Fiware-iot] Sayonara - and many thanks! Message-ID: <0D2446AEB6CAED48BB046223733964A54E39880627@DEWDFECCR01.wdf.sap.corp> Dear Colleagues, A long time has come to an end: After 15 years with SAP, 12 years of which with SAP Research, I am leaving the company and hence also the European research projects I am currently involved in. My last working day will be July 13. I hereby would like to thank all of you for the many positive interactions we had over the years, the interesting work experiences we enjoyed, and the many things I could learn in the process. Interesting times it was indeed! Introducing RFID technology to the company out of our labs in Tokyo, and seeing how that topic developed from simple prototypes and demos to actual products and customer solutions, was certainly one of the highlights. But also the research work on sensor networks and the Internet of Things was intellectually stimulating, and the cross-European nature of these projects allowed to meet and to collaborate with many smart people from other companies and research institutions. Helping to build up a new research lab in Zurich was an additional interesting challenge. But it is time for me now to change. I wanted to get back into the field, developing concrete customer solutions and products. I couldn't let pass the opportunity to join the Swiss office of a small company offering solutions in the cloud domain, as Head of Solution & Service Delivery. Especially since this company is headquartered in Tokyo, and thus providing me with a good possibility to deepen my links with Japan, its language, and its culture. My immediate work will not be related to IoT, but I hope that in the future we can add IoT in one way or another to the portfolio of the new company- I will definitely try to keep the link to the IoT community. I wish you all the best and a lot of success; and maybe our paths will cross again! -Stephan PS: You will be able to reach me at my private mail address (stephan.haller at hispeed.ch) or via LinkedIn. Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Althardstrasse 80, CH-8105 Regensdorf, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Fri Jul 13 14:13:34 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 13 Jul 2012 14:13:34 +0200 Subject: [Fiware-iot] synchronization of fiware IoT and fiware documentation Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59E858281@GRFMBX702BA020.griffon.local> Hi Denes, Thierry, Lorant, I just synchronized the protocol adapter GE description in the public fiware mediawiki with the more recent version contained in the fiware IoT mediawiki (see action point IoT05_11.06.2012) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter I also checked the Junit test in the public fiware mediawiki and it is in the correct format (probably during the call you looked in the fiware IoT mediawiki ) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Gateway_Protocol_Adapter_-_Unit_Testing_Plan Related to the deliverables D5.2 Software release D5.3 Installation and Administration guide D5.4 Users and Programmers guide If I understand correctly what Juanjo said in the call conference of 4th July our contribution will go in the next release of the deliverables, since our asset will be available in the September software release. About the D5.1 Open Specification we work with public specification by ZigBee Alliance so we don't think to contribute to this deliverable. Finally for the deliverables D5.5 Unit Testing Plan & Report D2.3 Architecture specifications D2.4 Technical roadmap We already contributed to these deliverables, please let us know if it is ok for you. Best regards, Sabrina and Gian Piero Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From lorant.farkas at nsn.com Mon Jul 16 09:05:15 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 16 Jul 2012 10:05:15 +0300 Subject: [Fiware-iot] private vs public GE-s Message-ID: <93D28BDF64839C468B848D14227151A203B7368F@FIESEXC014.nsn-intra.net> Dear All, Please make a statement preferably today on the private/public character of your GE-s: -NSN: Cumulocity (implements backend device management): private -NEC: ISIS (implements backend things management/IoT broker): ??? -TID: Configuration Management (implements backend things management/Configurator): ??? -Ericsson: Gateway (implements gateway device management): ??? -TI: Gateway (implements gateway protocol adapter): ??? -ATOS: SOL CEP engine (implements gateway data handling): ??? -Orange: Gateway (implements gateway data handling): ??? * Public = open to the whole world * Private = open to the PPP (Use Case Projects, EC ...) but not to the outside world Please also see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/FiwareDeliverables to understand where and how information about your private/public GE will go. I need this information for following the right delivery process. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From maarten.los at atosresearch.eu Mon Jul 16 10:05:13 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Mon, 16 Jul 2012 10:05:13 +0200 Subject: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting References: <461EDDC0FEB25648B2FE8B0145848AA5F40AB7@INTMAIL02.es.int.atosorigin.com> Message-ID: <461EDDC0FEB25648B2FE8B0145848AA501043ABB@INTMAIL02.es.int.atosorigin.com> Dear partners, Please find below the bridge details for today's meeting. Regards, Maarten LOS Maarten has invited you to a conference call: Join using Communicator If you don't have Microsoft? Office Communicator installed: Join using a Web browser AUDIO INFORMATION To join a conference from your phone, dial in using the following information: Phone: +34 91 14 20 779 [Spanish, English] Find a local phone number for your region Conference ID: 9114249 Passcode: Passcode is not required. Note: If you have an account on this corporate network, use your PIN to join. Have you set your PIN? TROUBLESHOOTING Unable to join the conference call? Copy and paste this link into your Internet browser: conf:sip:maarten.los at atos.net;gruu;opaque=app:conf:focus:id:3814A82809A34ED0958CFDB60957BDF%3Fconversation-id=9bb8d9b4146649ba93f04949eb1d6459 From: Maarten Los Sent: lunes, 09 de julio de 2012 9:18 To: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting Dear partners, As per the Doodle results, I would like to fix the meeting for Monday July 16, 1300h Madrid time. Bridge details will follow. Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Maarten Los Sent: mi?rcoles, 04 de julio de 2012 12:34 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FIWARE - IoT] - Data Handling GE - CEP Interface meeting Dear partners, As discussed in today's IoT Weekly Meeting, we would like to call a telco to discuss the interfaces of the CEP Component (both that of Orange and of Atos) within the IoT Architecture (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3IoT). Broadcasting this to the IoT list at large, just in case we miss anyone, but the main partners involved in the telco would be Orange, Ericsson and the WPA/WPL. We would kindly like to ask if you could state your availability by Friday COB on the following Doodle. Bridge details will be provided afterwards. http://www.doodle.com/rvcf843axt53pyru Here's a tentative agenda, please feel free to add anything you think is missing: Agenda - General interaction with Backend o Registering o NGSI9/NGSI10 interactions - General interaction within Gateway and/or other components, if any - Reception of Incoming events o Source(s) (currently understood to be Gateway Device Management GE - Data Handling API) o Data format + delivery method - Emission of Outgoing events o Destination(s) o Data format + delivery method Thanks and best regards, Maarten ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Jul 16 13:24:56 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 16 Jul 2012 14:24:56 +0300 Subject: [Fiware-iot] delivery plan 2.0 Message-ID: <93D28BDF64839C468B848D14227151A203B7383B@FIESEXC014.nsn-intra.net> Dear All, I need to reconsider my earlier statement: it has been decided that any delay in the M12 deliverables related to the technical work packages (in our case D5.1...D5.5) after 23rd of July will imply that the PM-s according to the plan between M12 and end of July by the respective partner will not be accepted for the respective deliverable. Example: assuming a partner has 7.5 PM-s allocated in WP5 between 1st of May and end of July, and the partner commits D5.1...D5.4 on the 23rd of July, the deliverables are accepted, but the partner fails in committing D5.5. Then 80% of the PM-s can be accepted between May and July, that is up to 6 PM-s. Because of this from WPA/WPL perspective I have to ask you to re-prioritize our activities to cover first D5.1...D5.5 now and everything else afterwards. This would mean we have to bring D5.5 Unit Testing Plan and Report to W29. I am bringing also the standardization plan and reporting contribution forward from W31 to W30 because of the high importance of this topic. The redesigned plan would be: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W29 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W30 _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Wednesday, July 11, 2012 2:06 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: list of actions for the partners Dear All, Sorry for missing our weekly call. Let's stay pragmatic and try to plan our activities according to my originally proposed planning, despite what has been discussed in the weekly call or disclosed in earlier e-mails. Partner contribution high level plan: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W30 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W31 -For the W28 and W29 deliverables I already captured every needed action partner by partner/person by person, it should already be in your inboxes. Tasks incorporate detailed information on what you should do and how. If something is not clear, please ask. -For the W30 and W31 activities I still need to create the tasks in forge, you will receive notifications about them. -If you need to delegate tasks (example: Tobias delegates something to Salvatore), please do it within the Fusion Forge task assigned to you, or let me know by e-mail. -If your task progresses in some way, please write an e-mail or make a comment in the task I assigned to you. We will in parallel monitor the outcomes and make comments if we see progress, but it would be nice if you do his proactively. -Please also mark in the task the number of hours it took you/your colleagues to finalize it, -I put an early estimate when the task was created. It will help us to better plan in the future and to monitor/assess the amount of work you spent on the respective task. -If you finish something belonging to W28, please start working on tasks belonging to W29, and so on. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From kzangeli at tid.es Mon Jul 16 14:49:06 2012 From: kzangeli at tid.es (Ken Zangelin) Date: Mon, 16 Jul 2012 14:49:06 +0200 Subject: [Fiware-iot] private vs public GE-s In-Reply-To: <93D28BDF64839C468B848D14227151A203B7368F@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203B7368F@FIESEXC014.nsn-intra.net> Message-ID: <50040DC2.4090403@tid.es> Hi Lorant, the configuration management component is private, as far as I've understood. Juanjo always has the last word on this, but I believe we've said it's to be private. Regards, /KZ On 07/16/2012 09:05 AM, Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Please make a statement preferably today on the private/public character of your GE-s: -NSN: Cumulocity (implements backend device management): private -NEC: ISIS (implements backend things management/IoT broker): ??? -TID: Configuration Management (implements backend things management/Configurator): ??? -Ericsson: Gateway (implements gateway device management): ??? -TI: Gateway (implements gateway protocol adapter): ??? -ATOS: SOL CEP engine (implements gateway data handling): ??? -Orange: Gateway (implements gateway data handling): ??? * Public = open to the whole world * Private = open to the PPP (Use Case Projects, EC ...) but not to the outside world Please also see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables to understand where and how information about your private/public GE will go. I need this information for following the right delivery process. Thanks & Br, Lorant ________________________________ 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 lorant.farkas at nsn.com Tue Jul 17 08:14:22 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 17 Jul 2012 09:14:22 +0300 Subject: [Fiware-iot] testbed cockpit Message-ID: <93D28BDF64839C468B848D14227151A203B739E4@FIESEXC014.nsn-intra.net> Dear All, Under the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbe d_V1_Implementation_Cockpit#Testbed_V1_Cockpit there is the "testbed cockpit" where we have to fill information about our assets. We neglected this so far, the only part having been filled is Things Management, by Salvatore. I guess the reason is that he was the only one from our WP having participated in the testbed WP weekly updates. Information about the cockpit: This is the page to monitor what will be delivered for the testbed V1 (checked by the GE owners) and when. - About the What Well as Testbed team we have (i) listed the GE to deliver for V1 on the base of the roadmap indications and direct feedbacks from GE owners and (ii) prepared the forms to allow the GE owners to check the requirements they already provided in January and eventually modify them (the open the form you have to click on the company name). By the way I want to point out (once again) that the filling and management of the forms is completely up to each GE owner (company). Then if you don't have anything to install by July...well...you have decided to not install anything! - About the When Well as Testbed team we have indicated for each GE the foreseen date for the V1 (i.e. end of July) and the postponed one by gathering such information from the roadmap document and by crosschecking it directly with the GE owners. I will create tasks for you in forge to fill this with the deadline end of W30. I filled out the table with the information I have on your assets, but for the details you need to click on the company name and create the respective page. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Tue Jul 17 10:40:22 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 17 Jul 2012 10:40:22 +0200 Subject: [Fiware-iot] R: private vs public GE-s In-Reply-To: <93D28BDF64839C468B848D14227151A203B7368F@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203B7368F@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59E858883@GRFMBX702BA020.griffon.local> Hi Lorant, The gateway protocol adapter component is public. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Farkas, Lorant (NSN - HU/Budapest) Inviato: luned? 16 luglio 2012 09:05 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] private vs public GE-s Dear All, Please make a statement preferably today on the private/public character of your GE-s: -NSN: Cumulocity (implements backend device management): private -NEC: ISIS (implements backend things management/IoT broker): ??? -TID: Configuration Management (implements backend things management/Configurator): ??? -Ericsson: Gateway (implements gateway device management): ??? -TI: Gateway (implements gateway protocol adapter): ??? -ATOS: SOL CEP engine (implements gateway data handling): ??? -Orange: Gateway (implements gateway data handling): ??? * Public = open to the whole world * Private = open to the PPP (Use Case Projects, EC ...) but not to the outside world Please also see https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables to understand where and how information about your private/public GE will go. I need this information for following the right delivery process. Thanks & Br, Lorant Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From lorant.farkas at nsn.com Tue Jul 17 11:12:31 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 17 Jul 2012 12:12:31 +0300 Subject: [Fiware-iot] partner penalties Message-ID: <93D28BDF64839C468B848D14227151A203B73B29@FIESEXC014.nsn-intra.net> Dear All, Please find below the planned partner penalties (the full story): * Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver. Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted. Planning of PMs for the remaining of the project will be adjusted accordingly. * Delivery of software that doesn't work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered. This intends to prevent that some partner delivers software which doesn't meet enough quality by July 23rd just to avoid costs rejections. * Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point). This means they would not suffer any impact. * PMs of any partner within a given WP (WP3-8) are distributed from month 10 on across deliverables as follows (note: we propose to include whatever distribution gets approved in the next amendment of the DoW): o Contributions to WP2 deliverables: 10% o FI-WARE Open Specifications: 20% o SW Release: 40% o Installation and Admin Guides: 7,5% o Users' and Programmers' Guides: 7,5% o Unit Testing Plan and Report: 15% * Deliverables of a given WP rejected by the WPL will be rejected. TID and the WPL agree on any amendment of the above rules that may apply (e.g., failing to deliver a given GE may not be the fault of all partners involved in development of that GE so they may agree not to apply penalizations to some partners). TID may reject some additional deliverables if it considers that they do not meet the defined guidelines or expected quality, after discussion with the WPL. * Similar rules would apply to WP9 (development tools) Thanks & Br, Lorant _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Monday, July 16, 2012 1:25 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: delivery plan 2.0 Importance: High Dear All, I need to reconsider my earlier statement: it has been decided that any delay in the M12 deliverables related to the technical work packages (in our case D5.1...D5.5) after 23rd of July will imply that the PM-s according to the plan between M12 and end of July by the respective partner will not be accepted for the respective deliverable. Example: assuming a partner has 7.5 PM-s allocated in WP5 between 1st of May and end of July, and the partner commits D5.1...D5.4 on the 23rd of July, the deliverables are accepted, but the partner fails in committing D5.5. Then 80% of the PM-s can be accepted between May and July, that is up to 6 PM-s. Because of this from WPA/WPL perspective I have to ask you to re-prioritize our activities to cover first D5.1...D5.5 now and everything else afterwards. This would mean we have to bring D5.5 Unit Testing Plan and Report to W29. I am bringing also the standardization plan and reporting contribution forward from W31 to W30 because of the high importance of this topic. The redesigned plan would be: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W29 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W30 _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Wednesday, July 11, 2012 2:06 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: list of actions for the partners Dear All, Sorry for missing our weekly call. Let's stay pragmatic and try to plan our activities according to my originally proposed planning, despite what has been discussed in the weekly call or disclosed in earlier e-mails. Partner contribution high level plan: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W30 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W31 -For the W28 and W29 deliverables I already captured every needed action partner by partner/person by person, it should already be in your inboxes. Tasks incorporate detailed information on what you should do and how. If something is not clear, please ask. -For the W30 and W31 activities I still need to create the tasks in forge, you will receive notifications about them. -If you need to delegate tasks (example: Tobias delegates something to Salvatore), please do it within the Fusion Forge task assigned to you, or let me know by e-mail. -If your task progresses in some way, please write an e-mail or make a comment in the task I assigned to you. We will in parallel monitor the outcomes and make comments if we see progress, but it would be nice if you do his proactively. -Please also mark in the task the number of hours it took you/your colleagues to finalize it, -I put an early estimate when the task was created. It will help us to better plan in the future and to monitor/assess the amount of work you spent on the respective task. -If you finish something belonging to W28, please start working on tasks belonging to W29, and so on. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 17 11:13:12 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 17 Jul 2012 12:13:12 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203B73B2B@FIESEXC014.nsn-intra.net> When: 2012. j?lius 18. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's have the following topics during this instance: 1. Update on action items 2. Delivery status of M12 deliverables 3. Sharing info from the last WPA/WPL meeting 4. AoB Thierry is on holidays, NSN will host this meeting. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 3683 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From Tobias.Jacobs at neclab.eu Tue Jul 17 12:05:16 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 17 Jul 2012 10:05:16 +0000 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A203B73B2B@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203B73B2B@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D168B023E@PALLENE.office.hd> Dear Lorant, all, Unfortunately NEC cannot participate in tomorrow's phone conference. This holds for all of us: Ernoe, Martin, Salvatore, Tobias. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Dienstag, 17. Juli 2012 11:13 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. j?lius 18. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's have the following topics during this instance: 1. Update on action items 2. Delivery status of M12 deliverables 3. Sharing info from the last WPA/WPL meeting 4. AoB Thierry is on holidays, NSN will host this meeting. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 17 14:51:34 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 17 Jul 2012 15:51:34 +0300 Subject: [Fiware-iot] delivery plan 2.0 - Status update In-Reply-To: <461EDDC0FEB25648B2FE8B0145848AA5010441CB@INTMAIL02.es.int.atosorigin.com> References: <461EDDC0FEB25648B2FE8B0145848AA5010441CB@INTMAIL02.es.int.atosorigin.com> Message-ID: <93D28BDF64839C468B848D14227151A203BB588D@FIESEXC014.nsn-intra.net> Outlook, we are in week 29 currently according to my instance. Maybe this is something of more general interest. Br, Lorant From: ext Maarten Los [mailto:maarten.los at atosresearch.eu] Sent: Tuesday, July 17, 2012 2:50 PM To: Farkas, Lorant (NSN - HU/Budapest) Subject: FW: [Fiware-iot] delivery plan 2.0 - Status update Hi Lorant, With the risk of asking something stupid, and sorry if I missed this, but... what is your reference for determining the week? Outlook, ISO and other sources seem to differ on what week we are living in.... According to Outlook, we're in week 30, but ISO is week 28. Thanks and regards, Maarten From: Maarten Los Sent: martes, 17 de julio de 2012 14:02 To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; laurent.artusio at orange.com Subject: RE: [Fiware-iot] delivery plan 2.0 - Status update Hi Lorant, >From our side, delivered: Admin Guide https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/SOL/CEP_Complex_Event_Processor_-_Installation_and_Administration_Guid e Open Specs https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandlingNew . Regarding the Admin Guide: minor final changes are expected based on the delivery methodology. Regarding the Open Specs: @Orange, please also review; also kindly make sure that no changes are overridden in the wiki (the SOL/CEP contribution of June 15 was blown away...) ; we've recovered it, but alas, the FI-WARE documentation tool of choice is not the easiest to work with ;) Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: lunes, 16 de julio de 2012 13:25 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] delivery plan 2.0 Importance: High Dear All, I need to reconsider my earlier statement: it has been decided that any delay in the M12 deliverables related to the technical work packages (in our case D5.1...D5.5) after 23rd of July will imply that the PM-s according to the plan between M12 and end of July by the respective partner will not be accepted for the respective deliverable. Example: assuming a partner has 7.5 PM-s allocated in WP5 between 1st of May and end of July, and the partner commits D5.1...D5.4 on the 23rd of July, the deliverables are accepted, but the partner fails in committing D5.5. Then 80% of the PM-s can be accepted between May and July, that is up to 6 PM-s. Because of this from WPA/WPL perspective I have to ask you to re-prioritize our activities to cover first D5.1...D5.5 now and everything else afterwards. This would mean we have to bring D5.5 Unit Testing Plan and Report to W29. I am bringing also the standardization plan and reporting contribution forward from W31 to W30 because of the high importance of this topic. The redesigned plan would be: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W29 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W30 _____________________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Wednesday, July 11, 2012 2:06 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: list of actions for the partners Dear All, Sorry for missing our weekly call. Let's stay pragmatic and try to plan our activities according to my originally proposed planning, despite what has been discussed in the weekly call or disclosed in earlier e-mails. Partner contribution high level plan: WP2 deliverables where we need to contribute: D2.3 Architecture specifications end of W30 D2.4 Technical roadmap end of W31 WP5 deliverables (fully ours): D5.1 Open Specifications end of W28 D5.2 Software release end of W29 D5.3 Installation and Administration guide end of W28 D5.4 Users and Programmers guide end of W29 D5.5 Unit Testing Plan & Report end of W30 WP11 deliverables where we need to contribute: D11.4 Standardization plan and Report end of W31 -For the W28 and W29 deliverables I already captured every needed action partner by partner/person by person, it should already be in your inboxes. Tasks incorporate detailed information on what you should do and how. If something is not clear, please ask. -For the W30 and W31 activities I still need to create the tasks in forge, you will receive notifications about them. -If you need to delegate tasks (example: Tobias delegates something to Salvatore), please do it within the Fusion Forge task assigned to you, or let me know by e-mail. -If your task progresses in some way, please write an e-mail or make a comment in the task I assigned to you. We will in parallel monitor the outcomes and make comments if we see progress, but it would be nice if you do his proactively. -Please also mark in the task the number of hours it took you/your colleagues to finalize it, -I put an early estimate when the task was created. It will help us to better plan in the future and to monitor/assess the amount of work you spent on the respective task. -If you finish something belonging to W28, please start working on tasks belonging to W29, and so on. Thanks & Br, Lorant ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Tue Jul 17 16:01:56 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 17 Jul 2012 16:01:56 +0200 Subject: [Fiware-iot] R: IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A203B73B2B@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203B73B2B@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59E858A51@GRFMBX702BA020.griffon.local> Dear Lorant, all, I will not be present at the conference tomorrow. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Farkas, Lorant (NSN - HU/Budapest) Inviato: marted? 17 luglio 2012 11:13 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT weekly meeting When: 2012. j?lius 18. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's have the following topics during this instance: 1. Update on action items 2. Delivery status of M12 deliverables 3. Sharing info from the last WPA/WPL meeting 4. AoB Thierry is on holidays, NSN will host this meeting. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From lorant.farkas at nsn.com Wed Jul 18 14:33:47 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 18 Jul 2012 15:33:47 +0300 Subject: [Fiware-iot] weekly meeting minutes Message-ID: <93D28BDF64839C468B848D14227151A203BB5C26@FIESEXC014.nsn-intra.net> Dear All, Please find the minutes of the weekly call under the following link: https://forge.fi-ware.eu/docman/view.php/11/1183/IoT-Minutes-Telco-18072 012.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 24 09:02:30 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Jul 2012 10:02:30 +0300 Subject: [Fiware-iot] delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Message-ID: <93D28BDF64839C468B848D14227151A203C10743@FIESEXC014.nsn-intra.net> Dear All, FYI, agreed with Arian yesterday. Action item required (I will create task for you in forge): decide by the end of the week whether you want your binaries and install/admin guide to be published for the commission in the testbed in the VM dedicated in the testbed to your GE or you want them to be published for the commission in the docman of forge project "fi-ware restricted" (will be renamed "fi-ware review"). Would not hurt if the various assets for a given GE (e.g. SOL CEP & Orange CEP, Config Management & IoT broker) took the same decision. Thanks & Br, Lorant From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Tuesday, July 24, 2012 12:27 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] On formula for delivering software and Installation/Administration Guidelines marked as PP and linked to GEs Dear colleagues, I have had a long conversation with our PO this afternoon and we managed to agree on the formula for delivering the software and Installation/Administration Guidelines linked to the GEs that are marked as PP. The agreement is that both deliverables can be made available to the EC for auditing/reviewing purposes on the servers (indeed, VMs) where the software will actually be hosted, this meaning either servers located in the datacenter linked to the FI-WARE Testbed or remote servers (this only applying to those cases where it was agreed that the GE would not be deployed on the FI-WARE Testbed datacenter). We just need to generate a document that identifies the server where the software (binaries) and Installation/Administration Guides will be available and also explains how the EC can get access to the binaries and Installation/Administration Guides. Note that software must be binaries and not VM images. I have push for adoption of this solution as a mean to cover all the concerns expressed by some of the partners. Based on the Collaboration Agreement signed by all parties, FI-WARE GE software binaries and Installation/Administration Guides will not be made available to FI-PPP partners unless they: * request them in writing * require them because they need them for execution of their respective projects within the FI-PPP * can explain that using them "as a Service" through a well defined API (from the FI-WARE Testbed or any other alternative hosting facility) is not enough * an agreement is signed between the GE owner and the FI-PPP partner requesting the software Note that while it's unlikely that a UC project may require access to binaries and Installation/Administration Guides in this first phase of the program ... I expect that these three conditions may fulfilled by several trials in phase 2 and 3 of the FI-PPP. Nevertheless, there will be some few cases where the above conditions would apply even in the current, first phase of the program. It is clear regarding the Cloud Proxy GE in my opinion, but maybe also true with respect to some IoT gateway -related GEs or other GEs that UC projects may need to deploy in local infrastructures. We will keep the "FI-WARE PPP Restricted" project only accessible to FI-WARE partners and the EC (plus reviewers). We will also probably rename it as "FI-WARE Review". GE owners are free to officially deliver their software (binaries) and Installation/Administration Guides on the SVN and docman tools of that project. They may also deliver only foreground software there. This would be an alternative to creation of a dedicated space, at the servers where the software is hosted, where the software should easily be identifiable against any other software. Actually, we will deliver a document to the EC where we will declare that the software is available in the SVN and docman system of this project in FusionForge. Please let us know what of the two options you will choose before end of this week. That way, we will be able to organize the final package of deliverables. In the case that any UC project requires access to binaries and Installation/Administration Guides of a given FI-WARE GE, the above conditions should be met and then we will discuss how the software should be delivered. Hope it helps. Don't hesitate to ask any doubt or question you may have. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT3443796.txt URL: From lorant.farkas at nsn.com Tue Jul 24 09:07:38 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Jul 2012 10:07:38 +0300 Subject: [Fiware-iot] Report on conversation with our PO on status of the FI-WARE project Message-ID: <93D28BDF64839C468B848D14227151A203C1074E@FIESEXC014.nsn-intra.net> Dear All, FYI, no action item wrt this one, just for reading and giving feedback. Thanks & Br, Lorant -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Tuesday, July 24, 2012 1:14 AM To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Report on conversation with our PO on status of theFI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From lorant.farkas at nsn.com Tue Jul 24 09:13:29 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Jul 2012 10:13:29 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203C10755@FIESEXC014.nsn-intra.net> When: 2012. j?lius 25. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (phone number: in the pdf, conference code: 3865541959#) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, I propose to discuss the following topics: 1. Open/pending action items 2. Feedback from the audit by the coordinator (if we receive them before the meeting) 3. Sharing info from the last WPA/WPL 4. Pending issues for this week (W30), in particular: catalogue, backlog entries, standardization contributions, cockpit, installation responsible (some of these you are aware of, for the rest I am just starting to create the forge tasks for the new ones) 5. AoB On this occasion both Thierry and myself will be available, D?nes is on holiday. Thanks & Br, Lorant Update on all instances because NSN has a new voice conferencing service. To join the voice conference: Dial the your country-specific local access number, indicated in the following pdf: <> Enter the conference code: 3865541959# ------------------------------------------------------- To join the online meeting Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D <> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 4011 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Local_access_numbers.pdf Type: application/pdf Size: 88754 bytes Desc: Local_access_numbers.pdf URL: From lorant.farkas at nsn.com Tue Jul 24 17:16:06 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Jul 2012 18:16:06 +0300 Subject: [Fiware-iot] FW: Review of Unit Test Plan (WP5 - IoT) Message-ID: <93D28BDF64839C468B848D14227151A203C10A2C@FIESEXC014.nsn-intra.net> Dear All, FYI. We will discuss this under "2. Feedback from the audit by the coordinator (if we receive them before the meeting)". Please prepare for the topic. Thanks & Br, Lorant -----Original Message----- From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Tuesday, July 24, 2012 5:13 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest) Cc: JUAN JOSE HIERRO SUREDA Subject: Re: Review of Unit Test Plan (WP5 - IoT) Dear Thierry & Lorant, This is the review of the Unit Testing plan. As told by Juanjo, there is a very short time to put it right. I assume that you already have the Report ready to append at the end of the deliverable and that such manual complies with the guidelines (one single report, not one per GE). Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_1.0_b_WP5.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 11809 bytes Desc: Audit_Release_1.0_b_WP5.xlsx URL: From lorant.farkas at nsn.com Wed Jul 25 07:29:52 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Jul 2012 08:29:52 +0300 Subject: [Fiware-iot] FW: Comments on Features linked to GEs in the IoT Chapter Message-ID: <93D28BDF64839C468B848D14227151A203C10AF6@FIESEXC014.nsn-intra.net> Dear All, Below feedback on the SW delivery deliverable/features part. We could discuss this as well in our meeting today under point no. 2. A more general feedback also attached, wich to some extent applies also to our chapter. Thanks & Br, Lorant From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Wednesday, July 25, 2012 12:28 AM To: 'Thierry.nagellen at orange-ftgroup.com'; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Comments on Features linked to GEs in the IoT Chapter Dear Thierry, Lorant, Denes, Please find my comments regarding revision/addition of Features linked to GEs in the IoT Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. 2. Backend Device Management GE Pretty good work. Congratulations ! Just a typo in the description of FIWARE.Feature.IoT.Backend.DeviceManagement.DisconnectedDeviceManagement where it is said "The FI-WARE Instance providers also needs" where one 's' or the other should be dropped (seems like the first one). Maybe also in this same Feature, it would be appropriate to move the text "The FI-WARE Instance providers also needs the system to automatically reconnect devices/IoT gateways with an optimal scheduling/a scheduling set by myself/scheduling depending on other factors (e.g. availability of an access network)" as part of the description so that the Goal gets shorter (you may consider replacing the mentioned text by ", handling automatic reconnection" in the goal itself. Just a suggestion. One thing I don't understand very well is why you have the Feature regarding CEP support ... Why should the Backend Device Management GE support CEP capabilities ? It's nice that you have add the last Feature regarding NGSI-based interface to the Things Management GE 3. Backend Things Management GE For obvious reasons, I don't have any particular comment at this point (you know it took several interactions until we got it, thanks to NEC for this collaborative effort) 4. Backend Advanced Connectivity GE My understanding is that this GE goes for the second release. Because of that, the degree of development reached is fine to me. The fact that there are more Epics than Features sounds reasonably to me at this point in the project (I wonder even whether the identified Features are functions we feel confident can be addressed in the course of a minor Release (3 months long) 5. Backend Template Handler GE Similar comments like with the previous GE. Just a minor comment. Descriptions linked to Features refer to "Epics" ... probably this was because you translated some Epics into Features. Changing this is not that critical (we have always mentioned that Features were like a kind of Epic that is enough well defined as to feel confident it may take a minor Release, i.e. 3 months, to develop it. 6. Gateway Device Management GE Maybe the description a bit short but clear enough compared to Features linked to another GEs, but overall it's fine. One thing that it is unclear to me is to what extend all the features are supported no matther whether the northbound interface is an ETSI M2M interface or not (e.g., an IETF Core interface) ... Could you elaborate on the matter ? Maybe it is worth to add some Feature regarding northbound interface that will be supported by this GE ... 7. Gateway Protocol Adapter GE Regarding the FIWARE.Feature.IoT.Gateway.ProtocolAdapter.Adapter.Codec Feature, I believe it would be worth elaborating on what specific Codecs will be supported. While the two first Features (Codec, BasicSecurity) seem to be independent of the specific protocol for which adaptation is supported, the rest of Features seem to be linked to adaptation to the ZigBee protocol. Shouldn't we identify those Features with an Id which makes adaptation to ZigBee explicit ? For example: FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ZigBee.BasicCommunication FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ZigBee.ResponseMessagesGeneration instead of: FIWARE.Feature.IoT.Gateway.ProtocolAdapter.BasicCommunication FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ResponseMessagesGeneration Regarding the FIWARE.Feature.IoT.Gateway.ProtocolAdapter.NativeProtocolAdapter.BasicSecurity Feature, I miss a more elaborated description, maybe explaining a bit how authentication between devices may work (if there is some web page or document which elaborates on that, it would be enough to provide a link here) 8. Gateway Data Handling GE No particular comments. Maybe it would be nice to revise the formula used in Goals to be more aligned with the formulas used in other GEs and also commented in the General Comments shared with all chapters. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware] Fwd: IMPORTANT: General comments regarding addition/revision of Features linked to FI-WARE GEs Date: Tue, 24 Jul 2012 16:28:43 +0300 Size: 21721 URL: From lorant.farkas at nsn.com Wed Jul 25 13:33:44 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Jul 2012 14:33:44 +0300 Subject: [Fiware-iot] weekly meeting minutes Message-ID: <93D28BDF64839C468B848D14227151A203C10D61@FIESEXC014.nsn-intra.net> Dear All, Please find the minutes of the weekly call under the following link: https://forge.fi-ware.eu/docman/view.php/11/1198/IoT-Minutes-Telco-25072 012.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Jul 26 07:55:08 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 26 Jul 2012 08:55:08 +0300 Subject: [Fiware-iot] FW: Review of more deliverables Message-ID: <93D28BDF64839C468B848D14227151A203C10F22@FIESEXC014.nsn-intra.net> Dear All, FYI, no particular issue in our chapter for these 2 deliverables, from a "formal" perspective. Thanks & Br, Lorant From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Wednesday, July 25, 2012 8:06 PM To: Farkas, Lorant (NSN - HU/Budapest); thierry.nagellen at orange.com Cc: JUAN JOSE HIERRO SUREDA Subject: Review of more deliverables Dear Lorant & Thierry, This is my review for the Instal & Admin l manual and also for the User and Programmer's manual. The problematic things are marked in light blue. Please be aware that you have a very short time to react so let your partners know ASAP. A few comments: * Things to be addressed are highlighted in blue. * Note that my review is "formal" (formats, structure, consistency, reasonable aspect) but the coordination (Juanjo) may add comments of a more technical nature afterwards. So an "ok" from me does not necessarily means a final approval by the project coordination. * General comment for all WPs: there are many GEs in some WP with an "Installation and Administration Guide" that is an installation manual only. Giving the need to deliver at once, we will not try to fix it immediately. After the delivery we will provide a deadline to address it and provide the administration part. Of course, the impact on the cost reporting could be affected by this. * This applies to part of the WPs only. The case of the Install and Admin Guides of GEs offered as a Service of nature PP the partner has to provide proper guides (what is needed by the administrator of the machine where it is running at your company ). This will given to the EC upon request and it will protected somehow (account/password, IP filtering, ...). In the deliverables at the end of the month we will provide simply a text stating that. We would give the manuals+binaries afterwards and only if they ask for it. I'd appreciate it if you could confirm what GEs are going to be provided as a Service (not to install on the testbed) in July. Theoretically this is in the testbed wiki but things change too fast and I prefer to ask you. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Audit_Release_1.0_b_WP5.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 11089 bytes Desc: Audit_Release_1.0_b_WP5.xlsx URL: From lorant.farkas at nsn.com Thu Jul 26 15:50:21 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 26 Jul 2012 16:50:21 +0300 Subject: [Fiware-iot] Comments on Features linked to GEs in the IoT Chapter In-Reply-To: <500F2187.6090907@tid.es> References: <500EF8C8.3050607@tid.es> <500F2187.6090907@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A203C11215@FIESEXC014.nsn-intra.net> Dear Juanjo, We believe we covered all your points, please see inline. Thanks & Br, Lorant From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Wednesday, July 25, 2012 12:28 AM To: 'Thierry.nagellen at orange-ftgroup.com'; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro" Subject: Comments on Features linked to GEs in the IoT Chapter Dear Thierry, Lorant, Denes, Please find my comments regarding revision/addition of Features linked to GEs in the IoT Chapter. If there is anything you disagree with and wish to discuss, I'm happy to. Cheers, -- Juanjo 1. General Comments Please check the General Comments for all chapters that have been sent. Several of those comments apply to your chapter. We will try to point here where they specifically apply to your chapter but don't miss to carry out a revision yourself. Does not apply, as discussed in the IoT weekly meeting. 2. Backend Device Management GE Pretty good work. Congratulations ! Just a typo in the description of FIWARE.Feature.IoT.Backend.DeviceManagement.DisconnectedDeviceManagement where it is said "The FI-WARE Instance providers also needs" where one 's' or the other should be dropped (seems like the first one). Maybe also in this same Feature, it would be appropriate to move the text "The FI-WARE Instance providers also needs the system to automatically reconnect devices/IoT gateways with an optimal scheduling/a scheduling set by myself/scheduling depending on other factors (e.g. availability of an access network)" as part of the description so that the Goal gets shorter (you may consider replacing the mentioned text by ", handling automatic reconnection" in the goal itself. Just a suggestion. Both issues corrected. One thing I don't understand very well is why you have the Feature regarding CEP support ... Why should the Backend Device Management GE support CEP capabilities ? Removed, as we discussed in the IoT weekly meeting. It's nice that you have add the last Feature regarding NGSI-based interface to the Things Management GE 3. Backend Things Management GE For obvious reasons, I don't have any particular comment at this point (you know it took several interactions until we got it, thanks to NEC for this collaborative effort) No issue here. 4. Backend Advanced Connectivity GE My understanding is that this GE goes for the second release. Because of that, the degree of development reached is fine to me. The fact that there are more Epics than Features sounds reasonably to me at this point in the project (I wonder even whether the identified Features are functions we feel confident can be addressed in the course of a minor Release (3 months long) No issue here. 5. Backend Template Handler GE Similar comments like with the previous GE. Just a minor comment. Descriptions linked to Features refer to "Epics" ... probably this was because you translated some Epics into Features. Changing this is not that critical (we have always mentioned that Features were like a kind of Epic that is enough well defined as to feel confident it may take a minor Release, i.e. 3 months, to develop it. Corrected (3 entries). 6. Gateway Device Management GE Maybe the description a bit short but clear enough compared to Features linked to another GEs, but overall it's fine. One thing that it is unclear to me is to what extend all the features are supported no matther whether the northbound interface is an ETSI M2M interface or not (e.g., an IETF Core interface) ... Could you elaborate on the matter ? Maybe it is worth to add some Feature regarding northbound interface that will be supported by this GE ... Added 2 northbound features, clarified in the meeting that the rest is generic. 7. Gateway Protocol Adapter GE Regarding the FIWARE.Feature.IoT.Gateway.ProtocolAdapter.Adapter.Codec Feature, I believe it would be worth elaborating on what specific Codecs will be supported. While the two first Features (Codec, BasicSecurity) seem to be independent of the specific protocol for which adaptation is supported, the rest of Features seem to be linked to adaptation to the ZigBee protocol. Shouldn't we identify those Features with an Id which makes adaptation to ZigBee explicit ? For example: FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ZigBee.BasicCommunication FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ZigBee.ResponseMessagesGeneration instead of: FIWARE.Feature.IoT.Gateway.ProtocolAdapter.BasicCommunication FIWARE.Feature.IoT.Gateway.ProtocolAdapter.ResponseMessagesGeneration Regarding the FIWARE.Feature.IoT.Gateway.ProtocolAdapter.NativeProtocolAdapter.BasicSecurity Feature, I miss a more elaborated description, maybe explaining a bit how authentication between devices may work (if there is some web page or document which elaborates on that, it would be enough to provide a link here) Not for this release, but currently under resolution (you see already zigbee in the name of the features, Sabrina from TI is currently editing in the wiki). 8. Gateway Data Handling GE No particular comments. Maybe it would be nice to revise the formula used in Goals to be more aligned with the formulas used in other GEs and also commented in the General Comments shared with all chapters. No issue. ________________________________ 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 Jul 27 09:31:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 09:31:42 +0200 Subject: [Fiware-iot] Installation on the Testbed and procedures Message-ID: <501243DE.3010807@tid.es> Dear all, As leader of the task D10.2 "FI-WARE Integration" and also from the coordination I'd like to make some clarifications of general interest. As you know, WP10 (Experimentation Support, Integrated Testing and Validation) has as main task the set-up and running of the FI-WARE Testbed. Given the importance of this goal, WP10 has a representative of each partner. This representative (not the WPL) should make sure that all people within his/her company are well informed of the situation and what we expect from them in the Testbed and the experimentation stage. Several partners are not doing this work (in same cases never attended the WP10 phc) and the project coordination is receiving complaints as many people don't seem to be well informed. We sometimes resort to the WPL to help here, but this is not the "official" channel. I will try to recap to give all the consortium an overview of the situation and what we need from you. GENERAL INFO * The Testbed Team is starting to send the details on how to install the testbed to the GE owners who declared that they are going to install their GE in July * Theoretically you should install your GE yourselves but we can give a hand deploying a KVM image for those who prefer this method (other hypervisors are not supported) * The GE owner is the one who administrates and maintains the GE, not the testbed team. If something goes wrong, he/she has to put it up and running again, the WP10 will only monitor the situation and will prompt about abnormal behaviour of the GE . * We have two tools to follow this up: * Implementation cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit * Integration Tracker : https://forge.fi-ware.eu/tracker/?atid=224&group_id=18&func=browse * Each release of each GE is represented by a ticket * The use of this is explained here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Integration_Plan#Integration_Process * If you do not have access to the testbed project and cannot reach this wiki and the tracker, request access following the standard procedure REQUESTS FOR GE OWNERS * We have an installation calendar. Please fill in the responsible person per GE and state the dates when you could install * http://www.doodle.com/bymgm9h9gnbfms8k * Fill the GE template in the Testbed Cockpit (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit ) declaring if the GE is multi-tenant or not (this deeply affects the GE usage by different Use case projects at the same time) * The access to the Testbed is limited per IP. Make sure that the IPs from which you are going to access the Testbed are listed here (if not, you will not be able to enter the testbed): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit (click on your enabler and see the wiki page with the details per enabler) * Alternatively, there is also a page that has company wide IPs (not particular to an enabler): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Operations_Cockpit * Make sure that when you install your GE, you update the corresponding ticket on the Integration tracker and also the Implementation cockpit. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Mon Jul 30 14:14:10 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 30 Jul 2012 12:14:10 +0000 Subject: [Fiware-iot] TR: [Fiware-wpl] Fwd: FI-WARE: extract executive summary draft review report Message-ID: <26830_1343650451_50167A93_26830_21_1_976A65C5A08ADF49B9A8523F7F81925C02D813@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, Please find below an extract from the review report related to the M12 review. As it was reflected during the first day, FI-Ware is not on line with its deadlines so we have to improve a lot how we are able to deliver FI-Ware results. Of course what we are doing during summertime is critical but next review at M18 especially with the demonstration that the testbed is a concrete place where softwares/GE run will be another critical deadline. We will have a dedicated meeting certainly tomorrow so we will come back with more comments after that. If you have any comments, questions or also improvement proposals regarding what the reviewers and the PO have written, feel free to send them to me so I could share them with the other teams tomorrow. BR Thierry 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? : lundi 30 juillet 2012 10:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: FI-WARE: extract executive summary draft review report Dear colleagues, We have just received the following extract of the executive summary draft review report. We haven't had time to review it. But certainly the review report is not as positive as we thought after the first year review meeting. Overall, it is worth to highlight that the project's assestment is: * Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule)" This, among other things, confirms us that the recent measurements put in place were required. Now, it's critical to demonstrate that we are going to deliver what was due and that the testbed will not get delayed. We'll come with additional comments later. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: extract executive summary draft review report Date: Mon, 30 Jul 2012 08:42:05 +0000 From: To: , CC: , , Dear all, Below is an extract from the draft executive summary of the draft M12 review report. The extract may deviate from the executive summary in the final version of the review report. It is sent since it contains some information, e.g. about deliverable acceptance, that you may want to know asap. Best regards, Arian. ====================== The objectives of the project during this period remain unchanged, but are brought into sharp focus due to the delay of two months plus now apparent, and the critical need to release the complete and comprehensive Generic Enabler (GE) Open Specifications and accompanying reference code as soon as possible in order to not risk destabilizing the entire FI PPP. Many primary technical deliverables expected at M12 are not yet available, which is extremely poor progress given that they are some of the main achievements planned for Month 12 and create the first useable foundation for Use Cases projects to build upon. Compounding this failure is the poor quality and incompleteness of various technical deliverables; a quite astounding result given the resources available to the project. According to the Description of Work (DoW), the main achievements for this period should be the first version of the GE open specifications, software prototypes and related guidance material and test plan. Only the specifications were delivered so far. However, they are inadequate for communication and unified understanding with the Use Case projects, are not of the required quality to serve the needs of those projects, and do not provide sufficient basis for practical implementation by software developers - all of which are fundamental to the rationale for and objectives of FI-WARE. It is unclear in many of the GE specifications which are the reusable and commonly shared functions, and which usage areas across various sectors would utilize these GEs. There are also no details on the protocols that support interoperability with other GEs or third party products or how this interoperability would be achieved. Moreover, a consolidated and consistent presentation of the specifications is still missing. There is a lot of confusion about what the GEs really are, or meant to be, within the FI-WARE consortium, and most probably the UC projects, not to mention the world at large. They are a mixed bag, including functional descriptions, specifications of (not necessarily well-defined) technical functions, specification of access and other operational protocols, specification of access to other existing "modules"/"components"/"devices" and so on, specifications to enable interfaces between existing protocols, specifications to enable deployment of other collection of protocols as "engines", etc. As mentioned in the DoW, "GE Open Specifications will contain all the information required in order to build compliant products which can work as alternative implementations of GEs developed in FI-WARE and therefore may replace a GE implementation developed in FI-WARE within a particular FI-WARE Instance." However, given the current state of the GE deliverables, there are severe doubts about how a FI-WARE instance ("platform") could be built from the GEs without a massive amount of "imagination" and tweaking to make them work together. There are also severe doubts about how a "Future Internet Application" could be portable across different FI-WARE Instances that implement the (same set of?) GEs that the Future Internet Application relies on. The GEs as currently defined are not, by themselves, implementable in the sense of delivering a practical software solution ("platform"). This is compounded by the difficulty of understanding what is really meant by a "coherent" set of GEs. Some GEs seem to have closer inter-relationships than others. Notwithstanding the (useful) clarifications and information orally provided at the review meeting, the inadequate and indeed scarce information within these specifications and the discrepancies between the Technical Roadmap and the available GE contents lead the reviewers to cast doubts on the project achievement so far, and its prospect. FI-WARE failed to meet its milestones for Month 12. Given the above, technical progress of the project for the first year is unacceptable. Moreover, any further delay is likely to significantly risk integrity of the entire FI-PPP and the smooth transition to Phase 2. The consortium made a generally positive and concerted effort so far as the review meeting is concerned. It presented itself as a credible team. The verbal presentations made at the meeting were typically more informative and explanatory than the written deliverables would lead readers to expect (some material within the presentation, such as the matrix of use cases using GEs, is highly appreciated by the reviewers). With evident technical capability, but lack of timely and quality delivery, managerial action is an absolute and urgent must for an accelerated FI-WARE recovery, and to ensure that the FI-PPP programme will deliver meaningful innovations. Collaboration with Use Case projects appears to be improving markedly thanks to key face-to-face training weeks, and enhancements to the way the Fusion Forge system is managed. However, there are still significant issues concerning the processing and documentation of the requirements/backlogs. A main conclusion from the review is that the Use Cases requirements are still not considered as high priority by FI-WARE. Feedback from Use Case projects, including implications for the technology perspective and choices made by FI-WARE, should be (more visibly) taken into account and demonstrated as such. Traceability is crucial for the credibility of the FI-WARE technical deliverables and uptake beyond the consortium; and accountability is required to justify financing from the public purse. The recently conducted architecture training weeks should be used as a stepping stone towards building an FI-PPP "culture" between all Programme participants. More such sessions should be planned, particularly around the test-bed integration deployment and use of the DevComE toolset. For its own part, DevComE is presently a positive highlight of the project. Integration planning for the test-bed is sound and detailed. The testing and the integration activities are among the project highlights. Both are carefully planned and well specified. As the development of the GEs is delayed, the integration activities still lack concreteness in terms of specific scenarios in which several of the GEs will be involved, which is a pity. Work undertaken regarding communication and dissemination is showing significant advancement, albeit with still substantial opportunity for improvement. Given the overall delay in the work plan, the postponement of many key deliverables, and the insufficient quality (and quantity) of the technical specifications, the reviewers consider that the resources were not utilized effectively within the first project year. The consortium has put reasonable effort into analysing and positioning FI-WARE in the current market context. The exploitation within the scope of "Smart Cities" is promising and welcome, but the Use Cases projects should be targeted as prime users. The business strategy is however absent, in so far that no credible and preliminary quantified business case has been presented yet. The consortium's position that the business case will arrive in the second year of the project is a matter of serious concerns; for example, the reviewers have the strong impression that nobody in the consortium has any notion of the overall amount of investment required to take FI-WARE results to the market, and the work presented is clearly (still) lacking substantive input from the business departments of the industrial partners. Despite the extensive comments in the Month 6 Review Report and notwithstanding the voluminous deliverable D11.2.1, there is still no unified or compelling marketing message, including no compelling unique selling proposition, of the FI-WARE results. The individual exploitation plans of the partners are timid. There is inadequate consideration of third party development and SME exploitation at the business level. The globalisation dimension of the exploitation plan is unconvincing. The consortium is reminded that the success of FI-WARE depends on the delivery of a genuine global solution, exploitable by partners inside and outside the consortium and beyond Europe. In summary, there is a glaring and alarming discrepancy between the high ambitions of FI-WARE given in the DoW and the very limited perspective of exploitation offered so far. The reviewers are disappointed that many of the recommendations made - dating back to the Month 6 review or even earlier - have not been sufficiently considered. Additionally, the reviewers are frustrated by the pattern of (extremely) late submission of the majority of the deliverables, and hastily communicated rescheduling of other deliverables with debatable arguments. Such behaviour is not acceptable in the business world; it is equally unacceptable in the context of European collaborative activity, especially in view of the public funding involved. b. Recommendations concerning the period under review The following deliverables require re-submission: * D2.3.1 by Month 15 (from Month 9 review) * D2.4.1 by Month 15 (from Month 9 review) * D2.1.2 by Month 18 * D3.1.1 by Month 18 * D4.1.1 by Month 18 * D5.1.1 by Month 18 * D6.1.1 by Month 18 * D7.1.1 by Month 18 * D8.1.1 by Month 18 * D11.1.1 by Month 18 * D11.2.1 by Month 18 * D11.3.1 by Month 18 The following recommendations are reiterated from the Month 6 review report (with the timeframe for R[1][2]1 adjusted in light of the Month 9 review) and were expected to be addressed in a satisfactory manner by the Month 12 review (original recommendations re-produced in italics): R [1-3]1. Given FI-WARE's intent to remain domain neutral, a comprehensive technology map must be created that clearly and unambiguously illustrates the relationships between all Generic Enablers to be produced by FI-WARE. This was expected to be documented in deliverable D2.3.1 originally due Month 9, for which re-submission is now due Month 15. Still to be addressed in the forthcoming resubmission of D2.3.1 due Month 15. As regards the "transparent encompassing architecture" for FI-WARE as a whole also asked for already in the first recommendation of the review report at M3, we advise the consortium to keep in mind and log this recommendation, and re-visit it in 2013, after the projects selected under Phase 2 have joined the FI PPP. R [1-3]3. Ensure meaningful interaction with standards bodies including Internet-related standards groups such as the IETF, the W3C, the IEEE, the ITU-T, the OMA, and the 3GPP/2. This is expected to be reported in deliverable D12.3.2 due Month 12 and/or deliverable D11.4.1 due Month 9. Still to be addressed in the forthcoming D11.4.2 due Month 15. R [1-3]6. Ensure there is a focus on attracting a development community for FI-WARE, and not only within the FI-PPP, but where possible within the partner organisations and the open community of potential users. This is expected to be considered in relation to deliverable D2.5.1 and reported in deliverable D12.2.2. Still to be addressed in the forthcoming D2.5.1. R [1-3]7. As there is substantial reliance on external technology sources, e.g., other FP7 projects and open source projects, contingencies should be prepared which address what actions to take should those projects fail to deliver, or are delayed with planned delivery upon which FI-WARE depends. This is expected to be documented in deliverable D1.1.2 due Month 12. The sourcing of technology is still not sufficiently clear. Contingency planning is still not adequately provided for or documented in D1.1.2. Please provide an adequate plan in the online version of the Project Management Handbook asap. R [1-3]8. There is a reasonable likelihood that FI-WARE chapters will be unable to achieve all that they would like to. A risk mitigation strategy should be put in place for this, with thought given in advance on how the project plans to prioritise resources if insufficient resources are available to cope with all planned work. This is expected to be documented in deliverable D1.1.2. The consortium is reminded that effort and funding allocations in the DoW are indicative and not sacrosanct. A robust risk management strategy is still missing from D1.1.2. Please provide such a strategy in the online version of the Project Management Handbook asap. R [1-3]9. Make sustained effort to enrol the support of stakeholders from the business and marketing departments of all major commercial partners in the project. External to the consortium, dissemination should go considerably beyond the "traditional groups" that are usually targeted for dissemination in FP7 projects. This concerns both the RTD communities and the business communities at large, within as well as outside Europe. Consumer organisations should also be considered and inputs be sought, to make sure that the FI-PPP results will be successfully adopted by the mass market. This is expected to be reported in deliverable D12.2.2. Progress has been made in relation to dissemination. The active involvement and support of the business and marketing personnel from the industrial project partners is still largely absent. R [1-3]10. Ensure that planning of the Open Calls starts early and the Open Calls are inclusive enough to attract any prospective submitters including specialist SMEs (without making a priori assumptions about who might be interested in the calls). The Open Calls should be used as a strategic opportunity for disseminating FI-WARE to FI stakeholders and engaging their interest in FI-WARE outputs. The Open Call processes and experience, including lessons learnt, should be documented and assimilated by the consortium for subsequent calls, and included in the relevant editions of deliverable D1.2.x for reporting and auditing purposes. Please take into full account our remarks on the management and administration of the Open Calls in Section 1a of the previous (M6) Review Report, and clarify the rationale for the selection of the topic(s) for the forthcoming first Open Call and to what extent the use case projects have a voice in the topic selection in the first and subsequent calls. The reviewers are still awaiting the reporting of the first Open Call. Progress to be re-assessed in relation to the planning/reporting of the next Open Call in the forthcoming D1.3.2. R [1-3]11. The reviewers cannot over-emphasise the importance of exploitation planning, including detailed documentation of IPR management. In our view, this is also intimately linked to enablement of third party exploitation. Please refer to our remarks in Sections 1a and 1b of the previous (M6) Review Report. It is obvious that high expectations are placed by the reviewers on deliverables D11.2.1 and D2.5.1 due Month 12. Please do not treat this as a paper exercise for satisfying the reviewers. Instead, they should be treated as initial blueprints for realistic business models backed by genuine commitment from especially the industrial partners. Unsatisfactory addressed. Exploitation planning lacks credibility and market traction. To be addressed in the resubmission of D11.2.1 due M18. R [1-3]12. All future deliverables should continue to be made available to the reviewers in pdf format. They should also be submitted on time. The consortium should investigate whether posting such files on its website or wiki might provide value for potential users, in addition to the wiki pages (at least those files relating to key deliverables). Please report the findings of the investigation at the next review. Unsatisfactory addressed. Large numbers of deliverables not submitted on time, yet again. Others have been rescheduled in a hasty manner. The reviewers strongly recommend corrective actions. Additionally, the reviewers request that project deliverables be made available as a consolidated file for future reviews. The consortium has no inclination to make deliverables available in a file format, other than to the EC and reviewers for pure compliance purposes, after evident resistance. The need to investigate the usefulness of such files to would-be users was dismissed. R [1-3]13. Improve the usefulness and attractiveness of the project website: make the information (even) more easy to find, bearing in mind that users might not be familiar with the FI-PPP; enhance the website as a marketing tool to would-be third parties and 'customers' of FI-WARE results (make the website answer the question to companies not involved in EU funded activities: why should I be interested in what FI-WARE is doing, and what is in it for me?). Consider the use of creditable Search Engine Optimization techniques. Unsatisfactorily addressed - no evidence of website improvement as a marketing tool. Significant improvement required for Month 17. The consortium is also encouraged to bring forward the implementation of the FI-WARE GE portal (not in DoW, but highly welcome) currently planned for Year 3. R [1-3]14. Put in place contingencies for loss of key people from the project. This is expected to be documented in deliverable D1.1.2. Recommendation addressed to some degree, for example by involving WP leaders in the management of backlog. Please provide a clear update in the online version of the Project Management Handbook asap. Recommendations still outstanding from the initial review of D2.2.1: * R2: the relationship between GEs and the Specific Enablers needs to be clarified and documented, bearing in mind that the former are potential candidates for standardisation in due course, and the latter are critical from the view point of making business out of FI-WARE results. Documentation is now expected at Month 9 with deliverable D2.3.1. Still to be addressed in the resubmitted version of the D2.3.1 due Month 15. * R9: The requested delivery schedule for the GEs, or at a minimum indication of prioritisation, has not been presented. This is now expected for deliverable D2.4.1 at Month 9. The information should be made visibly available in the public domain. Still not addressed, with mismatches between the Backlog, the Technical Roadmap and the Open Specifications delivered; To be addressed in the resubmitted version of the D2.4.1 due Month 15. c. Recommendations concerning future work R[3]15. Ensure that the quality of the GE specifications is high and consistent. Use GE specification for WP8 as a template for all other WPs. R[3]16. Clean up the backlog, and keep it up to date at all times. Specific resources must be dedicated to this. R[3]17. Focus on delivery of critical-path, high-priority (for the Use Cases) GEs. R[3]18. GE code releases must be synchronized with GE priorities indicated by Use Case projects. R[3]19. Ensure that architectural documentation clearly and unambiguously indicates the trace of source requirements and justification. R[3]20. Transparency and visibility in what was delivered and what is going to be delivered by the consortium in all future FI-WARE Releases. R[3]21. Meeting the "check points" set by the reviewers. For the next period leading up to the M18 review, the reviewers will be monitoring and assessing project progress against the following key "check points", in addition to DoW compliance and assessment of the project deliverables due: 1. Technical Paper including common usage scenarios for the GEs for wide dissemination (incl. to Use Case projects and third parties), month 15 2. Public availability matrix of use cases using the GEs; continuous update of the matrix, month 15 & thereafter 3. FI-WARE software release, month 15 4. Public availability of the SAP GEs in WP3, month 15 (done) 5. Testbed in operation, feedback from UC projects on using the testbed, month 17 6. Enhancement/re-design of the current website for impact creation, month 17 7. Hold additional architectural weeks, develop training plan for use of the DevComE framework, consider inviting 3rd party developers, month 18 8. Develop and publish a plan for fostering developer communities, month 18 9. Live demonstration of the FI-WARE test-bed with deployed GE software, Next review meeting 10. Presentation by senior business personnel from the main commercial partners of the consortium (at a minimum: TID, SAP, TI, Orange/FT) on corporate plans to bring the FI-WARE key results to the market, Next review meeting R[3]22. For the next period overall project resource allocation should be reviewed to identify the specific weaknesses leading to the failings identified in this review project; resources should be re-planned and re-allocated to rectify the failings where necessary. d. Assessment Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule) ============================== Some other considerations: After one year in the project, one may want to evaluate what has been achieved, esp taking into account that 12 MEuro has been spent. A specific feature of the first reporting period, and a direct result of the delays, is that efforts have been spent on tasks that did not result in submitted deliverables. The economy, effectiveness and efficiency of these efforts can therefore not be evaluated. More importantly, after one year in the project, one may want to evaluate what can be realistically achieved at the end of the project: - The status and maturity of single GEs differ a lot. More consistency and maturity in the specification of GEs needs to be achieved. The litmus test is that these specifications need to be sufficiently mature and complete so that independent software developers can use them to develop implementations that are interchangeable. Prospect: good. - It is not clear to what extent the GE Open Specifications satisfy the requirements from use cases, FI-WARE organisations, or otherwise. There is a risk that at the end of the project the GE Open Specifications do not satisfy the requirements of the use cases. - The baseline assets of each individual GE are not clear. Partly because of this, the roadmap is not clear. At the end of the project, there will be reference implementations, no doubt, but it is not clear to what extent the GE Open Specifications follow the existing baseline assets or v.v. There is a risk that the reference implementations do not satisfy the requirements of the use cases. - The IPR protection of the reference implementations is unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - Likewise, the exploitation plans of the owners of the reference implementations are unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - The division of budgets in FI-WARE is (largely) based on the existence of baseline assets. The more baseline assets a partner brought into the project, the larger its budget in FI-WARE. The advantage is that the work does not start from scratch. It is likely that these baseline assets are typically proprietary solutions. It can be expected that partners will give priority to their baseline assets, further developing these assets, and give less priority to fulfilling use case requirements. Although access to these assets by use case projects after the end of the FI-WARE project is addressed by clause 41, the exact conditions for access, the availability of the assets, and their maturity are unknown. This leaves use cases, possible FI-WARE Instance providers, and third party application developers in an uncertain situation, and clarity is necessary. - There is a high risk that current developments on GE reference implementations do not fulfil the requirements of the use cases. This could be accepted to some extent if these reference implementations would be based on clear requirements from the business departments of the technology providers, and if there were clear exploitation plans for these reference implementations. In such situation, usefulness to use cases would be offset by wide availability and accessibility. However, at the moment there is a high risk that at the end of the FI-WARE project the reference implementations will not fulfil the requirements from the use cases AND will not be accessible. The month 18 review and the Call 2 evaluation will provide an opportunity to analyse the situation with respect to a) the FI-WARE GEs and their reference implementations, b) the priorities of the phase 2 use cases, and c) the commitments of the FI-WARE beneficiaries. Regarding the FI-WARE GEs and their reference implementations, information is needed a.o. concerning: - The final list of GEs for which Open Specifications will be written - The extent to which these GEs fulfil requirements (from all sources), providing justification and accountability - For each GE: the reference implementation(s) of the GE - For each GE reference implementation: the baseline asset(s) upon which the reference implementation will be based, the current status, the owner, the relation to other GE (reference implementations) Regarding the phase 2 use cases: - The list of GEs the phase 2 use cases plan to use, and their priority - The list of GE reference implementations the phase 2 use cases plan to use, and their priority Regarding the commitment of the FI-WARE beneficiaries: - For each GE reference implementation: the conditions under which it will be available for FI-PPP programme participants and third parties beyond the lifetime of FI-WARE With respect to the last point, stated intentions in confidential exploitation plans are not sufficient. True commitment and therefore true assurance of the use cases and third parties of the sustainability of their efforts building on FI-WARE can be shown via e.g. a public statement by the GE reference implementation IPR holders. Such a public statement could follow lines as sketched below: - "Our developments in FI-WARE/FI-PPP will be made available as open-source, and/or - Our developments in FI-WARE will be proprietary, conforming to the GE Open Specifications, and we guarantee that they will be available on the market as of [date] under FRAND conditions and will be available for at least [y] years. The exact conditions will be specified within [x] months. In case our companies determine the product will no longer be commercially offered, the source code will be made available as open source and donated to [xyz], and/or - Company X is developing an implementation of a certain GE. Within FI-WARE, an open source reference implementation of the same GE is being developed. Company X builds a proprietary implementation, outside the FI-WARE project, using own funds, and/or - Our companies encourage the development of multiple implementations of a certain GE, will develop a reference implementation for each of the specified GEs within the context of the FI-WARE project, using public money, and will develop additional proprietary implementations [for GEs g,h,k] using own funds - We commit to safeguard the evolution and nature of the GEs for at least [x] years after the FI-PPP programme. - Etc" ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From t.elsaleh at surrey.ac.uk Mon Jul 30 17:31:33 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Mon, 30 Jul 2012 16:31:33 +0100 Subject: [Fiware-iot] Outdated GEs in Themes/Epics/Features Request form on Forge Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5924C0341@EXMB05CMS.surrey.ac.uk> Hello, I am trying to add an Epic Request in Forge, but the GEs declared seems to be outdated, since I cannot find the Things Management GE among others. Has anyone noticed this? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Mon Jul 30 19:49:03 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 30 Jul 2012 17:49:03 +0000 Subject: [Fiware-iot] FI-Ware Standardisation Message-ID: <8152E2132B13FB488CFD1947E2DEF19C32E47CD7@PALLENE.office.hd> Hi Lorant, all, looking at the table of the IoT-Chapter standardization bodies, I am missing ETSI M2M. I have added it. We are contributing here already on the "Semantic Support for M2M Data" work item. Or did I missed a discussion/decision not to include it? Note: I am adding it tentatively... - Ern? From Ernoe.Kovacs at neclab.eu Mon Jul 30 20:07:27 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 30 Jul 2012 18:07:27 +0000 Subject: [Fiware-iot] FI-Ware Standardisation / Zigbee Message-ID: <8152E2132B13FB488CFD1947E2DEF19C32E47EB6@PALLENE.office.hd> Hi all, I took the liberty to also add the ETSI M2M to Zigbee mapping as a item we are monitoring. @ Gian Piero, can it be formulated like this? Please check https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Mapping_Internet_of_Things - Ern? > -----Original Message----- > From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot- > bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs > Sent: Montag, 30. Juli 2012 19:49 > To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] FI-Ware Standardisation > > Hi Lorant, all, > > looking at the table of the IoT-Chapter standardization bodies, I am missing > ETSI M2M. I have added it. > > We are contributing here already on the "Semantic Support for M2M Data" > work item. > > Or did I missed a discussion/decision not to include it? > > Note: I am adding it tentatively... > - Ern? > > > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-iot From lorant.farkas at nsn.com Tue Jul 31 07:49:57 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 31 Jul 2012 08:49:57 +0300 Subject: [Fiware-iot] Outdated GEs in Themes/Epics/Features Request form onForge In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA5924C0341@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA5924C0341@EXMB05CMS.surrey.ac.uk> Message-ID: <93D28BDF64839C468B848D14227151A203C60296@FIESEXC014.nsn-intra.net> Hi, You are doing it in the wrong tracker. This is the right one: https://forge.fi-ware.eu/tracker/?func=browse&group_id=11 Br, Lorant From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext t.elsaleh at surrey.ac.uk Sent: Monday, July 30, 2012 5:32 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Outdated GEs in Themes/Epics/Features Request form onForge Hello, I am trying to add an Epic Request in Forge , but the GEs declared seems to be outdated, since I cannot find the Things Management GE among others. Has anyone noticed this? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jul 31 07:51:33 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 31 Jul 2012 08:51:33 +0300 Subject: [Fiware-iot] FI-Ware Standardisation In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C32E47CD7@PALLENE.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C32E47CD7@PALLENE.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A203C60298@FIESEXC014.nsn-intra.net> Hi Ern?, It is there in the 1st table, but maybe that is the wrong place. Thanks & Br, Lorant -----Original Message----- From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Sent: Monday, July 30, 2012 7:49 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: FI-Ware Standardisation Hi Lorant, all, looking at the table of the IoT-Chapter standardization bodies, I am missing ETSI M2M. I have added it. We are contributing here already on the "Semantic Support for M2M Data" work item. Or did I missed a discussion/decision not to include it? Note: I am adding it tentatively... - Ern? From Ernoe.Kovacs at neclab.eu Tue Jul 31 09:18:09 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Tue, 31 Jul 2012 07:18:09 +0000 Subject: [Fiware-iot] FI-Ware Standardisation In-Reply-To: <93D28BDF64839C468B848D14227151A203C60298@FIESEXC014.nsn-intra.net> References: <8152E2132B13FB488CFD1947E2DEF19C32E47CD7@PALLENE.office.hd> <93D28BDF64839C468B848D14227151A203C60298@FIESEXC014.nsn-intra.net> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C32E4AAFD@PALLENE.office.hd> Hi Lorant, if your refer to body row 2 in the Table 1. I entered yesterday evening. Now there is a consistent flow from Table 1 to Table 2 to Table 3. - Ern? > -----Original Message----- > From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] > Sent: Dienstag, 31. Juli 2012 07:52 > To: Ernoe Kovacs; fiware-iot at lists.fi-ware.eu > Subject: RE: FI-Ware Standardisation > > Hi Ern?, > > It is there in the 1st table, but maybe that is the wrong place. > > Thanks & Br, > > Lorant > > > -----Original Message----- > From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] > Sent: Monday, July 30, 2012 7:49 PM > To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Subject: FI-Ware Standardisation > > Hi Lorant, all, > > looking at the table of the IoT-Chapter standardization bodies, I am missing > ETSI M2M. I have added it. > > We are contributing here already on the "Semantic Support for M2M Data" > work item. > > Or did I missed a discussion/decision not to include it? > > Note: I am adding it tentatively... > - Ern? >