From T.Elsaleh at surrey.ac.uk Tue May 1 12:24:53 2012 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Tue, 1 May 2012 11:24:53 +0100 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D679E@EXMB05CMS.surrey.ac.uk> Hello Tobias, After going through the deliverable and familiarizing with the components of the GE, I would like to explain further the possible role for our (UoS) asset in the Things Management GE, i.e. what is currently termed the "inference engine", as it seems to look quite lonely in the architecture diagram. The purpose of the asset is to provide assistance for discovery of relevant things/resources when explicit querying does not provide any results. This could happen when values for attributes used for querying are not recognized by the repository platform, i.e. the configuration management component. In this case the IoT broker can make use of the "inference engine" for retrieving the closest results by using the attribute values as keywords and matching them to indexed entries for resources gathered at the time of publication. Technical details can be provided, but it would be good to understand the use of our asset in the first place. I've tried to illustrate this in the diagram attached. The term "inference engine" is somewhat generic and ambiguous. We suggest it be called either "discovery engine", or "discovery assistant engine" so as not to clash with the role of the IoT broker. I am noticing in the deliverable that it is being named "interference engine", but I hope it will not cause any interference with the other components in the GE. :) Any comments are welcome. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 27 April 2012 13:54 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. 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: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4959 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: unis-proposal-TM-GE-querying.png Type: image/png Size: 42185 bytes Desc: unis-proposal-TM-GE-querying.png URL: From jhierro at tid.es Wed May 2 09:24:35 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 02 May 2012 09:24:35 +0200 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A2036C5524@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2036C5524@FIESEXC014.nsn-intra.net> Message-ID: <4FA0E133.7080002@tid.es> Hi, I will try to attend this confcall, despite it's holiday in Madrid. I have taken a look at the draft of the Streamlined Architecture Description provided in the FI-WARE IoT private wiki. I believe contents need to be furthe elaborated before going public. Otherwise, many things would be left to interpretation and we should try to avoid it. I also wonder why we haven't reused many of the contents currently on the public Wiki which are still valid (I would say that the part that is more affected is the one on device-level management). From my point of view, much of what was there in the description of the IoT Broker and the Things/Resources Configuration Management applies "as is" ... or do we disagree here ? Preserving those pieces that were valid will be key in "selling" this last-minute update I guess ... 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 27/04/12 14:57, Farkas, Lorant (NSN - HU/Budapest) wrote: When: 2012. m?jus 2. 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 propose the following topics for our next meeting: 1. Architecture revisited: final polishing, report on our discussions with the chief architect 2. NGSI: NSN would give you a short demo on the implementation we have and we could have an update on the status of the specifications 3. Educational sessions: start discussing about the content of the presentations 4. M12 deliverables (exploitation plan, open specifications): status update 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) ________________________________ 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 May 2 09:43:33 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 2 May 2012 07:43:33 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D679E@EXMB05CMS.surrey.ac.uk> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D679E@EXMB05CMS.surrey.ac.uk> Message-ID: <8755F290097BD941865DC4245B335D2D08BCDCDB@Polydeuces.office.hd> Hi Tarek, Thanks a lot for your clarification regarding the 'discovery engine', formerly 'inference engine'. Let me ask some further questions. 1) Do I understand right that the Discovery Engine provides not the requested data itself, but references to IoT Resources? 2) If yes, would NGSI-9 be suitable as the interface between IoT Broker and Discovery Engine? Otherwise, would NGSI 10 be adequate? 3) What kind of communication takes place between the Discovery engine and the Configuration management? 4) Does the Discovery Engine also need access to actual data? Should this data come from the IoT Broker? Is NGSI-10 used for exchanging it? Please feel free to add you descriptions of the Discovery Engine to the private Wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement and create an updated version of the Things Management internal architecture FMC file in the svn (https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined-ThingsManagementGE-internal.graphml). Best regards Tobias From: T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Dienstag, 1. Mai 2012 12:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hello Tobias, After going through the deliverable and familiarizing with the components of the GE, I would like to explain further the possible role for our (UoS) asset in the Things Management GE, i.e. what is currently termed the "inference engine", as it seems to look quite lonely in the architecture diagram. The purpose of the asset is to provide assistance for discovery of relevant things/resources when explicit querying does not provide any results. This could happen when values for attributes used for querying are not recognized by the repository platform, i.e. the configuration management component. In this case the IoT broker can make use of the "inference engine" for retrieving the closest results by using the attribute values as keywords and matching them to indexed entries for resources gathered at the time of publication. Technical details can be provided, but it would be good to understand the use of our asset in the first place. I've tried to illustrate this in the diagram attached. The term "inference engine" is somewhat generic and ambiguous. We suggest it be called either "discovery engine", or "discovery assistant engine" so as not to clash with the role of the IoT broker. I am noticing in the deliverable that it is being named "interference engine", but I hope it will not cause any interference with the other components in the GE. :) Any comments are welcome. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 27 April 2012 13:54 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. 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: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4959 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Broker and NGSI interactions.pdf Type: application/pdf Size: 231276 bytes Desc: IoT-Broker and NGSI interactions.pdf URL: From jan.holler at ericsson.com Wed May 2 09:46:08 2012 From: jan.holler at ericsson.com (=?Windows-1252?Q?Jan_H=F6ller?=) Date: Wed, 2 May 2012 09:46:08 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> Message-ID: Dear Denes, A few questions and comments in return. * Does NEC provide the DH GE in the Gateway, and hence the NGSI interface? * Data Handling API comes from Gateway Device Mgmt GE (previously Core GE). What does it look like? Previously, Ericsson said to deliver a core Gw capability. Does this mean that the Gw DevMgmt GE can be omitted from Fiware and delivered by a use case project? Who will do this for the first integration, and what devices will be supported? * Who will deliver ETSI M2M compliant devices for the first release? * Who will deliver the ETSI M2M interface for the first release? * I also argue that having published interface to the "core" gateway GE is a good thing since it makes integration tasks with other assets easier, and that having that very simple is beneficial. Not relying on the fact that IETF CoRE exists and making good use of it is a bad decision. I note that our submission of a proposed modified FMC diagram on the Gateway part was not accepted, or did you not get it? I was in response to an action item from last week's meeting. I also think it is very unfortunate that you have separate meetings not involving those partners who are supposed to deliver assets. Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Friday, 27April, 2012 2:02 PM To: "thierry.nagellen at orange.com" >, "Farkas, Lorant (NSN - HU/Budapest)" >, ext Juanjo Hierro >, "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don?t mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don?t think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I?m unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 From lorant.farkas at nsn.com Wed May 2 09:51:06 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 2 May 2012 10:51:06 +0300 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> Message-ID: <93D28BDF64839C468B848D14227151A2036C5B8B@FIESEXC014.nsn-intra.net> Dear Jan, I am sure we can discuss all these within the 1st agenda point in our meeting today. Br, Lorant -----Original Message----- From: ext Jan H?ller [mailto:jan.holler at ericsson.com] Sent: Wednesday, May 02, 2012 9:46 AM To: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Denes, A few questions and comments in return. * Does NEC provide the DH GE in the Gateway, and hence the NGSI interface? * Data Handling API comes from Gateway Device Mgmt GE (previously Core GE). What does it look like? Previously, Ericsson said to deliver a core Gw capability. Does this mean that the Gw DevMgmt GE can be omitted from Fiware and delivered by a use case project? Who will do this for the first integration, and what devices will be supported? * Who will deliver ETSI M2M compliant devices for the first release? * Who will deliver the ETSI M2M interface for the first release? * I also argue that having published interface to the "core" gateway GE is a good thing since it makes integration tasks with other assets easier, and that having that very simple is beneficial. Not relying on the fact that IETF CoRE exists and making good use of it is a bad decision. I note that our submission of a proposed modified FMC diagram on the Gateway part was not accepted, or did you not get it? I was in response to an action item from last week's meeting. I also think it is very unfortunate that you have separate meetings not involving those partners who are supposed to deliver assets. Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Friday, 27April, 2012 2:02 PM To: "thierry.nagellen at orange.com" >, "Farkas, Lorant (NSN - HU/Budapest)" >, ext Juanjo Hierro >, "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 From lorant.farkas at nsn.com Wed May 2 11:44:02 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 2 May 2012 12:44:02 +0300 Subject: [Fiware-iot] tutorial on exploitation (D11.2, D11.3) Message-ID: <93D28BDF64839C468B848D14227151A2036C5CC0@FIESEXC014.nsn-intra.net> FYI. Thanks & Br, Lorant From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of ext Juan Bare?o Guerenabarrena Sent: Thursday, April 26, 2012 4:37 PM To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables- Action Plan Dear All Please find enclosed the action plan for the fulfillment of the WP11 Deliverables for the M12. First, we send you together the " 11.2 Pending tasks and tutorials" for its complementation. Be aware that for 11.2 and 11.3 most of your contributions are required to be fulfilled in the wiki (private) so in the table below you can find the appropriate direct links for that Thanks for your collaboration Juan Deliverable Section Activity Please follow the Private Link Who When 11.1 Market Analysis Market Analysis We will send around along this week the Market analysis with review tasks for each chapter regarding with their domain (Cloud, Data....) Private Document Atos 26/04/2012 All WPL review its chapter (Cloud, Data...) and maim conclusions Private Document All WP leaders 09/05/2012 D11.2 Exploitation Strategy, IPR Management and Sustainability FIWARE Exploitation Review the e-mail we sent previously with the first review of GE Business description on the 18th here All WP leaders 30/04/2012 IPR management Fill in the forge IPR section here All WP leaders fill in 30/04/2012 Sustainability Fill in. We include a first approach but we need the contribution from Test Bed part here Engineering 09/05/2012 Individual exploitation plans Review the new section here All partners 30/04/2012 D11.3 Market and Policy Awareness Market awareness We will send around along this week the first draft with review tasks for relevant partners Private Document Atos 26/04/2012 Indicated partners will review the deliverable and the main conclusions Private Document All WP leaders 09/05/2012 Identification of potential cities here All partners 09/05/2012 Identification of business associations and other bodies here All partners 09/05/2012 Commitment to host a national event here Thales 09/05/2012 Commitment to host a national event here Engineering &Telecom Italy 09/05/2012 Commitment to host a national event here SAP & DT in Germany 09/05/2012 Commitment to host a national event here Atos & Telefonica Spain 09/05/2012 Policy Awareness To fill the table Identification of relevance barriers here WP leaders 09/05/2012 Juan Bare?o Global Innovation, Business Development & Strategy Research & Innovation T +34 912148859 juan.bareno at atos.net Albarrac?n 25 28037 Madrid Spain www.atos.net www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Deliverable D11.2 Pending Actions and Tutorial.docx Type: application/octet-stream Size: 56977 bytes Desc: Deliverable D11.2 Pending Actions and Tutorial.docx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT6096326.txt URL: From T.Elsaleh at surrey.ac.uk Wed May 2 13:09:46 2012 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Wed, 2 May 2012 12:09:46 +0100 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCDCDB@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D679E@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D08BCDCDB@Polydeuces.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D6938@EXMB05CMS.surrey.ac.uk> Hello Tobias, Answers inline. I assume the term "querying" is used for data mainly. I guess the appropriate term is simply "discovering". Sorry for any mix-up I might have caused. Best regards, Tarek From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: 02 May 2012 08:44 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hi Tarek, Thanks a lot for your clarification regarding the 'discovery engine', formerly 'inference engine'. Let me ask some further questions. 1) Do I understand right that the Discovery Engine provides not the requested data itself, but references to IoT Resources? [T.E] yes, it returns references/metadata relating to the resource/thing in question 2) If yes, would NGSI-9 be suitable as the interface between IoT Broker and Discovery Engine? Otherwise, would NGSI 10 be adequate? [T.E] yes, I see NGSI-9 as the appropriate protocol for this. 3) What kind of communication takes place between the Discovery engine and the Configuration management? [T.E] Depending on the situation: - upon the publication of a resource/thing, the discovery engine retrieves from the Configuration Management (CM)/Repository the published metadata/description relating to the resource/thing, which the then parsed and indexed. This interaction would likely be initiated by the CM. - for updating, the CM informs the DE of the update for the particular resource/thing. - for deletion, the CM informs the DE of the deletion, so that DE deletes entry from its index. 4) Does the Discovery Engine also need access to actual data? Should this data come from the IoT Broker? Is NGSI-10 used for exchanging it? [T.E] no, this is not considered at this moment. Please feel free to add you descriptions of the Discovery Engine to the private Wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement and create an updated version of the Things Management internal architecture FMC file in the svn (https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined-ThingsManagementGE-internal.graphml). Best regards Tobias From: T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Dienstag, 1. Mai 2012 12:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hello Tobias, After going through the deliverable and familiarizing with the components of the GE, I would like to explain further the possible role for our (UoS) asset in the Things Management GE, i.e. what is currently termed the "inference engine", as it seems to look quite lonely in the architecture diagram. The purpose of the asset is to provide assistance for discovery of relevant things/resources when explicit querying does not provide any results. This could happen when values for attributes used for querying are not recognized by the repository platform, i.e. the configuration management component. In this case the IoT broker can make use of the "inference engine" for retrieving the closest results by using the attribute values as keywords and matching them to indexed entries for resources gathered at the time of publication. Technical details can be provided, but it would be good to understand the use of our asset in the first place. I've tried to illustrate this in the diagram attached. The term "inference engine" is somewhat generic and ambiguous. We suggest it be called either "discovery engine", or "discovery assistant engine" so as not to clash with the role of the IoT broker. I am noticing in the deliverable that it is being named "interference engine", but I hope it will not cause any interference with the other components in the GE. :) Any comments are welcome. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 27 April 2012 13:54 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. 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: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4959 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed May 2 13:26:46 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 2 May 2012 11:26:46 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D6938@EXMB05CMS.surrey.ac.uk> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D679E@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D08BCDCDB@Polydeuces.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCA5922D6938@EXMB05CMS.surrey.ac.uk> Message-ID: <8755F290097BD941865DC4245B335D2D08BCDE92@Polydeuces.office.hd> Dear Tarek, Thanks for your anwers. It is now much more clear to me. If you plan to complete the descriptions in the wiki and FMC accordingly, please make sure that you do not collide with Juanjo, who also plans to add something from tonight. Just out of curiosity: As far as I understood it, the Discovery Engine has exactly the same information as the Configuration Management has. Can you give an example of which additional information it can derive from that? Best Tobias From: T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Mittwoch, 2. Mai 2012 13:10 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hello Tobias, Answers inline. I assume the term "querying" is used for data mainly. I guess the appropriate term is simply "discovering". Sorry for any mix-up I might have caused. Best regards, Tarek From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: 02 May 2012 08:44 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hi Tarek, Thanks a lot for your clarification regarding the 'discovery engine', formerly 'inference engine'. Let me ask some further questions. 1) Do I understand right that the Discovery Engine provides not the requested data itself, but references to IoT Resources? [T.E] yes, it returns references/metadata relating to the resource/thing in question 2) If yes, would NGSI-9 be suitable as the interface between IoT Broker and Discovery Engine? Otherwise, would NGSI 10 be adequate? [T.E] yes, I see NGSI-9 as the appropriate protocol for this. 3) What kind of communication takes place between the Discovery engine and the Configuration management? [T.E] Depending on the situation: - upon the publication of a resource/thing, the discovery engine retrieves from the Configuration Management (CM)/Repository the published metadata/description relating to the resource/thing, which the then parsed and indexed. This interaction would likely be initiated by the CM. - for updating, the CM informs the DE of the update for the particular resource/thing. - for deletion, the CM informs the DE of the deletion, so that DE deletes entry from its index. 4) Does the Discovery Engine also need access to actual data? Should this data come from the IoT Broker? Is NGSI-10 used for exchanging it? [T.E] no, this is not considered at this moment. Please feel free to add you descriptions of the Discovery Engine to the private Wiki at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement and create an updated version of the Things Management internal architecture FMC file in the svn (https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined-ThingsManagementGE-internal.graphml). Best regards Tobias From: T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Dienstag, 1. Mai 2012 12:25 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; lorant.farkas at nsn.com Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Hello Tobias, After going through the deliverable and familiarizing with the components of the GE, I would like to explain further the possible role for our (UoS) asset in the Things Management GE, i.e. what is currently termed the "inference engine", as it seems to look quite lonely in the architecture diagram. The purpose of the asset is to provide assistance for discovery of relevant things/resources when explicit querying does not provide any results. This could happen when values for attributes used for querying are not recognized by the repository platform, i.e. the configuration management component. In this case the IoT broker can make use of the "inference engine" for retrieving the closest results by using the attribute values as keywords and matching them to indexed entries for resources gathered at the time of publication. Technical details can be provided, but it would be good to understand the use of our asset in the first place. I've tried to illustrate this in the diagram attached. The term "inference engine" is somewhat generic and ambiguous. We suggest it be called either "discovery engine", or "discovery assistant engine" so as not to clash with the role of the IoT broker. I am noticing in the deliverable that it is being named "interference engine", but I hope it will not cause any interference with the other components in the GE. :) Any comments are welcome. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 27 April 2012 13:54 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. 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: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. 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 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. 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 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4959 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed May 2 14:37:37 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 2 May 2012 15:37:37 +0300 Subject: [Fiware-iot] IoT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A2036C5E74@FIESEXC014.nsn-intra.net> Dear All, This is the link to the minutes of our weekly call: https://forge.fi-ware.eu/docman/view.php/11/936/IoT-Minutes-Telco-020520 12.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed May 2 15:38:23 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 2 May 2012 15:38:23 +0200 Subject: [Fiware-iot] Dedicated meeting for devices interfaces Message-ID: Dear all, As we discuss it this morning and for some of you who are interested in which kind of interfaces we could support for some FI-Ware releases and to have a pragmatic approach regarding ETSI M2M and other interfaces, please fulfill the doodle. http://www.doodle.com/3ydadshccabpcabh 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri May 4 09:15:31 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 4 May 2012 09:15:31 +0200 Subject: [Fiware-iot] TR: Dedicated meeting for devices interfaces Message-ID: Dear all I've just added a new slot on Monday morning because Ericsson is not available for the other ones so please update your votes. Thanks Thierry De : NAGELLEN Thierry RD-BIZZ-SOP Envoy? : mercredi 2 mai 2012 15:38 ? : fiware-iot at lists.fi-ware.eu Objet : Dedicated meeting for devices interfaces Dear all, As we discuss it this morning and for some of you who are interested in which kind of interfaces we could support for some FI-Ware releases and to have a pragmatic approach regarding ETSI M2M and other interfaces, please fulfill the doodle. http://www.doodle.com/3ydadshccabpcabh 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri May 4 13:44:19 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 4 May 2012 13:44:19 +0200 Subject: [Fiware-iot] Dedicated meeting for devices interfaces Message-ID: Quand : lundi 7 mai 2012 10:00-11:00 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Emplacement : Virtual meeting Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Hi all, As this slot is the only one available for Ericsson we will try to manage the meeting at this time. As we studied before some interfaces but not so much IETF, the meeting will begin with an IETF presentation from Ericsson. Webex facilities are provided by NSN as usual. BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 1951 bytes Desc: not available URL: From denes.bisztray at nsn.com Mon May 7 08:05:28 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Mon, 7 May 2012 08:05:28 +0200 Subject: [Fiware-iot] Dedicated meeting for devices interfaces In-Reply-To: References: Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05DE3638@DEMUEXC013.nsn-intra.net> Dear all, Please find the webex details below: Topic: Dedicated meeting for devices interfaces Date: Monday, May 7, 2012 Time: 10:00 am, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 701 509 168 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210856792&UID=503765542&PW=NNzkwYTFhYzVj&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 New PIN: 1628 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 Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. 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) From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext thierry.nagellen at orange.com Sent: Friday, May 04, 2012 1:44 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Dedicated meeting for devices interfaces Quand : lundi 7 mai 2012 10:00-11:00 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Emplacement : Virtual meeting Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Hi all, As this slot is the only one available for Ericsson we will try to manage the meeting at this time. As we studied before some interfaces but not so much IETF, the meeting will begin with an IETF presentation from Ericsson. Webex facilities are provided by NSN as usual. BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue May 8 12:26:07 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 8 May 2012 13:26:07 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203713CA8@FIESEXC014.nsn-intra.net> When: 2012. m?jus 9. 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 propose the following topics for our next meeting: 1. Standardization: "Lindsay Frost (WP11) on SDO activities" (topic proposed by Tobias) 2. Educational sessions: define agenda & presentors, fill in slots in the agenda with content (which GE in which slot). Share presentation guidelines with the partners -there will be a first proposal by us very soon (D?nes to send out) -we will discuss it during the meeting -!!!ASAP please register your participation under the link (only D?nes and Tarek registered until now from the WP) https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGJqeEFlblNEUkdxdkl2NW1sM0FWUUE#gid=2 3. Update on the architecture + next steps: will have yet another update with the chief architect on Tuesday, will inform you on the outcomes during the meeting 4. Update on M12 deliverables (except open specifications) 4.1 Update on Exploitation plan - discuss on the progress, who will do what in the next steps -as a preparation partners could do an effort to fill the respective part before the meeting -we will check what is available by partner before the meeting -we will try to have at least Orange & NSN partner parts completed before the meeting -we will try create the description at least for one GE-s before the meeting 4.2 Market & policy awareness: needs review by all partners -partners have 2 action items - identification of potential cities (http://www.google.com/url?q=https%3A%2F%2Fforge.fi-ware.eu%2Fplugins%2Fmediawiki%2Fwiki%2Fexploitation%2Findex.php%2FMarket_and_Policy_Regulation_Awareness%23Smartcities&sa=D&sntz=1&usg=AFQjCNGVxo5hz2mjJwdx5X-r9FbvGGkugw) and identification of business associations and other bodies (http://www.google.com/url?q=https%3A%2F%2Fforge.fi-ware.eu%2Fplugins%2Fmediawiki%2Fwiki%2Fexploitation%2Findex.php%2FMarket_and_Policy_Regulation_Awareness%23Business_Association&sa=D&sntz=1&usg=AFQjCNEyNY94z6LDkLTG9J7WNhG_sO4SeA) -as a preparation could you please check these two links to get familiarized with the topic 4.3 Update on Installation & Administration Guides - need to send comments to WP10 ASAP -as a preparation could you please check an e-mail forwarded by me on 23.04.2012, 14:45 -we will go briefly through the proposal in the meeting and collect feedback 4.4 Update on Unit Testing Plan: pending action from 2 weeks ago, we need to comment ASAP, otherwise they become final -as a preparation could you please check this e-mail with the original proposal and some comments from WP7 (I seem not to have the original proposal) <<[Fiware-wpa] Feedback by I2ND Chapter on Unit Testing Plan and Report deliverable proposal>> -we will go briefly through the proposal in the meeting and collect feedback 4.5 FI-WARE catalogue: need to check & provide feedback by the end of the week -will go briefly through the proposal in the meeting -as a preparation could you please take a look and register to the catalogue. The information was provided by Matteo Melideo in an e-mail on 15.03.2012, at 18:21 5. Open Specifications: discuss the next steps 6. Update on the tracker: we will inform you on the steps taken by the coordinator to put various trackers in order and try to plan next steps 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: 13849 bytes Desc: not available URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Garino Pierangelo" Subject: [Fiware-wpa] Feedback by I2ND Chapter on Unit Testing Plan and Report deliverable proposal Date: Fri, 13 Apr 2012 18:22:19 +0300 Size: 33626 URL: From denes.bisztray at nsn.com Tue May 8 13:55:29 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 8 May 2012 13:55:29 +0200 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A203713CA8@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203713CA8@FIESEXC014.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05E232D7@DEMUEXC013.nsn-intra.net> Hi all, I'd propose the following agenda for the educational session. I also noted the requested presentations and participation requests. Please note that currently nobody is registered to come to the educational sessions. Tuesday There will be joint sessions with DATA, namely: Session #1 (NEC participation necessary) NGSI basics (35') specs (35') binding(35') Session #2 Scenarios/examples based on NGSI(35') Pub/Sub GE (20') IoT Broker GE (20') (NEC presentation) Wednesday Session #1 15' general introduction (WPA/WPL presentation) 40' gateway device management GE (Ericsson presentation) 40' gateway data handling GE (Orange presentation) 15' q&a Session #2 30' centralised backend (NSN presentation) 30' etsi m2m (Telecom Italia presentation) 20' semantic capabilities in the backend (University of Surrey presentation) 10' q&a Best, D?nes 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: Tuesday, May 08, 2012 12:26 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. m?jus 9. 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 propose the following topics for our next meeting: 1. Standardization: "Lindsay Frost (WP11) on SDO activities" (topic proposed by Tobias) 2. Educational sessions: define agenda & presentors, fill in slots in the agenda with content (which GE in which slot). Share presentation guidelines with the partners -there will be a first proposal by us very soon (D?nes to send out) -we will discuss it during the meeting -!!!ASAP please register your participation under the link (only D?nes and Tarek registered until now from the WP) https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGJqeEFlblNEUkdxdkl2NW1sM0FWUUE#gid=2 3. Update on the architecture + next steps: will have yet another update with the chief architect on Tuesday, will inform you on the outcomes during the meeting 4. Update on M12 deliverables (except open specifications) 4.1 Update on Exploitation plan - discuss on the progress, who will do what in the next steps -as a preparation partners could do an effort to fill the respective part before the meeting -we will check what is available by partner before the meeting -we will try to have at least Orange & NSN partner parts completed before the meeting -we will try create the description at least for one GE-s before the meeting 4.2 Market & policy awareness: needs review by all partners -partners have 2 action items - identification of potential cities (http://www.google.com/url?q=https%3A%2F%2Fforge.fi-ware.eu%2Fplugins%2Fmediawiki%2Fwiki%2Fexploitation%2Findex.php%2FMarket_and_Policy_Regulation_Awareness%23Smartcities&sa=D&sntz=1&usg=AFQjCNGVxo5hz2mjJwdx5X-r9FbvGGkugw ) and identification of business associations and other bodies (http://www.google.com/url?q=https%3A%2F%2Fforge.fi-ware.eu%2Fplugins%2Fmediawiki%2Fwiki%2Fexploitation%2Findex.php%2FMarket_and_Policy_Regulation_Awareness%23Business_Association&sa=D&sntz=1&usg=AFQjCNEyNY94z6LDkLTG9J7WNhG_sO4SeA ) -as a preparation could you please check these two links to get familiarized with the topic 4.3 Update on Installation & Administration Guides - need to send comments to WP10 ASAP -as a preparation could you please check an e-mail forwarded by me on 23.04.2012, 14:45 -we will go briefly through the proposal in the meeting and collect feedback 4.4 Update on Unit Testing Plan: pending action from 2 weeks ago, we need to comment ASAP, otherwise they become final -as a preparation could you please check this e-mail with the original proposal and some comments from WP7 (I seem not to have the original proposal) <<[Fiware-wpa] Feedback by I2ND Chapter on Unit Testing Plan and Report deliverable proposal>> -we will go briefly through the proposal in the meeting and collect feedback 4.5 FI-WARE catalogue: need to check & provide feedback by the end of the week -will go briefly through the proposal in the meeting -as a preparation could you please take a look and register to the catalogue. The information was provided by Matteo Melideo in an e-mail on 15.03.2012, at 18:21 5. Open Specifications: discuss the next steps 6. Update on the tracker: we will inform you on the steps taken by the coordinator to put various trackers in order and try to plan next steps 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: From lorant.farkas at nsn.com Wed May 9 15:33:56 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 9 May 2012 16:33:56 +0300 Subject: [Fiware-iot] weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A203766FF8@FIESEXC014.nsn-intra.net> Dear All, The minutes are available under https://forge.fi-ware.eu/docman/view.php/11/942/IoT-Minutes-Telco-090520 12.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu May 10 10:52:39 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 10 May 2012 11:52:39 +0300 Subject: [Fiware-iot] educational sessions - please upload material in SVN Message-ID: <93D28BDF64839C468B848D14227151A203767273@FIESEXC014.nsn-intra.net> Dear All, In the SVN there is now a new subfolder, \documents\H12012_educational_sessions Please upload there the presentations you are creating. There is also a readme.txt file with the most recent news on: -venue, logistics -links -recommendations for presentation formats Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Thu May 10 12:34:53 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Thu, 10 May 2012 12:34:53 +0200 Subject: [Fiware-iot] Check and address points 4.3 ... 4.5 (AP: IoT07_09.05.2012) Message-ID: <36A93B31228D3B49B691AD31652BCAE9A599B4DF60@GRFMBX702BA020.griffon.local> Hi, regarding the action point 4.3 (Update on Installation & Administration Guides) we propose to add to the TOC for Sanity Check Procedures an entry "Structure of directories" with the meaning: provide a structure of the directories and of the most important files included to be controlled for the checking of the completeness of the installation. About the AP. 4.4 (Update on Unit Testing Plan) we have no comments at the moment. About the AP. 4.5 (FI-WARE catalogue) we have problems to access the registration (request timeout). We will try again, probably they're working on the catalogue web site. Best regards, Sabrina and Gian Piero Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From Tobias.Jacobs at neclab.eu Thu May 10 13:04:26 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 10 May 2012 11:04:26 +0000 Subject: [Fiware-iot] GET for context Attribute In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05E23D8B@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD05E23D8B@DEMUEXC013.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BDDB9B@PALLENE.office.hd> Hi Denes, There was as inconsistency between the binding document and the xsd. In the xsd a ContextAttributeResponse only contained a single attribute (see the email sent by Fabian last week's Wednesday). I changed the binding document accordingly, but I think that you are right, the ContextAttributeResponse should contain a list of attributes (as there might be multiple value instances), so I should rather have changed the xsd. If you agree with that view, I am happy correct this error. Sorry for the trouble! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Donnerstag, 10. Mai 2012 12:44 To: Tobias Jacobs Cc: Salvatore Longo Subject: GET for context Attribute Hi Tobias, There seems to be a huge error int he NGSI-10 document! The GET at Attribute of individual context entity returns only a single ContextAttribute! It supposed to return a queryContextAttributeResponse, with a contextAttributeList!! Can you check who edited this out of the document? Currently this is simply wrong! Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Thu May 10 17:10:48 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 10 May 2012 15:10:48 +0000 Subject: [Fiware-iot] Associations via NGSI-9 / Backend architecture Message-ID: <8755F290097BD941865DC4245B335D2D08BDEDC3@PALLENE.office.hd> Hi Juanjo, hi all, Please find here our approach of how associations between higher-level and lower-level entities can be modeled in NGSI-9: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Enhanced_Associations_by_OMA_NGSI-9 What is still missing on the wiki page is: - The main interactions. I think these can be taken from Juanjo's long email, maybe with some modifications/enhancements - Description of the Configuration Interface. In my view this could also be NGSI-9, at least in the first release. - Maybe more information about the Discovery Engine, if Surrey wants that. - Check the description of the Configuration Management - Some description of NGSI-9 (although we have not agreed on a binding yet, one could describe the main operations) - Some more details on the NGSI-10 page (I promised to do that some weeks ago) @Juanjo: How about I give you the ticket for the main ThingsManagement GE wiki page from now on. I can still work on the NGSI pages in parallel. If necessary, we can still work in parallel on the main page if we edit disjoint parts of it (i.e. use the edit buttons that are next to each section title). Best regards Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri May 11 09:24:54 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 11 May 2012 10:24:54 +0300 Subject: [Fiware-iot] link to standardization plan/topic from Lindsay Frost Message-ID: <93D28BDF64839C468B848D14227151A2037676B8@FIESEXC014.nsn-intra.net> Dear All, The standardization pages shown by Lindsay in our weekly call are accessible from http://wiki.fi-ware.eu. Please look for the "Standardization plan" subsection under "Exploitation". Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri May 11 09:43:01 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 11 May 2012 10:43:01 +0300 Subject: [Fiware-iot] FW: [Fiware-wpl] concerns on the privacy of the D11.x deliverables Message-ID: <93D28BDF64839C468B848D14227151A2037676D8@FIESEXC014.nsn-intra.net> FYI, please let me know if there are still some concerns left. Thanks & Br, Lorant From: ext Juan Bare?o Guerenabarrena [mailto:juan.bareno at atosresearch.eu] Sent: Friday, May 11, 2012 9:41 AM To: Farkas, Lorant (NSN - HU/Budapest); fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] concerns on the privacy of the D11.x deliverables Dear Lorant I confirm you that these are private and that we will apply the first option you propose, final conversion to pdf Br Juan From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: viernes, 11 de mayo de 2012 9:33 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] concerns on the privacy of the D11.x deliverables Dear All, Some partners raised concerns on the privacy of D11.x deliverables. Juan Bareno from ATOS confirmed that these are private. Still there are concerns that potential assignments of access rights might leak out information. The following options were discussed how these deliverables could be shared with reviewers: -conversion to pdf - in this case there are no concerns -reviewer will get dedicated account to access the exploitation wiki: there could be concerns because this wiki might contain other private information that only partners need to see, not the reviewers -create another private project with its own wiki that would be private for the members of that projects and allow reviewers to be members of that project, use that to publish consolidated D11.x deliverables Feedback is welcome on the mailing list, or if you agree we could briefly touch this during the next WPA/WPL meeting. Thanks & Br, Lorant ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Fri May 11 10:10:53 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 11 May 2012 10:10:53 +0200 Subject: [Fiware-iot] Exploitation Plan todos Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05E62D07@DEMUEXC013.nsn-intra.net> Dear all, As a reminder from the Wednesday meeting, I'd like to list the todo regarding the exploitation plan. In order to access the wiki of the Exploitation, one has to join the Exploitation project in the forge. https://forge.fi-ware.eu/projects/exploitation/ There are two important parts of the wiki. 1. Individual Exploitation plans: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual_Exploitation_Plans This has to be filled by every single company. 2. Business Description GE of Internet of Things https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things Here, the various GEs have to be described. The responsibilities are the following, Backend: - Things Management GE: NEC and Telef?nica - Backend Device Management GE: University of Surrey - Advanced Communications GE: Telecom Italia (as a task leader of IoT communication) - Security GE: Security WP possibly Gateway - Data Handling GE: Orange - Device Management GE: Ericsson - Business Protocol Adapter GE: Ericsson - Advanced Connectivity GE: Telecom Italia - Security GE: Security WP possibly After the list of GEs, there is a list of the tasks with the exploitation plan format. In case it helps, use them, but in the end, that section will be deleted. The currend description of the GEs are provided by me, feel free to change them Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon May 14 08:26:50 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 14 May 2012 09:26:50 +0300 Subject: [Fiware-iot] FW: [Fiware-wpa] Fwd: FI-WARE: 2nd review report (month 9) Message-ID: <93D28BDF64839C468B848D14227151A2037AB534@FIESEXC014.nsn-intra.net> Dear Partners, FYI. Very probably a topic that will be addressed in our weekly call. 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, May 14, 2012 6:16 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: FI-WARE: 2nd review report (month 9) Hi all, The EC has sent a review report on the activities carried out, as well as the deliverables due, before end of month 9. I have to confess that this has been a nice surprise (among other things, because it will help us to better focus our 1st year review by June 21-22) I haven't had time to read it completely, just a quick reading of the overall assessment. D2.3a, D2.4a, and D11.4a have been rejected and have to be re-submitted once detailed comments provided by the reviewers are addressed. The rest of deliverables are accepted though D.2.1.1 and D.1.3.1 with some reservations. The reviewers applaud the quality of the testbed design as documented in deliverable D10.1a. Regarding D2.3a and D2.4a, the following is said in the overall assessment: While much of the material produced for the key deliverable D2.3a is of good to very good quality, the level of quality is not consistent, with several major issues affecting deliverables D2.3a and D2.4a to the degree that remedial attention is required before they can be accepted. while regarding D11.4, the following is said in the overall assessment (probably we need to read the detailed comments to understand it better): deliverable D11.4a is also rejected due to a lack of clarity on how standardisation contributions will be properly aligned with one another Overall, the project is scored in the lower scale of acceptable progress so, definitively, we all have to devote the necessary resources to improve that score. I believe it is feasible if we carefully review the recommendations made in the review and implement the necessary remedy actions. Fortunately, some actions that have been already planned (e.g., educational sessions with the UC projects, dedicated team covering management of UC tickets, ...) are in this direction, but we will have to add some more. Please distribute among the members of your Chapter teams. 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 -------- Original Message -------- Subject: FI-WARE: 2nd review report (month 9) Date: Sun, 13 May 2012 16:47:06 +0200 From: Arian.ZWEGERS at ec.europa.eu To: JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA CC: Annalisa.Bogliolo at ec.europa.eu , Federica.TAGLIANI at ec.europa.eu , bel.piet1 at gmail.com , renaud.difrancesco at eu.sony.com , rdifrancesco at ymail.com , dgr at whitestein.com , msli at icfocus.co.uk , irena.pavlova at isoft-technology.com Dear Jose, Juanjo, Please find enclosed the outcome of the second FI-WARE review. No paper version will follow. Please distribute the review report to the partners in the consortium. Please acknowledge the receipt of this e-mail. This is an informal notification. The formal submission will follow soon and will not be different. Best regards, Arian Zwegers ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Review 2 Report.pdf Type: application/pdf Size: 148584 bytes Desc: FI-WARE Review 2 Report.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Cover FI-WARE review 2 report.pdf Type: application/pdf Size: 33689 bytes Desc: Cover FI-WARE review 2 report.pdf URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT2119374.txt URL: From lorant.farkas at nsn.com Mon May 14 12:19:28 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 14 May 2012 13:19:28 +0300 Subject: [Fiware-iot] Open Specs by the end of the week! Message-ID: <93D28BDF64839C468B848D14227151A2037AB7A4@FIESEXC014.nsn-intra.net> Dear All, I have not seen any progress recently on Open Specifications except the additions from Tobias on Things Management. The deliverable is meant to be delivered end of this week. Last week partners did not express that there would be any unclarities with respect to this topic. Please take ASAP action on the open specifications for the following, where we don't see too much progress yet: -Jakob, Jan: protocol adapter interface, gateway northbound interface (CoAP based) -Laurent: data handling API in the gateway, admin interface for CEP in the gateway -Tobias: Things Management GE interfaces (all 4 of them) Additional comment for Laurent: we acknowledge you did the merge of the former data handling GE-s to one wiki page, but beside a copy paste you should take care that figures need to have the right names for the boxes, sections need to be not per component, but only one section for the GE (e.g. there are many "main interactions", there should be only one) etc. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon May 14 12:58:32 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 14 May 2012 13:58:32 +0300 Subject: [Fiware-iot] WP12 Deliverables Action Plan (Please read carefully, as trips expenses claim might be rejected afterwards) Message-ID: <93D28BDF64839C468B848D14227151A2037AB818@FIESEXC014.nsn-intra.net> Dear Partners, FYI, yet another action to be finished end of this week. 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 CARLOS RALLI UCENDO Sent: Thursday, May 10, 2012 3:57 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] 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. Let us fix Friday next week (May 18th) EoB as the absolute deadline to close both documents by taking a snapshot of the corresponding sections in the Wiki. 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From lorant.farkas at nsn.com Tue May 15 08:54:48 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 15 May 2012 09:54:48 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2037ABBC0@FIESEXC014.nsn-intra.net> When: 2012. m?jus 16. 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 will cancel this instance as there is a parallel meeting between FI-WARE and InstantMobility between 10 - 13 as a preparation for the educational sessions. We will inform you in the afternoon on the outcomes. We will approach you in e-mail today and tomorrow on the immediate next steps we expect you to do. 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: 10619 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu May 17 07:30:47 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 17 May 2012 08:30:47 +0300 Subject: [Fiware-iot] FW: [Fiware-wpa] GUIDELINES on how to publish Open Specifications Message-ID: <93D28BDF64839C468B848D14227151A2037F24AA@FIESEXC014.nsn-intra.net> Dear All, FYI, we have to publish open specifications to the public wiki until Friday 12:00 CET. Howto-s are provided under the links. 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, May 16, 2012 7:02 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] GUIDELINES on how to publish Open Specifications Hi all, Nobody has raised any particular issue, so this is to give you GREEN FLAG to proceed publishing the Open Specifications on the Public Wiki, following the provided guidelines. You have until friday 12:00 CET to carry out the process. Indeed, I believe this can be done in less than one full day, but let's go for that deadline. Please communicate this to your teams. 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 15/05/12 11:12, Juanjo Hierro wrote: Dear colleagues, I have updated the guidelines defined in our private wiki on how to publish the FI-WARE Open Specifications. You can still find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications Please read the guidelines carefully. We WON'T start applying them until tomorrow after I send an email giving you green flag. This is to allow you to read the guidelines first, and raise any issue you may detect or formulate any doubt you may have. I will check issues/doubts after lunch today and will come back with a resolution on any issues before the green flag tomorrow based on discussions over the mailing lists. That way we will prevent that teams start publishing things before fixing any issue. Note that I have updated the template for RESTful API specifications in order to reflect the agreements after discussion of comments raised by the Security chapter. Following is a summary of these changes: * I have drop some standard/fixed contents of the "Intended Audience" section and moved them to the "How to read FI-WARE RESTful API Specifications" section on the single common page we have defined for common aspects in FI-WARE RESTful API specifications located at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Common_aspects_in_FI-WARE_Open_Restful_API_Specifications * I have also refined the text of the "How to Read This Document" section so that it refers to the the common "How to read FI-WARE RESTful API Specifications" section described above * I have moved the "Authentication" and the "Representation Transport" sections to the single common page we have defined for common aspects in FI-WARE RESTful API specifications * I have simplified the "Representation format" section taken advantage that many of the details that were there can be moved to the single common page we have defined for common aspects in FI-WARE RESTful API specifications * I have moved fixed contents of the "Limits" and "Extensions" sections to the single common page we have defined for common aspects in FI-WARE RESTful API specifications. Then, you only need to specify the list of valid error and response codes, together with some examples of valid responses. Nevertheless, it is not absolutely mandatory to adapt to the proposed updated template now if you had already completed your API specification following the previous template. However, the more, the better. You can defer final adaptation to end of June. 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 ________________________________ 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: ATT32622.txt URL: From lorant.farkas at nsn.com Thu May 17 16:22:48 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 17 May 2012 17:22:48 +0300 Subject: [Fiware-iot] asset selection reloaded for D11.2 Message-ID: <93D28BDF64839C468B848D14227151A2037F26A0@FIESEXC014.nsn-intra.net> Dear All, We have to fill in the exploitation plan also the IPR management section, we have not discussed this topic yet. This is available under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Internet_of_Things#Data_Handling_GE I tried to modify this in order to reflect our new streamlined architecture. I would need feedback (again) on the asset mapping in the new situation. As you know we have our backend and gateway GE-s described under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Internet_of_Things I attempted to make some order in the chaos, to do that properly I will need input from you. I will list here the list of assets I know of and the relation to backend/gateway GE that I assume, could you make corrections/additions from your perspective? Deadline for this is 17(19).05 EOB. Thanks & Br, Lorant Asset GE Input expected from ISIS backend things management Tobias, Salvatore, Martin, Ern? Fosstrak gateway data handling Thierry, Laurent M2M Planet / Pangoo ?? Thierry, Laurent Cumulocity backend device management, backend things management, advanced connectivity D?nes Sensei backend things management, gateway device management Ern?, Stephan SOL gateway data handling Maarten Orange CEP AS gateway data handling Thierry, Laurent Petals ESB gateway data handling Thierry, Laurent IoT-A backend things management Stephan, Jan, Jakob, Tarek, Payam IDAS backend things management Ken, Juanjo Ericsson gateway gateway data handling, gateway protocol adapter Jan, Jakob ZigBee HA gateway gateway protocol adapter Gian Piero, Sabrina LDPG backend things management Tarek, Payam -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Mon May 21 11:39:37 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 21 May 2012 09:39:37 +0000 Subject: [Fiware-iot] NGSI - 9 Message-ID: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon May 21 17:31:24 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 21 May 2012 17:31:24 +0200 Subject: [Fiware-iot] Any additional slides to add to the general introduction presentation on NGSI ? Message-ID: <4FBA5FCC.4040002@tid.es> Hi all, Just wondered whether you find the need to add some slide to the general introductory presentation that I distributed about NGSI, which we agreed I would use for the first slot of the joint Data/IoT session ... If so, please let me know. 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 From lorant.farkas at nsn.com Tue May 22 08:40:34 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 22 May 2012 09:40:34 +0300 Subject: [Fiware-iot] weekly meeting will be rescheduled Message-ID: <93D28BDF64839C468B848D14227151A2037F3095@FIESEXC014.nsn-intra.net> Dear All, Because many of the partners not being available, we would like to reschedule the weekly meeting. We would like to have a shorter session of 1 hour on Friday, please vote until Thursday EOB under the following link: http://www.doodle.com/xakgp4trcackminc If more than half of the partners are not available, we will cancel this meeting. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 23 09:53:39 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 23 May 2012 09:53:39 +0200 Subject: [Fiware-iot] Introductory presentation by Denes during FI-WARE Educational Week Message-ID: <4FBC9783.9000302@tid.es> Hi, Just wanted to say that I liked very much the introductory presentation made by Denes during the IoT session today. Looking forward downloading the slides soon. Good job. 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 From thierry.nagellen at orange.com Wed May 23 09:55:57 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 23 May 2012 09:55:57 +0200 Subject: [Fiware-iot] Introductory presentation by Denes during FI-WAREEducational Week In-Reply-To: <4FBC9783.9000302@tid.es> References: <4FBC9783.9000302@tid.es> Message-ID: Thanks a lot for your comment, Juanjo We hope that it will improve UC projects' understanding of what we are doing. BR Thierry -----Message d'origine----- De?: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: mercredi 23 mai 2012 09:54 ??: fiware-iot at lists.fi-ware.eu Objet?: [Fiware-iot] Introductory presentation by Denes during FI-WAREEducational Week Hi, Just wanted to say that I liked very much the introductory presentation made by Denes during the IoT session today. Looking forward downloading the slides soon. Good job. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot From jhierro at tid.es Wed May 23 10:06:25 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 23 May 2012 10:06:25 +0200 Subject: [Fiware-iot] Additional feedback on IoT during educational sessions Message-ID: <4FBC9A81.6010608@tid.es> Hi, Another valuable feedback we are receiving during the educational session on IoT is that some UC projects seek for process automation functionality regarding the IoT. The kind of process automation enablers the are looking for seem to me very much related to the original task on process/service automation we explained that it was our plan to support in the FI-WARE Product Vision (the UC projects indeed have made a reference to our Product Vision when raising the point). We have explained that GEs enabling process automation were not going to be there for the first FI-WARE Major Release but certainly will be considered for the next Major Release. We shouldn't forget addressing this point when planning activities for the second Major Release of FI-WARE. It would be nice to find out something like NGSI for this process automation at Thing-level (probably also at device-level, although I'm not so sure we should cover that or simply define/develop these enablers at Things-level) 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 From t.elsaleh at surrey.ac.uk Wed May 23 15:26:15 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 23 May 2012 14:26:15 +0100 Subject: [Fiware-iot] UoS semantic presentation uploaded In-Reply-To: <93D28BDF64839C468B848D14227151A2037F3095@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2037F3095@FIESEXC014.nsn-intra.net> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923482C3@EXMB05CMS.surrey.ac.uk> Hello Lorant, I have uploaded the UoS presentation on "Semantic Capabilities in the Backend" on the svn. Best regards, Tarek 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: 22 May 2012 08:41 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] weekly meeting will be rescheduled Dear All, Because many of the partners not being available, we would like to reschedule the weekly meeting. We would like to have a shorter session of 1 hour on Friday, please vote until Thursday EOB under the following link: http://www.doodle.com/xakgp4trcackminc If more than half of the partners are not available, we will cancel this meeting. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu May 24 07:15:33 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 24 May 2012 08:15:33 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20383DFC9@FIESEXC014.nsn-intra.net> When: 2012. m?jus 25. 11:00-12:00 (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, Based on the Doodle polls this is an invitation for the (shorter than usual) weekly IoT meeting. Proposed agenda items: 1. Review status on action items and identify next todos per partner (mainly concerning M9...12 deliverables) 2. Summary from the FI-WARE 1st educational week Thanks & Br, Lorant ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=3159687&UID=483150557&PW=NMmU0YmZmMmYy&RT=MTgjMjM%3D 2. 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: 9279 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu May 24 10:22:40 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 24 May 2012 11:22:40 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20383E131@FIESEXC014.nsn-intra.net> When: 2012. m?jus 25. 11:00-12:00 (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. *~*~*~*~*~*~*~*~*~* Need to cancel because of a very short notice WPA/WPL call, sorry for this. Dear All, Based on the Doodle polls this is an invitation for the (shorter than usual) weekly IoT meeting. Proposed agenda items: 1. Review status on action items and identify next todos per partner (mainly concerning M9...12 deliverables) 2. Summary from the FI-WARE 1st educational week Thanks & Br, Lorant ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=3159687&UID=483150557&PW=NMmU0YmZmMmYy&RT=MTgjMjM%3D 2. 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: 9273 bytes Desc: not available URL: From lorant.farkas at nsn.com Tue May 29 09:06:45 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 29 May 2012 10:06:45 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203877710@FIESEXC014.nsn-intra.net> When: 2012. m?jus 30. 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 propose the following points for our weekly meeting: -educational week: feedback from participants, participation in the next round, info exchange on the venue that we will try to find out before the meeting etc. -resource claiming per partner for the 1st year: Thierry would briefly give his insight on those figures -last review by the comission: we would elaborate on what has been accepted/reviewed (M9 deliverables), the reasoning and possible implications -unit testing plan: input from Juanjo in the attachment <<[Fiware-wpa] Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE>> -integration todos from Stefano/Matteo, please check this https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Integration_Plan (accessible from the MediaWiki of WP10) and also https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1 , link also available from the first one I will not be available for the meeting, D?nes will host it from NSN side. Volunteers for taking notes are welcome. 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: 11600 bytes Desc: not available URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-wpa] Detailed instructions on how to generate the Unit Testing Plan deliverable for a FI-WARE GE Date: Tue, 29 May 2012 00:34:41 +0300 Size: 16920 URL: From kzangeli at tid.es Tue May 29 14:42:22 2012 From: kzangeli at tid.es (Ken Zangelin) Date: Tue, 29 May 2012 14:42:22 +0200 Subject: [Fiware-iot] NGSI - 9 In-Reply-To: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> Message-ID: <4FC4C42E.2090407@tid.es> Hi guys. just to give you my humble opinion ... To me it seems like a better idea to have ngsi-9 and ngsi-10 separated. I don't find it really important though and if you think you'd gain a lot of time doing them together, then go that way ... I also wanted to remind you about what I asked for in Zurich ... If you could please send me the exact xml data chains that you send/expect to/from your 'dummy' config manager. This would be a huge help for me, implementing the real configMgr and especially, the integration in July would come almost for free after that ... As soon as you have it, pls ... ;-) /KZ On 05/21/2012 11:39 AM, Tobias Jacobs wrote: Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias ________________________________ 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 Tue May 29 15:34:41 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 29 May 2012 13:34:41 +0000 Subject: [Fiware-iot] [Fiware-ngsi] FW: NGSI - 9 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05F6CCDB@DEMUEXC013.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> <8755F290097BD941865DC4245B335D2D08BE7986@Polydeuces.office.hd> <3F4C11BC54A36642BFB5875D599F47BD05F6CCDB@DEMUEXC013.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BEEB02@Polydeuces.office.hd> Hi Denes, all, Do you think that we can come to a decision in tomorrow's WP5 phone conference? We might also want to make a plan about how and when to finalize the NGSI-9 binding. Maybe we can make this the first agenda point, so that also people from other WPs have the possibility to take part in the discussion and then leave the call. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Dienstag, 29. Mai 2012 15:03 To: Tobias Jacobs; fiware-ngsi at lists.fi-ware.eu Subject: RE: [Fiware-ngsi] FW: NGSI - 9 Dear All, As a generic answer, whatever the outcome of this decision will be, NSN is happy to implement it. However to give my to cents, I'd go strongly towards the one resource tree approach for two reasons: 1. Simpler indeed. A generic developer may get confused on the creation of the same resource structure twice 2. The various HTTP verbs may not collide as dedicated subresources can be introduced. The resource structure is just convenience after all, we can change it the way we like. And the non-convenience methods will not collide as they are different. Best, D?nes From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Monday, May 21, 2012 11:45 AM To: fiware-ngsi at lists.fi-ware.eu Subject: [Fiware-ngsi] FW: NGSI - 9 (apologies to everybody receiving this twice) Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue May 29 15:48:15 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 29 May 2012 16:48:15 +0300 Subject: [Fiware-iot] [Fiware-ngsi] FW: NGSI - 9 In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEEB02@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> <8755F290097BD941865DC4245B335D2D08BE7986@Polydeuces.office.hd> <3F4C11BC54A36642BFB5875D599F47BD05F6CCDB@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEEB02@Polydeuces.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A203877ADA@FIESEXC014.nsn-intra.net> Hi Tobias, I would not mix the 2 things. Other partners in IoT might not be interested in NGSI and there are many other topics. I propose to set up a vote for one/two resource trees in an e-mail to the NGSI list, where someone (Tobias? Denes?) gathers all the pros/cons for both approaches and partners could vote until the end of the week. For finalizing the binding I think we agreed NEC would start creating the document, partners would then give comments during the process. By asking the 1 tree/2 trees question we basically started this, I think J Thanks & Br, Lorant From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Tuesday, May 29, 2012 3:35 PM To: Bisztray, Denes (NSN - HU/Budapest); fiware-ngsi at lists.fi-ware.eu Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] FW: NGSI - 9 Hi Denes, all, Do you think that we can come to a decision in tomorrow's WP5 phone conference? We might also want to make a plan about how and when to finalize the NGSI-9 binding. Maybe we can make this the first agenda point, so that also people from other WPs have the possibility to take part in the discussion and then leave the call. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Dienstag, 29. Mai 2012 15:03 To: Tobias Jacobs; fiware-ngsi at lists.fi-ware.eu Subject: RE: [Fiware-ngsi] FW: NGSI - 9 Dear All, As a generic answer, whatever the outcome of this decision will be, NSN is happy to implement it. However to give my to cents, I'd go strongly towards the one resource tree approach for two reasons: 1. Simpler indeed. A generic developer may get confused on the creation of the same resource structure twice 2. The various HTTP verbs may not collide as dedicated subresources can be introduced. The resource structure is just convenience after all, we can change it the way we like. And the non-convenience methods will not collide as they are different. Best, D?nes From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Monday, May 21, 2012 11:45 AM To: fiware-ngsi at lists.fi-ware.eu Subject: [Fiware-ngsi] FW: NGSI - 9 (apologies to everybody receiving this twice) Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Tue May 29 16:17:33 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 29 May 2012 14:17:33 +0000 Subject: [Fiware-iot] [Fiware-ngsi] FW: NGSI - 9 In-Reply-To: <93D28BDF64839C468B848D14227151A203877ADA@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BE6961@Polydeuces.office.hd> <8755F290097BD941865DC4245B335D2D08BE7986@Polydeuces.office.hd> <3F4C11BC54A36642BFB5875D599F47BD05F6CCDB@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEEB02@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A203877ADA@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BEEB4F@Polydeuces.office.hd> Ok, sounds like a plan :) - Tobias From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Dienstag, 29. Mai 2012 15:48 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-ngsi] FW: NGSI - 9 Hi Tobias, I would not mix the 2 things. Other partners in IoT might not be interested in NGSI and there are many other topics. I propose to set up a vote for one/two resource trees in an e-mail to the NGSI list, where someone (Tobias? Denes?) gathers all the pros/cons for both approaches and partners could vote until the end of the week. For finalizing the binding I think we agreed NEC would start creating the document, partners would then give comments during the process. By asking the 1 tree/2 trees question we basically started this, I think :) Thanks & Br, Lorant From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Tuesday, May 29, 2012 3:35 PM To: Bisztray, Denes (NSN - HU/Budapest); fiware-ngsi at lists.fi-ware.eu Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] FW: NGSI - 9 Hi Denes, all, Do you think that we can come to a decision in tomorrow's WP5 phone conference? We might also want to make a plan about how and when to finalize the NGSI-9 binding. Maybe we can make this the first agenda point, so that also people from other WPs have the possibility to take part in the discussion and then leave the call. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Dienstag, 29. Mai 2012 15:03 To: Tobias Jacobs; fiware-ngsi at lists.fi-ware.eu Subject: RE: [Fiware-ngsi] FW: NGSI - 9 Dear All, As a generic answer, whatever the outcome of this decision will be, NSN is happy to implement it. However to give my to cents, I'd go strongly towards the one resource tree approach for two reasons: 1. Simpler indeed. A generic developer may get confused on the creation of the same resource structure twice 2. The various HTTP verbs may not collide as dedicated subresources can be introduced. The resource structure is just convenience after all, we can change it the way we like. And the non-convenience methods will not collide as they are different. Best, D?nes From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Monday, May 21, 2012 11:45 AM To: fiware-ngsi at lists.fi-ware.eu Subject: [Fiware-ngsi] FW: NGSI - 9 (apologies to everybody receiving this twice) Dear NGSI-interested people, We are more than late with the definition of a binding for OMA-NGSI 9. There is one fundamental question we need to settle before going into the details: Should the resource structure be the integrated into the NGSI-10 resource structure, or should NGSI-9 have its separated resource structure? Why have only one resource tree for both NGSI-9 and 10? - Simpler Why have a dedicated resource structure for NGSI-9 and 10 - More clear separation of concerns - There are hardly any components in FI-WARE that expose both interfaces anyway. Personally I am a bit more in favor of the second option, but not too strictly. Please feel free to convince me ;-) Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed May 30 11:05:57 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 30 May 2012 12:05:57 +0300 Subject: [Fiware-iot] FW: [Fiware-administrative] RV: Fwd: Errata corrige FI-WARE: 2nd review report (month 9) Ares(2012)632820 Message-ID: <93D28BDF64839C468B848D14227151A2038BE4B9@FIESEXC014.nsn-intra.net> Dear All, Please find attached the M9 review. Thanks & Br, Lorant From: fiware-administrative-bounces at lists.fi-ware.eu [mailto:fiware-administrative-bounces at lists.fi-ware.eu] On Behalf Of ext JAVIER DE PEDRO SANCHEZ Sent: Wednesday, May 30, 2012 10:25 AM To: fiware-administrative at lists.fi-ware.eu Subject: [Fiware-administrative] RV: Fwd: Errata corrige FI-WARE: 2nd review report (month 9) Ares(2012)632820 FYI. BR Javier. De: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] En nombre de Juanjo Hierro Enviado el: mi?rcoles, 30 de mayo de 2012 4:32 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Asunto: [Fiware-wpl] Fwd: Errata corrige: FI-WARE: 2nd review report (month 9) Ares(2012)632820 Hi all, Please find enclosed final report of the 2nd review of our project. Please distribute to your teams. 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: Errata corrige: FI-WARE: 2nd review report (month 9) Ares(2012)632820 Date: Tue, 29 May 2012 12:20:57 +0200 From: Federica.TAGLIANI at ec.europa.eu To: JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA CC: bel.piet1 at gmail.com , renaud.difrancesco at eu.sony.com , dgr at whitestein.com' , Renaud.DiFrancesco at eu.sony.com , msli at icfocus.co.uk , irena.pavlova at isoft-technology.com , Arian.ZWEGERS at ec.europa.eu , INFSO-ICT-285248 at ec.europa.eu Dear Mr Jimenez, dear Mr Hierro, Please ignore the previous e-mail and find enclosed the correct version of the outcome of the second FI-WARE review. Please distribute the review report to the partners in the consortium. Please acknowledge receipt of this e-mail. Kind regards, Federica Federica Tagliani Assistant to Arian Zwegers European Commission - DG INFSO/D.3 Software & Service Architectures and Infrastructures BU25 3/116, B-1049 Brussels Tel: 32-02-2974471 ________________________________ 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: Cover FI-WARE review 2 report.pdf Type: application/pdf Size: 35081 bytes Desc: Cover FI-WARE review 2 report.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Review 2 Report.pdf Type: application/pdf Size: 149965 bytes Desc: FI-WARE Review 2 Report.pdf URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT133749.txt URL: From t.elsaleh at surrey.ac.uk Wed May 30 12:07:48 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 30 May 2012 11:07:48 +0100 Subject: [Fiware-iot] possibility for remote presentation Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> Hello Denes, With regards to the 2nd educational session, would it be possible to hold a presentation on "semantic capabilities" remotely in case of no one being able to attend on behalf of Surrey?...even though there might be a need for extended discussions with the UC project representatives in order to extract significant interest for the GEs. :) This was done for one of the presentations in the previous educational session (via Skype). I'm thinking would WebEx be a good candidate for this? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed May 30 12:44:58 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 30 May 2012 12:44:58 +0200 Subject: [Fiware-iot] FW: [Fiware-training] Agenda & Logistics Details for the 2nd Week of the 'FI-PPP SW Architects Week' Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05F6D07C@DEMUEXC013.nsn-intra.net> The logistics of the Madrid Educational week. -----Original Message----- From: fiware-training-bounces at lists.fi-ware.eu [mailto:fiware-training-bounces at lists.fi-ware.eu] On Behalf Of ext CARLOS RALLI UCENDO Sent: Tuesday, May 29, 2012 6:11 PM To: fiware-training at lists.fi-ware.eu Subject: [Fiware-training] Agenda & Logistics Details for the 2nd Week of the 'FI-PPP SW Architects Week' Dear Colleagues, The Agenda is available in the same Googledoc we have been using so far: https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGJqeEFlblNEUkdxdkl2NW1sM0FWUUE#gid=1 There, you can also see the link to the logistics info (location, how-to-get-there, nearby hotels, etc) http://www.etsit.upm.es/la-escuela/how-to-find-etsit-upm.html?L=1 Regarding the organization of coffee-breaks and lunches, unfortunately, it is not possible to agree a reduced fee as we did in Zurich, so everyone will have to pay these services on their own. However, the host will ensure there is a dedicated space in the canteen for us although there will not be pastries in the breaks. 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 _______________________________________________ Fiware-training mailing list Fiware-training at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-training From lorant.farkas at nsn.com Wed May 30 14:01:02 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 30 May 2012 15:01:02 +0300 Subject: [Fiware-iot] possibility for remote presentation In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> Message-ID: <93D28BDF64839C468B848D14227151A2038BE696@FIESEXC014.nsn-intra.net> Hello Tarek, Technically we can arrange that, however whenever we raise to the chief architect, we face strong objections. So we would rather not do this. If there is a WPA/WPL meeting in the meantime, I will raise this again (not very likely we will have this soon, though). In the meantime could you disclose exactly which presentation was done remotely during the first week? 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 t.elsaleh at surrey.ac.uk Sent: Wednesday, May 30, 2012 12:08 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] possibility for remote presentation Hello Denes, With regards to the 2nd educational session, would it be possible to hold a presentation on "semantic capabilities" remotely in case of no one being able to attend on behalf of Surrey?...even though there might be a need for extended discussions with the UC project representatives in order to extract significant interest for the GEs. J This was done for one of the presentations in the previous educational session (via Skype). I'm thinking would WebEx be a good candidate for this? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed May 30 14:00:17 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 30 May 2012 14:00:17 +0200 Subject: [Fiware-iot] weekly minutes In-Reply-To: <93D28BDF64839C468B848D14227151A203766FF8@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A203766FF8@FIESEXC014.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05F6D0FE@DEMUEXC013.nsn-intra.net> Dear All, The minutes are available at: https://forge.fi-ware.eu/docman/view.php/11/1009/IoT-Minutes-Telco-30052012.docx In order to distribute the load of taking the minutes, I suggest doing a round-robin policy within the partners instead of the always-NSN policy. The next minute taker will be NEC for the IoT weekly in two weeks. They will designate who comes after them. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed May 30 14:12:12 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 30 May 2012 14:12:12 +0200 Subject: [Fiware-iot] Unit Testing Plan Wikipage Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05F6D119@DEMUEXC013.nsn-intra.net> Dear All, As discussed, I created a wikipage for the unit testing plan: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/IoT_Private_Wiki_Page_for_Unit_Testing_Plan Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed May 30 14:39:01 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 May 2012 14:39:01 +0200 Subject: [Fiware-iot] possibility for remote presentation In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> Message-ID: <4FC614E5.2050104@tid.es> Dear all, I enclose a message from Carlos addressed to the WP3 list. I believe that this clarifies the situation a bit. Best regards, Miguel El 30/05/2012 12:07, t.elsaleh at surrey.ac.uk escribi?: Hello Denes, With regards to the 2nd educational session, would it be possible to hold a presentation on ?semantic capabilities? remotely in case of no one being able to attend on behalf of Surrey?...even though there might be a need for extended discussions with the UC project representatives in order to extract significant interest for the GEs. :) This was done for one of the presentations in the previous educational session (via Skype). I?m thinking would WebEx be a good candidate for this? Best regards, Tarek -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: CARLOS RALLI UCENDO Subject: Re: [Fiware-apps] Educational Session Madrid Date: Wed, 30 May 2012 14:29:16 +0200 Size: 26854 URL: From Tobias.Jacobs at neclab.eu Wed May 30 15:16:37 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 30 May 2012 13:16:37 +0000 Subject: [Fiware-iot] IPR info Message-ID: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance! Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed May 30 15:26:23 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 30 May 2012 16:26:23 +0300 Subject: [Fiware-iot] IPR info In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> Hi Tobias, There are no stupid questions J Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/I PR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance! Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Carmen Perea Escribano" Subject: RE: Business description and IPR URGENT Date: Fri, 25 May 2012 10:06:10 +0300 Size: 31656 URL: From t.elsaleh at surrey.ac.uk Wed May 30 15:30:26 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 30 May 2012 14:30:26 +0100 Subject: [Fiware-iot] IPR info In-Reply-To: <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA592397942@EXMB05CMS.surrey.ac.uk> Hello Lorant, Is it possible for me to get access to this? Best regards, Tarek 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: 30 May 2012 14:26 To: ext Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions :) Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance!Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed May 30 15:33:59 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 30 May 2012 16:33:59 +0300 Subject: [Fiware-iot] IPR info In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA592397942@EXMB05CMS.surrey.ac.uk> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA592397942@EXMB05CMS.surrey.ac.uk> Message-ID: <93D28BDF64839C468B848D14227151A2038BE78A@FIESEXC014.nsn-intra.net> Hello Tarek, You need to ask access from WP10 (forge/projects/project list/exploitation and "apply" or something like this on the bottom, left hand side). For your convenience this is the current content saved from the wiki. Thanks & Br, Lorant From: ext t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: Wednesday, May 30, 2012 3:30 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hello Lorant, Is it possible for me to get access to this? Best regards, Tarek 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: 30 May 2012 14:26 To: ext Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions J Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/I PR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance!Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ipr.zip Type: application/x-zip-compressed Size: 36553 bytes Desc: ipr.zip URL: From Tobias.Jacobs at neclab.eu Wed May 30 15:35:17 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 30 May 2012 13:35:17 +0000 Subject: [Fiware-iot] IPR info In-Reply-To: <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BEEE3B@Polydeuces.office.hd> Thanks for clarifying, Lorant! I agree that the new GE structure should be represented here. If it is, the IoT-Broker can move into the Things Management GE (as shown on the wiki page) as a sub-component. Best Tobias From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Mittwoch, 30. Mai 2012 15:26 To: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions :) Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance! Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From carmen.perea at atosresearch.eu Wed May 30 15:36:54 2012 From: carmen.perea at atosresearch.eu (Carmen Perea Escribano) Date: Wed, 30 May 2012 15:36:54 +0200 Subject: [Fiware-iot] IPR info In-Reply-To: <93D28BDF64839C468B848D14227151A2038BE78A@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA592397942@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A2038BE78A@FIESEXC014.nsn-intra.net> Message-ID: <5CCF3D2E156C9647BCE68B9F242101BFBB8BF8@INTMAIL02.es.int.atosorigin.com> Dear all The IoT IPR link is https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Internet_of_Things If you need access go to https://forge.fi-ware.eu/project/request.php?group_id=16 BR Carmen 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: mi?rcoles, 30 de mayo de 2012 15:34 To: t.elsaleh at surrey.ac.uk Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IPR info Hello Tarek, You need to ask access from WP10 (forge/projects/project list/exploitation and "apply" or something like this on the bottom, left hand side). For your convenience this is the current content saved from the wiki. & nbsp;Thanks & Br, Lorant From: ext t.elsaleh at surrey.ac.uk [mailto:t. elsaleh@ : Wednesday, May 30, 2012 3:30 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hello Lorant, Is it possible for me to get access to this? Best regards, Tarek 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: 30 May 2012 14:26 To: ext Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions J Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green f advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? pan lang=EN-US> I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance!Tobias ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed May 30 15:38:17 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 May 2012 15:38:17 +0200 Subject: [Fiware-iot] IPR info In-Reply-To: <93D28BDF64839C468B848D14227151A2038BE78A@FIESEXC014.nsn-intra.net> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA592397942@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A2038BE78A@FIESEXC014.nsn-intra.net> Message-ID: <4FC622C9.7060909@tid.es> Hi all There are manuals for a few usual tasks within the project. Each project member should know that they are there so all of you take a look. My advice is to check if they resolve your questions before asking, it will save time. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Main_Page#FI-WARE_Project_Handbook The answer to this question is here (Lorant is right, you must apply for access to the exploitation project): * How to join a FI-WARE project in FusionForge Best regards, Miguel El 30/05/2012 15:33, Farkas, Lorant (NSN - HU/Budapest) escribi?: Hello Tarek, You need to ask access from WP10 (forge/projects/project list/exploitation and ?apply? or something like this on the bottom, left hand side). For your convenience this is the current content saved from the wiki. Thanks & Br, Lorant From: ext t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: Wednesday, May 30, 2012 3:30 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hello Lorant, Is it possible for me to get access to this? Best regards, Tarek 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: 30 May 2012 14:26 To: ext Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions :) Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don?t have this GE any more. Maybe we should have the new GE names here, but we don?t have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance!Tobias -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed May 30 16:23:40 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 30 May 2012 14:23:40 +0000 Subject: [Fiware-iot] IPR info In-Reply-To: <8755F290097BD941865DC4245B335D2D08BEEE3B@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEEE3B@Polydeuces.office.hd> Message-ID: <19293_1338387821_4FC62D6D_19293_6774_1_976A65C5A08ADF49B9A8523F7F81925CDCF8@PEXCVZYM13.corporate.adroot.infra.ftgroup> The work I did is based on the previous architecture picture to keep consistency between deliverables. The IoT broker was a dedicated GE but I agree that now it is "just" a component of Things Management GE. The new streamlined architecture is not validated currently by Juanjo and we could have some questions from the reviewers dealing in some deliverables with some GEs which disappear in another one. This is also a point for updating the wiki in a consistent way. We should delete some old pictures to avoid any misunderstanding. Of course I expect to show the new architecture picture during the review because it is the 3rd iteration to clarify also the view for the UC projects but it is difficult to communicate on this new picture without to publish it! BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : mercredi 30 mai 2012 15:35 ? : Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] IPR info Thanks for clarifying, Lorant! I agree that the new GE structure should be represented here. If it is, the IoT-Broker can move into the Things Management GE (as shown on the wiki page) as a sub-component. Best Tobias From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Mittwoch, 30. Mai 2012 15:26 To: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions :) Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance! Tobias _________________________________________________________________________________________________________________________ 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 lorant.farkas at nsn.com Wed May 30 16:32:56 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 30 May 2012 17:32:56 +0300 Subject: [Fiware-iot] IPR info In-Reply-To: <19293_1338387821_4FC62D6D_19293_6774_1_976A65C5A08ADF49B9A8523F7F81925CDCF8@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D08BEEDF9@Polydeuces.office.hd> <93D28BDF64839C468B848D14227151A2038BE77C@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BEEE3B@Polydeuces.office.hd> <19293_1338387821_4FC62D6D_19293_6774_1_976A65C5A08ADF49B9A8523F7F81925CDCF8@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <93D28BDF64839C468B848D14227151A2038BE804@FIESEXC014.nsn-intra.net> Dear All, We are waiting for the green light for more than 2 weeks now and it's basically a blocking point. D?nes started a consistency alignment in the wiki, starting with the "materializing..." part, where we need to add the unit testing plan. Tracker would be updated in parallel with that. And as D2.3 was rejected, that would be the next step to change in our view. We can revert the changes, but if we don't do it now, we will not achieve any deliverable by "M12", I believe. Thanks & Br, Lorant From: ext thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Wednesday, May 30, 2012 4:24 PM To: Tobias Jacobs; Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info The work I did is based on the previous architecture picture to keep consistency between deliverables. The IoT broker was a dedicated GE but I agree that now it is "just" a component of Things Management GE. The new streamlined architecture is not validated currently by Juanjo and we could have some questions from the reviewers dealing in some deliverables with some GEs which disappear in another one. This is also a point for updating the wiki in a consistent way. We should delete some old pictures to avoid any misunderstanding. Of course I expect to show the new architecture picture during the review because it is the 3rd iteration to clarify also the view for the UC projects but it is difficult to communicate on this new picture without to publish it! BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : mercredi 30 mai 2012 15:35 ? : Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] IPR info Thanks for clarifying, Lorant! I agree that the new GE structure should be represented here. If it is, the IoT-Broker can move into the Things Management GE (as shown on the wiki page) as a sub-component. Best Tobias From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Mittwoch, 30. Mai 2012 15:26 To: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IPR info Hi Tobias, There are no stupid questions J Yes, this is the place according to our knowledge. See attached the e-mail requiring ASAP action. Additionally Thierry put here IoT broker which is questionnable if we don't have this GE any more. Maybe we should have the new GE names here, but we don't have a green flag from Juanjo to start advertising the new streamlined architecture (and the new GE names). In our view this should be done, since in the educational week we already showed new names. 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 Tobias Jacobs Sent: Wednesday, May 30, 2012 3:17 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IPR info Hi Thierry, hi all, This might be an stupid question, but as Thierry mentioned that some IPR information has to be entered in some deliverable by tomorrow EoB, can someone give me a hint on where this info has to be entered? I found that page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management in the private wiki of the Exploitation Chapter. It is the right place? Thanks in advance! Tobias _________________________________________________________________________________________________________________________ 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 t.elsaleh at surrey.ac.uk Wed May 30 17:10:23 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 30 May 2012 16:10:23 +0100 Subject: [Fiware-iot] possibility for remote presentation In-Reply-To: <4FC614E5.2050104@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923978C1@EXMB05CMS.surrey.ac.uk> <4FC614E5.2050104@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5923979AF@EXMB05CMS.surrey.ac.uk> Hello Miguel, Lorant, Just to clarify, I raised this issue not because I don't feel like going but due to the fact that I have to get a visa for EU travel. I really don't see my case as optional. Payam is in the US at the moment, but will try his best to make it for next Wednesday to present. Anyway in future, if there is another meeting in Spain, I hope I can rely on yourself or Carlos to assist in getting a visa. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: 30 May 2012 13:39 To: fiware-iot at lists.fi-ware.eu Cc: CARLOS RALLI UCENDO Subject: Re: [Fiware-iot] possibility for remote presentation Dear all, I enclose a message from Carlos addressed to the WP3 list. I believe that this clarifies the situation a bit. Best regards, Miguel El 30/05/2012 12:07, t.elsaleh at surrey.ac.uk escribi?: Hello Denes, With regards to the 2nd educational session, would it be possible to hold a presentation on "semantic capabilities" remotely in case of no one being able to attend on behalf of Surrey?...even though there might be a need for extended discussions with the UC project representatives in order to extract significant interest for the GEs. :) This was done for one of the presentations in the previous educational session (via Skype). I'm thinking would WebEx be a good candidate for this? Best regards, Tarek -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu May 31 13:31:34 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 31 May 2012 14:31:34 +0300 Subject: [Fiware-iot] D2.4 revised Message-ID: <93D28BDF64839C468B848D14227151A2038BEC92@FIESEXC014.nsn-intra.net> 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.ph p/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: