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

Clarify the relationship between OpenAPI 3.1 and the JSON Schema version #2363

Closed
darrelmiller opened this issue Oct 1, 2020 · 2 comments
Closed
Assignees
Milestone

Comments

@darrelmiller
Copy link
Member

The current 3.1 spec says,

The Schema Object allows the definition of input and output data types. These types can be objects, but also primitives and arrays. This object is a superset of the JSON Schema Specification Draft 2019-09.

We should agree on wording to clarify that future versions of JSON Schema (assuming non-breaking) are also usable with OpenAPI 3.1. (wordsmithing required)

In order to achieve forward compatibility with JSON Schema, we need to define the OpenAPI keywords as a vocabulary. And define how the OpenAPI vocabulary is applied to the JSON.

@darrelmiller darrelmiller added this to the v3.1.0-final milestone Oct 1, 2020
@darrelmiller
Copy link
Member Author

Wait to see if JSON Schema 2020 makes it out to meet our schedule. We can decide on wording at the last minute.

@MikeRalphson
Copy link
Member

#2399 is merged.

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

2 participants