2017-03-10 09:53:22 +0100 | commented question | Support for Device Pairing? Hi, That is not the way the FIWARE IoT model works as long as devices and their measurements and actions are translated into data objects at the NGSI level (attributes and command attributes). Data (attributes) may belong to specific groups of users (or even a single user) via the IDM security enab |
2017-03-10 09:33:20 +0100 | commented question | Ultralight Evolution There is no published Ultralight v1 version, it was an internal evolution/simplification of the previous standard used by IDAS (SensorML or SML). The first open/published one was Ultralight2.0. |
2016-12-07 15:34:02 +0100 | commented question | FIware IoT Ready / benefits for agricultural applications It works exactly in the same way, IoT device manufacturers will benefit from 1) interoperability at the data context level and thus compliancy with more projects 2) business opportunities arising within the FIWARE community. Actually, interoperability is already a key topic for agrifood machinery. |
2015-11-26 04:38:38 +0100 | answered a question | Fiware for data collection from IOT devices Hi, You should use what we call "Common Simple scenario " described in the FIWARE IoT Architecture here: https://forge.fiware.org/plugins/medi...ofThings%28IoT%29ServicesEnablementArchitecture This means you should be using: 1) Orion ContextBroker (as the northbund data inteface). http://catalogue.fiware.org/enablers/... 2) IDAS IoT Agents (These are connectors from well-known IoT comm protocols to the Orion ContextBroker). The exact IoT Agent depends on your devices/gateways implementations. We do support UL2.0/HTTP, MQTT and LWM2M/CoAP. Also there is a node.js library to build up your own IoT Agent in case you do not use any of the above mentioned standards. Cheers, |