Closed redmitry closed 5 months ago
Hi Dmitry,
yes, this was addressed recently in issue #83, so maybe there are still some implementations that have not updated this.
Best,
Oriol
Closing this since the schema had been fixed; erroneous implementations can be pointed to the respective issue & PR.
Hello,
In the HandoverType example beaconCommonComponents.json#HandoverType one of the "id" has a value "CUSTOM" which is not a qualified CURIE. Current CURIE pattern : beaconCommonComponents.json#CURIE defines CURIE being qualified :
Many implementations just put the word "CUSTOM" from the example that makes responses invalid.
Cheers,
D.