Henry Andrews

Hmm... I have run into a problem with `$ref`-ing Encoding Objects, at least if we add support for examples to them. And it feels like we should given that we...

@lornajane given the potential confusion with Encoding Objects I'm leaning that way. I will update this PR. There are also always Overlays if people really want to re-use Encoding Objects...

With apologies for the rebase, it was easier to `git reset --soft` and re-add the Media Type parts than to manually remove the Encoding Object parts. This should now _only_...

@MikeSpreitzer that's because they're not re-releases and you can't really change tags in git (not without causing tons of problems). For the `versions` directory, the markdown on the `main` branch...

@MikeSpreitzer if that doesn't make sense, it would help to know what you're trying to do with the tags. When we made that change, we couldn't really figure out how...

Improvements to Examples to support the improvements to data modeling and serialization (streaming, query strings, multipart, and XML), all of which involve complex relationships between data values and serialization formats:...

@hudlow regarding your questions: Any media type, or any variation of a media type, that cannot be represented as desired in an embedded string can be shown as an external...

See also #3256 Formally define 3.x URL Templating behavior.

@lornajane this is actually for adding to the format registry (something like `format: oas-path-template`, `format: runtime-oas-path-template`. It's stayed open because we did not have a formal definition for what that...

@baywet it depends on those improvements! Otherwise we didn't have a formal specification for what the proposed `format` values meant, which is why they were rejected and this issue was...