iotagent-node-lib
iotagent-node-lib copied to clipboard
Actuation should align any discrepancies with NGSI-LD 1.6.1 Annex H Best Practice
The latest NGSI-LD Specification has been published. Opening an issue similar to #1258 and #1259 to discuss questions further.
iotagent-node-lib is now listed as an Informative reference within the latest published NGSI-LD 1.6.1 Specification, as such it follows or is already the basis of much of Annex H for Suggested actuation workflows
Any divergence should already be minimal, but some changes will need to be made regarding differences between 1.5.1 and 1.6.1 Registrations.
H.3.1 Suggests adding an additional Property for listing available commands
The additional Property dedicated to the list of available commands is as follows:
"commands": {
"type": "Property",
"value": ["<cmd_name1>","<cmd_name2>", …, "<cmd_nameN>"]
}
How should this be implemented? Is it something common to NGSI-v2 and NGSI-LD or is it NGSI-LD only? Is this something to be added to the ldSupport
configuration or another config.js
parameter?
4.3.6 Distributed Operations
Introduces multiple operation types for distributed operations - "I'm an Actuator" is just another flag in the registration payload. How should this be supported? Is an ldSupport
configuration parameter needed for backwards compatibility.
Related to https://github.com/telefonicaid/iotagent-ul/issues/573
- The ETSI NGSI-LD committee defines what should happen across brokers.
- The Scorpio codebase is updated to accept registrants which are not full brokers
- The Orion-LD codebase is updated to accept true federations
- The IoT Agent Node lib is updated to provide whatever flags are necessary when making a registration to describe its implementation as a partial broker.
- A stable release of the IoT Agent Node lib is completed and added to the IoT Agent for JSON
- A stable release of the IoT Agent for JSON is completed.
Point 1. has now been published. This discussion should decide what needs to be done to implement point 4.
- [x] The ETSI NGSI-LD committee defines what should happen across brokers.
- [x] The Scorpio codebase is updated to accept registrants which are not full brokers
- [x] The Orion-LD codebase is updated to accept true federations
- [x] The IoT Agent Node lib is updated to provide whatever flags are necessary when making a registration to describe its implementation as a partial broker.
- [x] A stable release of the IoT Agent Node lib is completed and added to the IoT Agent for JSON
- [x] A stable release of the IoT Agent for JSON is completed.
Closing