Carsten Brandt

it is possible to extend the OpenAPI description. So adding properties is generally allowed. Strictly following the spec would mean that you need to prefix additional properties with `x-`.

validation currently means to check if the existing elements are used correctly. It would be possible to add some kind of strict mode that would also complain about cases like...

> Since such a property cannot be accessed as `$obj->x-internal-id` it is possible to access these like `$obj->{'x-internal-id'}`. Converting the name is a bit arbitrary, need to think about it....

realted to #121

I have never used Security and SecurityRequirement definitions before, but according to this documentation (https://swagger.io/docs/specification/authentication/) it seems it needs to look like this in YAML: ```yaml get: security: - BearerAuth:...

Seems structure changed to differentiate between openapi version 3.0 and 3.1. So we can adjust reference when support for 3.1 is implemented.

I have not taken a look into what exactly needs to be changed to support OAS 3.1, but somehow spec objects need to know which version of the spec they...

which part of the example code gets parsed as object instead of array? Could you provide a complete test set of files that reproduce the issue?

Thanks for reporting. The error message shown here is the result of running `justinrainbow/json-schema` validator against the schema provided by OpenAPI https://github.com/OAI/OpenAPI-Specification/tree/main/schemas/v3.0 Not sure if there is anything I can...

> I'm using this library to read the description and example properties from the schema, but it seem that those properties are protected. what makes you think that? what is...