David Biesack

Thanks @P0lip . Do you know why #2030 was closed? I don't see this as having been resolved. One option may be to define two schema validation functions, so one...

I've also wanted a solution for this, not so much for internationalized variants, but for normal API evolution. For example, a path is called `x`, but after feedback from your...

@grapefruit since this is already tagged at "OpenAPI.Next Proposal" and remains Open, this ticket should suffice. If think adding another won't help.

OpenAPI 3.1 allows defining [reusable path item objects](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object) so one can define the full operation(s) in as reusable path items in `#/components/pathItems`, then reference them: ```yaml paths: /route/a: $ref: '#/components/paths/my-reusable-ops'...

@mitar OAS 3.1 already allows a `$ref` in an object to have siblings. OAS 3.1 no longer defines its [reference objects](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#referenceObject) as [JSON Reference](https://datatracker.ietf.org/doc/html/draft-pbryan-zyp-json-ref-03) objects (as was done in [OAS...

OAS allows `description` and `summary` on `$ref` objects, but not specification extensions. So you can't add arbitrary other properties within the OAS structure. JSON Schema does not have this restriction...

I would prefer link schemes based on `operationId` rather than paths, which I find awkward and also a bit fragile when an API is in early stages. Admittedly, supporting references...

One issue with using Markdown anchors is that there is no standard anchor pattern across all the possible tools that render (HTML or other) API doc. slate, redoc, swagger-ui, shins...

@webron just bumping this one for visibility -it's a few years old, but seems doable. Details on my April 2019 reply.

@cdivilly Please use `type`, not `mediaType`, as per [RFC 4287 3.1.1.1 The "type" Attribute](https://tools.ietf.org/html/rfc4287).