Merge branch 'OpenAPI.next' into 2016-11-grammar-diction

Author: Ron

DEVELOPMENT.md

@@ -27,7 +27,7 @@ The specification _will change_ from the original 2.0 version.  We should typica
  - Use labels for the workflow of specification changes.  For example, this may be labeled as `proposed`, `needs migration review`, `needs tooling review`, `needs documentation`, `rejected`, `needs approval`.  These labels must be assigned by project committers
  - An issue will be opened for each feature change.  Embedded in the issue OR ideally linked in a file via pull-request (PR), a document should be supplied for use cases for the change
  - A PR will be used to describe the _proposed_ solution, and linked to the original issue
- - Not all committers will contribute to ever single proposed change.  There may be many open proposals at once, and multiple efforts may happen in parallel
+ - Not all committers will contribute to every single proposed change.  There may be many open proposals at once, and multiple efforts may happen in parallel
  - When the OpenApi.next spec is complete and approved for release, the branch will be merged to master.
 
 ## Approving Changes

IMPLEMENTATIONS.md

@@ -0,0 +1,39 @@
+### Implementations
+
+Below is a list of known tooling implementing the 3.0.0 specification. Because
+the 3.0.0 specification has not yet been released, please consult the details of
+any projects listed below for notes about stability and roadmap.  The process 
+to create the best possible 3.0.0 specification includes feedback from end-users
+and tooling creators alike, and it is strongly encouraged that draft tooling be
+made available for early users of the OAS.
+
+These tools are not necessarily endorsed by the OAI.
+
+#### Low-Level tooling
+
+| Title          | Project Link | Language |Description                          |
+|----------------|--------------|----------|---------------------|
+| swagger-parser | [GitHub/swagger-api](https://github.com/swagger-api/swagger-parser/tree/feature/3.0.0-rc0) | Java | Swagger 1.0, 1.1, 1.2, 2.0 to Open API Specification converter |
+| swagger-models | [GitHub/swagger-api](https://github.com/swagger-api/swagger-core/tree/feature/3.0.0-rc0/modules/swagger-models) | Java | Open API 3.0 Java Pojos |
+| KaiZen OpenAPI Parser | [GitHub/RepreZen/KaiZen-OpenAPI-Parser](https://github.com/RepreZen/KaiZen-OpenAPI-Parser) | Java | High-performance Parser, Validator, and Java Object Model for OpenAPI 3.x |
+| openapi3-ts | [GitHub/metadevpro/openapi3-ts](https://github.com/metadevpro/openapi3-ts) | TypeScript | TS Model & utils for OpenAPI 3.0.x contracts |
+| swagger2openapi | [GitHub/mermade/swagger2openapi](https://github.com/mermade/swagger2openapi) | Node.js | An OpenAPI / Swagger 2.0 to OpenAPI 3.0.x converter and validator |
+| Tavis.OpenApi | [GitHub/tavis-sofware/Tavis.OpenApi](https://github.com/tavis-software/Tavis.OpenApi/) | dotnet | C# based parser with definition validation and migration support from V2 |
+
+
+#### User Interfaces
+
+| Title          | Project Link | Language |Description                          |
+|----------------|--------------|----------|---------------------|
+| openapi-viewer | [GitHub/koumoul/openapi-viewer](https://github.com/koumoul-dev/openapi-viewer) | Vue.js | Browse and test a REST API described with the OpenAPI 3.0 Specification |
+
+
+#### Server Implementations
+
+
+#### Code Generators
+
+| Title          | Project Link | Language |Description                          |
+|----------------|--------------|----------|---------------------|
+| baucis-openapi3 | [Github/metadevpro/baucis-openapi3](https://github.com/metadevpro/baucis-openapi3) | Node.js | [Baucis.js](https://github.com/wprl/baucis) plugin for generating OpenAPI 3.0 compliant API contracts |
+| Google Gnostic | [GitHub/googleapis/gnostic](https://github.com/googleapis/gnostic) | Go | Compile OpenAPI descriptions into equivalent Protocol Buffer representations |

README.md

@@ -1,5 +1,9 @@
 # The OpenAPI Specification
 
+### Draft implementations of tooling supporting the 3.0.0 specification can be found here!
+
+[3.0.0 Implementations](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/IMPLEMENTATIONS.md)
+
 This is the working branch for the next version of the OpenAPI Specification. You can read more about the Open API Initiative (OAI) at [https://openapis.org](https://openapis.org).
 
 The current, released version of the OpenAPI Specification is 2.0, through donation of the Swagger Specification to the OAI by SmartBear Software.  If you are interested in the release specification, please see the [master branch](https://github.com/OAI/OpenAPI-Specification/blob/master/README.md) of this project.

fixtures/v2.0/json/resources/resourceWithLinkedDefinitions_part1.json

@@ -24,13 +24,13 @@
       "200": {
         "description": "pet response",
         "schema": {
-          "$ref": "#/definitions/Pet"
+          "$ref": "https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/fixtures/v2.0/json/resources/resourceWithLinkedDefinitions.json#/definitions/Pet"
         }
       },
       "default": {
         "description": "error payload",
         "schema": {
-          "$ref": "#/definitions/ErrorModel"
+          "$ref": "https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/fixtures/v2.0/json/resources/resourceWithLinkedDefinitions.json#/definitions/ErrorModel"
         }
       }
     }