Merge branch 'master' into master

Author: handrews

_data/validator-libraries-modern.yml

@@ -26,13 +26,23 @@
       url: https://github.com/pboettch/json-schema-validator
       draft: [7]
       license: MIT
+- name: Clojure
+  implementations:
+    - name: json-schema
+      url: https://github.com/luposlip/json-schema
+      draft: [7]
+      license: Eclipse Public License 2.0
 - name: Elixir
   implementations:
     - name: Elixir JSON Schema validator
       url: https://github.com/jonasschmidt/ex_json_schema
       draft: [4]
       notes: "Draft-06+ progress: issue [24](https://github.com/jonasschmidt/ex_json_schema/issues/24); branch [multi-draft-support](https://github.com/jonasschmidt/ex_json_schema/tree/multi-draft-support)"
       license: MIT
+    - name: JsonXema
+      url: https://github.com/hrzndhrn/json_xema
+      draft: [7, 6, 4]
+      license: MIT
 - name: Go
   implementations:
     - name: gojsonschema
@@ -61,6 +71,13 @@
       notes:
       draft: [7]
       license: Apache License 2.0
+- name: Kotlin
+  implementations:
+    - name: Medeia-validator
+      url: https://github.com/worldturner/medeia-validator
+      notes: streaming validator for Kotlin and Java clients; works with Jackson and Gson
+      draft: [7, 6, 4]
+      license: Apache License 2.0
 - name: JavaScript
   implementations:
     - name: ajv

draft-07/json-schema-release-notes.md

@@ -23,7 +23,7 @@ more clearly than before.
 
 keyword | change | notes
 ---- | ---- | ----
-[`"$comment"`](json-schema-core.html#rfc.section.10) | added to Core | Intended for notes to schema maintainers, as opposed to [`"description"`](json-schema-validation.html#rfc.section.10.1) which is suitable for display to end users
+[`"$comment"`](json-schema-core.html#rfc.section.9) | added to Core | Intended for notes to schema maintainers, as opposed to [`"description"`](json-schema-validation.html#rfc.section.10.1) which is suitable for display to end users
 [`"if"`, `"then"`, `"else"`](json-schema-validation.html#rfc.section.6.6) | added to Validation | explicit conditional schema evaluation 
 [`"readOnly"`](json-schema-validation.html#rfc.section.10.3) | moved from Hyper-Schema to Validation | not limited to hypermedia environments
 [`"writeOnly"`](json-schema-validation.html#rfc.section.10.3) | added to Validation | general write-only fields, including but not limited to passwords

implementations.md

@@ -264,6 +264,7 @@ _TODO: Sort by draft support._
 -   [JSON Editor](https://json-editor.tangramjs.com) - *An online, schema-aware editor for JSON document*
 -   [Eclipse IDE](https://www.eclipse.org/downloads/eclipse-packages) - *Rich JSON edition supporting schema for instantaneous validation and error reporting, completion, documentation.*
 -   [WebStorm](https://www.jetbrains.com/webstorm/), [IntelliJ IDEA](https://www.jetbrains.com/idea/), and other [JetBrains IDEs](https://www.jetbrains.com/products.html?fromMenu#type=ide) - *Code completion, documentation, and validation for JSON files using JSON Schema*
+-   [JsonDraft](https://jsondraft.com/) - *Tree view JSON and JSON Schema editor online. Create and Save reusable components, Share JSON.*
 
 
 Schema Repositories

index.md

@@ -41,7 +41,7 @@ permalink: /
 
 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.
 
-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 2018**.  We had hoped for December but the holiday season and other life events have prevented that.
+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.
 
 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.
 
@@ -85,6 +85,7 @@ JSON Schema is hypermedia ready, and ideal for annotating your existing JSON-bas
 
 Interested? Check out:
 
+* [Understanding JSON Schema](/understanding-json-schema/)
 * The [specification](./specification.md)
 * [Learning resources](./learn/index.md)
 * the growing list of [JSON (Hyper-)Schema software](./implementations.md)