Clarify OpenAPI vs Swagger - part 1 #1244
Closed
Conversation
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
This clarifies the spec parts of this page. We still have an issue with identifying the tools for the spec with Swagger, while the tools for the spec should be listed somewhere non-proprietary and the Swagger list should be within (or referred to by) that list.
earth2marsh
reviewed
Jun 30, 2017
| @@ -1,4 +1,4 @@ | |||
| # The OpenAPI Specification (fka The Swagger Specification) | |||
| # The OpenAPI Specification (originally cloned from The Swagger Specification) | |||
Member
There was a problem hiding this comment.
Technically, the spec repo was transferred, not cloned. This isn't a copy of the Swagger spec, it is an evolution.
Contributor
There was a problem hiding this comment.
#TDC: "fka" -> "formerly"
earth2marsh
reviewed
Jun 30, 2017
| ### [OpenAPI 2.0 Specification](versions/2.0.md) | ||
|
|
||
| This repository contains the existing Swagger 1.2, 2.0 specifications as well as proposals for the next version of the specification, which will be called the OpenAPI Specification 3.0. The proposals live in the [OpenAPI.next](https://github.com/OAI/OpenAPI-Specification/tree/OpenAPI.next) branch. | ||
| This repository contains the existing Swagger 1.2 and Swagger 2.0 specifications, the OpenAPI Specification 2.0 which is identical to the Swagger 2.0 specification, as well as proposals for the next version of the specification, which will be called the OpenAPI Specification 3.0. The proposals live in the [OpenAPI.next](https://github.com/OAI/OpenAPI-Specification/tree/OpenAPI.next) branch. |
Member
There was a problem hiding this comment.
Suggest: the OpenAPI Specification 2.0, which is identical to the Swagger 2.0 specification but with a new name, (adds comma and emphasizes the name change)
Contributor
|
#TDC: Thanks @usarid. Please make this PR against the OpenAPI.next branch |
Contributor
Contributor
Author
|
This was implemented as #1281 so closing this. |
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.
This clarifies the spec parts of this page. We still have an issue with identifying the tools for the spec with Swagger, while the tools for the spec should be listed somewhere non-proprietary and the Swagger list should be within (or referred to by) that list.