Hi There.

I'm hopeful this mailed can assist in answering my question or forwarding to an appropriate location.

I'm interested in why Fiware decided to use a context management model composed of JSON structures rather than the LWM2M Object/Resource/Instance model? Is there a document that has some rational for this or perhaps someone reading this knows the history?

Since Fiware is based on NGSI, which is part of OMA, I would have thought that it would have embraced the OMA LWM2M object model definition.

I know there is a Fiware agent that supports LWM2M, but this means that the agent is effectively mapping from the LWM2M object/resource/instance model into the NGSI/Fiware JSON structure. What value did this bring opposed to supporting the LWM2M object/resource/instance model all the way up and through the Context Broker / Orion?

Thanks in advance for your thoughts and assistance

... Altan

__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the following links:

• http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
• http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE

Fiware-general-help mailing list
Fiware-general-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-general-help

[Created via e-mail received from: altan@aol.com]