Hello Fano, The owl files can be found at: http://iot3.ee.surrey.ac.uk/S2W/IoTA-Models/. There are also files that provide an example of an instance (individual) of the model. For location, we also plan to link the models to Geonames as well. The property we use for this is called "hasGlobalLocation". With regards to translation, I understand that the CML that you receive complies with a naming convention for attributes e.g. "temperature" and not "temp". Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 14:37 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; Barnaghi P Dr (Electronic Eng) Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, So far we've decided to use standard (eventually de-facto) ontologies if they exist (e.g. for location information we plan to use geonames). We haven't commited to any as far as resources and things are concerned. So we can use IoT-A ontologies. Is there a web site where the corresponding owl files can be retrieved? We plan to use SPARQL to explore the ontologies and the instances and the relations, mainly for tuning the NGSi to RDF translation (see below). I agree that transforming from RDF/OWL to NGSi is easier because the former is more expressive than the latter, so transforming is just dropping some info from the source document to produce the target document, but I think that transforming NGSi to RDF is doable as this is what we're actually working on after having successfully transformed CML (PubSub CAP native context modeling language) into RDF. However this transformation has to be partly hardcoded and on a scope by scope basis, because semantics of the document in the source language is mainly implicit and has to be made explicit in the target language. Best regards, Fano De : t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk> [mailto:t.elsaleh at surrey.ac.uk] Envoyé : mercredi 12 juin 2013 11:51 À : RAMPARANY Fano OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>; ralli at tid.es<mailto:ralli at tid.es>; p.barnaghi at surrey.ac.uk<mailto:p.barnaghi at surrey.ac.uk> Objet : RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hello Fano, Yes we are planning to support this epic and its respective features. I think we need to clarify what exactly do you want to query for? ...what information, what ontology? Currently we are supporting the IoT-A ontologies that describe Resources (Sensors, Actuators, Processing unit, Storage, Tag), Virtual Entities (i.e. Things) and Services (what the user interacts with to access the Resource). Attached is a paper that illustrates the ontologies. If you are interested in using of these please let me know. On another note, a discussion we had in the WP previously was how to map the IoT-A ontologies to the FIWARE IoT Concepts (Thing, IoT Resource, Device) and vice-versa. For: · IoT-A Virtual Entity -> FIWARE Thing · IoT-A Resource -> FIWARE IoT Resource · The IoT-A Service will be embedded in the FIWARE Thing and IoT Resource using the NGSI-9 "ProvidingApplication" element, i.e. a URL to an web application/service endpoint. In the case of translating, from ontology to NGSI is doable, but vice-versa is near impossible unless a registered NGSI-9 Description complies with a specific format for naming. Please let me know your opinion on this. Best regards, Tarek From: fano.ramparany at orange.com<mailto:fano.ramparany at orange.com> [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 08:20 To: Tobias Jacobs; CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE 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> [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<mailto:t.elsaleh at surrey.ac.uk> Cc : fiware-iot at lists.fi-ware.eu<mailto: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<mailto:t.elsaleh at surrey.ac.uk> Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; p.barnaghi at surrey.ac.uk<mailto: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. _________________________________________________________________________________________________________________________ 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/3e2bd24c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy