You have defined your schema correctly, except that it doesn’t match the data you say you are validating. If you change the property names to match the schema, you still have one issue. If you want to allow “toll” and “message” to be null, you can do the following. { “type”: “array”, “items”: { “type”: … Read more
No, it is not possible. From the docs, json-schema: …a JSON based format for defining the structure of JSON data. It is quite limited for making data values validation because it is not the purpose of the standard. Many people have asked this before because it is common to request a kind of “unique Id” … Read more
In JSON Schemas, you can either put a schema per file and then access them using their URL (where you stored them), or a big schema with id tags. Here is for one big file: { “id”: “#root”, “properties”: { “author”: { “id”: “#author”, “properties”: { “first_name”: { “type”: “string” }, “last_name”: { “type”: “string” … Read more
To test a string value (not a property name) against a RegEx, you should use the “pattern” keyword: { “type”: “object”, “properties”: { “progBinaryName”: { “type”: “string”, “pattern”: “^[A-Za-z0-9 -_]+_Prog\\.(exe|EXE)$” } } } P.S. – if you want the pattern to match the key for the property (not the value), then you should use “patternProperties” … Read more
I asked this same question on the JSON schema google group, and it was answered quickly. User fge asked that I post his response here: Hello, The current specification is draft v4, not draft v3. More specifically, the validation specification is here: https://datatracker.ietf.org/doc/html/draft-fge-json-schema-validation-00 The web site is not up to date, I don’t know why… … Read more
So far the closest thing I’ve been able to find is warlock, which advertises this workflow: Build your schema >>> schema = { ‘name’: ‘Country’, ‘properties’: { ‘name’: {‘type’: ‘string’}, ‘abbreviation’: {‘type’: ‘string’}, }, ‘additionalProperties’: False, } Create a model >>> import warlock >>> Country = warlock.model_factory(schema) Create an object using your model >>> sweden … Read more
additionalProperties is your keyword: { “type” : “object”, “additionalProperties” : { “type” : “object”, “required” : [ “age”, “gender” ], “properties” : { “age” : { “type” : “string” }, “gender” : { “type” : “string” } } } } additionalProperties can have the following values with different meanings: “additionalProperties”: false No more properties are … Read more
JSON Schema doesn’t use an object oriented paradigm, so concepts like inheritance don’t translate well. JSON Schema is a collection of constraints. It’s subtractive rather than additive like most people are used to. This means that given an empty schema, the set of valid JSON documents is the set of all JSON documents. As you … Read more
What you want to do can be achieved using the not keyword. If the not schema validates, the parent schema will not validate. { “type”: “object”, “properties”: { “x”: { “type”: “integer” } }, “required”: [ “x” ], “not”: { “required”: [ “z” ] } }
This is definitely possible with version 3 of the draft. Since you have a complete list of allowed countries, then you could do something like this: { “type”: [ { “title”: “New Zealand (no postcode)”, “type”: “object”, “properties”: { “country”: {“enum”: [“NZ”, “NZL”, “NEW ZEALAND”]} } }, { “title”: “Other countries (require postcode)”, “type”: “object”, … Read more