FIX: Declare context definition to be JSON schema, fix validation err…

…ors (#1867)

* fix(schema): Use integer instead of int for type definitions

* fix(schema): Use number instead of float for type definitions

* feat(metaschema): Declare meta.context.context to be JSON schema

* rf(schema): Remove indirection in context description

* chore(schema): Bump schema minor version

src/metaschema.json

@@ -51,7 +51,8 @@
           "additionalProperties": false
         },
         "context": {
-          "type": "object"
+          "description": "The context object is itself JSON schema",
+          "$ref": "http://json-schema.org/draft-07/schema#"
         },
         "expression_tests": {
           "type": "array",

src/schema/README.md

@@ -215,7 +215,7 @@ We see expressions may contain:
 -   Comparison operators such as `==` (equality) or `in` (subfield exists in field)
 -   Functions such as `intersects()`
 
-In fact, the full list of fields is defined in the `meta.context.context` object,
+In fact, the full list of fields is defined in the `meta.context` object,
 which (currently) contains at the top level:
 
 -   `schema`: access to the schema itself

src/schema/SCHEMA_VERSION

@@ -1 +1 @@
-0.9.1-dev
+0.10.0-dev

src/schema/meta/associations.yaml

@@ -1,4 +1,4 @@
-# These rules indicate whether an association (defined in meta.context.context.associations)
+# These rules indicate whether an association (defined in meta.context.associations)
 # applies to a given file. These are hints to allow implementations to avoid unnecessary
 # directory and file reads.
 #