Mike Ralphson

Closing due to inactivity and empty description - but please feel free to reopen the issue if necessary.

@fmvilas sorry I never replied to the above, must have missed it. I believe these are the currently open related OAS issues: * https://github.com/OAI/OpenAPI-Specification/issues/1973 * https://github.com/OAI/OpenAPI-Specification/issues/1616 * https://github.com/OAI/OpenAPI-Specification/issues/782

@geoffreywiseman OAS (or whatever version the next release ends up as being) will support `$ref` with a sibling `description` property.

Sorry, there should have been a 3.1 in there, which got lost in editing!

> Is this going to be available in v3.1 ? 3.1.0 is already out. You can override the `description` of a `parameterObject` in a `$ref`, but not (yet) the `required`...

In OpenAPI 3.x does this have any advantages (apart from perhaps readability) over the more JSON-schema recipe: ``` deliver_methods: type: string anyOf: - enum: - parcel - letter - email...

@JonKohler from the documentation you linked to (emphasis mine): > For this reason, enums are **not** automatically turned into strongly typed enum types - instead they are rendered in the...

> In short, if we boil this back to the need to have both extensible enums as well as having some metadata about those enums (description, etc), then that is...

@JonKohler the short answer is that the spec. is just markdown and anyone can, and is very welcome to, PR changes against it. Though a PR could just be a...

How will the canonical form represent circular schemas in **a document** if all `$ref`s are to have been resolved? JSON has no mechanism to support this, and we ban the...