Henry Andrews

From a purely JSON Schema perspective, JSON Schema is defined over a data model, meaning it works on the parsed data. So not JSON or YAML text, and not encoded...

Schema validation definitely happens prior to Parameter/Encoding-Object-driven serialization. As noted in PR #3840, an API can require some sort of pre-serialization to have more control over the string representation, but...

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921! This is addressed by the new Appendix B.

As you can see in PR #3893, I dug into the history and it looks like SHOULD is correct.

PRs merged for 3.0.4 and 3.1.1!

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921! This is addressed by changes to the example table and the new Appendix E on percent-encoding.

Given that we're very explicit about where Reference Objects are allowed (and we've done the best we can about the Path Item `$ref` mess), it's not clear to me what...

@sebastien-rosset > Don't you think some of these considerations and recommendations should be in the OAI spec? The spec is very light on that topic. For example, every RFC must...

@sebastien-rosset I suspect what I proposed two years ago would also still work. There's another approach in [Appendix E](https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.appendix.E) of draft 2019-09. The reason I brought up the `if` option...

@sebastien-rosset is there a summary of what you think needs to be done now, based on the current state of the in-development 3.0.4 and 3.1.1 releases? I see this is...