[Fiware-ngsi] NGSI examples of IoT Concepts

[Tobias Jacobs]

Hi Tarek,

OMA NGSI 9/10 by itself is based on the concepts on entities and their attributes.  There is no built-in distinction between Devices, Resources, Things.

Also the currently discussed association concept does not change this point of view. In associations like "entity1 --> entity2", both are just entities. The terms "device-level entity" and "thing-level entity" are just used as role names in order to distinguish what is before the arrow from what is behind the arrow, but this does not restrict the kinds of entities that can be associated with each others.

For examples, you might want to have a look at https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples, although these examples are mainly for explaining how the message bodies of the operations look like.

Best regards
Tobias


From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk]
Sent: Donnerstag, 14. März 2013 18:22
To: Tobias Jacobs; fiware-ngsi at lists.fi-ware.eu
Cc: fiware-iot at lists.fi-ware.eu
Subject: RE: NGSI examples of IoT Concepts

Hello Tobias,

Thanks for the clarification. I think "concept" is what I meant. Let me take a step back.

So, what "concepts" can be defined in NGSI? a Thing , a Device, an IoT Resource...? Are they somehow "explicitly" distinguished from each other in NGSI?

Are there any NGSI (XML) examples available for each concept?

Best regards,
Tarek





From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu]
Sent: 14 March 2013 16:55
To: Elsaleh T Mr (Electronic Eng); fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: RE: NGSI examples of IoT Abstractions

Hi Tarek,

I have to admit that I do not understand very well your question.
When you say "IoT Abstraction" do you mean different abstraction levels in the information model?

With the association concept we envision something like device-level information and thing-level information, and the translation between both levels. However, syntactically we do not distinguish between these levels, as NGSI is used for both.

On the other hand, "Gateway" is not an abstraction level, but a part of the architecture. What I suggested in the F2F meeting was to also add "Backend" to this list at the beginning of the architecture description.

In general, this list at the beginning of the architecture description does not describe so much the abstraction levels, but rather contains definitions of the terminology used in the architecture document.

Best regards
Tobias


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 t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>
Sent: Donnerstag, 14. März 2013 12:44
To: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] NGSI examples of IoT Abstractions

Hello All,

This matter was brought up in the IoT F2F meeting, but could someone provide examples of the FIWARE IoT abstractions - i.e. Thing, Device, Gateway and Resource? Or at least how you would envision it?

By the way, wasn't there another IoT Abstraction we wanted to add?

Best regards,
Tarek

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20130315/4fbc2bfb/attachment.html>