Hi Tarek, The partners involved in development of the Publish/Subscribe Broker GE within the Data/Context Management chapter (Telecom Italia and Orange) are trying to deal with incorporation of semantic meta-data linked to events (context elements) and published through the Publish/Subscribe Broker GE. I copy Boris Moltchanov from Telecom Italia who is dealing with coordination of the developments linked to this GE. While I guess that having two implementations of the NGSI spec may be Ok (though we have to find out how to justify it) what certainly has to be achieved is that the final APIs finally offered to the application developer are the same, so that applications are not programmed in a different way depending on what Publish/Subscriber Broker GE it connects to. And this doesn't only affect number and name of operations but structure of data (which certainly affects the signature of operations). I would suggest that we setup a dedicated thread of discussion over the email where each can explain its respective approach and we can reach the necessary alignment. Would you believe that we should link that thread of discussion through both the fiware-data and fiware-iot mailing lists ? I guess not all members in that list want to get spammed ;-) My current thinking would be that of creating a dedicated mailing list for discussion about the NGSI interface implementation were partners involved in trying to implement this interface in both the FI-WARE IoT and FI-WARE Data chapters would be members, besides the respective WPLs, WPAs, the deputy chief architect of FI-WARE and myself. Your feedback is welcome. Best regards, -- Juanjo On 06/12/11 18:33, T.Elsaleh at surrey.ac.uk<mailto:T.Elsaleh at surrey.ac.uk> wrote: Hello All, I would like to describe the asset proposed by UniS and the activities we are currently conducting. We are working on developing an RDF representation of OMA-NGSI for IoT entities and resources. This will be done according to the information models that we have developed for the IoTA project. The following is a list of the planned and ongoing activities: · Creating entity/resource templates in RDF format based on OMA-NGSI representation. · Providing a repository for the RDF data based on our Linked Sensor Data Platform. · Developing RESTful interfaces for publish/access/query · Supporting SPARQL query over the representations · We can also work with other partners to demonstrate mapping with other description models e.g. SensorML, by annotating SensorML using OMA-NGSI based RDF data. Please let us know if you have any concerns and comments. Best regards, Tarek Elsaleh Research Assistant Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: 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] On Behalf Of thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> Sent: 01 December 2011 13:03 To: rheras at tid.es<mailto:rheras at tid.es>; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Subject: Re: [Fiware-iot] Basic examples OGC- ETSI.M2M Hi all, Some comments about our decisions and next steps : 1 – Based on the collective work done in October we have decided to use for the time being OMA-NGSI and ETSI M2M for northbound and southbound API and to establish relationships with OGC but also with IoT-A and ETSI M2M to evaluate further improvements 2 – We are working on Future Internet and it is not so risky to choose ETSI M2M based on ETSI M2M community which is very large and because this community has reached a first stable version of technical specifications. 3 – Focusing today on OGC should be also a bad signal for UC projects which are not using OGC but some other standards. Typically, the existing structure in OGC is like the EPC Global structure and the 3 related projects would not adopt our GE if we have to encapsulate EPC in OGC, and this is the same concern for ONVIF regarding OGC. We have to provide an agnostic approach regarding existing standards. 4 – OMA-NGSI provides a very high level description and we have to explain/comment this description to find a generic format valuable for all the other standards description (OGC, ONVIF, EPC…) which will provide this agnostic layer. 5 – Some partners interested in some dedicated standards have to demonstrate, through NGSI and ETSI M2M implementation that the related standards could provide advanced features and and could propose NGSI and ETSI M2M improvements. 6 - In the same way, we could push improvements to the other standards for dedicated issues as security or nomadic things So at the end of November, we have to define these NGSI details (so provide your feedback regarding your knowledge in several standards) and to implement the first functions for ETSI M2M on the selected assets as provided by the task leaders. BR Thierry 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 Ricardo de las Heras Envoyé : jeudi 1 décembre 2011 11:55 À : fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Objet : [Fiware-iot] Basic examples OGC- ETSI.M2M Dear partners, as we agreed in the last conf. call, TID have prepared some examples about how we use the OGC standard (SensorML+ O&M) within the IDAS platform. Additionally I attach you a simple example about how the ETSI standard could work as a container of an OGC descriptive XML document, but this option is not implemented yet in the IDAS platform, although we are considering to include it in the medium-long term roadmap. Our main concert in this way is about how the industry will accept it, at this time we don't know any sensor/device ETSI compliant manufacturer, this is a critical point for the final success of the ETSI standard, so at present I think this would be a risky bet. Please provide any type of additional information you have about this issue. thanks, best regards, RHer at s. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es> Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D<http://www.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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2012.0.1873 / Virus Database: 2102/4650 - Release Date: 12/01/11 ________________________________ 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: <https://lists.fiware.org/private/old-fiware-data/attachments/20111207/2f2c642f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy