Update work-in-progress index for "draft-08"

and also link to it from the front page.

No documents in this commit, they will be in the next one.

Author: handrews

index.md

@@ -7,6 +7,9 @@ permalink: /
 ***The current version is [draft-07](specification.html)!***
 {: style="color:gray; font-size: 150%; text-align: center;"}
 
+***The next draft work-in-progres is [in final review](work-in-progress/)!***
+{: style="color:red; font-size: 150%; text-align: center;"}
+
 **JSON Schema** is a vocabulary that allows you to **annotate** and **validate** JSON documents.
 
 
@@ -37,21 +40,13 @@ permalink: /
 
 ## Project Status
 
-### Update as of 31 March 2019
-
-**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.**
-
-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.
-
-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,
-
-As of March, everyone is back to working towards the publication of the draft as schedules permit.
+### Update as of 27 May 2019
 
-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.
+**The forthcoming draft is in [final review](work-in-progress/).**
 
 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.
 
-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).
+Additionally, numerous life issues reduced the availability of key contributors during the process.
 
 ### The Path to Standardization
 

work-in-progress/index.md

@@ -7,7 +7,116 @@ permalink: /work-in-progress
 * TOC
 {:toc}
 
-**draft-07** (a.k.a. **draft-handrews-\*-00**) has been released!
-Please see the [specification](../documentation.md) page for details.
+## The Next Draft (by whatever name) Is Ready for Final Pre-Publication Review!
+
+The forthcoming draft is now feature-frozen and entering the final four-week feedback
+period before publication.  This final review will last from May 27th to June 24th, 2019.
+
+The timeline may be compressed if, after at least two weeks, there is a clear consensus that
+the drafts are solid and it would be best to publish sooner rather than later.
+
+The following sorts of feedback are particularly desired:
+
+* Clarity, readability, and accessibility to new readers
+* Contradictions, inconsistencies and other bugs
+* Anything so egregious that implementation would be infeasible or impossible
+
+New features or major changes to existing features will be deferred to a future draft,
+and work on the next draft will begin immediately after this one is published.
+
+## What Is This Draft Called, Anyway?
+
+We have typically referred to this as `draft-08`, following our own convention of just
+incrementing the draft number for meta-schemas regardless of the IETF identifier.
+
+However, this is frowned upon by the IETF and has in fact been a source of confusion.
+It worked well up to and including `draft-04`, as even after the split into multiple
+documents, `draft-zyp-json-schema-04` (the core spec) at least ended in `-04`!
+Unfortnately, after that point, the numbers stopped matching in any way.
+
+Assuming this new draft gets published more or less as presented in this WIP,
+and by the end of June, it will be:
+
+* IETF identifiers: `draft-handrews-*-02`
+* Meta-schema identifiers: `draft/2019-06`
+
+Meta-schemas will now be identified with dates, which can be correlated with the publication
+and expiration dates of the IETF documents.  This will make it more clear when a bugfix
+meta-schema is produced, and also make it more obvious that the IETF and meta-schema identifiers
+are not expected to match exactly.
+
+## Pre-Built Review Documents
+
+To encourage as many reviewers as possible, pre-built documents are available.  These may
+slightly lag those in the GitHub repository, although all efforts will be made to keep them
+in sync during the review period.  After the review period, these will be removed.  In particular,
+using "WORK IN PROGRESS" meta-schemas **is not allowed** and **will break** as soon as the files
+are moved to their permanent homes.
+
+### Specifications:
+
+As always, these are the actual normative documents:
+
+_**NOTE:** Links to meta-schemas and among the drafts will not work correctly in these review copies._
+
+* [WIP: JSON Schema (core)](/work-in-progress/WIP-jsonschema-core.html)
+* [WIP: JSON Schema Validation](/work-in-progress/WIP-jsonschema-validation.html)
+* [WIP: JSON Schema Hyper-Schema](/work-in-progress/WIP-jsonschema-hyperschema.html)
+* [WIP: Relative JSON Pointer](/work-in-progress/WIP-relative-json-pointer.html)
+
+### General use meta-schemas:
+
+These are the traditional non-normative meta-schemas, which serve the same purpose as
+in previous drafts, although their internal structure is different.
+
+_**NOTE:** when published, the `.json` will be removed from the final URI_
+
+* [WIP: schema.json](/work-in-progress/WIP-schema.json) (core and validation)
+* [WIP: links.json](/work-in-progress/WIP-links.json) (individual link description object)
+* [WIP: hyper-schema.json](/work-in-progress/WIP-hyper-schema.json) (hyper-schema, references schema and links)
+
+### Single-vocabulary meta-schemas:
+
+The new draft introduces the concept of modular vocabularies.  Most schema authors will not directly
+reference these meta-schemas.  Instead, they are combined in useful ways by the general use meta-schemas.
+However, those wishing to build custom meta-schemas may find it useful to choose different subsets of
+the standard keywords depending on the custom meta-schema's intended purpose.
+
+_**NOTE:** when published, the `.json` will be removed from the final URI_
+
+* [WIP: meta/core.json](/work-in-progress/meta/WIP-core.json) (core keywords, from the core spec)
+* [WIP: meta/applicator.json](/work-in-progress/meta/WIP-applicator.json) (applicator keywords, from the core spec)
+* [WIP: meta/validation.json](/work-in-progress/meta/WIP-validation.json) (validation assertions, from the validation spec)
+* [WIP: meta/meta-data.json](/work-in-progress/meta/WIP-meta-data.json) (meta-data annotations, from the validation spec)
+* [WIP: meta/format.json](/work-in-progress/meta/WIP-format.json) (the format keyword, from the validation spec)
+* [WIP: meta/content.json](/work-in-progress/meta/WIP-content.json) (content keywords, from the validation spec)
+* [WIP: meta/hyper-schema.json](/work-in-progress/meta/WIP-hyper-schema.json) (hyper-schema keywords, from the hyper-shema spec)
+
+### Output schema:
+
+The new draft also introduces recommended output formats for reporting errors and annotations.
+
+_**NOTE:** when published, the `.json` will be removed from the final URI_
+
+* [WIP: schema.json](/work-in-progress/output/WIP-schema.json) (schema for recommended output formats)
+* [WIP: verbose-example.json](/work-in-progress/output/WIP-verbose-example.json) (example of the most verbose output format)
+* [WIP: hyper-schema.json](/work-in-progress/output/WIP-hyper-schema.json) (format used by the proposed hyper-schema test suite, and used in examples in the specification)
+
+## Providing Feedback and Tracking Progress in GitHub
+
+We are **particularly interested** in feedback on whether the wording and concepts is an
+improvement in terms of how easy it is to understand and learn the specifications.
+
+Note that _all drafts have Changelog appendicies_, for a concise list of notable changes.
+
+* The active sources are on the
+["master" branch of json-schema-org/json-schema-spec](https://github.com/json-schema-org/json-schema-spec)
+* The [draft-08 milestone](https://github.com/json-schema-org/json-schema-spec/milestone/6)
+  tracks all issues and PRs for this draft
+  _(yes, it's still called draft-08 here because GitHub doesn't handle milestone renames well)_
+* Check the [open PRs](https://github.com/json-schema-org/json-schema-spec/pulls)
+  to see what is already being changed from other feedback
+* [file an issue](https://github.com/json-schema-org/json-schema-spec/issues/new?milestone=draft-08)
+  or [join us on Slack](https://join.slack.com/t/json-schema/shared_invite/enQtMjk1NDcyNDI2NTAwLTcyYmYwMjdmMmUxNzZjYzIxNGU2YjdkNzdlOGZiNjIwNDI2M2Y3NmRkYjA4YmMwODMwYjgyOTFlNWZjZjAyNjg) to submit feedback
+  _(technically there is also a [mailing list](https://groups.google.com/forum/#!forum/json-schema) but it gets very little traffic and is not closely monitored)_
 
-This page will remain empty until draft-08 enters the final pre-publication review period.