Closed floitsch closed 2 months ago
openaq.local/2.0.0 Has a similar issue (just true
instead of false
):
https://github.com/APIs-guru/openapi-directory/blob/main/APIs/openaq.local/2.0.0/openapi.yaml#L52
Turns out the meaning of exclusiveMinimum and exclusiveMaximum has changed in a later draft, and I missed that these openapi documents were based on openapi 3.0.x which still used the wright-json-schema-validation draft.
In that draft these properties must be booleans: https://datatracker.ietf.org/doc/html/draft-wright-json-schema-validation-00#section-5.3
Sorry for the noise.
According to the json-schema spec, the
exclusiveMaximum
andexclusiveMinimum
values must be numbers: https://json-schema.org/draft/2020-12/json-schema-validation#name-exclusivemaximumHowever, the groundhog-day document has 'false' as values: https://github.com/APIs-guru/openapi-directory/blob/433a94f3e9e268f2b000b0b497785ede34332a7f/APIs/groundhog-day.com/1.2.1/openapi.yaml#L568