Mike Ralphson

If you're planning on integrating with the directory, please feel free to PR against the README whenever is appropriate. Just FYI, the definitions which originate in non-OpenAPI 2.0 format (primarily...

Update: we now no longer use the more lax OpenAPI v2.0 validator. All issues **except** `azure.com` ones should now be fixed. The `service` values for these need to be aligned...

@seriousme thank you for the report and analysis. When you are processing files named `swagger.yaml` remember these will be OpenAPI 2.0 and will need converting before you validate them with...

> A response needs to contain either a $ref or a description, not both According to the 3.0 spec, additional properties in a reference object are ignored (not disallowed).

> additionalProperties must be boolean. According to the v3.0 spec: > additionalProperties - Value can be boolean or object. Inline or referenced schema MUST be of a [Schema Object](#schemaObject) and...

@seriousme britbox, keycloak and nasa/apod definitions fixed. Many thanks.

`ato.gov.au` the schema definition for the `Reference` object appears to leave `additionalProperties` as the default `true` so it **does allow** additional properties other than `$ref`. Because of the "SHALL be...

That URL now seems to require authentication.

If you're still interested, can you tell me why you need this feature?

Thanks!