Skip to content

Reference latest JSON RFC8259 instead of RFC7159 #4487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ralfhandl opened this issue Mar 21, 2025 · 0 comments · Fixed by #4646
Closed

Reference latest JSON RFC8259 instead of RFC7159 #4487

ralfhandl opened this issue Mar 21, 2025 · 0 comments · Fixed by #4646
Assignees
@ralfhandl
Labels
editorial Wording and stylistic issues
Milestone
v3.2.0

Comments

@ralfhandl
Copy link
Contributor

ralfhandl commented Mar 21, 2025 •
edited
Loading

https://datatracker.ietf.org/doc/html/rfc8259 obsoletes the currently referenced https://datatracker.ietf.org/doc/html/rfc7159
@ralfhandl ralfhandl added this to the v3.2.0 milestone Mar 21, 2025
ralfhandl added a commit to ralfhandl/OpenAPI-Specification that referenced this issue Mar 26, 2025
@ralfhandl
Fixes OAI#4487
2b0b342
This was referenced Mar 26, 2025
Merged
Closed
@ralfhandl ralfhandl self-assigned this Mar 26, 2025
@ralfhandl ralfhandl added the editorial Wording and stylistic issues label Mar 26, 2025
@lornajane lornajane mentioned this issue Jun 1, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ralfhandl ralfhandl

Labels
editorial Wording and stylistic issues
Projects
None yet
Milestone
v3.2.0
Development

Successfully merging a pull request may close this issue.

Update stated number of parameter locations (tiny fix!) lornajane/OpenAPI-Specification
1 participant
@ralfhandl