Skip to content
This repository was archived by the owner on Nov 2, 2023. It is now read-only.

Favor term 'draft' over 'version' #126

Merged
merged 2 commits into from
Jun 14, 2017

Conversation

adamvoss
Copy link
Contributor

@adamvoss adamvoss commented Jun 7, 2017

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.

@adamvoss adamvoss changed the title Favor term draft over version Favor term 'draft' over 'version' Jun 7, 2017
@handrews handrews merged commit 3598c12 into json-schema-org:master Jun 14, 2017
@handrews
Copy link
Contributor

Nice catch! This is better, more consistent terminology. Thanks!

@adamvoss adamvoss deleted the clarify-these-are-drafts branch August 26, 2017 14:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants