Henry Andrews

OK, digging through this more, it was actually fixed in 3.1.0 with the following new text added to `style` (which, along with `explode` (but not `allowReserved`), was extended to support...

@OAI/tsc review request: It's unclear how to clarify 3.0.4 here. Even 3.1.1 is a bit murky, but the only thing I can think of for 3.0.4 is to more-or-less backport...

After a great deal of GitHub archaeology, I've determined that the intent was for `contentType` vs `style` to provide approximate parity with the Parameter Object's `content` vs `schema`. A PR...

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921!

In my attempt to handle this with other URI resolution concerns in PR #3838, @ralfhandl pointed out that CommonMark content is rendered and viewed separately from the source YAML/JSON. My...

Merged to both 3.0.4 and 3.1.1 - we'll sync up 3.2.0 once those are ready to ship.

@frankkilcommins RFC 6901 [specifically states](https://datatracker.ietf.org/doc/html/rfc6901#autoid-6) that JSON Pointers are *not* the fragment syntax for `application/json`, and RFC 8259 [does not define](https://datatracker.ietf.org/doc/html/rfc8259#autoid-17) any fragment syntax. This, of course, has not stopped...

Note that there's an issue for updating the spec.openapis.org site already: OAI/OpenAPI-Specification#3576

Shouldn't this be coordinated with the existing draft RFC to register the main OAS media types?

@frankkilcommins I recall some conversation (but have forgotten where it was) about ***not*** using the `vnd.` prefix so workflows are aligned with the [OAS media type registrations](https://www.ietf.org/archive/id/draft-ietf-httpapi-rest-api-mediatypes-05.html). Was that resolved,...