bumping version number to 1.8.0; updating readme with draft-7 docs

Author: erosb

README.md

@@ -6,18 +6,19 @@
 * [Maven installation](#maven-installation)
   * [Java7 version](#java7-version)
 * [Quickstart](#quickstart)
-* [Draft 4 or Draft 6?](#draft-4-or-draft-6)
+* [Draft 4 or Draft 6 or Draft 7?](#draft-4-or-draft-6-or-draft-7)
 * [Investigating failures](#investigating-failures)
   * [JSON report of the failures](#json-report-of-the-failures)
 * [Eary failure mode](#early-failure-mode)
 * [Default values](#default-values)
+* [readOnly and writeOnly context](#readonly-and-writeonly-context)
 * [Format validators](#format-validators)
   * [Example](#example)
 * [Resolution scopes](#resolution-scopes)
 
 <a href="http://jetbrains.com"><img src="./jetbrains-logo.png" /></a> Supported by JetBrains.
 
-This project is an implementation of the JSON Schema [Draft v4][draft-zyp-json-schema-04] and [Draft v6](https://tools.ietf.org/html/draft-wright-json-schema-01) specifications.
+This project is an implementation of the JSON Schema [Draft v4][draft-zyp-json-schema-04], [Draft v6](https://tools.ietf.org/html/draft-wright-json-schema-01) and [Draft v7](https://tools.ietf.org/html/draft-handrews-json-schema-validation-00) specifications.
 It uses the [org.json API](http://stleary.github.io/JSON-java/) (created by Douglas Crockford) for representing JSON data.
 
 # When to use this library?
@@ -27,7 +28,7 @@ But - as you may have already discovered - there is also an [other Java implemen
 of the JSON Schema specification. So here are some advices about which one to use:
  * if you use Jackson to handle JSON in Java code, then [java-json-tools/json-schema-validator] is obviously a better choice, since it uses Jackson
  * if you want to use the [org.json API](http://stleary.github.io/JSON-java/) then this library is the better choice
- * if you need JSON Schema Draft 6 support, then you need this library.
+ * if you need JSON Schema Draft 6 / 7 support, then you need this library.
  * if you want to use anything else for handling JSON (like GSON or javax.json), then you are in a little trouble, since
 currently there is no schema validation library backed by these libraries. It means that you will have to parse the JSON
 twice: once for the schema validator, and once for your own processing. In a case like that, this library is probably still
@@ -42,7 +43,7 @@ Add the JitPack repository and the dependency to your `pom.xml` as follows:
 <dependency>
     <groupId>com.github.everit-org.json-schema</groupId>
     <artifactId>org.everit.json.schema</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 ...
 <repositories>
@@ -83,24 +84,25 @@ try (InputStream inputStream = getClass().getResourceAsStream("/path/to/your/sch
 }
 ```
 
-## Draft 4 or draft 6?
+## Draft 4, Draft 6 or Draft 7?
 
-JSON Schema has currently 3 major releases, Draft 3, Draft 4 and Draft 6. This library implements the 2 newer ones, you can have a quick look at the differences [here](https://github.com/json-schema-org/json-schema-spec/wiki/FAQ:-draft-wright-json-schema%5B-validation%5D-01#changes).
+JSON Schema has currently 4 major releases, Draft 3, Draft 4, Draft 6 and Draft 7. This library implements the 3 newer ones, you can have a quick look at the differences [here](https://github.com/json-schema-org/json-schema-spec/wiki/FAQ:-draft-wright-json-schema%5B-validation%5D-01#changes) and [here](https://tools.ietf.org/html/draft-handrews-json-schema-validation-00#appendix-B).
 Since the two versions have a number of differences - and draft 6 is not backwards-compatible with draft 4 - it is good to know which version will you use.   
 
 The best way to denote the JSON Schema version you want to use is to include its meta-schema URL in the document root with the `"$schema"` key. This is a common notation, facilitated by the library to determine which version should be used.
 
 Quick reference:
   * if there is `"$schema": "http://json-schema.org/draft-04/schema"` in the schema root, then Draft 4 will be used
   * if there is `"$schema": "http://json-schema.org/draft-06/schema"` in the schema root, then Draft 6 will be used
+  * if there is `"$schema": "http://json-schema.org/draft-07/schema"` in the schema root, then Draft 7 will be used
   * if none of these is found then Draft 4 will be assumed as default
 
-If you want to specify the meta-schema version explicitly then you can change the default from Draft 4 to Draft 6 by configuring the loader this way:
+If you want to specify the meta-schema version explicitly then you can change the default from Draft 4 to Draft 6 / 7 by configuring the loader this way:
 
 ```java
 SchemaLoader loader = SchemaLoader.builder()
                 .schemaJson(yourSchemaJSON)
-                .draftV6Support()
+                .draftV6Support() // or draftV7Support()
                 .build();
 Schema schema = loader.load().build();
 ```
@@ -218,7 +220,7 @@ detailed error report, but under some circumstances it is more appropriate to st
 checking the rest of the JSON document. To toggle this fast-failing validation mode
  * you have to explicitly build a `Validator` instance for your schema instead of calling `Schema#validate(input)`
  * you have to call the `failEarly()` method of `ValidatorBuilder`
- 
+
 Example:
 
 ```java
@@ -267,24 +269,62 @@ System.out.println(input.get("prop")); // prints 1
 If there are some properties missing from `input` which have `"default"` values in the schema, then they will be set by the validator
 during validation.
 
-## Format validators
+## readOnly and writeOnly context
 
+The library supports the `readOnly` and `writeOnly` keywords which first appeared in Draft 7. If you want to utilize this feature, then before validation you need to tell the vaildator if the
+validation happens in read or write context. Example:
 
-Starting from version `1.2.0` the library supports the [`"format"` keyword][draft-fge-json-schema-validation-00 format]
-(which is an optional part of the specification), so you can use the following formats in the schemas:
+schema.json:
+
+```json
+{
+   "properties": {
+     "id": {
+       "type": "number",
+       "readOnly": true
+     }
+   }  
+}
+```
 
- * date-time
- * email
- * hostname
- * ipv4
- * ipv6
- * uri
+Validation code snippet:
+```java
 
-If you use the library in Draft 6 mode, then the followings are also supported:
+Validator validator = Validator.builder()
+                .readWriteContext(ReadWriteContext.WRITE)
+                .build();
+
+validator.performValidation(schema, new JSONObject("{\"id\":42}"));
+```
+
+In this case we told the validator that the validation happens in `WRITE` context, and in the input JSON object the `"id"` property appears, which is marked as `"readOnly"` in the schema, therefore this call will throw a `ValidationException`.
+
+## Format validators
+
+
+Starting from version `1.2.0` the library supports the [`"format"` keyword][draft-fge-json-schema-validation-00 format]
+(which is an optional part of the specification).
+
+The supported formats vary depending on the schema spec version you use (since the standard formats were introduced in different versions on the validation specification).
+
+Here is a compatibility table of te supported standard formats:
+
+|                      | Draft 4            | Draft 6            | Draft 7            |
+----------------------------------------------------------------------------
+| date-time            | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| email                | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| hostname             | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| ipv4                 | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| ipv6                 | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| uri                  | :white_check_mark: | :white_check_mark: | :white_check_mark: |
+| uri-reference        |                    | :white_check_mark: | :white_check_mark: |
+| uri-template         |                    | :white_check_mark: | :white_check_mark: |
+| json-pointer         |                    | :white_check_mark: | :white_check_mark: |
+| date                 |                    |                    | :white_check_mark: |
+| time                 |                    |                    | :white_check_mark: |
+| regex                |                    |                    | :white_check_mark: |
+| relative-json-pointer|                    |                    | :white_check_mark: |
 
- * uri-reference
- * uri-template
- * json-pointer  
 
 The library also supports adding custom format validators. To use a custom validator basically you have to
 

core/pom.xml

@@ -21,7 +21,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>org.everit.json</groupId>
     <artifactId>org.everit.json.schema</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
     <packaging>bundle</packaging>
     <properties>
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

pom.xml

@@ -6,7 +6,7 @@
 
     <groupId>org.everit.json</groupId>
     <artifactId>org.everit.json.schema.parent</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 
     <packaging>pom</packaging>
 

tests/pom.xml

@@ -24,7 +24,7 @@
     <parent>
         <groupId>org.everit.json</groupId>
         <artifactId>org.everit.json.schema.parent</artifactId>
-        <version>1.7.0</version>
+        <version>1.8.0</version>
     </parent>
 
     <artifactId>org.everit.json.schema.tests</artifactId>