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

Commit a25a614

Browse files
authored
Merge pull request #237 from handrews/update
Add a status update and more about getting to RFC
2 parents d099352 + f913607 commit a25a614

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

index.md

+13-3
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,19 @@ permalink: /
3737

3838
## Project Status
3939

40-
The JSON Schema project intends to shepherd the Core, Validation, and Hyper-Schema specifications to RFC status. Currently, we are continuing to improve our self-published Internet-Drafts. The next step will be to get the drafts adopted by an IETF Working Group.
40+
### Update as of 9 September 2018
41+
42+
We expect to publish a new round of drafts (Core, Validation, Hyper-Schema, Relative JSON Pointer) before the end of the year. While Hyper-Schema and Relative JSON Pointer are currently expired, they are just as much under active development as Core and Validation (which expire in October).
43+
44+
There are several major PRs that still need to be written for Core and Hyper-Schema. Major changes generally require a minimum two-week review period. Once all major changes are in-place, there is a four-week final review period before publication. For these reasons, the earliest likely date for the next round of drafts is **November 2018**.
45+
46+
Progress on the next set of Internet-Drafts can be tracked on GitHub. The [draft-08](https://github.com/json-schema-org/json-schema-spec/milestone/6) milestone will track the evolving scope of the draft (although see [issue #612](https://github.com/json-schema-org/json-schema-spec/issues/612) for a discussion of whether "draft-08" is the right name for this milestone).
47+
48+
### The Path to Standardization
49+
50+
The JSON Schema project intends to shepherd all four draft series to RFC status. Currently, we are continuing to improve our self-published Internet-Drafts. The next step will be to get the drafts adopted by an IETF Working Group. We are actively investigating how to accomplish this.
51+
52+
If you have experience with such things and would like to help, please contact us!
4153

4254
In the meantime, publication of Internet-Draft documents can be tracked through the IETF:
4355
* [JSON Schema (core)](https://datatracker.ietf.org/doc/draft-handrews-json-schema/)
@@ -49,8 +61,6 @@ Internet-Drafts expire after six months, so our goal is to publish often enough
4961

5062
The intention, particularly for vocabularies such as validation which have been widely implemented, is to remain as compatible as possible from draft to draft. However, these are still drafts, and given a clear enough need validated with the user community, major changes can occur.
5163

52-
Progress on the next set of Internet-Drafts can be tracked on GitHub. The [draft-08](https://github.com/json-schema-org/json-schema-spec/milestone/6) milestone will track the evolving scope of the draft
53-
5464
## Quickstart
5565

5666
The JSON document being validated or described we call the *instance*, and the document containing the description is called the *schema*.

0 commit comments

Comments
 (0)