You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the beaconMapResponse (/map) there are some endpoint URLs that are defined as "format": "uri" while what is actually put / expected "format": "uri-template".
For instance, Endpoint.singleEntryUrl expects the entry identifier. Also additional endpoints should be correctedRealatedEndpoint.url .
Currently strict Json Schema Validator reports errors on all endpoints that have path parameters {}.
Cheers,
Dmitry
The text was updated successfully, but these errors were encountered:
Not critical bug correction.
Draft 7 validators should fail validating "singleEntryUrl": "https://beacons.bsc.es/beacon/v2.0.0/datasets/{id}" because "{}" characters forbidden in URI.
On the other hand in 2020-12 "format" property shouldn't be considered by default (should be ignored).
The question whether we want to enable "format" validation in 2020-12 and if validator used in beacon validator.
may be programmatically configured to enable "format" vaildation.
understand "vocabulary" way to enable "format" validation via JSON schema mechanism.
Hello,
In the beaconMapResponse (/map) there are some endpoint URLs that are defined as
"format": "uri"
while what is actually put / expected"format": "uri-template"
.For instance, Endpoint.singleEntryUrl expects the entry identifier. Also additional endpoints should be correctedRealatedEndpoint.url .
Currently strict Json Schema Validator reports errors on all endpoints that have path parameters {}.
Cheers,
Dmitry
The text was updated successfully, but these errors were encountered: