docs: refactored and updated the json schemas (#131)

Author: georgeRobertson

docs/advanced_guidance/json_schemas/contract/components/base_entity.schema.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/base_entity.schema.json",
     "title": "base_entity",
     "description": "A complete entity specification within data ingest",
@@ -10,7 +10,8 @@
             "description": "A mapping of field names to their Python types. These will either be strings representing Python types (if there are no argumements to the type), and field specification objects otherwise",
             "additionalProperties": {
                 "$ref": "field.schema.json"
-            }
+            },
+            "minProperties": 1
         },
         "aliases": {
             "description": "A mapping of field name to allowed field alias",
@@ -26,5 +27,7 @@
                 "type": "string"
             }
         }
-    }
+    },
+    
+    "required": ["fields"]
 }

docs/advanced_guidance/json_schemas/contract/components/contact_error_details.schema.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/contract_error_details.schema.json",
     "title": "base_entity",
     "description": "A mapping of field names to the custom error code and message required if these fields were to fail validation during the data contract phase. For nested fields, these should be specified using struct '.' notation (eg. fieldA.fieldB.fieldC)",

docs/advanced_guidance/json_schemas/contract/components/entity.schema.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/entity.schema.json",
     "title": "entity",
     "description": "A concrete entity specification within data ingest",

docs/advanced_guidance/json_schemas/contract/components/field.schema.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/field.schema.json",
     "title": "field",
     "description": "The type of a field, specified as a bare Python type if there are no argumements, and as an object otherwise. This can also be a reference to a type defined in the dataset",
@@ -9,6 +9,10 @@
         },
         {
             "$ref": "field_specification.schema.json"
+        },
+        {
+            "type": "string",
+            "minLength": 1
         }
     ]
 }

docs/advanced_guidance/json_schemas/contract/components/field_error_detail.schema.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/field_error_detail.schema.json",
     "title": "field_error_detail",
     "description": "The custom details to be used for a field when a validation error is raised during the data contract phase",

docs/advanced_guidance/json_schemas/contract/components/field_error_type.schema copy.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "https://json-schema.org/draft-07/schema",
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
     "$id": "data-ingest:contract/components/field_error_type.schema.json",
     "title": "field_error_detail",
     "description": "The error type for a field when a validation error is raised during the data contract phase",