Document required changes to support draft-06 about djv HOT 1 CLOSED

1. Check and change if necesarry if boolean values could be a valid schema

Boolean values are equivalent to the following behaviors:
 true Always passes validation, as if the empty schema {} |  
 false Always fails validation, as if the schema { "not":{} }

2. Optionally check for $schema in the root, and warn about presence in subschemas

The "$schema" keyword SHOULD be used in a root schema. It MUST NOT appear in subschemas.

3. Use $id instead of id

9.2. The "$id" keyword

4. Check other keywords

all core keywords prefixed with "$"

5. Add contains keyword validation

The value of this keyword MUST be a valid JSON Schema.
An array instance is valid against "contains" if at least one of its

6. Add propertyNames keyword validation

If the instance is an object, this keyword validates if every property name in the instance validates against the provided schema. Note the property name that the schema is testing will always be a string.

7. Change exclusiveMaximum, exclusiveMinimum from boolean to number

8. Add const keyword validation

The value of this keyword MAY be of any type, including null. An instance validates successfully against this keyword if its value is equal to the value of the keyword.

9. Add examples keyword validation (warning)

The value of this keyword MUST be an array. There are no restrictions placed on the values within the array.

10. Change format uriref -> uri-reference
11. Add format uri-template
12. Add format json-pointer

13. Allow empty "required" and "dependencies" arrays

14. Fixed "type" reference to primitive types

from djv.