We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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 :
Definition of an identifier in the CURIE 'prefix:local-part`'format.
Many implementations just put the word "CUSTOM" from the example that makes responses invalid.
Cheers,
D.
The text was updated successfully, but these errors were encountered:
Hi Dmitry,
yes, this was addressed recently in issue #83, so maybe there are still some implementations that have not updated this.
Best,
Oriol
Sorry, something went wrong.
Closing this since the schema had been fixed; erroneous implementations can be pointed to the respective issue & PR.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: