Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoyé : jeudi 18 avril 2013 16:37 À : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>" <t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>> escribió: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130612/eba3361e/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy