Cleaning schemas a bit.

[stefalce]

Here are some things I didn't find cool about json schemas:

• type Int is out of the documentation but its schema is still present.
• little endian numbers are not in the specification docs but have schemas.
• the datatype.json schema seems to be unused by the validator (something else may depend on it).
• the latest version of ajv errors because strict mode isn't respected.

The strict mode error doesn't mean much except the schema has something unclear or meaningless. Validation for strict mode or not is identical. For example in the container schema there is a non necessary additionalItems which annoyingly throws an error if strict mode is on.

{
   "type":"array",
   "items":{
      "type":"object",
      "properties":{
         "anon":{
            "type":"boolean"
         },
         "name":{
            
         },
         "type":{
            "$ref":"dataType"
         }
      },
      "oneOf":[
         {
            "required":[
               "anon"
            ]
         },
         {
            "required":[
               "name"
            ]
         }
      ],
      "required":[
         "type"
      ],
      "additionalProperties":false
   },
   "additionalItems":false
}

[stefalce]

I've done more tests, I found a problem in cstring. Since it hasn't 'type: "array"' it validates all non array data as true. Also currently json like ["container"] or [] is considered valid (at least in newer versions), ajv strict mode is useful as it requires to state minItems. Schemas could also be rewritten using the const keyword instead of the single item enum.

[rom1504]

Please propose PRs for fixes