From lorant.farkas at nsn.com Wed Nov 2 08:59:27 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 2 Nov 2011 09:59:27 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20289D8AA@FIESEXC014.nsn-intra.net> When: 2011. november 2. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Topics for today: 1. Closing the API exercise 2. EPIC-s 3. AoB On NSN side D?nes will host this meeting, I might join later. Br, Lorant 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: 10695 bytes Desc: not available URL: From denes.bisztray at nsn.com Wed Nov 2 11:53:22 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 2 Nov 2011 11:53:22 +0100 Subject: [Fiware-iot] IoT Weekly Minutes 02/11/2011 Message-ID: <3F4C11BC54A36642BFB5875D599F47BD050CB66C@DEMUEXC013.nsn-intra.net> Dear All, Please find under this link the meeting minutes from 02/11. https://forge.fi-ware.eu/docman/view.php/11/558/IoT-Minutes-Telco-02112011.docx Feel free to edit and correct, there were some understanding issues with Payam's comments. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Wed Nov 2 12:29:22 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 2 Nov 2011 12:29:22 +0100 Subject: [Fiware-iot] Uploaded the IoT Communication EPIC's In-Reply-To: <93D28BDF64839C468B848D14227151A20289D8AA@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A20289D8AA@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A563D7DBF5@GRFMBX702BA020.griffon.local> Hi Thierry, I just uploaded in the Mediawiki the EPIC's related to the task IoT Communication (I've already prepared those last week but I had some problems to uploaded them). I've changed some EPIC's title in order to make them aligned with the task description. The changes are the following: * Protocol Integration has become Connection Protocol Adapter * Protocol Abstraction has become Communication Protocol Abstraction Definition * Protocol Generation has been removed since there is no correspondence in the task description * Location Awareness has become Mobility Management * Offline Management plus Reconnection Management has become Discontinuous Connectivity Management * Transparent Connection has been removed since there is no correspondence in the task description * User Access Control has become Access Policy Control * Device Access Control has been removed since there is no correspondence in the task description Now the EPICs structure reflects the structure of the task description. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From denes.bisztray at nsn.com Wed Nov 2 14:14:26 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 2 Nov 2011 14:14:26 +0100 Subject: [Fiware-iot] EPICs and Features Message-ID: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BacklogFiware-T5.2-v0.2.xls Type: application/vnd.ms-excel Size: 72704 bytes Desc: BacklogFiware-T5.2-v0.2.xls URL: From Tobias.Jacobs at neclab.eu Wed Nov 2 15:05:49 2011 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 2 Nov 2011 14:05:49 +0000 Subject: [Fiware-iot] IoT Weekly Minutes 02/11/2011 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD050CB66C@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD050CB66C@DEMUEXC013.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08B72B1F@PALLENE.office.hd> Hi all, I uploaded a new version of the minutes with some minor corrections. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Wednesday, November 02, 2011 11:53 AM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Weekly Minutes 02/11/2011 Dear All, Please find under this link the meeting minutes from 02/11. https://forge.fi-ware.eu/docman/view.php/11/558/IoT-Minutes-Telco-02112011.docx Feel free to edit and correct, there were some understanding issues with Payam's comments. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Nov 3 13:33:58 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 3 Nov 2011 14:33:58 +0200 Subject: [Fiware-iot] FW: Materializing Internet of Things (IoT) Services Enablement in FI-WARE Message-ID: <93D28BDF64839C468B848D14227151A2028DA182@FIESEXC014.nsn-intra.net> FYI, my own comments in bold green/red. Br, Lorant ________________________________ From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Wednesday, November 02, 2011 6:16 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest) Cc: JUAN JOSE HIERRO SUREDA Subject: Materializing Internet of Things (IoT) Services Enablement in FI-WARE Dear Thierry & Lorant, I am sending private emails to all WPLs with further comments to the "Materializing Internet of Things (IoT) Services Enablement in FI-WARE " section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . My general impression is that we are a bit lagging behind in this chapter and that efforts will have to be made to reach deadlines with enough quality to undergo a review. General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory ) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * IoT Communications/Connectivity Management * Cumulocity - "Programming artifacts" empty - done * FossTrak -The page is virtually empty and it does not follow the template. - Thierry!!! please fill the asset description according to template * IoT Communications/Service Control * Cumulocity - same as before - done * FossTrak - same as before - Thierry!!! please fill the asset description according to template * IoT Communications/Device Frontend * No assets! - done * IoT Resource Management/Services and Resources Interaction * IDAS - "Programming artifacts" empty - Ricardo!!! please fill artifacts according to template * Cumulocity - same as before - done * Fosstrak - same as before - Thierry!!! please fill the asset description according to template * ISIS - incomplete and the parts with text are very poorly populated - Ern? or Martin !!! please fill the asset description according to template * IoT-A ... - empty - Ricardo !!! please fill the asset description according to template * SOL - "Publicly available documentation - TBD" - Maarten !!! please fill the asset description according to template * Sensei - "Technologies used" empty - Ern?/Martin !!! please fill the asset description according to template * IoT Resource Management/Discovery and Resolution of Things * IoT-A - same as before * SOL - same as before * Sensei - same as before * IoT Data Handling/Local Storage * Assets in common with previous entries on the page. The "..." after Sensei hints that there are missing assets or text! Haven't we identified them by now? - Ern?/Martin !!! Please provide short description in the main page as well * IoT Data Handling/Data Pooling * Assets in common with previous entries on the page. The "..." after Sensei hints that there are missing assets or text! Haven't we identified them by now? * * IoT Data Handling/Data Access Policy * Assets in common with previous entries on the page. - Thierry!!! * IoT Data Handling/Data Handling * Assets in common with previous entries on the page. The "..." after Sensei hints that there are missing assets (or text)! Haven't we identified them by now? - we don't understand * IoT Process Automation/Template Handlers * No assets! - done * IoT Process Automation/Semantic * No assets! - done * IoT Process Automation/Exposure * No assets! Very immature, not worked on. Ern?/Martin !!! Stephan !!! Please fill the asset description according to templates 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu Nov 3 13:47:02 2011 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 03 Nov 2011 13:47:02 +0100 Subject: [Fiware-iot] [Suspected Spam] Re: FW: Materializing Internet of Things (IoT) Services Enablement in FI-WARE In-Reply-To: <93D28BDF64839C468B848D14227151A2028DA182@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2028DA182@FIESEXC014.nsn-intra.net> Message-ID: <4EB28D46.80504@tid.es> * "Assets in common with previous entries on the page. The ??? after Sensei hints that there are missing assets (or text)! Haven?t we identified them by now? - we don't understand" If I see "Sensei ..." in several places, as a reader I understand that something is missing here. And my interpretation is that either someone is going to add more assets after Sensei or that someone is going to add more text about this one. In any case, it gives the impression that it is temporary and there's work ongoing. We have to close it and leave it a stable state for now. Regards, Miguel El 03/11/2011 13:33, Farkas, Lorant (NSN - HU/Budapest) escribi?: FYI, my own comments in bold green/red. Br, Lorant ________________________________ From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Wednesday, November 02, 2011 6:16 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest) Cc: JUAN JOSE HIERRO SUREDA Subject: Materializing Internet of Things (IoT) Services Enablement in FI-WARE Dear Thierry & Lorant, I am sending private emails to all WPLs with further comments to the "Materializing Internet of Things (IoT) Services Enablement in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . My general impression is that we are a bit lagging behind in this chapter and that efforts will have to be made to reach deadlines with enough quality to undergo a review. General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source?? To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * IoT Communications/Connectivity Management * Cumulocity ? ?Programming artifacts? empty - done * FossTrak ?The page is virtually empty and it does not follow the template. - Thierry!!! please fill the asset description according to template * IoT Communications/Service Control * Cumulocity ? same as before - done * FossTrak ? same as before - Thierry!!! please fill the asset description according to template * IoT Communications/Device Frontend * No assets! - done * IoT Resource Management/Services and Resources Interaction * IDAS ? ?Programming artifacts? empty - Ricardo!!! please fill artifacts according to template * Cumulocity ? same as before - done * Fosstrak ? same as before - Thierry!!! please fill the asset description according to template * ISIS ? incomplete and the parts with text are very poorly populated - Ern? or Martin !!! please fill the asset description according to template * IoT-A ... ? empty - Ricardo !!! please fill the asset description according to template * SOL ? ?Publicly available documentation - TBD? - Maarten !!! please fill the asset description according to template * Sensei ? ?Technologies used? empty - Ern?/Martin !!! please fill the asset description according to template * IoT Resource Management/Discovery and Resolution of Things * IoT-A - same as before * SOL ? same as before * Sensei ? same as before * IoT Data Handling/Local Storage * Assets in common with previous entries on the page. The ??? after Sensei hints that there are missing assets or text! Haven?t we identified them by now? - Ern?/Martin !!! Please provide short description in the main page as well * IoT Data Handling/Data Pooling * Assets in common with previous entries on the page. The ??? after Sensei hints that there are missing assets or text! Haven?t we identified them by now? * * IoT Data Handling/Data Access Policy * Assets in common with previous entries on the page. - Thierry!!! * IoT Data Handling/Data Handling * Assets in common with previous entries on the page. The ??? after Sensei hints that there are missing assets (or text)! Haven?t we identified them by now? - we don't understand * IoT Process Automation/Template Handlers * No assets! - done * IoT Process Automation/Semantic * No assets! - done * IoT Process Automation/Exposure * No assets! Very immature, not worked on. Ern?/Martin !!! Stephan !!! Please fill the asset description according to templates 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Nov 3 17:12:21 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 3 Nov 2011 18:12:21 +0200 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> Message-ID: <93D28BDF64839C468B848D14227151A2028DA37D@FIESEXC014.nsn-intra.net> Dear All, Attached the respective e-mail mentioned by D?nes. I just realized you might not have received it, if that is the case I apologize. 1 additional remark about themes: Ricardo, you created 2 themes for one of your GE-s and neither of them has content in it. Earlier recommendation is that there is 1 theme per GE: Themes, are much more high-level or abstract than EPICs. The frontier between Themes and EPICs is also fuzzy, but is not that relevant as the frontier between EPICs and User Stories because this last frontier is what matters to know when you may stop refining. Indeed, we may adopt a convention regarding what to call Theme and what to call an EPIC. For example, we may map the notion of "Theme" to the notion of Generic Enabler in FI-WARE. Therefore, there would be a Theme linked to the "Publish/Subscribe Broker GE" which establishes as a goal that "Applications should be able to publish data and subscribe to data of their interest". The "target usage" text in the FI-WARE Product Vision / High-level Description deliverable for a given GE may well work as the content for the description of the corresponding Theme. So I suggest that either 1. task leaders create 1 theme per GE that states the goal of the respective GE, with full content, if they are able to do it by EOB tomorrow or 2. task leaders do not attempt to create themes at all Thanks & Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Wednesday, November 02, 2011 2:14 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] EPICs and Features Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-wpa] IMPORTANT Next steps regarding planning of first release and sprint Date: Mon, 24 Oct 2011 02:30:22 +0200 Size: 1991539 URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-wpa] Hints and examples about entries for the FI-WARE backlog Date: Wed, 10 Aug 2011 18:06:46 +0200 Size: 117538 URL: From rheras at tid.es Thu Nov 3 20:09:43 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 03 Nov 2011 20:09:43 +0100 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> Message-ID: <4EB2E6F7.5080304@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Nov 4 08:25:41 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 4 Nov 2011 09:25:41 +0200 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <4EB2E6F7.5080304@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> <4EB2E6F7.5080304@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> Hi Ricardo, Please see my comments inline. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Thursday, November 03, 2011 8:10 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Hi Denes, I would like to check with you the idea I have with this decomposition, for me a spring in Fiware will be = 1 month. OK. So, 1 Sprint = includes 1 or more User stories (depends on the size of the team) = 1 month (covering always a COMPLETE FUNCTIONALITY=> a complete loop of Definitio + Developement + Tests) OK. A release = 1 Feature = 3 User stories = 3 months approx. Not OK. 1 release of the IoT chapter = set of features. Approx 3 month - this is true a EPIC = Several sprints = 1 or more Features Not OK. 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. finally in the high level, a Theme = it should describe a generic enabler. There will be most likely one theme per GE. OK In this way, as a basic example, if you define: Feature=Directory of resources Not OK. Feature = epic, as said earlier User story 1 = To register a new resource => Sprint 1 month including (Definition + Develpment + Testing) User story 2 = To register a new Thing => Sprint 1 month including (Definition + Develpment + Testing) User story 3 = To get information about a resource => Sprint 2 month including (Definition + Develpment + Testing) User story 3 = To get information about a Thing => Sprint 2 month including (Definition + Develpment + Testing) etc. User stories are the right level, I think So pay attention I have not defined an User Story for defining a component, it is supposed to be included as part of every spring, and as long as you advance with new springs you can define new User Stories, but there is not any explicitly for the definition process. I don't know if this is right or not for you, but this is the idea I've based my T5.2 decomposition, br, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 rheras at tid.es Fri Nov 4 08:50:43 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 04 Nov 2011 08:50:43 +0100 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> <4EB2E6F7.5080304@tid.es> <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> Message-ID: <4EB39953.2020402@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Nov 4 09:25:44 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 4 Nov 2011 10:25:44 +0200 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <4EB39953.2020402@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> <4EB2E6F7.5080304@tid.es> <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> <4EB39953.2020402@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2028DA57C@FIESEXC014.nsn-intra.net> Dear Ricardo, The workflow could be: 1. we make sure all epics are in order, by EOB today. I will take a look at 16:00 PM and continue tomorrow morning to make the sync with the tracker 2. we start agreeing which epics could be part of the first release. If you have feature proposals for RM, then that can be already relabelled from "EPIC" to "Feature". But it is essential that no epic/feature should be in a "placeholder" status, that is when I click on it, it should not open the edit window, but it should be in a state where each field is filled 3. we start creating user stories for the identified features I recommend to take a look at cloud hosting, they are following exactly this pattern as I see. Realistically, if I look at all tasks, we might finalize the epics today but I don't see good chances that we have features defined for all tasks by the end of the day. Thanks & Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, November 04, 2011 8:51 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Thank you Lorant for your clarifications, 1 release of the IoT chapter = set of features => Yes, it's OK for me but regarding 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. following it, at this time we should only have to detail all as EPICs? as Features only would go the a first set of EPICs planned for going included in the first release? thanks again, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Hi Ricardo, Please see my comments inline. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Thursday, November 03, 2011 8:10 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Hi Denes, I would like to check with you the idea I have with this decomposition, for me a spring in Fiware will be = 1 month. OK. So, 1 Sprint = includes 1 or more User stories (depends on the size of the team) = 1 month (covering always a COMPLETE FUNCTIONALITY=> a complete loop of Definitio + Developement + Tests) OK. A release = 1 Feature = 3 User stories = 3 months approx. Not OK. 1 release of the IoT chapter = set of features. Approx 3 month - this is true a EPIC = Several sprints = 1 or more Features Not OK. 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. finally in the high level, a Theme = it should describe a generic enabler. There will be most likely one theme per GE. OK In this way, as a basic example, if you define: Feature=Directory of resources Not OK. Feature = epic, as said earlier User story 1 = To register a new resource => Sprint 1 month including (Definition + Develpment + Testing) User story 2 = To register a new Thing => Sprint 1 month including (Definition + Develpment + Testing) User story 3 = To get information about a resource => Sprint 2 month including (Definition + Develpment + Testing) User story 3 = To get information about a Thing => Sprint 2 month including (Definition + Develpment + Testing) etc. User stories are the right level, I think So pay attention I have not defined an User Story for defining a component, it is supposed to be included as part of every spring, and as long as you advance with new springs you can define new User Stories, but there is not any explicitly for the definition process. I don't know if this is right or not for you, but this is the idea I've based my T5.2 decomposition, br, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 rheras at tid.es Fri Nov 4 09:40:18 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 04 Nov 2011 09:40:18 +0100 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <93D28BDF64839C468B848D14227151A2028DA57C@FIESEXC014.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> <4EB2E6F7.5080304@tid.es> <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> <4EB39953.2020402@tid.es> <93D28BDF64839C468B848D14227151A2028DA57C@FIESEXC014.nsn-intra.net> Message-ID: <4EB3A4F2.8080005@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Nov 4 09:52:04 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 4 Nov 2011 10:52:04 +0200 Subject: [Fiware-iot] EPICs and Features In-Reply-To: <4EB3A4F2.8080005@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD050CB835@DEMUEXC013.nsn-intra.net> <4EB2E6F7.5080304@tid.es> <93D28BDF64839C468B848D14227151A2028DA4D8@FIESEXC014.nsn-intra.net> <4EB39953.2020402@tid.es> <93D28BDF64839C468B848D14227151A2028DA57C@FIESEXC014.nsn-intra.net> <4EB3A4F2.8080005@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2028DA5E5@FIESEXC014.nsn-intra.net> Hi Ricardo, Inline. Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, November 04, 2011 9:40 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features HI Lorant, I think that the critical difference is how is your level of decomposition of a EPIC to be tackled in a release, I mean, if the 'element' can't be included in a unique release, it is a EPIC. Yes, and even more, if the element can't be included in a sprint, already then it is an epic. This EPIC needs additional decomposition in order to be included in a release (3 months), so then you have 'Features' with a deep level of detail that allows you to be developed in a release (3 months). True. So I think the difference is not only a temporal point of view, True. So when we "relabel", we should somehow make sure no feature exceeds 3 months. R. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear Ricardo, The workflow could be: 1. we make sure all epics are in order, by EOB today. I will take a look at 16:00 PM and continue tomorrow morning to make the sync with the tracker 2. we start agreeing which epics could be part of the first release. If you have feature proposals for RM, then that can be already relabelled from "EPIC" to "Feature". But it is essential that no epic/feature should be in a "placeholder" status, that is when I click on it, it should not open the edit window, but it should be in a state where each field is filled 3. we start creating user stories for the identified features I recommend to take a look at cloud hosting, they are following exactly this pattern as I see. Realistically, if I look at all tasks, we might finalize the epics today but I don't see good chances that we have features defined for all tasks by the end of the day. Thanks & Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, November 04, 2011 8:51 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Thank you Lorant for your clarifications, 1 release of the IoT chapter = set of features => Yes, it's OK for me but regarding 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. following it, at this time we should only have to detail all as EPICs? as Features only would go the a first set of EPICs planned for going included in the first release? thanks again, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Hi Ricardo, Please see my comments inline. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Thursday, November 03, 2011 8:10 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Hi Denes, I would like to check with you the idea I have with this decomposition, for me a spring in Fiware will be = 1 month. OK. So, 1 Sprint = includes 1 or more User stories (depends on the size of the team) = 1 month (covering always a COMPLETE FUNCTIONALITY=> a complete loop of Definitio + Developement + Tests) OK. A release = 1 Feature = 3 User stories = 3 months approx. Not OK. 1 release of the IoT chapter = set of features. Approx 3 month - this is true a EPIC = Several sprints = 1 or more Features Not OK. 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. finally in the high level, a Theme = it should describe a generic enabler. There will be most likely one theme per GE. OK In this way, as a basic example, if you define: Feature=Directory of resources Not OK. Feature = epic, as said earlier User story 1 = To register a new resource => Sprint 1 month including (Definition + Develpment + Testing) User story 2 = To register a new Thing => Sprint 1 month including (Definition + Develpment + Testing) User story 3 = To get information about a resource => Sprint 2 month including (Definition + Develpment + Testing) User story 3 = To get information about a Thing => Sprint 2 month including (Definition + Develpment + Testing) etc. User stories are the right level, I think So pay attention I have not defined an User Story for defining a component, it is supposed to be included as part of every spring, and as long as you advance with new springs you can define new User Stories, but there is not any explicitly for the definition process. I don't know if this is right or not for you, but this is the idea I've based my T5.2 decomposition, br, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Nov 8 09:18:03 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 8 Nov 2011 10:18:03 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2029252A8@FIESEXC014.nsn-intra.net> When: 2011. november 9. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, The agenda proposal for tomorrow: 1. User stories/work items: -we will explain this new "work item" concept and the relationship with user stories 2. Backlog & tracker: what do we still have to do until November the 10th (epics/themes/user stories/work items/tracker) 3. Revised architecture: D?nes created such an architecture and we should talk this through to see whether we have the same understanding 4. Next steps: -we need to plan what we do in the first, shorter sprint (that is from now until the 30th of November), per partner - clarification of epics (that is in fact the short definition of work items), eventually implementation (if that is the case) -we need to discuss when and how do we plan the second sprint (December) Thanks & Br, Lorant 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: 11013 bytes Desc: not available URL: From denes.bisztray at nsn.com Tue Nov 8 09:43:43 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 8 Nov 2011 09:43:43 +0100 Subject: [Fiware-iot] IoT SE Complete Architecture Message-ID: <3F4C11BC54A36642BFB5875D599F47BD0515F5FC@DEMUEXC013.nsn-intra.net> Dear All, I created a component-level overview of the IoT SE architecture. I recommend the task leaders to have a look at it. It would be nice to make clear where the various GEs may run. https://forge.fi-ware.eu/docman/view.php/11/570/v01-CompleteArchitecture.pptx Please comment and correct it. As a second step it would be nice to put the selected assets to the components to see how the various things interact with each other. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Nov 8 14:41:32 2011 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 8 Nov 2011 14:41:32 +0100 Subject: [Fiware-iot] IoT SE Complete Architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD0515F5FC@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD0515F5FC@DEMUEXC013.nsn-intra.net> Message-ID: Hi Denes, all, I think that in this view the things-level API could be hosted into the gateway. Typically a gateway could represent a building or a floor and resources and services discovery are useful at the gateway level, may be a local catalog and location service. BR THierry De : Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Envoy? : mardi 8 novembre 2011 09:44 ? : fiware-iot at lists.fi-ware.eu Cc : rheras at tid.es; Guerra Sabrina; ext Fici Gian Piero; NAGELLEN Thierry RD-BIZZ-SOP Objet : IoT SE Complete Architecture Dear All, I created a component-level overview of the IoT SE architecture. I recommend the task leaders to have a look at it. It would be nice to make clear where the various GEs may run. https://forge.fi-ware.eu/docman/view.php/11/570/v01-CompleteArchitecture.pptx Please comment and correct it. As a second step it would be nice to put the selected assets to the components to see how the various things interact with each other. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Nov 9 09:49:49 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 9 Nov 2011 09:49:49 +0100 Subject: [Fiware-iot] IoT SE Complete Architecture In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD0515F5FC@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD0515FD31@DEMUEXC013.nsn-intra.net> Hi Thierry, all, I just updated the architecture diagram based on your requirements, here it is: https://forge.fi-ware.eu/docman/view.php/11/578/v02-CompleteArchitecture.pptx Best, D?nes From: ext thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Tuesday, November 08, 2011 2:42 PM To: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: rheras at tid.es; sabrina.guerra at telecomitalia.it; gianpiero.fici at telecomitalia.it Subject: RE: IoT SE Complete Architecture Hi Denes, all, I think that in this view the things-level API could be hosted into the gateway. Typically a gateway could represent a building or a floor and resources and services discovery are useful at the gateway level, may be a local catalog and location service. BR THierry De : Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Envoy? : mardi 8 novembre 2011 09:44 ? : fiware-iot at lists.fi-ware.eu Cc : rheras at tid.es; Guerra Sabrina; ext Fici Gian Piero; NAGELLEN Thierry RD-BIZZ-SOP Objet : IoT SE Complete Architecture Dear All, I created a component-level overview of the IoT SE architecture. I recommend the task leaders to have a look at it. It would be nice to make clear where the various GEs may run. https://forge.fi-ware.eu/docman/view.php/11/570/v01-CompleteArchitecture.pptx Please comment and correct it. As a second step it would be nice to put the selected assets to the components to see how the various things interact with each other. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Nov 9 13:02:59 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 9 Nov 2011 14:02:59 +0200 Subject: [Fiware-iot] IoT Weekly Minutes 09/11/2011 Message-ID: <93D28BDF64839C468B848D14227151A20295C8B1@FIESEXC014.nsn-intra.net> Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/580/IoT-Minutes-Telco-091120 11.docx The e-mail from Juanjo on "work items" for your information, one of my AP-s is to send it over: <<[Fiware-wpa] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint>> Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-wpa] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Date: Fri, 4 Nov 2011 15:02:51 +0200 Size: 2001031 URL: From lorant.farkas at nsn.com Thu Nov 10 15:32:56 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 10 Nov 2011 16:32:56 +0200 Subject: [Fiware-iot] Wiki + tracker frozen today at 17:00 Message-ID: <93D28BDF64839C468B848D14227151A20295D0D8@FIESEXC014.nsn-intra.net> Dear All, All of you from the IoT WP editing Wiki and tracker please stop latest at 17:00 today. It would even be better if you stopped now and I will still make some editing until 17:00. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Nov 14 08:00:48 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 14 Nov 2011 09:00:48 +0200 Subject: [Fiware-iot] FW: [Fiware-wpa] Comments on the Backlog information available on theWiki/Tracker Message-ID: <93D28BDF64839C468B848D14227151A20295D7F9@FIESEXC014.nsn-intra.net> I am really sorry for this, applies to us as well... * You have capitalized all letters of the field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story). While not super-critical it leaves a bad impression and it would be better to fix it. The issue here is that you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. Not so hard if the task is distributed, otherwise is a bit painful. Could task leaders take care of this ASAP (Orange for Data Handling, TID for Resource Management, TI for Communications, NSN for Process automation)? Please give feedback. If I don't hear from you until 10 AM, NSN will start doing it for all tasks. 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, November 14, 2011 7:01 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Comments on the Backlog information available on theWiki/Tracker Hi all, Please find enclosed the email I have just sent to the FI-WARE Apps team regarding issues I have found after a more detailed analysis of the info about backlog entries both on the Wiki and the tracker. I forward it to all of you because there may be some issues that might be also present in your backlog. While I'm elaborating the detailed comments for each and every chapter and I will forward them to you asap, I'm dealing with each chapter in sequence, so that it is worth that you give it some time to review the ones that I have sent to other chapters and try to extract those that may apply to yours. In the meantime, you may also take care of the comments I forwarded to you last Friday. Overall, those dealing with updates on the FI-WARE Product Vision (High-level Description) needed to address comments by reviewers, since we are going to generate a .pdf book for the official submission of the FI-WARE Product Vision deliverable tonight, based on contents of the Wiki at that time. Cheers, -- Juanjo -------- Original Message -------- Subject: [Fiware-apps] Detailed comments on the Apps Backlog information available on the Wiki/Tracker Date: Mon, 14 Nov 2011 06:54:26 +0100 From: Juanjo Hierro To: andreas.friesen at sap.com , Leidig, Torsten CC: fiware-apps at lists.fi-ware.eu Dear Andreas, Torsten, Markus, Here it is a list of issues you have to review regarding backlog entries both on the Wiki and the tracker. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of that market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). I copy the FI-WARE Apps team so that they receive the comments as soon as possible and start to analyze them. They should wait for your further instructions regarding those issues for which they find that the action to be done is not that clear or too hard to implement. Best regards, -- Juanjo Apps/Services Ecosystem and Delivery: * General comments: * There are some tickets on the tracker that may need to be deleted ... apparently they do not match any entry on the Wiki (e.g., one with summary="Service Assembly" issued by Nazila Gol mohammadi) * The language used for describing goals in the template defined in August for backlog entries has not been followed in many cases. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * You refer to "Model Repository" and on the tracker, while talking about "Service Repository" and "Registry" on the Wiki. Please fix this and keep one single vocabulary. BTW, whatever terms you finally decide to go should also be used accordingly in the FI-WARE Product Vision. * Are you sure that you are going to get all what you have labeled as "STORY" finished by end of the first Sprint (i.e., end of November) ? When planning a Story like FIWARE.STORY.Apps.Repository.UploadServiceDescription in the first Sprint ... Are you considering not just the specification of the final interfaces to be supported by the baseline asset or even its implementation? If it was just the specification, probably you need to translate Stories into Features and then define a work-item linked to creating the interface specifications that you can address in the first Sprint. * The "Description" field of some backlog entries on the Wiki is empty. This is not acceptable. * There are some tickets on the tracker that have assigned an Id which doesn't map the convention "FIWARE..Apps.." ... are they deprecated entries that were created long time ago as some kind of test of the tracker ? If so, please delete. * All entries that have been planned for the first Sprint, should have "FIWARE.Release.1.1" as value of the "FI-WARE Release Id" in the tracker. * You have capitalized all letters of the field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story). While not super-critical it leaves a bad impression and it would be better to fix it. The issue here is that you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. Not so hard if the task is distributed, otherwise is a bit painful. * USDL: * There is one entry that is labeled as to be address in Sprint FIWARE.Sprint.1.1.2. This would not be consistent with Agile principles: you can only plan what user-stories/work-items will come in the current (or about to start) sprint. You never plan what will go in following sprints. Maybe it's a typo ... * Regarding the only feature that has been identified ... it sounds like a bit strange that you declare as goal "The feature will provide basic description elements for services including general information, composition, simple pricing and service level agreements." ... saying "USDL will provide basic description elements ..." instead, sounds a bit more appropriate. * Model Repository: * There is a ticket for which I haven't found a correspondence on the Wiki: FIWARE.STORY.Apps.Registry.RegisterStore * A typo in ticket "FIWARE.STORY.Apps.Repository.RetrieveServiceDescription". You have FIWARE.1.1.1 instead of FIWARE.Sprint.1.1.1 as Sprint Id. * The goals in some tickets are defined as "TBD". You just need to copy&paste the goal of the corresponding entry on the Wiki. * There is an backlog entry described on the Wiki but without ticket on the tracker * Registry: * I miss a ticket on the tracker linked to the FIWARE.STORY.Apps.Registry.RegisterStore entry on the Wiki * I'm afraid there is a typo and should read "has" when you say: "Provider information will also be described using a Linked Data vocabulary, which have to be defined." in FIWARE.STORY.Apps.Registry.LDProviderSpecification * What's the difference between the FIWARE.STORY.Apps.Registry.LDProviderSpecification and the FIWARE.STORY.Apps.Registry.RegisterProvider ? Reading the goal is hard to say. * Marketplace: * The goal in some tickets is defined as "TBD". You just need to copy&paste the goal of the corresponding entry on the Wiki. * I believe that comprising all functions to be supported by the Marketplace in a single "Feature" is too much. It had been more elegant to have a separate feature per each function (Offering, Storing, Rating, Review, Search, Discovery, Comparison, Analytics, Monitoring). As highlighted as general comment, It is not clear whether each Story identified as FIWARE.STORY.Apps.Marketplace.API refers to just specification of the API or even the implementation of such API. Are you going to complete both the specification and implementation within the 1st Sprint (i.e., end of November) ? If it was just trying to cover the specification of the API, it had been better to turn each Story identified as FIWARE.STORY.Apps.Marketplace.API into a Feature identified as FIWARE.Feature.Apps.Marketplace. planned for the first minor release (note that we have dropped the "API" in the last part of the Id) and then create a Work-item (you just need to create the ticket, not the description on the Wiki) identified as FIWARE.WorkItem.Apps.Marketplace.API planned for the first Sprint. * The ticket linked to the FIWARE.STORY.Apps.Marketplace.OfferingAPI entry seems to be repeated, please delete one. * Store: * Where are the tickets on the tracker linked to these entries ? Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker) * BM&BE Provisioning System: * Where are the tickets on the tracker linked to these entries ? Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker) * Revenue Settlement and Share System: * For a matter of consistency across all entries in the backlog, you should drop the term "Goal" in the Description within the tracker. * Comment general above (similar to the one given for the markeplace) also applies here: please confirm that those stories planned for 1st Sprint do not just deal with definition of interface specifications * Composition: * Apparently, lots of entries whose description is available on the Wiki do not have a corresponding ticket on the tracker. * This is more fundamental: there are several Composition technologies considered here. I rather believe each should have been categorized as an independent Generic Enabler, with its own backlog. Why should we mix the backlog linked to the Ericsson Common Composition Engine with the backlog linked to the WireCloud Mashup Platform ? Maybe it's too late to get this fixed for the official review but deserves discussion. If agreed with the change, I can live without updating the contents of the FI-WARE Vision (Apps/Services Ecosystem and Delivery chapter) but establishing the distinction between the different GEs within the "Materializing Applications/Services Ecosystem and Delivery in FI-WARE" page on the Wiki. * Mediation: * Where are the tickets on the tracker linked to these entries ? Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker) * SLA Management: * Where are the tickets on the tracker linked to these entries ? Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker) * Multi-channel/Multi-device Access System: * Where are the tickets on the tracker linked to these entries ? Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker) ________________________________ 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: ATT00001..txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT2130484.txt URL: From jhierro at tid.es Mon Nov 14 12:38:30 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 14 Nov 2011 12:38:30 +0100 Subject: [Fiware-iot] Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker In-Reply-To: <4EC0FD21.6070406@tid.es> References: <4EC0FD21.6070406@tid.es> Message-ID: <4EC0FDB6.305@tid.es> Hi, I forward the email I have just sent to both Thierry and Lorant to the FI-WARE Apps team so that they receive the comments as soon as possible and start to analyze them. They should wait for your further instructions, overall regarding those issues for which they find that the action to be done is not that clear or too hard to implement. Thanks, -- Juanjo -------- Original Message -------- Subject: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Date: Mon, 14 Nov 2011 12:36:01 +0100 From: Juanjo Hierro To: 'Thierry.nagellen at orange-ftgroup.com' , Farkas, Lorant (NSN - HU/Budapest) CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear Thierry and Lorant, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). Please forward them to members of your team as soon as possible. I copy the rest of the WPLs and WPAs because I haven't sent my detailed comments to all of them and it might be worth that they review your comments to find out what may apply to them as well. This may help them to anticipate any issue on their respective chapters. Best regards, -- Juanjo IoT Service Enablement: * General comments: * It seems like there are contents on the Wiki that are replicated !!! Please avoid duplication * You have capitalized all letters of the field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story). While not super-critical it leaves a bad impression and it would be better to fix it. The issue here is that you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. Not so hard if the task is distributed, otherwise is a bit painful. * Some entries linked to Features have a value assigned to the "FI-WARE Sprint Id" field which doesn't make sense. The "FI-WARE Sprint Id" field should only be filled for user-stories or WorkItems. * IoT Communication/Connectivity Management: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ConnectivityManagement.DiscontinuousConnectivityManagement: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... Note that in the case of WorkItems you won't need to create an entry on the Wiki. * IoT Communication/Service Control: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ServiceControl.NameResolution: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Communication/Device FrontEnd: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a ticket on the tracker linked to a backlog entry with Id = FIWARE.EPIC.IoT.DevicesFrontEnd.NativeProtocol but I guess it should refer to FIWARE.Epic.IoT.DevicesFrontEnd.NativeProtocolAdapter. The URL should also be fixed accordingly. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Resource Management/Services and Resources Interaction: * There are some tickets on the tracker that do not follow the convention defined for the Id of the entry. You have, for example, FIWARE.Userstory.IoT.ResourcesAndServicesDiscovery.DiscoverResource.Definition and "UserStory" should be "Story". It is correct on the Wiki but not the tracker. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There are some inconsistencies between backlog entries on the tracker and on the Wiki. Please align. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Are you sure that you are going to get all what you have labeled as "Story" and planned for the first FI-WARE Sprint finished by end of November ? When planning a Story in the first Sprint ... Are you considering not just the specification of the final interfaces to be supported by the baseline asset or even its implementation? If it was just the specification, probably you need to translate Stories into Features and then define a work-item linked to design/definition of the interface specifications that you can address in the first Sprint. * IoT Resource Management/Discovery and Resolution of Things: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Template Handler * There is a ticket linked to a backlog entry referred as FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution which doesn't have correspondence with anything on the Wiki * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Semantic * There is a ticket linked to a backlog entry referred as FIWARE.EPIC.IoT.Semantic.SemanticMediator which doesn't have correspondence with anything on the Wiki. Apparently, it links to one Feature listed on the Wiki so seems like it's just a matter of labeling the entry as linked to a feature rather than an Epic. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Exposure * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.ThingBasedQuery * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.AsynchronousThingBasedInteraction * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Local Storage * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Pooling * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Access Policy * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Handling * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.DataHandling.EventsGenerator.M2mPlanet, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Isis, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Ngsi or FIWARE.Feature.IoT.DataHandling.EventsGenerator.EventTemplate. * The ticket linked to entry FIWARE.FEATURE.IoT.DataHandling.IoTSubscribe.Device seems to be duplicated on the tracker ... Maybe one should be linked to IoTPublish.Device ? * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). ________________________________ 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: ATT00001..txt URL: From lorant.farkas at nsn.com Mon Nov 14 13:00:25 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 14 Nov 2011 14:00:25 +0200 Subject: [Fiware-iot] FW: Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Message-ID: <93D28BDF64839C468B848D14227151A2029A4C65@FIESEXC014.nsn-intra.net> FYI ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Monday, November 14, 2011 12:39 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Hi, I forward the email I have just sent to both Thierry and Lorant to the FI-WARE Apps team so that they receive the comments as soon as possible and start to analyze them. They should wait for your further instructions, overall regarding those issues for which they find that the action to be done is not that clear or too hard to implement. Thanks, -- Juanjo -------- Original Message -------- Subject: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Date: Mon, 14 Nov 2011 12:36:01 +0100 From: Juanjo Hierro To: 'Thierry.nagellen at orange-ftgroup.com' , Farkas, Lorant (NSN - HU/Budapest) CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear Thierry and Lorant, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). Please forward them to members of your team as soon as possible. I copy the rest of the WPLs and WPAs because I haven't sent my detailed comments to all of them and it might be worth that they review your comments to find out what may apply to them as well. This may help them to anticipate any issue on their respective chapters. Best regards, -- Juanjo IoT Service Enablement: * General comments: * It seems like there are contents on the Wiki that are replicated !!! Please avoid duplication * You have capitalized all letters of the field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story). While not super-critical it leaves a bad impression and it would be better to fix it. The issue here is that you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. Not so hard if the task is distributed, otherwise is a bit painful. * Some entries linked to Features have a value assigned to the "FI-WARE Sprint Id" field which doesn't make sense. The "FI-WARE Sprint Id" field should only be filled for user-stories or WorkItems. * IoT Communication/Connectivity Management: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ConnectivityManagement.DiscontinuousConnectivityManagement: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... Note that in the case of WorkItems you won't need to create an entry on the Wiki. * IoT Communication/Service Control: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ServiceControl.NameResolution: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Communication/Device FrontEnd: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a ticket on the tracker linked to a backlog entry with Id = FIWARE.EPIC.IoT.DevicesFrontEnd.NativeProtocol but I guess it should refer to FIWARE.Epic.IoT.DevicesFrontEnd.NativeProtocolAdapter. The URL should also be fixed accordingly. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Resource Management/Services and Resources Interaction: * There are some tickets on the tracker that do not follow the convention defined for the Id of the entry. You have, for example, FIWARE.Userstory.IoT.ResourcesAndServicesDiscovery.DiscoverResource.Definition and "UserStory" should be "Story". It is correct on the Wiki but not the tracker. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There are some inconsistencies between backlog entries on the tracker and on the Wiki. Please align. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Are you sure that you are going to get all what you have labeled as "Story" and planned for the first FI-WARE Sprint finished by end of November ? When planning a Story in the first Sprint ... Are you considering not just the specification of the final interfaces to be supported by the baseline asset or even its implementation? If it was just the specification, probably you need to translate Stories into Features and then define a work-item linked to design/definition of the interface specifications that you can address in the first Sprint. * IoT Resource Management/Discovery and Resolution of Things: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Template Handler * There is a ticket linked to a backlog entry referred as FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution which doesn't have correspondence with anything on the Wiki * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Semantic * There is a ticket linked to a backlog entry referred as FIWARE.EPIC.IoT.Semantic.SemanticMediator which doesn't have correspondence with anything on the Wiki. Apparently, it links to one Feature listed on the Wiki so seems like it's just a matter of labeling the entry as linked to a feature rather than an Epic. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Exposure * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.ThingBasedQuery * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.AsynchronousThingBasedInteraction * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Local Storage * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Pooling * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Access Policy * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Handling * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.DataHandling.EventsGenerator.M2mPlanet, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Isis, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Ngsi or FIWARE.Feature.IoT.DataHandling.EventsGenerator.EventTemplate. * The ticket linked to entry FIWARE.FEATURE.IoT.DataHandling.IoTSubscribe.Device seems to be duplicated on the tracker ... Maybe one should be linked to IoTPublish.Device ? * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). ________________________________ 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: ATT00001..txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT2258566.txt URL: From lorant.farkas at nsn.com Tue Nov 15 13:39:26 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 15 Nov 2011 14:39:26 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2029A53EF@FIESEXC014.nsn-intra.net> When: 2011. november 16. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We will dedicate the meeting tomorrow to work items/user stories. Task leaders please prepare for this. To remind: -work items are "work to be done" in the first sprint (from now until end of November) in case we don't reach the level of user stories -user stories are "work to be done", consituents of "features", visible also in the wiki -"features" are packages of user stories that we deal within 1 release (from now until end of January) Tomorrow we should: 1. gain an understanding for each task about the planned work items (what is required to reach the user story level) and user stories (in case these exist) for our current sprint 2. in case of user stories gain an understanding which partner is going to implement exactly what over what asset 3. speak about the planning of the 2nd sprint, between 1-31 December which should already be a real sprint (only user stories, no more work items) Thanks & Br, Lorant 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: 11184 bytes Desc: not available URL: From denes.bisztray at nsn.com Wed Nov 16 12:35:42 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 16 Nov 2011 12:35:42 +0100 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 Message-ID: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/614/IoT-Minutes-Telco-16112011.docx Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Nov 16 13:17:59 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 16 Nov 2011 13:17:59 +0100 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> Message-ID: <0D2446AEB6CAED48BB046223733964A54C42F61C88@DEWDFECCR01.wdf.sap.corp> I made a small change correcting what was said regarding the availability of the IoT-A assets. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Mittwoch, 16. November 2011 12:36 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/614/IoT-Minutes-Telco-16112011.docx Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Wed Nov 16 14:21:58 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Wed, 16 Nov 2011 13:21:58 +0000 Subject: [Fiware-iot] (no subject) Message-ID: Hi Lorant, A colleague of mine, Tarek Elsaleh is joining our FI-WARE team at University of Surrey. He will register on Forge. At the mean time, can you please add him to the IoT mailing list. Tarek has been involved in research and implementation tasks in Sensei and IoT-A projects; so he has the background on some of the features that are going to be developed in the context of FI-Ware IoT. Many thanks, Payam From lorant.farkas at nsn.com Wed Nov 16 16:48:26 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 16 Nov 2011 17:48:26 +0200 Subject: [Fiware-iot] (no subject) In-Reply-To: References: Message-ID: <93D28BDF64839C468B848D14227151A2029DEEED@FIESEXC014.nsn-intra.net> Hi Payam, He has to register himself to the mailing list on lists.fi-ware.eu to fiware-iot, I cannot add him myself, only approve. For Forge I can register him to the FIWARE project and to our IoT chapter part, once he registers in Forge. Now I don't see him yet in the user list. Thanks & Br, Lorant -----Original Message----- From: ext P.Barnaghi at surrey.ac.uk [mailto:P.Barnaghi at surrey.ac.uk] Sent: Wednesday, November 16, 2011 2:22 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); T.Elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu Subject: Hi Lorant, A colleague of mine, Tarek Elsaleh is joining our FI-WARE team at University of Surrey. He will register on Forge. At the mean time, can you please add him to the IoT mailing list. Tarek has been involved in research and implementation tasks in Sensei and IoT-A projects; so he has the background on some of the features that are going to be developed in the context of FI-Ware IoT. Many thanks, Payam From rheras at tid.es Wed Nov 16 17:35:59 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Wed, 16 Nov 2011 17:35:59 +0100 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> Message-ID: <4EC3E66F.6080604@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Nov 17 16:55:03 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 17 Nov 2011 17:55:03 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2029DF5D6@FIESEXC014.nsn-intra.net> When: 2011. november 24. 12:30-14:00 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* 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: 10521 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Nov 17 16:56:02 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 17 Nov 2011 17:56:02 +0200 Subject: [Fiware-iot] FW: TR: Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Message-ID: <93D28BDF64839C468B848D14227151A2029DF5DB@FIESEXC014.nsn-intra.net> The promised examples on work items. Br, Lorant ________________________________ From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Monday, November 14, 2011 4:10 PM To: thierry.nagellen at orange.com Cc: Farkas, Lorant (NSN - HU/Budapest); jhierro >> "Juan J. Hierro" Subject: Re: TR: [Fiware-iot] Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker On 14/11/11 15:13, thierry.nagellen at orange.com wrote: Hi Juanjo This point regarding Workitems is not clear to me. You agreed during the last WPL/WPA telco that IoT is a bit late because of assets selection and standards analysis Yes ... and that we have to delete all empty entries (in our case, typically User Stories) Yes, I recommended to avoid sections linked to Features or UserStories, for example, where you simply had an empty list (a single empty bullet). and now you expect we create some WokrItems entries. Yes, what I expect to see is something in the backlog (either in the form of UserStory or WorkItem) that explain to me what you are going to do in the 1st Sprint. Otherwise ... How could I answer the question about what does the IoT chapter team planning to get done by end of November ? As we explained that we will spend the next 10 days to describe the missing User Stories, do you want a WorkItems " describe user stories"? Or in another case do we have to describe the User Stories now ... and this is impossible. If you are simply going to work on refining identified Epic/Features that's fine. Just want to know. On the other hand, I envision that there are some WorkItems that would be nice to reflect like "Analyzing compatibility of the NGSI and OGC specifications for the Northbound APIs exposed to programmers" which give some more info and allow us to monitor progress. What do you expect exactly regarding WorkItems? To reflect any work to be done during the 1st sprint (that is, the period betwwen now and end of november) that would make sense to record and monitor beyond just "refinement of existing Epics/Features in order to identify Work Items and User Stories for the next sprint" (working on refinement of backlog entries doesn't need to be reflected in the form of backlog entries itself). A good example of Work Item (don't not if addressed in the first sprint or later) is the one I have mentioned regarding analysis of OGC and NGSI, but let me elaborate on another example of WorkItems and UserStories that may be helpful in describing how the Backlog may evolve ... You may find out that we wish to support Features A, B and C for a given Generic Enabler that is part of the IoT Service Enablement Architecture. For example, you may have a GE which is a kind of Directory, supporting three Features: * A=creation/deletion/modification of entries, * B=discovery of entries that match some given criteria, * C=ability to subscribe to events linked to creation/deletion/modification of entries in the Directory. You may decide that such Features will be exposed through a well defined API. Therefore, all the three Features may get refined into: * one single WorkItem M consisting in "Specifying a well-defined REST interface 'I' through which operations exposing features A and B are exposed", * another WorkItem N consisting on "Extending specifications of interface 'I' to include operations supporting feature C", * three UserStories O, P and Q corresponding to implementation of the operations in the REST interface 'I' exposing features A, B and C respectively. Then, you may decide: * to address WorkItem M in Sprint X of the first minor release and then in Sprint X+1, also of the first minor release, you decide to address the implementation of UserStories O and P * leave WorkItem N and UserStory Q to the second minor release of FI-WARE. Note that in this example we are illustrating how Agile works differently than the traditional waterfall models: we are not waiting for finalizing the complete specification of interface 'I' to start implementing part of it. Does it make sense to you ? Hope these examples help. If you believe so, don't hesitate to share with the rest of your team. Best regards, -- Juanjo BR Thierry 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? : lundi 14 novembre 2011 12:39 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Fwd: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Hi, I forward the email I have just sent to both Thierry and Lorant to the FI-WARE Apps team so that they receive the comments as soon as possible and start to analyze them. They should wait for your further instructions, overall regarding those issues for which they find that the action to be done is not that clear or too hard to implement. Thanks, -- Juanjo -------- Original Message -------- Subject: Detailed comments on the IoT Backlog information available on the Wiki/Tracker Date: Mon, 14 Nov 2011 12:36:01 +0100 From: Juanjo Hierro To: 'Thierry.nagellen at orange-ftgroup.com' , Farkas, Lorant (NSN - HU/Budapest) CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear Thierry and Lorant, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). Please forward them to members of your team as soon as possible. I copy the rest of the WPLs and WPAs because I haven't sent my detailed comments to all of them and it might be worth that they review your comments to find out what may apply to them as well. This may help them to anticipate any issue on their respective chapters. Best regards, -- Juanjo IoT Service Enablement: * General comments: * It seems like there are contents on the Wiki that are replicated !!! Please avoid duplication * You have capitalized all letters of the field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story). While not super-critical it leaves a bad impression and it would be better to fix it. The issue here is that you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. Not so hard if the task is distributed, otherwise is a bit painful. * Some entries linked to Features have a value assigned to the "FI-WARE Sprint Id" field which doesn't make sense. The "FI-WARE Sprint Id" field should only be filled for user-stories or WorkItems. * IoT Communication/Connectivity Management: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ConnectivityManagement.DiscontinuousConnectivityManagement: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... Note that in the case of WorkItems you won't need to create an entry on the Wiki. * IoT Communication/Service Control: * Something strange happens with the entry identified as FIWARE.EPIC.IoT.ServiceControl.NameResolution: It exists in the tracker but not on the Wiki ... The URL that is provided in the ticket works but navigates to a Wiki page that is not the one that you would expect. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Communication/Device FrontEnd: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a ticket on the tracker linked to a backlog entry with Id = FIWARE.EPIC.IoT.DevicesFrontEnd.NativeProtocol but I guess it should refer to FIWARE.Epic.IoT.DevicesFrontEnd.NativeProtocolAdapter. The URL should also be fixed accordingly. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Resource Management/Services and Resources Interaction: * There are some tickets on the tracker that do not follow the convention defined for the Id of the entry. You have, for example, FIWARE.Userstory.IoT.ResourcesAndServicesDiscovery.DiscoverResource.Definition and "UserStory" should be "Story". It is correct on the Wiki but not the tracker. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There are some inconsistencies between backlog entries on the tracker and on the Wiki. Please align. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Are you sure that you are going to get all what you have labeled as "Story" and planned for the first FI-WARE Sprint finished by end of November ? When planning a Story in the first Sprint ... Are you considering not just the specification of the final interfaces to be supported by the baseline asset or even its implementation? If it was just the specification, probably you need to translate Stories into Features and then define a work-item linked to design/definition of the interface specifications that you can address in the first Sprint. * IoT Resource Management/Discovery and Resolution of Things: * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Template Handler * There is a ticket linked to a backlog entry referred as FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution which doesn't have correspondence with anything on the Wiki * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Semantic * There is a ticket linked to a backlog entry referred as FIWARE.EPIC.IoT.Semantic.SemanticMediator which doesn't have correspondence with anything on the Wiki. Apparently, it links to one Feature listed on the Wiki so seems like it's just a matter of labeling the entry as linked to a feature rather than an Epic. * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * The language used for describing goals in the template defined in August for backlog entries has not been followed in some of the backlog entries linked to this GE. Some people may argue that description of goals doesn't follow the standard Agile conventions. Such conventions try to emphasize what the users will get in terms of functionality. * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Process Automation/Exposure * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Epic.IoT.Exposure.ProcessRemoteExecution * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.ThingBasedQuery * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.Exposure.AsynchronousThingBasedInteraction * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Local Storage * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Pooling * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Access Policy * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). * IoT Data Handling/Data Handling * There is a value of "3" associated to the field "FI-WARE Sprint Id" for some entries linked to Features ... has no sense. * Don't see ticket on the tracker linked to entry FIWARE.Feature.IoT.DataHandling.EventsGenerator.M2mPlanet, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Isis, FIWARE.Feature.IoT.DataHandling.EventsGenerator.Ngsi or FIWARE.Feature.IoT.DataHandling.EventsGenerator.EventTemplate. * The ticket linked to entry FIWARE.FEATURE.IoT.DataHandling.IoTSubscribe.Device seems to be duplicated on the tracker ... Maybe one should be linked to IoTPublish.Device ? * No User-Story or WorkItem has been identified ... What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... I remind you that WorkItems do not require to create contents on the Wiki, only the tracker (this simplifies things a bit). ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakob.saros at ericsson.com Tue Nov 22 16:54:22 2011 From: jakob.saros at ericsson.com (Jakob Saros) Date: Tue, 22 Nov 2011 16:54:22 +0100 Subject: [Fiware-iot] Updated asset matrix Message-ID: <9870BEE781B2694BA446B8FD65882E85294A73F74F@ESESSCMS0363.eemea.ericsson.se> Dear all, Following a discussion with and recommendation by Gian Piero, we have uploaded an updated asset matrix based on version 33, now version 34 available under "Partner asset selection" on the forge. The updated version contains a requirement fulfillment description of the Ericsson offered assets. The assets are existing today (i.e. stable running code). In order to progress this we will propose a separate call early next week to discuss how to fit our assets into the existing selection. Best regards, Jakob Saros JAKOB SAROS Experienced Researcher Ericsson AB Services and Software F?r?gatan 6 164 80, Kista, Sweden Phone +46 10 7146042 SMS/MMS +46 761196042 jakob.saros at ericsson.com www.ericsson.com This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture (Device Independent Bitmap) 1.jpg Type: image/jpeg Size: 798 bytes Desc: Picture (Device Independent Bitmap) 1.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture (Device Independent Bitmap) 2.jpg Type: image/jpeg Size: 7752 bytes Desc: Picture (Device Independent Bitmap) 2.jpg URL: From maarten.los at atosresearch.eu Tue Nov 22 16:54:45 2011 From: maarten.los at atosresearch.eu (Maarten Los) Date: Tue, 22 Nov 2011 16:54:45 +0100 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 In-Reply-To: <0D2446AEB6CAED48BB046223733964A54C42F61C88@DEWDFECCR01.wdf.sap.corp> References: <3F4C11BC54A36642BFB5875D599F47BD052240C5@DEMUEXC013.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54C42F61C88@DEWDFECCR01.wdf.sap.corp> Message-ID: <76BD4E6231F77947B6885C75E5214FA5065CF8CF@INTMAIL01.es.int.atosorigin.com> Dear partners, I made some changes as well (about device level CEP deployment) and the last comment was incorrectly attributed to me (possibly it was Martin) Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: mi?rcoles, 16 de noviembre de 2011 13:18 To: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 I made a small change correcting what was said regarding the availability of the IoT-A assets. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Mittwoch, 16. November 2011 12:36 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 16/11/2011 Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/614/IoT-Minutes-Telco-16112011.docx Best, D?nes ------------------------------------------------------------------ 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 rheras at tid.es Tue Nov 22 17:19:03 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Tue, 22 Nov 2011 17:19:03 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Message-ID: <4ECBCB77.9090404@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-T5.2-Analysis-v2.jpg Type: image/jpeg Size: 69480 bytes Desc: not available URL: From denes.bisztray at nsn.com Wed Nov 23 08:34:33 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 23 Nov 2011 08:34:33 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <4ECBCB77.9090404@tid.es> References: <4ECBCB77.9090404@tid.es> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD052A91B1@DEMUEXC013.nsn-intra.net> Dear Ricardo, The API taskforce discussion was closed weeks ago. The conclusion document can be found here: https://forge.fi-ware.eu/docman/view.php/11/550/v04-API-Conclusion.docx We decided to use ETSI M2M for device - backend communication. TID agreed. From OGC we ONLY use the O&M for data description. You were on holiday that week, please read the document. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Tuesday, November 22, 2011 5:19 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear partners involved in T5.2, as you know during these two weeks we are tackling the first sprint of this release. In this way, we had defined two work items that in the short term should help us to establish the priorities of our future developments, i.e.: https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 The first one is the selection of the final asset that will cover the Resource Directory component of this task. So far, we had defined the photo attached, defining mainly 3 assets as strong candidates: IDAS, Fosstrak and Cumulocity. We should take a decision about that, before starting the directory's interface definition (work item n? 2). I would like to open the discussion with you about this point, defining the list of points we have to take into account for the final decision . Requirements, maturity of the asset and protocols managed could be one of the most relevant points for taking into account. What do you think? Any other? Maybe the effort of every of the partners involved in T5.2 could be relevant for this decision now? At the same time, we should have also to clarify which protocol will finally be selected for the communication between resources and the resource directory. IMHO OGC SWE could be one of our best options according to results of the analysis we did some weeks ago. I see NGSI more in the upper side, for applications interface. What's your opinion? thanks, looking forward to receiving your feedback, best, R. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 P.Barnaghi at surrey.ac.uk Wed Nov 23 11:27:01 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Wed, 23 Nov 2011 10:27:01 +0000 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <4ECBCB77.9090404@tid.es> References: <4ECBCB77.9090404@tid.es> Message-ID: Hi Ricardo, all, Can you please clarify the following points: - What will the discovery mechanism is going to retrieve and where it will refer to? We can provide a query and search mechanisms but assuming the data is stored as OWL/RDF data that can be accessed via SPARQL end-points. - The data models as we discussed will be according to OMA NGSI and IoT information models and we will use Restful interface to publish/access the description. But again I don't know what is meant by the communication protocol between resources and resource directory. Our understanding is the resources will publish their description (according to an agree description framework) in a resource directory, the resource descriptions then will be accessible via a common enabler (a restful interface) and/or can be queried using a query/search enabler (SPARQL-end point interface). - We are not also clear that according to the descriptions, how our linked data platform should be integrated in this design, if the resource directory and discovery engines are considered using two different designs. Thanks, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: 22 November 2011 16:19 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear partners involved in T5.2, as you know during these two weeks we are tackling the first sprint of this release. In this way, we had defined two work items that in the short term should help us to establish the priorities of our future developments, i.e.: https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 The first one is the selection of the final asset that will cover the Resource Directory component of this task. So far, we had defined the photo attached, defining mainly 3 assets as strong candidates: IDAS, Fosstrak and Cumulocity. We should take a decision about that, before starting the directory's interface definition (work item n? 2). I would like to open the discussion with you about this point, defining the list of points we have to take into account for the final decision . Requirements, maturity of the asset and protocols managed could be one of the most relevant points for taking into account. What do you think? Any other? Maybe the effort of every of the partners involved in T5.2 could be relevant for this decision now? At the same time, we should have also to clarify which protocol will finally be selected for the communication between resources and the resource directory. IMHO OGC SWE could be one of our best options according to results of the analysis we did some weeks ago. I see NGSI more in the upper side, for applications interface. What's your opinion? thanks, looking forward to receiving your feedback, best, R. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 rheras at tid.es Wed Nov 23 12:20:50 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Wed, 23 Nov 2011 12:20:50 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD052A91B1@DEMUEXC013.nsn-intra.net> References: <4ECBCB77.9090404@tid.es> <3F4C11BC54A36642BFB5875D599F47BD052A91B1@DEMUEXC013.nsn-intra.net> Message-ID: <4ECCD712.608@tid.es> An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Nov 23 12:36:11 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 23 Nov 2011 12:36:11 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <4ECCD712.608@tid.es> References: <4ECBCB77.9090404@tid.es> <3F4C11BC54A36642BFB5875D599F47BD052A91B1@DEMUEXC013.nsn-intra.net> <4ECCD712.608@tid.es> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD052E1D4B@DEMUEXC013.nsn-intra.net> Dear Ricardo, There was a dedicated meeting on standards discussion. Minutes here: https://forge.fi-ware.eu/docman/view.php/11/534/IoT-API-Taskforce-25102011.docx Conclusion document still here: https://forge.fi-ware.eu/docman/view.php/11/550/v04-API-Conclusion.docx I'm sorry Ricardo, but I don't want to open the API discussion on the list again. If you disagree with the conclusions please organize a meeting with the participants of the taskforce. Best, D?nes From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Wednesday, November 23, 2011 12:21 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear D?nes, all, yes, I had read the minutes when I came back of my holidays, but that report only explained a recommendation where TID was not completely involved as you know that week. That was 'only a recommendation', not a final decission. The next conf.call we had on 2nd Nov, I remember we said, extracted from the minutes, based on that report: ---------------------- ETSI M2M is good for device level primitives. It is thus recommended for that. SWE has good sensor management information data. Information model. ETSI m2m has container resources, it is a black box, can have everything. It make sense to use the OGC ? Thierry : At this moment we do not have time to discuss this in more detail. We have this as a vision now, and do those parts when we can. For device management we need further discussion, we take more time for that. ---------------------- NGSI seems OK, agreed, but in the low level (ETSI/OGC) it seems it was not definitively agreed, isn't it? --- So, I'm sorry for coming to this point again, but at that time after the call and after reading those minutes for me was not definitively closed this decision. Anyway, I'm not saying the combination of ETSI-M2M and OGC-SensorML-SWE would not be a good solution, indeed as you know IDAS platform manages the sensor observations using OGC SensorML, we only would need to modify the API envelope for achieve an ETSI-M2M standard compliant, I only say that the idea I had in mind was that it was not completely agreed, the same for the assets selection. At this time none of the assets are ETSI-M2M compliant, so this point, as API 'envelope standard' is not a differentiate point for the set of assets. IMHO both issues, asset selection and final standards selection should converge in the same decision regarding the asset selection. Anyway, my previous email was one step further, now how we proceed for the asset selection and for the Resource Directory API specification? thanks D?nes, br, Ricardo. ------------------------------------------- >From v04-API-Conclusion.docx: Device/Resource-level API The Device/Resource -level API is directly connected to the IoT platform and used to perform device management functionalities, i.e. device configuration, firmware update and generic FCAPS functionality. Functional Model: Since NGSI is a thing-level API, it cannot perform all tasks on the lower levels. Since ETSI M2M offers the most extensive support for device-level primitives, we recommend it for the low-level primitives. The support for SWE is still under discussion, as it provides more functionality on the resource level that ETSI M2M does, in particular a semantic model of sensor and measurement information. Information Model: The actual data exchange in ETSI M2M takes places by writing into and reading from so-called container resources in the Service Capability Layer. These containers accept generic data, the format of which has to be agreed upon by the applications and the service provider side. We recommend to model sensor information and sensor observations using OGC SWE SensorML and OGC SWE O&M, respectively. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Ricardo, The API taskforce discussion was closed weeks ago. The conclusion document can be found here: https://forge.fi-ware.eu/docman/view.php/11/550/v04-API-Conclusion.docx We decided to use ETSI M2M for device - backend communication. TID agreed. From OGC we ONLY use the O&M for data description. You were on holiday that week, please read the document. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Tuesday, November 22, 2011 5:19 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear partners involved in T5.2, as you know during these two weeks we are tackling the first sprint of this release. In this way, we had defined two work items that in the short term should help us to establish the priorities of our future developments, i.e.: https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 The first one is the selection of the final asset that will cover the Resource Directory component of this task. So far, we had defined the photo attached, defining mainly 3 assets as strong candidates: IDAS, Fosstrak and Cumulocity. We should take a decision about that, before starting the directory's interface definition (work item n? 2). I would like to open the discussion with you about this point, defining the list of points we have to take into account for the final decision . Requirements, maturity of the asset and protocols managed could be one of the most relevant points for taking into account. What do you think? Any other? Maybe the effort of every of the partners involved in T5.2 could be relevant for this decision now? At the same time, we should have also to clarify which protocol will finally be selected for the communication between resources and the resource directory. IMHO OGC SWE could be one of our best options according to results of the analysis we did some weeks ago. I see NGSI more in the upper side, for applications interface. What's your opinion? thanks, looking forward to receiving your feedback, best, R. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 rheras at tid.es Wed Nov 23 12:43:47 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Wed, 23 Nov 2011 12:43:47 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: References: <4ECBCB77.9090404@tid.es> Message-ID: <4ECCDC73.2090400@tid.es> An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Wed Nov 23 17:48:00 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Wed, 23 Nov 2011 16:48:00 +0000 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <4ECCDC73.2090400@tid.es> References: <4ECBCB77.9090404@tid.es> <4ECCDC73.2090400@tid.es> Message-ID: Hi Ricardo, Thank for your reply and comments. - SensoerML is more a sensor description language and I think what is planned here are more generic IoT resources and as we agreed the descriptions it will be provided based on OMA NGSI and IoT-A information models and those descriptions will be stored in the Resource Directory. - for registration we need a common interface (to publish the data according to the designated models) and it seems the implementation technology for the interface will be Restful. So I don't see how SensorML fits here. - if the data is not in RDF form, our discovery engine won't work! Simply because we use logical reasoning and probabilistic machine learning that process semantic data that describe the resources/services; I understand that our information model should support legacy data, but that's another issues that how we annotate legacy data and still should not affect our model (so SnesorML is seen separate from our description model here). Please see: http://www.w3.org/2005/Incubator/ssn/XGR-ssn-20110628/#Semantic_Markup PS. However, if the group has agreed on any of the items or if it is decided to use SensorML and stored it in the resource directory, then we will follow the group's decision. But unfortunately we then won't be able to provide the discovery mechanism. Best regards, Payam ________________________________ From: Ricardo de las Heras [mailto:rheras at tid.es] Sent: 23 November 2011 11:44 To: Barnaghi P Dr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; Elsaleh T Mr (Electronic Eng) Subject: Re: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - HI Payam, I'm going to answer to your three questions, under my personal point of view: - Discovery mechanisms should retrieve the information from the resource directory, so I understand the information about the registered sensors would be stored in the OGC-SensorML format, because NGSI and M2M-ETSI only provide an envelope for the information, not a data/registering description. I don't know if you could adapt the search mechanism for using this format instead of RDF. I don't know if it would have a direct conversion way. - Yes, we need a protocol for register the sensors on the directory, using a SensorML (OGC) standard as D?nes explained, that's the meaning of this communication protocol between resources and resource directory. - I'm not sure about how you could access to the resource directory from the discovery engine, how flexible could be your discovery engine for managing data not stored in RDF format. Maybe the question is if we would have to store the information in the resource directory using RDF format or OGC-O&M. At this time I had personally assumed it would be in O&M, but we can discuss it of course. It would depend again of the final asset selected there. regards, Ricardo. P.Barnaghi at surrey.ac.uk wrote: Hi Ricardo, all, Can you please clarify the following points: - What will the discovery mechanism is going to retrieve and where it will refer to? We can provide a query and search mechanisms but assuming the data is stored as OWL/RDF data that can be accessed via SPARQL end-points. - The data models as we discussed will be according to OMA NGSI and IoT information models and we will use Restful interface to publish/access the description. But again I don't know what is meant by the communication protocol between resources and resource directory. Our understanding is the resources will publish their description (according to an agree description framework) in a resource directory, the resource descriptions then will be accessible via a common enabler (a restful interface) and/or can be queried using a query/search enabler (SPARQL-end point interface). - We are not also clear that according to the descriptions, how our linked data platform should be integrated in this design, if the resource directory and discovery engines are considered using two different designs. Thanks, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: 22 November 2011 16:19 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear partners involved in T5.2, as you know during these two weeks we are tackling the first sprint of this release. In this way, we had defined two work items that in the short term should help us to establish the priorities of our future developments, i.e.: https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 The first one is the selection of the final asset that will cover the Resource Directory component of this task. So far, we had defined the photo attached, defining mainly 3 assets as strong candidates: IDAS, Fosstrak and Cumulocity. We should take a decision about that, before starting the directory's interface definition (work item n? 2). I would like to open the discussion with you about this point, defining the list of points we have to take into account for the final decision . Requirements, maturity of the asset and protocols managed could be one of the most relevant points for taking into account. What do you think? Any other? Maybe the effort of every of the partners involved in T5.2 could be relevant for this decision now? At the same time, we should have also to clarify which protocol will finally be selected for the communication between resources and the resource directory. IMHO OGC SWE could be one of our best options according to results of the analysis we did some weeks ago. I see NGSI more in the upper side, for applications interface. What's your opinion? thanks, looking forward to receiving your feedback, best, R. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________ 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 Nov 24 10:14:35 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 24 Nov 2011 11:14:35 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A202A648C5@FIESEXC014.nsn-intra.net> When: 2011. november 24. 12:30-14:00 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, For our meeting between 12:30 - 14:00 I would propose the following topics: 1. Thierry informs us on the outcomes of the review meeting 2. Task leaders report on the status of work items and what has been discussed within the tasks in the last week Thanks & Br, Lorant 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: 11005 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Nov 24 15:54:21 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 24 Nov 2011 16:54:21 +0200 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 24/11/2011 Message-ID: <93D28BDF64839C468B848D14227151A202A64C3E@FIESEXC014.nsn-intra.net> Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/651/IoT-Minutes-Telco-24112011.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Fri Nov 25 14:22:35 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 25 Nov 2011 14:22:35 +0100 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: References: <4ECBCB77.9090404@tid.es> <4ECCDC73.2090400@tid.es> Message-ID: <4ECF969B.2030604@tid.es> An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Mon Nov 28 13:20:07 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Mon, 28 Nov 2011 12:20:07 +0000 Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - In-Reply-To: <4ECF969B.2030604@tid.es> References: <4ECBCB77.9090404@tid.es> <4ECCDC73.2090400@tid.es> <4ECF969B.2030604@tid.es> Message-ID: Dear Ricardo, Thank you for your email and the comments. You are right; OMA NGSI only provides high level descriptions and does not include detailed attributes to describe IoT resources; however, it has an attribute for advance feature that can be used to link the semantically described detailed attribute to the main description. The proposal to use NGSI is based on NEC and Telecom Italia's previous work which is also uses ideas from SENSEI information model. During the meeting, I suggested if we are going to use NGSI then IOT-A information model can be used to define the advanced attributes; With regards to the SensorML, it provides some of the semantics for the modelling purpose but in principal, SensorML describes "geometric, dynamic, and observational characteristics of sensors and sensor systems" and in FI-WARE IOT we need a more boarder scope than only Sensors and O&M data; So one option could be adopting IoT-A models for FI-WARE and representing the model attributes in a semantic form according to NGSI model (as a template); The SensorML description can be then annotated using the proposed model. Regarding your second comment, I also share your views; we also need to consider the compatibility between different assets and solutions that we select. Thanks and regards, Payam ________________________________________ From: Ricardo de las Heras [mailto:rheras at tid.es] Sent: 25 November 2011 13:23 To: Barnaghi P Dr (Electronic Eng); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - Dear Payam, @ll, one clarification please, I read the minutes and you said yesterday: " Payam: we discussed f2f in Turin that we use semantic description based on OMA NGSI? - why go back to that discussion? 2nd: if data is stored in a format, it will impact the discovery." sorry but I don't understand it, as far as I know NGSI doesn't define a semantic description, I'm not an expert on it, but when I had a look to the specification, it only provides very high concepts for interchanging context information between entities, maybe I ignore some parts of the specification, please could you clarify for me this point? BTW, SensorML seems to provide semantic capabilities, adding tags for including semantic annotations, maybe this could be a good option for solving the problem with your discovery process, if it only works with RDF. Could we explore it? what do you think? Furthermore, a personal reflection now, and a open question I leave for all the partners involved on WP5, not only for you Payam: If we are proposing an IoT solution in Fiware based on our previous assets, it is supposed that we only would have to apply 'slight' modifications for including them in Fiware, isn't it? So, now, if we are proposing in the final solution new standards and requirements not covered by any of the assets available, and them implies developments almost starting from the scratch..., my question: who will develop them? because the current budget assigned to all of us can only cover the 'light' modifications needed in Fiware, not the development of a new system. So please, let's put our feet on the ground and let's try to define feasible and realistic solutions, otherwise maybe we will achieve a good final solution but very far of the current set of assets we are managing as candidates, and then, the next step will probably be that none of us will be dispose to tackle the required developments with the current budget we have here. So, do you honestly think my exposition is realistic or not? Thanks in advance for your answer, and sorry but I'm a little bit confused with the current situation we have regarding all those issues now, I'll try to arrange a conference call soon about this topics, as we agreed yesterday, but previously I would like to define with you what would be the concrete focus of the discussion there, have a nice week-end, R;) P.Barnaghi at surrey.ac.uk wrote: Hi Ricardo, ? Thank for your reply and comments. ? ? - SensoerML is more a sensor description language and I think what is planned here are more generic IoT resources and as we agreed the descriptions it will be provided based on OMA NGSI and IoT-A information models and those descriptions will be stored in the Resource Directory. ? - for registration we need a common interface (to publish the data according to the designated models) and it seems the implementation technology for the interface will be Restful. So I don't see how SensorML fits here. ? - if the data is not in RDF form, our discovery engine won't work! Simply because we use logical reasoning and probabilistic machine learning that process semantic data that describe the resources/services; I understand that our information model should support legacy data, but that's another issues that how we annotate legacy data and still should not affect our model (so SnesorML is seen separate from our description model here). Please see: http://www.w3.org/2005/Incubator/ssn/XGR-ssn-20110628/#Semantic_Markup ? ? PS. However, if the group has agreed on any of the items or if it is decided to use SensorML and stored it in the resource directory, then we will follow the group's decision. But unfortunately we then won't be able to provide the discovery mechanism. ? Best regards, Payam ? ? ________________________________________ From: Ricardo de las Heras [mailto:rheras at tid.es] Sent: 23 November 2011 11:44 To: Barnaghi P Dr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; Elsaleh T Mr (Electronic Eng) Subject: Re: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - ? HI Payam, I'm going to answer to your three questions, under my personal point of view: - Discovery mechanisms should retrieve the information from the resource directory, so I understand the information about the registered sensors would be stored in the OGC-SensorML format, because NGSI and M2M-ETSI only provide an envelope for the information, not a data/registering description. I don't know if you could adapt the search mechanism for using this format instead of RDF. I don't know if it would have a direct conversion way. - Yes, we need a protocol for register the sensors on the directory, using a SensorML (OGC) standard as D?nes explained, that's the meaning of this communication protocol between resources and resource directory. - I'm not sure about how you could access to the resource directory from the discovery engine, how flexible could be your discovery engine for managing data not stored in RDF format. Maybe the question is if we would have to store the information in the resource directory using RDF format or OGC-O&M. At this time I had personally assumed it would be in O&M, but we can discuss it of course. It would depend again of the final asset selected there. regards, Ricardo. P.Barnaghi at surrey.ac.uk wrote: Hi Ricardo, all, ? Can you please clarify the following points: ? - What will the discovery mechanism is going to retrieve and where it will refer to? We can provide a query and search mechanisms but assuming the data is stored as OWL/RDF data that can be accessed via SPARQL end-points. ? - The data models as we discussed will be according to OMA NGSI and IoT information models and we will use Restful interface to publish/access the description. But again I don't know what is meant by the communication protocol between resources and resource directory. Our understanding is the resources will publish their description (according to an agree description framework) in a resource directory, the resource descriptions then will be accessible via a common enabler (a restful interface) and/or can be queried using a query/search enabler (SPARQL-end point interface). ? - We are not also clear that according to the descriptions, how our linked data platform should be integrated in this design, if the resource directory and discovery engines are considered using two different designs. ? ? Thanks, Payam ? ? ________________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: 22 November 2011 16:19 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] T5.2 Resource management - Work Items 1 & 2 - ? Dear partners involved in T5.2, as you know during these two weeks we are tackling the first sprint of this release. In this way, we had defined two work items that in the short term should help us to establish the priorities of our future developments, i.e.: https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 The first one is the selection of the final asset that will cover the Resource Directory component of this task. So far, we had defined the photo attached, defining mainly 3 assets as strong candidates: IDAS, Fosstrak and Cumulocity. We should take a decision about that, before starting the directory's interface definition (work item n? 2). I would like to open the discussion with you about this point, defining the list of points we have to take into account for the final decision . Requirements, maturity of the asset and protocols managed could be one of the most relevant points for taking into account. What do you think? Any other? Maybe the effort of every of the partners involved in T5.2 could be relevant for this decision now? At the same time, we should have also to clarify which protocol will finally be selected for the communication between resources and the resource directory. IMHO OGC SWE could be one of our best options according to results of the analysis we did some weeks ago.? I see NGSI more in the upper side, for applications interface. What's your opinion? thanks, looking forward to receiving your feedback, best, R. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ? ________________________________________ 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 ? -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ? ________________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telef?nica I+D ------------------------------------- ________________________________________ 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 Nov 29 09:55:00 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 29 Nov 2011 10:55:00 +0200 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A202A9C031@FIESEXC014.nsn-intra.net> When: 2011. november 30. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, The meeting tomorrow is cancelled. Task leaders should now focus on the planning of the 2nd sprint and interact with the asset owners from their respective tasks. Thanks & Br, Lorant 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: 10734 bytes Desc: not available URL: From lorant.farkas at nsn.com Tue Nov 29 09:55:31 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 29 Nov 2011 10:55:31 +0200 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A202A9C032@FIESEXC014.nsn-intra.net> When: 2011. november 30. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, The meeting tomorrow is cancelled. Task leaders should now focus on the planning of the 2nd sprint and interact with the asset owners from their respective tasks. Thanks & Br, Lorant 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: 10639 bytes Desc: not available URL: From denes.bisztray at nsn.com Tue Nov 29 14:19:36 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 29 Nov 2011 14:19:36 +0100 Subject: [Fiware-iot] private wiki usable Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05365937@DEMUEXC013.nsn-intra.net> Dear All, I just set up the private wiki for our chapter. You find it under the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Main_Page We are supposed to start planning the next sprints by defining user stories. Since user stories are implementation-level descriptions, the internal architecture of the baseline assets are prone to be exposed. Thus feel free to use it. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Nov 30 13:34:15 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 Nov 2011 13:34:15 +0100 Subject: [Fiware-iot] Need your help: vote for a submission from FI-WARE Message-ID: <4ED622C7.4030905@tid.es> Dear all, Acting on behalf of FI-WARE, Thierry Nagellen has just submitted a topic for workshop in the Future Internet Assembly to be celebrated in Aalborg. This topic could have the FI PPP as sponsor and we should have technical presentations (from FI-Ware partners but also from other contributors as Smart Santander or IoT-A projects) and some new Use Cases to improve the requirements picture We need your support to get there and there is very little time left. We would appreciate it if you could go to this link, login with a gmail user and vote if you like it: http://www.future-internet.eu/home/shape-fia.html?modSeries=111dab&modTopic=40&modSubmission=5c4fe7 Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx