Mike Ralphson

As intended. See lengthy discussions in #1004 - note specification extensions are allowed also. What fields do you think are missing?

It's just a hint to consoles / SDKs (and all other use-cases) that a client certificate must be obtained **in some way** and presented in the TLS connection.

> unless we want to continue the years old OAI trend of making PR comments part of the spec/docs Can you run that sentence by me one more time? I...

> “the spec is clear but Darrel said this in an issue a few years ago” or “this issue says X and that pull request says Y but the spec...

As a result of #2604 the filename for this proposal should change to use a dated prefix. Please could you update this PR to match? You can use the original...

As we have the `attribute` property on the `xml` object already, perhaps it makes sense to add a `text` property (also of type boolean) to indicate that the property represents...

@andygaga2018 to make things clear, both of the examples above are proposals for future versions of the OpenAPI Specification. They won't work today in any existing tools.

The issue is still open / unresolved. As per our development guide, it isn't the kind of thing which can be changed in a patch release.

Just a note that JSON Schema draft 2020-12 (which will be referenced by OAS 3.1) does support some of these constructs, such as `$ref` with siblings and `$comment`. `enum`s with...

Just a reminder, please use github reactions, rather than "+1" comments (two recent ones deleted).