From denes.bisztray at nsn.com Fri Jun 1 11:09:56 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 1 Jun 2012 11:09:56 +0200 Subject: [Fiware-iot] Architecture open specification Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05F6D96F@DEMUEXC013.nsn-intra.net> Dear All, The architecture open specification is now overridden with the new architecture. I would like to ask Telef?nica to complete the Things Management GE description, as it is noted as Under Construction. The old can be still found under this link on our private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Fri Jun 1 12:16:33 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 1 Jun 2012 10:16:33 +0000 Subject: [Fiware-iot] D2.4 revised In-Reply-To: <93D28BDF64839C468B848D14227151A2038BEC92@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2038BEC92@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BEF09E@Polydeuces.office.hd> Hi all, We just reviewed the D2.4 private wikipage, added a few things, and marked other things for deletion. @all: Please check. Best 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: Donnerstag, 31. Mai 2012 13:32 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] D2.4 revised Dear All, I tried to update D2.4 in our private folder, because as you know D2.4 was rejected and additionally we have now new GE names. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT#Gateway Could you please doublecheck the statements and make corrections/additional suggestions if appropriate: Orange, Ericsson for the GW parts NEC, Telefonica, USurrey for the backend parts When we close that, I will be able to transfer the content to the public wiki, http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services (you could also use this to see what I modified). Deadline for this: EOB tomorrow FYI I asked support to install a Gantt plugin to MediaWiki, once we have that I have the plan to create a Gantt diagram with WP5 todos/deliverables. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Fri Jun 1 12:45:05 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 1 Jun 2012 12:45:05 +0200 Subject: [Fiware-iot] some info about Telecom Italia assets Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59D212804@GRFMBX702BA020.griffon.local> Hi all, in order to clarify our position and to give more details about our assets, we provide you the ZigBee Network Device Gateway Specification (see ZigBee_GDS_4-6-11.pdf.) of which our asset is an implementation, moreover we provide you the whitepaper "Understanding ZigBee Gateway" (see Whitepaper-UnderstandingZigBeeGateway.pdf) too. As you know we are going to provide two assets: the first one, GAL, is an implementation of the ZigBee Network Device Gateway Specification, and exposes a REST interface to communicate with the ZigBee devices, the second one, JGAL, is a Java wrapper of the GAL and exposes a Java interface. 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: Whitepaper-UnderstandingZigBeeGateway.pdf Type: application/pdf Size: 275618 bytes Desc: Whitepaper-UnderstandingZigBeeGateway.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ZigBee_GDS_4-6-11.pdf Type: application/pdf Size: 1970654 bytes Desc: ZigBee_GDS_4-6-11.pdf URL: From t.elsaleh at surrey.ac.uk Fri Jun 1 13:01:36 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Fri, 1 Jun 2012 12:01:36 +0100 Subject: [Fiware-iot] D2.4 revised In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEF09E@Polydeuces.office.hd> References: <93D28BDF64839C468B848D14227151A2038BEC92@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEF09E@Polydeuces.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA592397C49@EXMB05CMS.surrey.ac.uk> Hello Lorant, For D2.4 I would like to add this under the Backend Things Management GE in the Second Release: * "A discovery engine which indexes things/resources descriptions in the form of clusters, which in turn allows the scoping of queries to particular description clusters upon discovery, hence allowing more efficient description retrieval from repositories. It also ranks the results of a particular query by comparing which description best matches the query specification." Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 01 June 2012 11:17 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: Salvatore Longo Subject: Re: [Fiware-iot] D2.4 revised Hi all, We just reviewed the D2.4 private wikipage, added a few things, and marked other things for deletion. @all: Please check. Best 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: Donnerstag, 31. Mai 2012 13:32 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] D2.4 revised Dear All, I tried to update D2.4 in our private folder, because as you know D2.4 was rejected and additionally we have now new GE names. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT#Gateway Could you please doublecheck the statements and make corrections/additional suggestions if appropriate: Orange, Ericsson for the GW parts NEC, Telefonica, USurrey for the backend parts When we close that, I will be able to transfer the content to the public wiki, http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services (you could also use this to see what I modified). Deadline for this: EOB tomorrow FYI I asked support to install a Gantt plugin to MediaWiki, once we have that I have the plan to create a Gantt diagram with WP5 todos/deliverables. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Jun 1 13:53:23 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 1 Jun 2012 14:53:23 +0300 Subject: [Fiware-iot] D2.4 revised In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEF09E@Polydeuces.office.hd> References: <93D28BDF64839C468B848D14227151A2038BEC92@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEF09E@Polydeuces.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A2038BF20C@FIESEXC014.nsn-intra.net> Hi Tobias, Tarek. Thanks for the comments, I made all the suggested changes. Regarding the comment wrt Things Management GE in the GW: my mistake, it was meant Device Management. The outcome is visible under http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services We have still some gaps, like we have nothing in the roadmap for the Security GE-s. But this is one of the smaller problems currently. I would like to ask from you for the remaining time of this week to think how we could address the unit testing plan. You will find in the "Materializing..." pages (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE) already the placeholders. We have to fill at least Backend.ThingsManagement, Backend.DeviceManagement, Gateway.DeviceManagement Gateway.DataHandling and Gateway.ProtocolAdapter Basically we need 1 test case per 1st release feature (although test cases can cover more than 1 feature). This would be also an opportunity to revise the features one by one as well, they were created quite some time ago, especially now when we tried to update them with terms from the new streamlined architecture. We try to do something with D?nes on the Backend Device Management GE and later on today there will be an example from the coordinator that we will forward to you. Thanks & Br, Lorant From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Friday, June 01, 2012 12:17 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: Salvatore Longo; Martin Bauer Subject: RE: D2.4 revised Hi all, We just reviewed the D2.4 private wikipage, added a few things, and marked other things for deletion. @all: Please check. Best 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: Donnerstag, 31. Mai 2012 13:32 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] D2.4 revised Dear All, I tried to update D2.4 in our private folder, because as you know D2.4 was rejected and additionally we have now new GE names. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4IoT#Gateway Could you please doublecheck the statements and make corrections/additional suggestions if appropriate: Orange, Ericsson for the GW parts NEC, Telefonica, USurrey for the backend parts When we close that, I will be able to transfer the content to the public wiki, http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services (you could also use this to see what I modified). Deadline for this: EOB tomorrow FYI I asked support to install a Gantt plugin to MediaWiki, once we have that I have the plan to create a Gantt diagram with WP5 todos/deliverables. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Mon Jun 4 16:03:40 2012 From: stephan.haller at sap.com (Haller, Stephan) Date: Mon, 4 Jun 2012 16:03:40 +0200 Subject: [Fiware-iot] NGSI test cases In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEEDC3@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BEEDC3@Polydeuces.office.hd> Message-ID: <0D2446AEB6CAED48BB046223733964A54E362B80E8@DEWDFECCR01.wdf.sap.corp> All, We have prepared a first version of the JUnit test cases for NGSI-10, see https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/IoT_Private_Wiki_Page_for_NGSI10-Testing We will work on the implementation of the other test cases. As I have mentioned earlier however, we need access to an NGSI-Server against which to test - it is not in our intention to develop such a server just for testing purposes! See please, can someone provide us with such a server; either as binaries to be installed locally, or just a URL of a server instance that is accessible online. Regards, -Stephan From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Mittwoch, 30. Mai 2012 14:16 To: Haller, Stephan; Tschirschnitz, Fabian; Zamani Farahani, Armin Cc: Salvatore Longo; Martin Bauer Subject: NGSI test cases Dear SAP colleagues, As we need to prepare the unit test plan, could you give us some information about the NGSI test cases you have created / will create? Thanks a lot in advance Salvatore and Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jun 5 10:14:12 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 5 Jun 2012 11:14:12 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20390996C@FIESEXC014.nsn-intra.net> When: 2012. j?nius 6. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Cancelled due to educational week in Madrid. Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10306 bytes Desc: not available URL: From sabrina.guerra at telecomitalia.it Fri Jun 8 12:24:56 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 8 Jun 2012 12:24:56 +0200 Subject: [Fiware-iot] Protocol Adapter test cases Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59D68B367@GRFMBX702BA020.griffon.local> Hi all, we've inserted the junit test cases of the Protocol Adapter GE in the wiki at the following links: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/IoT_Private_Wiki_Page_for_Unit_Testing_Plan and http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Gateway_Protocol_Adapter_-_Unit_Testing_Plan . We placed them into both directories because we don't know the correct page where to place these tests. Moreover we've added a new svn directory, JUnitTestProtocolAdapter, containing the documentation (094910r12ZB_GWG-ZigBee_IP_Gateway_Test_Specification) and the zip of the junit test cases, JUnitTestProtocolAdapter.zip. Best regards, Sabrina 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 Jun 12 09:49:05 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 12 Jun 2012 10:49:05 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203992F81@FIESEXC014.nsn-intra.net> When: 2012. j?nius 13. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We need to cancel again, as we are preparing for the review. We will send out tomorrow a draft version of the review slideset for comments. In parallel we will send you personalized e-mails on the next practical steps for the M12 deliverables. Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10557 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Jun 14 07:26:00 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 14 Jun 2012 08:26:00 +0300 Subject: [Fiware-iot] FW: [Fiware-wpa] Fwd: [Fiware-wpl] Action Point onDissemination/Collaboration Deliverables Message-ID: <93D28BDF64839C468B848D14227151A20399398C@FIESEXC014.nsn-intra.net> Dear Partners, FYI, please record collaboration & dissemination activities that have not been recorded so far. 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: Monday, June 11, 2012 9:46 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: [Fiware-wpl] Action Point onDissemination/Collaboration Deliverables I cannot do more than emphasize the relevance of this action. One of the deliverables that were due in month 12 and we agreed not to delay was the updated release of the report on communication, collaboration and dissemination activities. In order to achieve that milestone It's rather important to provide the required input. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: [Fiware-wpl] Action Point on Dissemination/Collaboration Deliverables Date: Fri, 8 Jun 2012 14:28:01 +0200 From: CARLOS RALLI UCENDO To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear Colleagues, As previously discussed on our conference call, a key Action Point on all of us related to the Dissemination and Collaboration deliverables has been set. Find enclosed below a previous e-mail with a detailed explanation on this subject. Please, do forward this within your chapters and remind your teams to contribute (deadline: wednesday next week EoB). Thanks for your cooperation, Best regards, Inicio del mensaje reenviado: De: CARLOS RALLI UCENDO Fecha: 10 de mayo de 2012 15:57:00 GMT+02:00 Para: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Cco: CARLOS RALLI UCENDO Asunto: WP12 Deliverables Action Plan (Please read carefully, as trips expenses claim might be rejected afterwards) Dear WPl, As per month 12, Fi-WARE 'Collaboration & Dissemination' chapter committed to deliver the following two deliverables: - D12.2b Report on Communication and Dissemination activities (M12). - D12.3.b Report on Collaboration activities (M12). Fortunately, we thought and provided in advance a permanent structure in the wiki, so those contents were to be continuously updated as they happened. The overall chapter (public) placeholder is at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Communication,_Collaboration_and_Dissemination --> Sections and expected contributions: 1) The first section 'Web Site, social channels and promotional material' has been regularly updated by my colleague Miguel Carrillo, so I will be just adding some statistics related to WEB accesses, twitter followers/retweets, etc. Unless you have specific feedback/suggestions we are not expecting any contrib here. 2) 'Communication Activities' is placeholder structured to describe Press releases, Interviews, Newsletters, Infodays and support to other projects/initiatives. ALL PARTNERS who have performed any of these activities so far are expected to fill in this Wiki-doc with a specific subsection following others as example (time-ordered list). 3) Collaboration Activities: In this section ATOS & TID team will perform updates to improve the descriptions of cooperation with UCs in the architecture weeks, cooperation in the context of AB, cooperation through instruments such as Infinity and Concord and other joint efforts with FI initiatives and ICT instruments. I will be sending today an specific e-mail to ATOS team for these contributions. 4) Disseminations activities: This is the place for Scientific papers and pannels, articles, book chapters, events, training materials, tutorials ... Definitely we expect this section to grow with updates from MOST PARTNERS in the coming days before the deadline. Please create subsections in a time-ordered manner following existing ones as template. We are quite surprised and concerned mainly with the low number of entries in section 4, that the EC may point out as a weak relation/influence of partners with the scientific/R&D community. Also WPl and architects are expected to have had a bit more contribution to what regards to section 2. We are sure there have been many national/international presentations where you have disseminated/explained the idea and expected goals of FI-WARE. Please, take into account that trips claimed as FI-WARE expenses will not be accepted in the absence of the correspondent entry (specifically, in the PDF snapshot that we will send to the EC after the deadline below), unless there is a clear and convincing clarification. Thanks for your cooperation and, please, do forward this e-mail to all members in your teams. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @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 ________________________________ 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: Attached Message Part URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT2720184.txt URL: From thierry.nagellen at orange.com Thu Jun 14 09:44:05 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 14 Jun 2012 07:44:05 +0000 Subject: [Fiware-iot] URGENT APs befor Review Message-ID: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: ? technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! ? Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and D?nes should also remove it from the architecture figure. tomorrow EOB Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB Backend Device Management: we have something, but not compliant to the guidelines. D?nes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB ? SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) ? Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) ? User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) ? Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? Backend Device Management: D?nes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " _________________________________________________________________________________________________________________________ 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 message was scrubbed... From: ext Juanjo Hierro Subject: [Fiware] Fwd: Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE Date: Thu, 31 May 2012 07:15:56 +0300 Size: 20254 URL: From thierry.nagellen at orange.com Thu Jun 14 11:50:27 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 14 Jun 2012 09:50:27 +0000 Subject: [Fiware-iot] URGENT: Update of testbed cockpit wiki page Message-ID: <12255_1339667428_4FD9B3E4_12255_320_5_976A65C5A08ADF49B9A8523F7F81925C0111E6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Another urgent topic but just a quick answer and I will update the wiki... Extract from Telefonica email: "The thing is that D10.3 (Integration Plan) is already delayed more than 3 months due to numerous adverse circumstances and we can almost release it now. It looks like all the problems have been tackled and there's just a last thing to deal with. There are tests related to GEs from IoT that are missing in the doc(or maybe they do not apply) but we need your inputs." We have just to fullfill the cockpit wiki page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit And you have the related email from Paolo Zampognaro. I assume that each of you have subscribed to this testbed mailing list because each developers team has to do it to managed the whole process from specifications to available code on the tesbed. The relevant actions for us are: * NEC: is it ok for the IoT Broker or delayed in September * Ericsson: is it ok for the Things management part in the Gateway or delayed in September * TI: is it ok for device backend management (Zigbee part) or delayed in September. Based on the technical roadmap, the other are delayed in September. Thanks for your quick feedback. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com _________________________________________________________________________________________________________________________ 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 message was scrubbed... From: Paolo Zampognaro Subject: [Fiware-testbed] Testbed cockpit ready Date: Wed, 13 Jun 2012 16:02:07 +0000 Size: 16187 URL: From sabrina.guerra at telecomitalia.it Thu Jun 14 14:40:41 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Thu, 14 Jun 2012 14:40:41 +0200 Subject: [Fiware-iot] R: URGENT: Update of testbed cockpit wiki page In-Reply-To: <12255_1339667428_4FD9B3E4_12255_320_5_976A65C5A08ADF49B9A8523F7F81925C0111E6@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <12255_1339667428_4FD9B3E4_12255_320_5_976A65C5A08ADF49B9A8523F7F81925C0111E6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59D9E69DB@GRFMBX702BA020.griffon.local> Hi Thierry, in response to your question ? TI: is it ok for device backend management (Zigbee part) or delayed in September. We assumed our integration is due for September. So we are working with this timeframe. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: gioved? 14 giugno 2012 11:50 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT: Update of testbed cockpit wiki page Priorit?: Alta Dear all, Another urgent topic but just a quick answer and I will update the wiki... Extract from Telefonica email: "The thing is that D10.3 (Integration Plan) is already delayed more than 3 months due to numerous adverse circumstances and we can almost release it now. It looks like all the problems have been tackled and there's just a last thing to deal with. There are tests related to GEs from IoT that are missing in the doc(or maybe they do not apply) but we need your inputs." We have just to fullfill the cockpit wiki page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit And you have the related email from Paolo Zampognaro. I assume that each of you have subscribed to this testbed mailing list because each developers team has to do it to managed the whole process from specifications to available code on the tesbed. The relevant actions for us are: ? NEC: is it ok for the IoT Broker or delayed in September ? Ericsson: is it ok for the Things management part in the Gateway or delayed in September ? TI: is it ok for device backend management (Zigbee part) or delayed in September. Based on the technical roadmap, the other are delayed in September. Thanks for your quick feedback. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com _________________________________________________________________________________________________________________________ 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. 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 Tobias.Jacobs at neclab.eu Thu Jun 14 15:32:11 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 14 Jun 2012 13:32:11 +0000 Subject: [Fiware-iot] URGENT APs befor Review In-Reply-To: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D08BF0F9B@Polydeuces.office.hd> Hi Thierry, Please find my comments in green below. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: Donnerstag, 14. Juni 2012 09:44 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] URGENT APs befor Review Importance: High Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: ? technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! ? Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and D?nes should also remove it from the architecture figure. tomorrow EOB For NEC it is ok to delete the the configuration interface. However, it is an interface of Telefonica's Configuration Management component, so they should decide on that. Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB I think this "revised-under construction" page has been started by Juanjo, so I do not feel competent to decide what is useful there and what is not. For me it would be ok to remove it, but again this is rather Telefonica's decision. Backend Device Management: we have something, but not compliant to the guidelines. D?nes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB ? SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) Done (by Salvatore). ? Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) ? User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) ? Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? OK, I added the test page by SAP to the unit test page of the Backend Things Management GE in the public wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Backend_Things_Management_-_Unit_Testing_Plan#Test_Description Backend Device Management: D?nes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ _________________________________________________________________________________________________________________________ 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. ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Thu Jun 14 15:45:17 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 14 Jun 2012 13:45:17 +0000 Subject: [Fiware-iot] URGENT APs befor Review In-Reply-To: <8755F290097BD941865DC4245B335D2D08BF0F9B@Polydeuces.office.hd> References: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D08BF0F9B@Polydeuces.office.hd> Message-ID: <29579_1339681518_4FD9EAEE_29579_3171_1_976A65C5A08ADF49B9A8523F7F81925C01139D@PEXCVZYM13.corporate.adroot.infra.ftgroup> HI Tobias Thanks a lot for your reactivity. I'm on line with your comments. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : jeudi 14 juin 2012 15:32 ? : NAGELLEN Thierry RD-BIZZ; fiware-iot at lists.fi-ware.eu; Juanjo Hierro; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Objet : RE: URGENT APs befor Review Hi Thierry, Please find my comments in green below. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: Donnerstag, 14. Juni 2012 09:44 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] URGENT APs befor Review Importance: High Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: ? technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! ? Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and D?nes should also remove it from the architecture figure. tomorrow EOB For NEC it is ok to delete the the configuration interface. However, it is an interface of Telefonica's Configuration Management component, so they should decide on that. Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB I think this "revised-under construction" page has been started by Juanjo, so I do not feel competent to decide what is useful there and what is not. For me it would be ok to remove it, but again this is rather Telefonica's decision. Backend Device Management: we have something, but not compliant to the guidelines. D?nes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB ? SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) Done (by Salvatore). ? Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) ? User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) ? Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? OK, I added the test page by SAP to the unit test page of the Backend Things Management GE in the public wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Backend_Things_Management_-_Unit_Testing_Plan#Test_Description Backend Device Management: D?nes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ _________________________________________________________________________________________________________________________ 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. ________________________________ ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " _________________________________________________________________________________________________________________________ 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 sabrina.guerra at telecomitalia.it Thu Jun 14 17:56:45 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Thu, 14 Jun 2012 17:56:45 +0200 Subject: [Fiware-iot] R: URGENT APs befor Review In-Reply-To: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59D9E6AE8@GRFMBX702BA020.griffon.local> Hi all, we updated the Protocol Adapter GE wiki page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter#Contacts) adding information about the ZigBee Protocol Adapter. Moreover we've an observation about the second picture in the page: the Protocol Adapter Interface looks like it's an external interface outside the gateway, while it should be an interface between protocol adapter interface and the Gateway Device Management GE. Please have a look to the attached picture to see what we mean. If you agree you may modify the corresponding FMC image. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: gioved? 14 giugno 2012 09:44 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT APs befor Review Priorit?: Alta Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: ? technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! ? Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and D?nes should also remove it from the architecture figure. tomorrow EOB Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB Backend Device Management: we have something, but not compliant to the guidelines. D?nes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB ? SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) ? Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) ? User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) ? Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? Backend Device Management: D?nes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ _________________________________________________________________________________________________________________________ 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. ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " 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: ModifiedProtocolAdapterImage.jpg Type: image/jpeg Size: 40340 bytes Desc: ModifiedProtocolAdapterImage.jpg 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 denes.bisztray at nsn.com Fri Jun 15 15:51:27 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 15 Jun 2012 15:51:27 +0200 Subject: [Fiware-iot] Tracker and Materializing Wiki Message-ID: <3F4C11BC54A36642BFB5875D599F47BD060820E4@DEMUEXC013.nsn-intra.net> Dear All, Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync. 1. Please check the tracker in case we made some errors. 2. Whenever someone makes changes to one, should change the other as well. Please keep this in mind. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakob.saros at ericsson.com Fri Jun 15 17:20:50 2012 From: jakob.saros at ericsson.com (Jakob Saros) Date: Fri, 15 Jun 2012 17:20:50 +0200 Subject: [Fiware-iot] URGENT APs befor Review In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A59D9E6AE8@GRFMBX702BA020.griffon.local> References: <10487_1339659846_4FD99646_10487_586_14_976A65C5A08ADF49B9A8523F7F81925C010FE0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <36A93B31228D3B49B691AD31652BCAE9A59D9E6AE8@GRFMBX702BA020.griffon.local> Message-ID: <9870BEE781B2694BA446B8FD65882E8546466E02D5@ESESSCMS0363.eemea.ericsson.se> Hi Sabrina, Thanks for pointing this out! You are indeed correct. I took the liberty of updating this myself since I noticed that the original FMC was not in the svn so it would have been difficult for you to update. It's added now btw. BR, Jakob ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Guerra Sabrina Sent: den 14 juni 2012 17:57 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] R: URGENT APs befor Review Hi all, we updated the Protocol Adapter GE wiki page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter#Contacts) adding information about the ZigBee Protocol Adapter. Moreover we've an observation about the second picture in the page: the Protocol Adapter Interface looks like it's an external interface outside the gateway, while it should be an interface between protocol adapter interface and the Gateway Device Management GE. Please have a look to the attached picture to see what we mean. If you agree you may modify the corresponding FMC image. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: gioved? 14 giugno 2012 09:44 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT APs befor Review Priorit?: Alta Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: ? technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! ? Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and D?nes should also remove it from the architecture figure. tomorrow EOB Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB Backend Device Management: we have something, but not compliant to the guidelines. D?nes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB ? SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) ? Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) ? User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) ? Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? Backend Device Management: D?nes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com ________________________________ _________________________________________________________________________________________________________________________ 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. ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " 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:269521615 at 15062012-02DF]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 sabrina.guerra at telecomitalia.it Fri Jun 15 18:55:17 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 15 Jun 2012 18:55:17 +0200 Subject: [Fiware-iot] R: Tracker and Materializing Wiki In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD060820E4@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD060820E4@DEMUEXC013.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59DDCD736@GRFMBX702BA020.griffon.local> Hi Denes and Lorant, thanks for your work in which you've reorganized the backlogs. We've analyzed the issues assigned to me and we report our observations: ? Many issues are related to the Advanced Connectivity GE that, as far as I know, is not covered by any assets, both in the backend and in the gateway. They are 97 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.MobilityManagement 101 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.TrafficFlowManagement 104 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.QualityOfServiceControl 1840 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.MobilityManagement 1841 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.SessionManagement 1842 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.TrafficFlowManagement 1843 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.QualityOfServiceControl 1861 FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.M2MDeviceSessionManagement 1862 FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.NativeDeviceSessionManagement ? There are two issues that perhaps have a wrong name because the ConnectivityStatusManagement in my opinion is actually the DiscontinuousConnectivity in the Device Management GE 555 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.ConnectivityStatusManagement 1844 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.ConnectivityStatusManagement ? About the Security GE I don't know who is the partner which will provide it. So there are two epics that are in the Security GE 102 FIWARE.Epic.IoT.Backend.Security.AccessPolicyControl 1845 FIWARE.Epic.IoT.Gateway.Security.AccessPolicyControl ? A question for Ericsson: does your asset implement AddressTranslation module (that is: The IoT resources must be addressable both at application and at device/gateway level so there must be a mechanism to translate the incoming addresses to an internal unified platform address to identify each resource)? 558 FIWARE.Epic.IoT.Gateway.DeviceManagement.AddressTranslation ? Finally there are some themes that perhaps have an incorrect name. ConnectivityManagement should be AdvancedConnectivity and Service Control should be DeviceManagement 584 FIWARE.Theme.IoT.Backend.ConnectivityManagement 1868 FIWARE.Theme.IoT.Gateway.ConnectivityManagement 585 FIWARE.Theme.IoT.Backend.ServiceControl 1867 FIWARE.Theme.IoT.Gateway.ServiceControl Do you agree with our observations or do you have any other opinions? Best regards, Sabrina and Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest) Inviato: venerd? 15 giugno 2012 15:51 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Tracker and Materializing Wiki Dear All, Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync. 1. Please check the tracker in case we made some errors. 2. Whenever someone makes changes to one, should change the other as well. Please keep this in mind. Best, D?nes 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 Jun 18 12:27:31 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 18 Jun 2012 13:27:31 +0300 Subject: [Fiware-iot] R: Tracker and Materializing Wiki In-Reply-To: A<36A93B31228D3B49B691AD31652BCAE9A59DDCD736@GRFMBX702BA020.griffon.local> References: <3F4C11BC54A36642BFB5875D599F47BD060820E4@DEMUEXC013.nsn-intra.net> A<36A93B31228D3B49B691AD31652BCAE9A59DDCD736@GRFMBX702BA020.griffon.local> Message-ID: <93D28BDF64839C468B848D14227151A2039D6D51@FIESEXC014.nsn-intra.net> Hi Sabrina, Thank you very much for the action. Please find my comments inline. Thanks & Br, Lorant From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Guerra Sabrina Sent: Friday, June 15, 2012 6:55 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] R: Tracker and Materializing Wiki Hi Denes and Lorant, thanks for your work in which you've reorganized the backlogs. We've analyzed the issues assigned to me and we report our observations: ? Many issues are related to the Advanced Connectivity GE that, as far as I know, is not covered by any assets, both in the backend and in the gateway. They are 97 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.MobilityManagement 101 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.TrafficFlowManagement 104 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.QualityOfServiceControl 1840 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.MobilityManagement 1841 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.SessionManagement 1842 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.TrafficFlowManagement 1843 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.QualityOfServiceControl 1861 FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.M2MDeviceSessionManagement 1862 FIWARE.Feature.IoT.Gateway.AdvancedConnectivity.SessionManagement.NativeDeviceSessionManagement Yes, advanced connectivity is a new GE accoring to the new streamlined architecture and there is no identified asset so far for them. If you check the technical roadmap, we should provide this GE in the backend by the 2nd major release (Q3 of 2013). In addition, there is nothing mentioned in the technical roadmap about QoS control, traffic flow management etc, just the discontinuous connectivity. Additionally, advanced connectivity is not mentioned in the gateway scope at all. Action items as a result (I would recommend to please put them as "work items" in the forge to show progress - if not done by EOB tomorrow, I would do it myself on Wednesday, we were criticized because of not showing progress of the work in the tracker): 1. identify assets for advanced connectivity GE - Sabrina/Gian Piero. I would start this by asking around from partners with more detailed info on how you see such an asset. This could be even a topic for our next weekly call. One could maybe start with exploring those assets that provide backend/gateway side device management. You could organize a meeting with the owners of device management-related assets in the first round. Name of the work item could end with AssetIdentification or something like that 2. if no assets are identified, propose this as a topic for the next open call - Sabrina/Gian Piero. No need to record this as a work item now 3. start editing the technical roadmap from the perspective of this GE, put the features of the advanced connectivity GE in the releases - Sabrina/Gian Piero. As a safe approach one could put every item in the final release, for now, and then follow it up, once we have the feedback from the asset owner dealing with discontinuous connectivity. Name of the work item could end with RoadmapUpdate or something like that ? There are two issues that perhaps have a wrong name because the ConnectivityStatusManagement in my opinion is actually the DiscontinuousConnectivity in the Device Management GE 555 FIWARE.Epic.IoT.Backend.AdvancedConnectivity.ConnectivityStatusManagement 1844 FIWARE.Epic.IoT.Gateway.AdvancedConnectivity.ConnectivityStatusManagement 4. Change the info in the technical roadmap concerning the statement on advanced connectivity - discontinuous connectivity belongs to Device Management - Sabrina/Gian Piero. No need to record this as a work item 5. Please put these epics under the Device Management GE - Sabrina/Gian Piero. No need to record this as a work item ? About the Security GE I don't know who is the partner which will provide it. So there are two epics that are in the Security GE 102 FIWARE.Epic.IoT.Backend.Security.AccessPolicyControl 1845 FIWARE.Epic.IoT.Gateway.Security.AccessPolicyControl 6. Action on Lorant/Denes/Thierry to have a work item on identifying an asset, communicating with the security WP leader etc. ? A question for Ericsson: does your asset implement AddressTranslation module (that is: The IoT resources must be addressable both at application and at device/gateway level so there must be a mechanism to translate the incoming addresses to an internal unified platform address to identify each resource)? 558 FIWARE.Epic.IoT.Gateway.DeviceManagement.AddressTranslation 7. Could you please directly address this question to them, they might not even read this row hidden in the details, but if they see their name, they will react - Gian Piero/Sabrina ? Finally there are some themes that perhaps have an incorrect name. ConnectivityManagement should be AdvancedConnectivity and Service Control should be DeviceManagement 584 FIWARE.Theme.IoT.Backend.ConnectivityManagement 1868 FIWARE.Theme.IoT.Gateway.ConnectivityManagement 585 FIWARE.Theme.IoT.Backend.ServiceControl 1867 FIWARE.Theme.IoT.Gateway.ServiceControl 8. We agree, could you please update them? - Gian Piero/Sabrina Do you agree with our observations or do you have any other opinions? Best regards, Sabrina and Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest) Inviato: venerd? 15 giugno 2012 15:51 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Tracker and Materializing Wiki Dear All, Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync. 1. Please check the tracker in case we made some errors. 2. Whenever someone makes changes to one, should change the other as well. Please keep this in mind. Best, D?nes 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. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From sabrina.guerra at telecomitalia.it Mon Jun 18 15:25:00 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Mon, 18 Jun 2012 15:25:00 +0200 Subject: [Fiware-iot] R: R: Tracker and Materializing Wiki In-Reply-To: <93D28BDF64839C468B848D14227151A2039D6D51@FIESEXC014.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD060820E4@DEMUEXC013.nsn-intra.net> A<36A93B31228D3B49B691AD31652BCAE9A59DDCD736@GRFMBX702BA020.griffon.local> <93D28BDF64839C468B848D14227151A2039D6D51@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59DDCDA39@GRFMBX702BA020.griffon.local> Hi Lorant, we've done point 8 of your reply. Best regards, Sabrina Da: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Inviato: luned? 18 giugno 2012 12:28 A: Guerra Sabrina; fiware-iot at lists.fi-ware.eu Oggetto: RE: [Fiware-iot] R: Tracker and Materializing Wiki Hi Sabrina, Thank you very much for the action. Please find my comments inline. Thanks & Br, Lorant ? Finally there are some themes that perhaps have an incorrect name. ConnectivityManagement should be AdvancedConnectivity and Service Control should be DeviceManagement 584 FIWARE.Theme.IoT.Backend.ConnectivityManagement 1868 FIWARE.Theme.IoT.Gateway.ConnectivityManagement 585 FIWARE.Theme.IoT.Backend.ServiceControl 1867 FIWARE.Theme.IoT.Gateway.ServiceControl 8. We agree, could you please update them? - Gian Piero/Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest) Inviato: venerd? 15 giugno 2012 15:51 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Tracker and Materializing Wiki Dear All, Lorant and myself compared the updated Materializing Internet of Things (IoT) Services Enablement in FI-WARE wikipage with the Forge Tracker. Now they are in complete sync. 1. Please check the tracker in case we made some errors. 2. Whenever someone makes changes to one, should change the other as well. Please keep this in mind. Best, D?nes Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CD4D66.86CF7C00]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From lorant.farkas at nsn.com Tue Jun 19 10:22:47 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 19 Jun 2012 11:22:47 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2039D71C4@FIESEXC014.nsn-intra.net> When: 2012. j?nius 20. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Cancelled because of Y1 review. Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10379 bytes Desc: not available URL: From lorant.farkas at nsn.com Tue Jun 19 10:23:38 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 19 Jun 2012 11:23:38 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2039D71C5@FIESEXC014.nsn-intra.net> When: 2012. j?nius 20. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Cancelled because of Y1 review. Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10293 bytes Desc: not available URL: From sabrina.guerra at telecomitalia.it Tue Jun 19 17:53:22 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 19 Jun 2012 17:53:22 +0200 Subject: [Fiware-iot] New Features for Protocol Adapter Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59DDCDF01@GRFMBX702BA020.griffon.local> Hi all, in order to provide an accurate and complete description of the Protocol Adapter GE we added a number of features both in the tracker and in the wiki page "Materializing Internet of Things (IoT) Services Enablement in FI-WARE" at the section "Gateway Protocol Adapter GE". Moreover we've updated the Junit tests list at the following links : https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/IoT_Private_Wiki_Page_for_Unit_Testing_Plan and http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Gateway_Protocol_Adapter_-_Unit_Testing_Plan adding the references to the features that the single tests relate. Best regards, Sabrina and Gian Piero Da: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 13 giugno 2012 10:22 A: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware] IMPORTANT REMINDER: Fwd: Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE Hi all, This is a reminder of the task that partners implementing the different GEs should be taking care of. The most urgent things you should be working on since some time, because they required some time, were: * the addition of features that, complementing the existing ones, provide a accurate and complete description of the features by the GE * the development of the unit testing programs to be run in order to test the different features For the former, it is clear where they are placed (Materializing the FI-WARE Vision) and the format is also clear since months. The second is a matter of having the required unit testing programs ready, each GE will have its own suite of unit testing programs. Soon we will provide instructions about how to write down the wiki page for the Unit Testing Plan linked to each GE. Best regards, -- Juanjo -------- Original Message -------- Subject: Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE Date: Mon, 28 May 2012 23:34:41 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, As you know, a Unit Testing Plan deliverable has to be produced for each of the GEs to be released as part of the first FI-WARE Release. Note that this Unit Testing Plan has nothing to do with the Integration Testing Plan which has been asked by the Testbed Chapter team. The approach proposed to tackle this deliverable was initially shared in April 10th, and was approved after the integration of some of the compiled comments during the joint WPLs/WPAs confcall that took place in May 7th. Here, we will try to elaborate on the details about how to generate this deliverable per GE on the public wiki. The very first step will be extend the set of Features listed for each GE within the corresponding section of the "Materializing the FI-WARE Vision" part of the public wiki. As per now, each GE was supposed to have already a number of Features, Epics and User-Stories listed on the "Materializing the FI-WARE Vision" part of the wiki. However, listed Features were supposed to only map to new features to be incorporated in the baseline assets for the first FI-WARE Release (i.e., features that required some sort of development on the baseline asset). Now, we will extend these list of Features so that the whole list of Features provide a comprehensive and complete description of the set of features that will be supported by the GE in the first FI-WARE Release. Note that with this first step, we hope that we will be able to address some of the comments made by reviewers on the "FI-WARE Technical Roadmap" deliverable, arguing that the information provided in that deliverable was too abstract (see [1]). Making this first step, we will be able to add a link to the set of features to be supported by each FI-WARE GE from the "FI-WARE Technical Roadmap" deliverable. This way, the argument about lack of concreteness should fly away. Once we have completed the set of Features for a given GE and listed them within the corresponding section inside the "Materializing the FI-WARE Vision" part of the wiki, we will create a last section, right after the section listing the User-Stories, that will be titled "Unit Testing Plan" and will contain a link to a wiki page describing the Unit Testing Plan that will be applied to the GE. This wiki page will be titled " - Unit Testing Plan" and will be structured into one section titled "Information Common to all tests" and then several sections, each linked to a Unit Test. Each Unit Test, will contain: * a subsection titled "Tested Features" which contains a list of links to the wiki pages describing the Features that are tested through the Unit Test * a subsection titled "Test description" which contains detailed information about: * what client programs and (potentially) data sets will be used to run the test * how to run the test: * this should be detailed enough to allow an administrator/operator of a FI-WARE Instance to test if the GE is working properly * dependencies on third party libraries or software should be specified * expected results to be obtained by running the client programs with the referred data set * (note: it would be highly recommended to define a maven project which would be used to run the test and where all dependencies are specified Note that a separate Unit Test may be defined per tested Feature. However, this is not mandatory so a given Unit Test may be used to test several features. What is important is that the Test description provides the information that is needed to run the tests, not only by the developer of the GE but also by any party (e.g., an administrator/operator of a FI-WARE Instance containing that GE) who decides to use the Unit Testing Plan to verify that the GE is working properly in a given FI-WARE Instance setup. A link to the corresponding section in the Unit Testing Plan document at the wiki will be included in a "how-to-test" field of the corresponding backlog entry. We will soon inform you whether this field will be created in the template linked to Features descriptions in the public Wiki or in the ticket at the tracker that corresponds to the Feature. We couldn't provide a reference example of the formula described above because the wiki was down, but we hope to provide it along this week. Nevertheless, don't hesitate to make any question or complement this proposal. Your input is more than welcome. Please, share these instructions with members of your respective teams. [1] - Comments from reviewers: * The vague description of functionalities (such as "Extended support for network context data management and resource management") will not allow the Use Case projects to understand the FI-WARE propositions correctly, might lead to wrong expectations and might create further difficulties in the collaboration * Listing feature deliverables as a set of abilities is also unacceptable. The roadmap should instead indicate the delivery schedule for precise Generic Enablers, which should then be described in terms of the abilities they will provide. 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 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 sabrina.guerra at telecomitalia.it Thu Jun 21 13:39:56 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Thu, 21 Jun 2012 13:39:56 +0200 Subject: [Fiware-iot] vacations Message-ID: <36A93B31228D3B49B691AD31652BCAE9A59DDCE4A0@GRFMBX702BA020.griffon.local> Hi all, Next two weeks I am on holiday but Gian Piero will be present. Best regards, Sabrina 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 Jun 26 07:47:08 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 26 Jun 2012 08:47:08 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203A5C0EE@FIESEXC014.nsn-intra.net> When: 2012. j?nius 27. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's have the next weekly call around the following topics: 1. Outcomes of the review 2. Next steps, next todos for the partners in the IoT WP Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10541 bytes Desc: not available URL: From kzangeli at tid.es Wed Jun 27 08:49:10 2012 From: kzangeli at tid.es (KEN GUNNAR ZANGELIN) Date: Wed, 27 Jun 2012 08:49:10 +0200 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A203A5C0EE@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203A5C0EE@FIESEXC014.nsn-intra.net> Message-ID: <73E88672-53C5-48A3-ADC5-3D539685C3ED@tid.es> Hi all, I won't be able to make it for the telco today, because of a doctor's appointment. /KZ On Jun 26, 2012, at 07:08 , Farkas, Lorant (NSN - HU/Budapest) wrote: When: 2012. j?nius 27. 10:00-11:30 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let?s have the next weekly call around the following topics: 1. Outcomes of the review 2. Next steps, next todos for the partners in the IoT WP Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let?s resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant 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 ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 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 ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 9369002 Making a conference call * from the office: 8071870 (in Finland and Germany) * from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click ?Support?. You can contact me at: lorant.farkas at nsn.com Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ 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 Tobias.Jacobs at neclab.eu Wed Jun 27 10:13:15 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 27 Jun 2012 08:13:15 +0000 Subject: [Fiware-iot] phone problem Message-ID: <8755F290097BD941865DC4245B335D2D08BFB493@PALLENE.office.hd> Hi, we are having a phone problem here, we wil try to reconnect to the confcall as soon as possible. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jun 27 12:32:07 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 27 Jun 2012 13:32:07 +0300 Subject: [Fiware-iot] weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A203A5C97D@FIESEXC014.nsn-intra.net> Dear All, Please find the minutes of the weekly call under https://forge.fi-ware.eu/docman/view.php/11/1130/IoT-Minutes-Telco-27062 012.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jun 27 12:56:21 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 27 Jun 2012 13:56:21 +0300 Subject: [Fiware-iot] Raw notes from the review Message-ID: <93D28BDF64839C468B848D14227151A203A5C9C3@FIESEXC014.nsn-intra.net> Dear All, Please find this information from the review that we also discussed during our weekly call. 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: Friday, June 22, 2012 5:00 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Raw notes from the review Hi, Please find below the raw notes that I got during the report made by Arian right after the review meeting. Cheers, -- Juanjo === Positive points: you appear as a team and relaxed. Project positive vision. You believe in what are you doing and we believe it is real. effort in collaboration, communication and dissemination sounds pretty good but strategic plan should be pretty Engineering contribution is pretty good. DevCommE, should name is still a disaster :-) Technical work is better that the way is presented. People are serious and show High enphasis on software that works. That is minimum should I2ND: has progressed significantly Security: good progress, example to the rest FI-WARE still a normal FP7 project but the PPP Testbed: good progress, like matrix on usage by UC usage No so positive: Thinking "good technology" sells itself alone and this is native Too many times "this will come later" ("ma?ana") Difficult to distinguish Discrepancies in the backlog that have to be fixed Discrepancies in the management reports (e.g. Zigbee according to Relaxed attitude wrt delay To improve regarding impact. Example is the Website. Economic model behind (business case) has to be considered more and earlier. Should be clear. Nice that you mention that you are starting to involve the Business but has to be visible. Lack of justification and accountability in deliverables. It's not only about White paper regarding encompassing of GEs will be important Distinction between GEs and SEs Management has improved. Workload has been distributed. Some partners are not that visible. In the reporting it should be visible what each is doing, overall academia partners. Architectural weeks very positive and we encourage to continue this in the future. Recommendations: Like to see evidence of using the FI-WARE Testbed from UC projects. They assume that they will start right after Measure point sometime mid September / October regarding usage of FI-WARE Testbed Some of the GEs might seem not to be critical then and therefore it might be then a point at which it would be sensible to reconsider what is being done. Should be a plan for justification and accountability. They need to check how recommendations have been Different templates being used regarding the Open Specifications. Clean up backlog and continues correct. Restricted GEs (SAP) should be publicly available by end of July. Business Model WG at FI-PPP should be a useful tool as a vehicle to discuss the Business aspects. Next review in FI-WARE Testbed location (Sevilla ?) in month 18. They want to see people from the Business Units: Telefonica, SAP, Telecom Italia and Orange. Would like to see planning regarding training of DevCommE Deliverables: They will not comment on that now. We'll see in the report. === -- ------------- 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 Wed Jun 27 12:59:40 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 27 Jun 2012 13:59:40 +0300 Subject: [Fiware-iot] Wiki page with description of numeration schema in thetrackers Message-ID: <93D28BDF64839C468B848D14227151A203A5C9C8@FIESEXC014.nsn-intra.net> Dear All, Please find attached information on releases numbers. This should be used whenever you update the features in the tracker. 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: Wednesday, June 20, 2012 5:46 AM 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] Wiki page with description of numeration schema in thetrackers Hi all, Please find in the following link a description of the numbering schema to follow. That way, this importan information is not lost in the emails. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering The link is on the "Getting Started with FI-WARE" section of the home page of the Wiki and is also part of the Project Handbook (not only the home list for members of the FI-WARE team but also when describing how to create entries on the tracker) and is also referred from the wiki page elaborating on adoption of Agile in FI-WARE: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Main_Page#Handbook_for_the_FI-WARE_team http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology#Management_of_the_FI-WARE_Backlog 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 On 14/06/12 17:24, Juanjo Hierro wrote: Dear all, Unfortunately, we made a mistake with the numbering of Releases and Sprints in our previous mail sent by Miguel Carrillo. We apologize for that and thanks to Alex Glikson for pointing it out. Sprints actually started in November 2011. Therefore, the right Sprint numbers until April are the following: Nov 11: 1.1.1 Dec 11: 1.1.2 Ene 12: 1.1.3 Feb 12: 1.2.1 Mar 12: 1.2.2 Abr 12: 1.2.3 As you know, we have extended the duration of the development of the first Release until end of June, and we should be consistent with that. This means that we should have planned three additional Sprints, entering into a 1.3 Minor Release, regarding activities linked to those GEs that will be delivered by end of June and will be available on the FI-WARE Testbed by end of July: May 12: 1.3.1 Jun 12: 1.3.2 Jul 12: 1.3.3 The Sprint in July (1.3.3) should be focused on carrying out activities linked to setup the delivered GEs in the FI-WARE Testbed (these activities typically to be registered in the backlogs as Work Items). During that Sprint, you may also plan some last-minute developments. Note that Features that we may have planned for a given minor release (e.g., release 1.2) but couldn't be implemented by end of that minor release should be replanned for a future minor release, typically the next one if it were a matter of lacking of time (wrong estimation). We should have followed this rule during your development. You should always reflect such re-plannings by means of updating the ReleaseId field in the re-planned Features. The release id of a given Feature should always identify the Minor Release at which it is planned that all developments linked to implementation of the Feature have been completed (therefore the feature is completely supported in the product). This means that if you hadn't finished the development of Feature X in release 1.2, which is when it was initially planned, you should update the release id of Feature X to become release 1.3. Note also that we announced that some features of some of the GEs initially planned for the 1st Major Release would not be available on the Testbed until end of September. These means that we have extended duration of the development for those GEs and, again, we should be consistent with that. For such GEs, the Sprint numbering we suggest to follow in the period from start of July until end of September is the following: Jul 12: 1.3.3 Aug 12: 1.4.1 Sep: 1.4.2 There are GEs that will be delivered as part of Major Release 1 but will further evolve in Major Release 2. When do activities for Release 2 start for such GEs ? * They will start in August for those GEs that will make available all features planned for Release 1 by end of July in the FI-WARE Testbed * They will start in October for those GEs that will make available all features planned for Release 1 by end of September in the FI-WARE Testbed In order to make sure that numbering of all Sprints linked to the 2nd Major Release get synchronized for all GEs from October on, we suggest to adopt the following numbering of Sprints: Aug 12: 2.0.1 Sep 12: 2.0.2 Oct 12: 2.1.1 Nov 12: 2.1.2 Dec 12: 2.1.3 Note that during August and September, there will be some GEs that will be running Sprints numbered as 1.4.1 and 1.4.2, while there will be GEs that will be running Sprints numbered as 2.0.1 and 2.0.2. This should all be natural because this simply reflects that the developments under 1.4.1 and 1.4.2 are officially part of Release 1, to be made available on the Testbed by end of September, while developments under 2.0.1 and 2.0.2 are officially part of Release 2. We will not allow updates of the FI-WARE Testbed linked to Release 2 developments until end of October 2012. Those updates would integrate results of Sprint 2.1.1 in all cases and, for those GEs whose development had started earlier in August, those updates should also incorporate results from Sprints 2.0.1 and 2.0.2. The idea is to allow upgrades of the FI-WARE Testbed every Sprint following an Agile approach from then on. Note, however, that updating the software that implements a given GE will not be mandatory at the end of each Sprint during Release 2, it would be just optional (some GE owners may be interested in this to gather feedback from UC projects as early as possible). Updating the software at least every minor release (i.e., every three months) would be the default option. There are some GEs for which development have started earlier than August 12. No problem if you followed the numbering linked to Sprints under Release 1 until that month. From August on, just adopt the numbering suggested above for Sprints linked to Release 2. Please make sure you keep consistent with this overall numbering of Releases when updating trackers linked to your chapter. We will document all this on the Wiki, so this info becomes available at any time. Thanks to those who raised the need for doing so. 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 On 13/06/12 17:13, Miguel Carrillo wrote: Dear all, The information sent by Fernando at the end of this message is of high importance and it has to be understood. We have to use a consistent terminology for Releases and Sprints in the project. We have checked it in the backlog and unfortunately it is not always the case. I attach the excel file we used to deliver the backlog to the EC, based on a snapshot of the backlog trackers of the chapters taken last Friday. To understand what we mean, you can check the modifications we made to the sprint and release fields by hand on the spreadsheet. Those chapters who do not have User Stories in Release 1.3 (more precisely, Sprint 1.3.1), are sending the message that they are doing nothing now (hopefully not the case!). Please amend it. This convention of Releases and Sprints is something general, this means that a given chapter cannot decide autonomously to follow a different schedule/numbering. We need to show a coherent face to the outside world. I send you this directly as this is of general interest and the WPAs/WPLs are focusing on the upcoming review, it must get to everyone. Best regards, Miguel -------- Mensaje original -------- Asunto: [FIWARE] Wrong numeration schema in the tracker... Fecha: Wed, 13 Jun 2012 12:03:23 +0200 De: FERNANDO LOPEZ AGUILAR A: Irena Trajkovska , Javier Cervi?o , Joaquin Salvachua CC: MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA , "fiware-cloud at lists.fi-ware.eu" Dear Javier and Irena, I was checking the tracker and I could see some inconsistencies in the tracker numeration. Please check it taking into account the following indication. FIWARE.Release.x.y FIWARE.Sprint.x.y.z Dic Ene Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dic Release 1.1 1.1 1.1 1.2 1.2 1.2 1.3 Sprint 1.1.1 1.1.2 1.1.3 1.2.1 1.2.2 1.2.3 1.3.1 Please consider that you cannot have an entry with assigned Sprint in a status Open should be either Closed or Under Execution. Please check all your entries in the tracker in order to check it and correct the possible wrong numeration schema ASAP. Best regards, Fernando L?pez Aguilar Cloud Computing fla at tid dot es +34 914 832 729 Telef?nica I+D (R&D) Ronda de la Comunicaci?n s/n Distrito C, Edificio Oeste 1, Planta 5 28050 Madrid, Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware ________________________________ 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 ________________________________ 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: ATT4718484.txt URL: From lorant.farkas at nsn.com Fri Jun 29 12:54:31 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 29 Jun 2012 13:54:31 +0300 Subject: [Fiware-iot] software delivery Message-ID: <93D28BDF64839C468B848D14227151A203A9AB50@FIESEXC014.nsn-intra.net> Dear All, FYI on software delivery and one question: who could upload here something very soon, to have something to show? Gian Piero: ZigBee HA binaries, perhaps? Jakob: OSGI from your gateway, perhaps? Tobias, Salvatore: something from you? Laurent: do you have something preliminary based on Android? Sorry once more for the short notice and in case of any questions please do not hesitate to ask. 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 Miguel Carrillo Sent: Wednesday, June 27, 2012 5: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] Software delivery (how to provide Deliverable D.x.2.a) Dear all, As editing the wiki will take a bit longer I will write a (rather long) email and will explain how to proceed with some aspects of the software delivery that were not clearly explained yet. Given the urgency of this I send it to the general list but please proceed to discuss any concerns internally in your respective WP lists. This message refers to software delivery. This means: * 1) Delivery for installation on the testbed(packages, properties and binaries) * 2) Source code delivery - this does not apply to those GE who have agreed not to provide it I will add all tall his to the private wiki later, putting alongside all the guidelines that are there already. First of all, the software delivery will take place on the forge. As regards the project within the forge, we will use the project of the WP (Iot, Data, Apps, Tools...) PART 1 - Delivery for installation on the testbed ======================================== The packages, properties and binaries go to the "Files" part of the project. We have already delivered a GE in cloud and you can use it as an example: * https://forge.fi-ware.eu/frs/?group_id=14 First you create a Package (this goes with the GE name) Then you create 3 blocks per GE (using the "Create New Release" feature) * Packages (rpm, debian... ) - this does not apply to the particular example we provide but it should apply in many cases in your GEs * Binaries * Properties - miscelaneous files Please follow the same naming convention for the 3 blocks (Packages, Binaries, Properties). Add all three even if one of them is empty in your particular case. I see that this deliverable is Public according to the DoW so this should be publicly available, not private (the WPL must administrate this). If there are any particular concerns, let me know (privately - please do not reply to this email, it gets to more than 100 people!). For the WPL/WPA - hint: if you still cannot see this publicly, go to the admin part of the "Users" of the "Admin" section of the project and tweak the "Observer" user. (this is not visible to most users, just those with admin right on the project) PART 2 - Delivery of source code ======================================== Depending on the GE, you may have decided to provide this or not. We would expect this for most of the GEs. This goes to the "SCM" tool in the project. There you have a link to subversion where you can upload all the software. The admin of each WP (WPL and WPA, please proceed to do so) has the right to make their SCM public on the internet on the admin page of the SCM: It is "all or nothing". Once this is made public, you cannot hide branches. Let us settle this: the SVN will be made public for each technical WP so the code that is uploaded here will be public. If something is private, you will not upload it here. When the testbed environment is fully set up we will send further instructions to provide extended info for the deployment (we will ask for maven - *.pom files - or test scripts, for instance). But this is not strictly necessary to meet the deadline that is upon us so we will do it later (but very soon!) 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: efiedbge.png Type: image/png Size: 6424 bytes Desc: efiedbge.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bfehcjbg.png Type: image/png Size: 8244 bytes Desc: bfehcjbg.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ddjafjfg.png Type: image/png Size: 3857 bytes Desc: ddjafjfg.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hgjjbjad.png Type: image/png Size: 2746 bytes Desc: hgjjbjad.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT6384126.txt URL: