Settle on "2019-09" rather than "draft/2019-09"

Author: handrews

draft/2019-09/release-notes.md

@@ -104,7 +104,7 @@ yes         | off           | not validated
 
 Obviously, each implementation will behave consistently from schema to schema, although some formats may be supported more thoroughly than others despite the wording in the specification.  However, complex formats are, in practice, supported to different degrees in each implementation.  If they are supported at all.
 
-**Summary of draft/2019-09 behavior**
+**Summary of 2019-09 behavior**
 
 The goal with this draft is to make the default behavior predictable, with the inconsistent behavior as an opt-in feature.  This is not entirely satisfactory, but we feel that it is a good first step to reduce the number of complaints seen around surprising results.  This way, there should at least be fewer surprises.
 

index.md

@@ -7,7 +7,7 @@ permalink: /
 **NEW DRAFT PUBLISHED!**
 {: style="color:red; font-size: 200%; text-align: center;"}
 
-The current version is [draft/2019-09](specification.html)!
+The current version is [2019-09](specification.html)!
 {: style="color:gray; font-size: 150%; text-align: center;"}
 
 **JSON Schema** is a vocabulary that allows you to **annotate** and **validate** JSON documents.
@@ -42,7 +42,11 @@ The current version is [draft/2019-09](specification.html)!
 
 16 September 2019: Draft 2019-09 (formerly known as draft-08) has been published!
 
-See the [Specification page](specification.html) for details.
+The IETF document IDs are of the form `draft-handrews-*-02`.  We are now using dates
+for meta-schemas, which are what implementations should use to determine behavior,
+so we will usually refer to `2019-09` (without the word "draft") on this web site.
+
+See the [Specification page](specification.html) for details about naming and numbering.
 
 ### The Path to Standardization
 

specification-links.md

@@ -208,7 +208,7 @@ For links to the somewhat more readably formatted versions on this web site, and
       </a></small></tt><br>
     </td>
     <td>
-      <tt><small>draft/2019&#8209;09</small></tt>
+      <tt><small>2019&#8209;09</small></tt>
     </td>
     <td>
       Draft 8

specification.md

@@ -11,9 +11,9 @@ title: Specification
 Draft numbering
 ---------------
 
-The latest Internet-Drafts at the IETF are the **draft-handrews-json-schema\*-02** documents, which correspond to the **draft/2019-09** meta-schemas. These were published on **2019-09-16**.
+The latest Internet-Drafts at the IETF are the **draft-handrews-json-schema\*-02** documents, which correspond to the **2019-09** meta-schemas. These were published on **2019-09-16**.
 
-For a full explanation of both the IETF and meta-schema numbering schemes, how they correspond, and why we are now using the date-based `draft/2019-09` rather than `draft-08`, see the [Specification Links](specification-links.html) page.
+For a full explanation of both the IETF and meta-schema numbering schemes, how they correspond, and why we are now using the date-based `2019-09` rather than `draft-08`, see the [Specification Links](specification-links.html) page.
 
 Specification documents
 -----------------------
@@ -41,7 +41,7 @@ Meta-schemas
 
 The meta-schemas are schemas against which other schemas can be validated. They are self-descriptive: the JSON Schema meta-schema validates itself, while the JSON Hyper-Schema meta-schema both validates itself and defines its own "self" link.
 
-The latest meta-schema is **draft/2019**.  For an explanation of the change to date-based identifiers, see the [Specification Links](specification-links.html) page.
+The latest meta-schema is **2019-09**.  For an explanation of the change to date-based identifiers, see the [Specification Links](specification-links.html) page.
 
 _If you are accessing these JSON document links **from a web browser**, you will need to **save the file** then open it as a JSON document.  This is due to limitations with GitHub Pages._
 
@@ -76,11 +76,11 @@ Migrating from older drafts
 The release notes discuss the changes impacting users and implementers:
 
 - JSON Schema Core and Validation
-    - [Draft-07 to Draft 2019-09](draft/2019-09/release-notes.html)
+    - [Draft-07 to 2019-09](draft/2019-09/release-notes.html)
     - [Draft-06 to Draft-07](draft-07/json-schema-release-notes.html)
     - [Draft-04 to Draft-06](draft-06/json-schema-release-notes.html)
 - JSON Hyper-Schema
-    - [Draft-07 to Draft 2019-09](draft/2019-09/release-notes.html#hyper-schema-vocabulary)
+    - [Draft-07 to 2019-09](draft/2019-09/release-notes.html#hyper-schema-vocabulary)
     - [Draft-04 to Draft-07](draft-07/json-hyper-schema-release-notes.html)
     - [Draft-04 to Draft-06](draft-06/json-hyper-schema-release-notes.html)