3.1 Runtime Expression ABNF: use exact same name as in RFC7159#4877
Merged
ralfhandl merged 1 commit intoOAI:v3.1-devfrom Aug 17, 2025
Merged
3.1 Runtime Expression ABNF: use exact same name as in RFC7159#4877ralfhandl merged 1 commit intoOAI:v3.1-devfrom
ralfhandl merged 1 commit intoOAI:v3.1-devfrom
Conversation
handrews
approved these changes
Aug 16, 2025
Member
handrews
left a comment
handrews
left a comment
There was a problem hiding this comment.
Oh I see what happened. I deliberately did not backport this b/c I misread it as coming from RFC5234 which uses CHAR, but RFC7159 (cited here) does use char (as does RFC8259 which is cited in 3.2).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We already did this in v3.2.