Skip to content
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

Adopt or Align with open API Stand #41

Open
samperd opened this issue Dec 20, 2016 · 2 comments
Open

Adopt or Align with open API Stand #41

samperd opened this issue Dec 20, 2016 · 2 comments

Comments

@samperd
Copy link

samperd commented Dec 20, 2016

Since we last visited this issue a few more environmental drivers have popped up.

I propose we either re-examine this standard and align more closely with the Open API Standard (https://www.openapis.org/). Or alternatively we just adopt the Open API Standard.

@gnewton
Copy link

gnewton commented Dec 20, 2016

I would vote for just adopting Open API Standard. With respect to #42, I would prefer that OAS was chosen, as opposed to Swagger (are they different?). From https://www.openapis.org/faq#OAIFAQ-Swagger it is not clear (to me) how Swagger and OAS will move forward, and if they might diverge. If they do not diverge, then adopting OAS is not a problem. If they do diverge and we have chosen Swagger but most of industry chooses OAS, then it is a problem...

@LaurentGoderre
Copy link
Member

I agree with @gnewton I would rather we adhere to a Standard than an implementation

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

No branches or pull requests

3 participants