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
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,14 +40,20 @@ permalink: /
40
40
41
41
## Project Status
42
42
43
-
### Update as of 27 May 2019
43
+
### Update as of 26 Aug 2019
44
44
45
-
**The forthcoming draft is in [final review](work-in-progress).**
45
+
***All PRs from our final review feedback for the next draft have been posted!***
46
+
47
+
_The draft will be published as soon as we have sufficient reviews from the spec team and/or implementation owners. As this is summer vacation season, that may still take a few weeks._
46
48
47
49
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.
48
50
49
51
Additionally, numerous life issues reduced the availability of key contributors during the process.
50
52
53
+
And finally, the feedback process demonstrated that our first attempt at a publishable draft needed substantial additional work, adding another few months to the timeline.
54
+
55
+
Since the most intractable problems are all addressed to one degree or another in this draft, we do not anticipate future drafts taking so long.
56
+
51
57
### The Path to Standardization
52
58
53
59
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.
Copy file name to clipboardExpand all lines: work-in-progress/index.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,20 +7,17 @@ permalink: /work-in-progress
7
7
* TOC
8
8
{:toc}
9
9
10
-
## The Next Draft (by whatever name) Is Ready for Final Pre-Publication Review!
10
+
## The Next Draft (by whatever name) Is Approaching Publication!
11
11
12
-
The forthcoming draft is now feature-frozen and has gone through the initial four-week pre-publication review period.
12
+
The draft is feature-complete, including late additions based on our first try at a final review period several months ago.
13
13
14
-
_**UPDATE: July 28th, 2019** We continue to incorporate feedback and clarify sections of the new draft. We expect to finally publish the draft during August._
14
+
We will be working on a more user-friendly and extensive guide to the new draft shortly.
15
15
16
-
The following sorts of feedback are particularly desired:
16
+
### Update as of 26 Aug 2019
17
17
18
-
* Clarity, readability, and accessibility to new readers
19
-
* Contradictions, inconsistencies and other bugs
20
-
* Anything so egregious that implementation would be infeasible or impossible
18
+
***All PRs from our final review feedback have been posted.***
21
19
22
-
New features or major changes to existing features will be deferred to a future draft,
23
-
and work on the next draft will begin immediately after this one is published.
20
+
_The draft will be published as soon as we have sufficient reviews from the spec team and/or implementation owners. As this is summer vacation season, that may still take a few weeks._
0 commit comments