Skip to content

OpenAPI v3.1 Specification missing #4624

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.

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

Open
AaronNGray opened this issue May 21, 2025 · 6 comments
Open

OpenAPI v3.1 Specification missing #4624

AaronNGray opened this issue May 21, 2025 · 6 comments
Labels
Needs attention The author has replied and people with triage rights should take action.

Comments

@AaronNGray
Copy link

Cannot find either JSON or YAML spec of OpenAPI 3.1 specification

@handrews
Copy link
Member

Do you mean schemas? They are on the spec site.

@lornajane
Copy link
Contributor

Thanks @handrews , you beat me to it :) @AaronNGray was this what you are looking for?

@AaronNGray
Copy link
Author

Yes, thank you very much.

There's atleast one existing project that refers to the broken links. Are there any canonical URI's to textual version of 3.0.3 and 3.1.0, like 3.0 :-
https://github.com/OAI/OpenAPI-Specification/blob/3.1.0/schemas/v3.0/schema.yaml

@github-actions github-actions bot added Needs attention The author has replied and people with triage rights should take action. and removed Needs author feedback labels May 21, 2025
@lornajane
Copy link
Contributor

I think the specification documents themselves explain that the spec site links should be considered the canonical version. The schemas also should be used from that site

@AaronNGray
Copy link
Author

AaronNGray commented May 21, 2025

It really need to be electronically accessible by URI without pre/post processing, the others are : /

@handrews
Copy link
Member

@AaronNGray they are- the URLs on that site are the canonical URLs and reflected in the $id / id values.

A programmatic way to figure out the most recent canonical URL is in the road map, but lacks the volunteers needed to improve the web site infrastructure (which is the main blocker) and implement a solution (easy enough if the infrastructure is updated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs attention The author has replied and people with triage rights should take action.
Projects
None yet
Development

No branches or pull requests

3 participants