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

We will use Open-API 2.0 instead of 3.0 #4

Closed

ypriverol opened this issue Aug 17, 2018 · 1 comment

Labels

Milestone

First beta releas...

Contributor

ypriverol commented Aug 17, 2018

We will use the Open-api 2.0 because code autogeneration is supported by many tools.

Contributor Author

ypriverol commented Aug 19, 2018 •

edited

Loading

Some of the problem using swagger 2.0 is that it support single server only.

schemes: 
  - http
  - https
host: www.proteomexchange.org
basePath: /proxi/v2

Not the multiple server representation. My proposal is to leave only the proteomexchange representation here. This is related with issue #3

My proposal is to have a representation for ProteomeXchange as the reference.

ypriverol mentioned this issue

Update api-swagger.yaml #2

Merged

ypriverol added this to the First beta release of PROXI specification milestone

ypriverol added the proxi-schemas label

ypriverol closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment