This repository was archived by the owner on Nov 2, 2023. It is now read-only.
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.
s/draft/version/g
in implementations.md and a few other similar changes.In reading the numerous discussions in this repository and the spec repository concerning historical versions of the specification, I began to recognize there may be some impedance presents itself in the terminology used and the IFTE draft process.
Personally, I think this change is largely immaterial, in that in various segments of the software development community the drafts will function as versions. That is simply the nature of how quickly things change. However, I recognize it correct to call them drafts (Draft 5 is the 5th released version and is a version of the specification but there is no JSON Schema Version 5) and think this change makes the site more consistent and may help with understanding of the process used by JSON Schema.