[Fiware-ngsi] NGSI 9 interface

[Martin Bauer]

Hi Lorant, all,

As mentioned a couple of times before, we at NEC have some concerns regarding the use of the NGSI-9 interface as the primary interface to the Thing/Resource Management GE.

The purpose of the NGSI-9 interface is to enable Context Management Components to interact with external sources and peer Context Management Components from other providers. The assumption is that the External Source or Context Management Component implements an NGSI-10 interface, so only a reference (URI) pointing to this interface is foreseen in the respective data structures.
For IoT, this is not the case, i.e., we cannot assume that all our (internal) resources implement NGSI-10. We at least want to support ETSI M2M, but possibly also other interfaces. The NGSI-9 interface does not allow the specification of such interfaces (and should not, as the internal structure of the Context Management Component is out of scope of the NGSI interfaces). Therefore it is not sufficient for finding (and providing enough information about) general IoT resources associated to things.

Whereas the NGSI-9 interface at least fits from a general point of view, as it allows matching things/attributes (or attribute domains) to the respective components that can provide the information, there does not seem to be an appropriate interface for finding resources based on a resource description. We cannot assume that only Thing-level access to information is required. Instead we may want to use actuation, of find appropriate resources to integrate in a business process etc. In this case we need to be able to specify the resource we are looking for and match that to the respective resource description.
In these cases we need to be able to match syntactic/semantic interface descriptions etc., so the interface should be expressive enough for that purpose.

Best regards,

Martin

------------------------------------------
Dr. Martin Bauer
Senior Researcher
NEC Europe Ltd.
NEC Laboratories Europe
Software & Services Research Division
Kurfürsten-Anlage 36
D-69115 Heidelberg
Tel: +49/ (0)6221/4342-168
Fax: +49/ (0)6221/4342-155
E-Mail: Martin.Bauer at neclab.eu<mailto:Martin.Bauer at neclab.eu>
http://www.nw.neclab.eu<http://www.nw.neclab.eu/>

*************************************************************
NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 2832014

From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest)
Sent: Monday, February 13, 2012 9:09 AM
To: fiware-ngsi at lists.fi-ware.eu
Subject: [Fiware-ngsi] NGSI 9 interface


Hi Ricardo, Tobias,

Regarding NGSI 9 and the configuration management component we discussed the following during our bi-weekly follow-up with Juanjo:

First impression - NGSI 9 provides all the operations that are indeed needed to be provided from the configuration management component to applications? Example: need to discover relationships between entities, linked to IoT resources that relate to a given thing and does not know whether that is something for which existing NGSI 9 adapts. If not, a set of API-s should be more than NGSI 9. NGSI 9 would be there for basic configuration management, additional interfaces extending NGSI 9 are also needed. AP Ricardo, NEC: clarify what is needed on top of NGSI 9 for configuration management

Could you please take the initiative to start clarifying this topic on this mailing list?

Thanks & Br,

Lorant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20120214/d10c0336/attachment.html>