You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 2, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: index.md
+10-4Lines changed: 10 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -37,13 +37,19 @@ permalink: /
37
37
38
38
## Project Status
39
39
40
-
### Update as of 16 December 2018
40
+
### Update as of 31 March 2019
41
41
42
-
We expect to publish a new round of drafts (Core, Validation, Hyper-Schema, Relative JSON Pointer) in early 2019, and are actively working on the last few PRs. While the drafts are currently expired, they are still under active development. This project is staffed by volunteers, and life occasionally disregards IETF expiration schedules.
42
+
**You may be wondering _what in the world is going on with this draft?_ The short version is: we are entering the home stretch. There are some ideas for simplifying `$id` that we are considering, and then there will be a final review period for feedback on overall flow and clarity.**
43
43
44
-
The last two major PRs (for modular vocabularies and a standardized output format) are under review and have gotten several rounds of feedback. Once those are complete, there will be a four-week final review period during which we will take feedback on the overall flow and content before publication. Therefore, the likely publication date will be in **January or Feburary 2019**. We had hoped for December but the holiday season and other life events have prevented that.
44
+
As for the long version: The original intent was to publish by the time the previous draft by or at least soon after the current Core and Validation drafts expired on 20 September, 2018. The project is a volunteer project, and one editor was driving most of the large changes in this draft.
45
45
46
-
This draft has taken more time than expected because it tackles deep, long-term issues that have long been a challenge for JSON Schema. This includes building in a formal extensibility mechanism so that we can more easily draw a line to finalize the contents of the Core and Validation specifications.
46
+
Unfortunately, that editor had a lot of Real Life Stuff(tm) to deal with this past year, including changing jobs (which put things on hold from about May through August or so) and then a run of minor health issues (which put things on hold from November through February). Other contributors made progress during those times,
47
+
48
+
As of March, everyone is back to working towards the publication of the draft as schedules permit.
49
+
50
+
We expect to publish a new round of drafts (Core, Validation, Hyper-Schema, Relative JSON Pointer) in the next month or two, and are actively working on the last few PRs. While the drafts are currently expired, they are still under active development. This project is staffed by volunteers, and life occasionally disregards IETF expiration schedules.
51
+
52
+
This draft has also taken more time than expected because it tackles deep, long-term issues that have long been a challenge for JSON Schema. This includes building in a formal extensibility mechanism so that we can more easily draw a line to finalize the contents of the Core and Validation specifications.
47
53
48
54
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).
0 commit comments