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

JSON Schema as separate ApiDOM namespace #1814

Open
char0n opened this issue Aug 9, 2022 · 0 comments
Open

JSON Schema as separate ApiDOM namespace #1814

char0n opened this issue Aug 9, 2022 · 0 comments
Assignees
Labels
ApiDOM Epic JSON Schema JSON Schema related work

Comments

@char0n
Copy link
Member

char0n commented Aug 9, 2022

The goal of this epic is to have JSON Schema and their various drafts and versions as separate ApiDOM namespace.

Here is the list of specification we want to support and the version of JSON Schema each of the spec is using:

Draft 5 is actually a Draft 4:

You might come across references to Draft 5. There is no Draft 5 release of JSON Schema. Draft 5 refers to a no-change revision of the Draft 4 release. It does not add, remove, or change any functionality. It only updates references, makes clarifications, and fixes bugs. Draft 5 describes the Draft 4 release. If you came here looking for information about Draft 5, you'll find it under Draft 4. We no longer use the "draft" terminology to refer to patch releases to avoid this confusion.

Refs #1075 (comment)
Refs #1075

Resources:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ApiDOM Epic JSON Schema JSON Schema related work
Projects
None yet
Development

No branches or pull requests

1 participant