Skip to content

v3.2: ports from 3.3 (June/July 2026)#5420

Draft
karenetheridge wants to merge 11 commits into
OAI:v3.2-devfrom
karenetheridge:ether/v3.2-ports-from-3.3-202606
Draft

v3.2: ports from 3.3 (June/July 2026)#5420
karenetheridge wants to merge 11 commits into
OAI:v3.2-devfrom
karenetheridge:ether/v3.2-ports-from-3.3-202606

Conversation

@karenetheridge

Copy link
Copy Markdown
Member

Backports from 3.3 to 3.2 of recent spec edits.

Will continue populating this list until all 3.3 PRs are merged.

I think all of these are suitable for inclusion into 3.2.1, as they are all clarifications rather than introducing new capabilities.

  • no schema changes are needed for this pull request

…rmat

In JSON, property keys are always strings; in YAML they may or not be
depending on the parser, but other formats may also be in use (TOML, TOON
etc). What matters is the resulting type(s) of the decoded data, not the
specific formatting used for the serialized form.
Appendix D no longer talks about percent-encoding of headers, as the
specification is now clear that percent-encoding of headers is never done
(with the exception of the use of style:form in Cookie headers).
We are specifically talking about the "encoding" keyword here, and the
multipart/form-data media-type (most other multipart types decode to arrays).
This change is accompanied by an edit to the "Forms" page in the Media-Type
Registry.
We have the names for each part, as the parsed data uses the format:

  [
    { <name>: <value> },
    { <name>: <value> },
    ...
  ]
@karenetheridge karenetheridge force-pushed the ether/v3.2-ports-from-3.3-202606 branch from 0a5b864 to a5edad7 Compare July 2, 2026 22:49
@karenetheridge karenetheridge changed the base branch from main to v3.2-dev July 2, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant