Hi Sabrina, Thanks for pointing this out! You are indeed correct. I took the liberty of updating this myself since I noticed that the original FMC was not in the svn so it would have been difficult for you to update. It's added now btw. BR, Jakob ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Guerra Sabrina Sent: den 14 juni 2012 17:57 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] R: URGENT APs befor Review Hi all, we updated the Protocol Adapter GE wiki page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter#Contacts) adding information about the ZigBee Protocol Adapter. Moreover we've an observation about the second picture in the page: the Protocol Adapter Interface looks like it's an external interface outside the gateway, while it should be an interface between protocol adapter interface and the Gateway Device Management GE. Please have a look to the attached picture to see what we mean. If you agree you may modify the corresponding FMC image. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: giovedì 14 giugno 2012 09:44 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT APs befor Review Priorità: Alta Dear all, At the end of this email you will find some pending issues for IoT WP (Telefonica email) and we have the review next week! Of course these actions are last minutes actions but some of them did not have any feedback based on our previous emails. So take them into account carefully because some questions and bad comments would be done by reviewers next weeks. We are all on the same boat, so a failure will impact all of us, and good points are also for all of us! To solve this here are the expected actions: · technical roadmap: NSN updated it with the new GE names. There was not any feedback from partners except NEC and USurrey. All partners should take a look. We have to validate it EOB today! · Open specs (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications) Status: we should resubmit this deliverable now Backend Things Management: available, not fully compliant with the guidelines (authentication, limits sections not available) but mostly compliant. TM GE configuration interface is missing. Tobias could re-check compliance and decide what to do with TM GE configuration interface. I think last status was that this interface should not be mentioned, then this subsection should be deleted, and Dénes should also remove it from the architecture figure. tomorrow EOB Backend Things Management (revised - under construction): Tobias to remove it, but before that please try to take useful parts of it to Backend Things Management, e.g. overview tomorrow EOB Backend Device Management: we have something, but not compliant to the guidelines. Dénes just to make it compatible and "will be improve for next minor release" Gateway Device Management: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB Gateway Data Handling: we have nothing, Laurent/Laurence to create a first framework and message that will be achieved for next minor release, now both Data Handling and Gateway Device Management are standalone (take example from Tobias, if we specify only NGSI 9/10 and not the data handling API. Gateway Protocol Adapter: we have something very basic, but not compliant to guidelines, Jakob/Jan to take action tomorrow EOB · SW release (Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_Test_Cases_-_V1) Action on all partners: check statements from the wiki page from the GE perspective in which they are involved and send us comments on what should be changed on the page (Wednesday 20th EOB) · Install and admin guide (Guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.3, sent out to IoT list on 23.04.2012) Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late",there was no follow-up, there is is no real guideline on where on the public wiki (or anywhere else) should we publish it (No action here) · User and programmer guide Status: was requested to be delayed to M14, coordinator said "no change, because we are anyway 2 months late", "sort of programmer's tutorial, not so formal. Will be provided in Wiki format", no more details till now (No action here) · Unit testing plan and report (Guidelines: see joined email) Status: no concrete example from Telefonica despite having been promised 10 days ago. Imporvement expected for Wednesday 20th EOB Backend Things Management: Stephan provided it in the private Wiki, Tobias to move it into the public wiki. Then it would be in a rather good shape. Tobias could you also check the compliance with the guidelines? Backend Device Management: Dénes provided initial content, could add more detailed based on the initial content he provided Gateway Data Handling: nothing available, Laurent should create it Gateway Device Management: nothing available, Jan/Jakob should create it Gateway Protocol Adapter: Sabrina created good content for ZigBee GW, Jan/Jakob should add their part Table 1. Deliverables Del. no. Deliverable name Version WP no. Lead beneficiary Nature Dissemination level[1] Delivery date from Annex I (proj month) Actual / Forecast delivery date Dd/mm/yyyy Status No submitted/ Submitted Contractual Yes/No Comments D5.1.1 GE Open Specifications. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.2.1 SW Release (version of components delivered for integration in testbed). 5 7 P PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.3.1 Installation and Administration Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.4.1 User and Programmers Guide. 5 7 R PU 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) D5.5.1 Unit Testing Plan and Report. 5 7 R PP 12 PENDING (FT) PENDING (FT) Yes PENDING (FT) Table 2. Milestones Milestone no. Milestone name Work package no Lead beneficiary Delivery date from Annex I dd/mm/yyyy Achieved Yes/No Actual / Forecast achievement date dd/mm/yyyy Comments MS4 Core Platform v1 specifications 5 1 12 PENDING (FT) PENDING (FT) Specifications report. PENDING (FT) Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> ________________________________ _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ [1] PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services). Make sure that you are using the correct following label when your project has classified deliverables. EU restricted = Classified with the mention of the classification level restricted "EU Restricted" EU confidential = Classified with the mention of the classification level confidential " EU Confidential " EU secret = Classified with the mention of the classification level secret "EU Secret " Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:269521615 at 15062012-02DF]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120615/8114165e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120615/8114165e/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy