Hi, this is just a question.
As the uptake of Lucid ramps up, the schema is likely to be updated and new versions released, but FD's using device profiles validated by earlier versions will already be in the production.
When an SA loads a device profile it needs to know the version of the Lucid Schema that the device profile should be validated against.
The device Profile does have a version number in it:
Can SA Developers rely on that "lucid" version number to identify the version of schema it needs to load to validate the device profile?
By this I mean using the number to construct this "$id" string:
"$id": "https://lucidprotocol.org/**3**/lucid.schema.json",
Will this number be updated to 3.1 9 (or higher) on the next release to to take into account the addition of cVER in UP/data and any other schema fixes?
Hi, this is just a question.
As the uptake of Lucid ramps up, the schema is likely to be updated and new versions released, but FD's using device profiles validated by earlier versions will already be in the production.
When an SA loads a device profile it needs to know the version of the Lucid Schema that the device profile should be validated against.
The device Profile does have a version number in it:
Can SA Developers rely on that "lucid" version number to identify the version of schema it needs to load to validate the device profile?
By this I mean using the number to construct this "$id" string:
"$id": "https://lucidprotocol.org/**3**/lucid.schema.json",
Will this number be updated to 3.1 9 (or higher) on the next release to to take into account the addition of cVER in UP/data and any other schema fixes?