Hi Carlos, I agree, and I have already started the editing. As I mentioned in the last phc with regards to IoT Discovery (previously ConfMan), the main (mandatory) content will focus on specifying how the GE takes the role of an NGSI-9 server, and how NGSI-9 clients can interact with it. The content will then specify optional components that can enhance discovery. What we have listed for now are geographic, probabilistic, and semantic. The content before touched on implementation specifics, which should not be the case. I believe there should be no reference to a GE implementation. Any implementation specifics should be mentioned somewhere else. The closest candidate for this I see is the User's and Programmers Guide. The architecture document should only specify "how" a component is expected to function and interact with other components/GEs. My status is as below: · Enabler: Backend IoT Discovery GE · Status: on-going updates. Target date 20/03/2015 · Responsible: Tarek Elsaleh (t.elsaleh at surrey.ac.uk) · Link: o http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTDiscovery Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.org [mailto:fiware-iot-bounces at lists.fi-ware.org] On Behalf Of CARLOS RALLI UCENDO Sent: 17 March 2015 11:58 To: fiware-iot at lists.fi-ware.org Subject: [Fiware-iot] New version of the overall architecture Hi all, I have just updated the overall IoT architecture. There is a problem with the forge today so you will not see some graphics correctly. As soon as support guys handle this ticket it will get OK. http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture The previous page is at: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture_PREVIOUS The new version of this main page featuring the following changes: - It describes better our architecture following the terms and functions we discussed in the FICORE kick off meeting in Madrid. * Now we talk about IoT Backend and IoT Edge instead of IoT Backend and IoT Gateways. * We say IoT Discovery GE (Univ Surrey) instead of IoT Conf.Man. Tarek, I have moved your page accordingly. Would you mind to update the text and other references ? (I think it is much better thank keeping the old Conf.Man GE, do you all agree ?) - The text is much clear and we divide the architecture in "Complete Architectiure" but also we include "Typical Architecture Scenarios" so people may understand different practical implementations (this is a strong demand from developers in the pasts hackathons/developers events). I have included the typical scenario (I) but I have also included a second one with Data handling and IoT Broker + IoT Discovery. However we may split this II scenario in several ones in the near future if you wish to. - I have removed the reference to ETSI-M2M in this main page, as long as it will be a reference in the BE Dev Man GE where it really makes sense (and most likely it will be replaced by OneM2N southbound architecture = OMA-LWM2M/CoAP). Important for all: I need that you e-mail me tomorrow 14h the latest with your GE and the status of the architecture page. We need this to report to the coordination (Miguel/Manuel): For instance, in my case tomorrow my par will be: * Enabler: Backend Device Management GE * Status: Updated (Other status: not yet started, on-goon updates. Target date dd/mm/yyyy, etc) * Responsible: Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>) * Link: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (carlos.ralliucendo at telefonica.com<mailto:carlos.ralliucendo at telefonica.com>) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es<http://the-internet6.blogspot.com.es/> Telefónica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FIWARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.<http://www.fi-ware.eu/>org Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-iot/attachments/20150318/cbc0b445/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy