I would like to know if I can define a JSON schema (draft 4) that requires at least one of many properties possible for an object. I already know of `allOf`, `anyOf` and `oneOf` but just can&#39;t figure out how to use them in the way I want.

Here are some example JSON to illustrate :

    // Test Data 1 - Should pass
    {
        
        &quot;email&quot;: &quot;hello@example.com&quot;,
        &quot;name&quot;: &quot;John Doe&quot;
    }
    // Test Data 2 - Should pass
    {
        &quot;id&quot;: 1,
        &quot;name&quot;: &quot;Jane Doe&quot;
    }
    // Test Data 3 - Should pass
    {
        &quot;id&quot;: 1,
        &quot;email&quot;: &quot;hello@example.com&quot;,
        &quot;name&quot;: &quot;John Smith&quot;
    }
    // Test Data 4 - Should fail, invalid email
    {
        &quot;id&quot;: 1,
        &quot;email&quot;: &quot;thisIsNotAnEmail&quot;,
        &quot;name&quot;: &quot;John Smith&quot;
    }

    // Test Data 5 - Should fail, missing one of required properties
    {
        &quot;name&quot;: &quot;John Doe&quot;
    }

I would like to require at least `id` or `email` (also accepting both of them) and still pass validation according to format. Using `oneOf` fails validation if I provide both (test 3), `anyOf` passes validation even if one of them is not valid (test 4)

Here is my schema :

    {
        &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
        &quot;id&quot;: &quot;https://example.com&quot;,
        &quot;properties&quot;: {
            &quot;name&quot;: {
                &quot;type&quot;: &quot;string&quot;
            }
        },
        &quot;anyOf&quot;: [
            {
                &quot;properties&quot;: {
                    &quot;email&quot;: {
                        &quot;type&quot;: &quot;string&quot;,
                        &quot;format&quot;: &quot;email&quot;
                    }
                }
            },
            {
                &quot;properties&quot;: {
                    &quot;id&quot;: {
                        &quot;type&quot;: &quot;integer&quot;
                    }
                }
            }
        ]
    }

Can you help me how to achieve correct validation for my use case ?

How to define a JSON schema that requires at least one of many properties

I&#39;ve seen this [other question](https://stackoverflow.com/q/10809459/940217) but it&#39;s not quite the same, and I feel like my issue is simpler, but just isn&#39;t working.

My data would look like this:

    [
        { &quot;loc&quot;: &quot;a value 1&quot;, &quot;toll&quot; : null, &quot;message&quot; : &quot;message is sometimes null&quot;},
        { &quot;loc&quot;: &quot;a value 2&quot;, &quot;toll&quot; : &quot;toll is sometimes null&quot;, &quot;message&quot; : null}
    ]

I&#39;m wanting to use [AJV](https://github.com/epoberezkin/ajv) for JSON validation in a Node.js project and I&#39;ve tried several schemas to try to describe my data, but I always get this as the error:


    [ { keyword: &#39;type&#39;,
        dataPath: &#39;&#39;,
        schemaPath: &#39;#/type&#39;,
        params: { type: &#39;array&#39; },
        message: &#39;should be array&#39; } ]


The schema I&#39;ve tried looks like this:

    {
      &quot;type&quot;: &quot;array&quot;,
      &quot;items&quot;: {
        &quot;type&quot;: &quot;object&quot;,
        &quot;properties&quot;: {
          &quot;loc&quot;: {
            &quot;type&quot;: &quot;string&quot;
          },
          &quot;toll&quot;: {
            &quot;type&quot;: &quot;string&quot;
          },
          &quot;message&quot;: {
            &quot;type&quot;: &quot;string&quot;
          }
        },
        &quot;required&quot;: [
          &quot;loc&quot;
        ]
      }
    }


I&#39;ve also tried to generate the schema using [this online tool](http://jsonschema.net/#/) but that also doesn&#39;t work, and to verify that that should output the correct result, I&#39;ve tried validating that output against [jsonschemavalidator.net](http://www.jsonschemavalidator.net/), but that also gives me a similar error:

    Found 1 error(s)
     Message:
     Invalid type. Expected Array but got Object.
     Schema path:
     #/type

JSON Schema definition for array of objects

Suppose that I have schema like

    fname: string
    lname: string
    age: string

None of them are required. User can send me any of those attributes above but nothing else that is not declared. They can pass me `fname`, `lname` and `age` or all. But if they pass me all and additional property like `middle_name` the message should be rejected.

How would I define a schema like this?

Json Schema validation: do not allow fields other than those declared in schema

# The `required` field in JSON Schema

JSON Schema features the `properties`, `required` and `additionalProperties` fields. For example,

    {
        &quot;type&quot;: &quot;object&quot;,
        &quot;properties&quot;: {
            &quot;elephant&quot;: {&quot;type&quot;: &quot;string&quot;},
            &quot;giraffe&quot;: {&quot;type&quot;: &quot;string&quot;},
            &quot;polarBear&quot;: {&quot;type&quot;: &quot;string&quot;}
        },
        &quot;required&quot;: [
            &quot;elephant&quot;,
            &quot;giraffe&quot;,
            &quot;polarBear&quot;
        ],
        &quot;additionalProperties&quot;: false
    }

Will validate JSON objects like:

    {
        &quot;elephant&quot;: &quot;Johnny&quot;,
        &quot;giraffe&quot;: &quot;Jimmy&quot;,
        &quot;polarBear&quot;: &quot;George&quot;
    }

But will fail if the list of properties is not *exactly* `elephant, giraffe, polarBear`.

# The problem
I often copy-paste the list of `properties` to the list of `required`, and suffer from annoying bugs when the lists don&#39;t match due to typos and other silly errors.

**Is there a shorter way to denote that all properties are required, without explicitly naming them?**

JSON Schema - require all properties

I want to have a JSON Schema with unknown property names in an array of objects. 
A good example is the meta-data of a web page: 

          &quot;meta&quot;: {
            &quot;type&quot;: &quot;array&quot;,
            &quot;items&quot;: {
              &quot;type&quot;: &quot;object&quot;,
              &quot;properties&quot;: {
                &quot;unknown-attribute-1&quot;: {
                  &quot;type&quot;: &quot;string&quot;
                },
                &quot;unknown-attribute-2&quot;: {
                  &quot;type&quot;: &quot;string&quot;
                },
                ...
              }
            }
          }
Any ideas please, or other way to reach the same?

JSON Schema with unknown property names

I have a POJO class:

    public class Stock {
     int id;
     String name;
     Date date;
    }

Are there any annotations or development framework/API that can convert POJO to JSON schema like below:

    {&quot;id&quot;:
          {				
            &quot;type&quot; : &quot;int&quot;
          },
    &quot;name&quot;:{   
            &quot;type&quot; : &quot;string&quot;
           }
    &quot;date&quot;:{
            &quot;type&quot; : &quot;Date&quot;
          }
    }

And also I can expand the schema to add information like `&quot;Required&quot; : &quot;Yes&quot;`, description for each field, etc., by specifying some annotations or configurations on POJO and can generate JSON Schema like below:
    
    {&quot;id&quot;:
          {				
            &quot;type&quot; : &quot;int&quot;,
            &quot;Required&quot; : &quot;Yes&quot;,
            &quot;format&quot; : &quot;id must not be greater than 99999&quot;,
            &quot;description&quot; : &quot;id of the stock&quot;
          },
    &quot;name&quot;:{   
            &quot;type&quot; : &quot;string&quot;,
            &quot;Required&quot; : &quot;Yes&quot;,
            &quot;format&quot; : &quot;name must not be empty and must be 15-30 characters length&quot;,
            &quot;description&quot; : &quot;name of the stock&quot;
           }
    &quot;date&quot;:{
            &quot;type&quot; : &quot;Date&quot;,
            &quot;Required&quot; : &quot;Yes&quot;,
            &quot;format&quot; : &quot;must be in EST format&quot;,
            &quot;description&quot; : &quot;filing date of the stock&quot;
          }
    }



Generate JSON schema from Java class

We have this json schema [draft](https://datatracker.ietf.org/doc/html/draft-zyp-json-schema-03). I would like to get a sample of my JSON data and generate a skeleton for the JSON schema, that I can rework manually, adding things like description, required, etc, which can not be infered from the specific examples.

For example, from my input `example.json`:

    {
        &quot;foo&quot;: &quot;lorem&quot;, 
        &quot;bar&quot;: &quot;ipsum&quot;
    }
 
I would run my json_schema_generator tool and would get:

    { &quot;foo&quot;: {
        &quot;type&quot; : &quot;string&quot;,
        &quot;required&quot; : true,
        &quot;description&quot; : &quot;unknown&quot;
      },
      &quot;bar&quot;: {
        &quot;type&quot; : &quot;string&quot;,
        &quot;required&quot; : true,
        &quot;description&quot; : &quot;unknown&quot;
      }
    }

This example has been coded manually, so it has maybe errors.
Is there any tool out there which could help me with the conversion JSON -&gt; JSON schema?

Tool to generate JSON schema from JSON data

In jsonSchema you can indicate whether defined fields are mandatory or not using the &quot;required&quot; attribute:

    {
    	&quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
    	&quot;type&quot;: &quot;object&quot;,
    	&quot;properties&quot;: {
    		&quot;header&quot;: {
    			&quot;type&quot;: &quot;object&quot;,
    			&quot;properties&quot;: {
    				&quot;messageName&quot;: {
    					&quot;type&quot;: &quot;string&quot;
    				},
    				&quot;messageVersion&quot;: {
    					&quot;type&quot;: &quot;string&quot;
    				}
    			},
    			&quot;required&quot;: [
    				&quot;messageName&quot;,
    				&quot;messageVersion&quot;
    			]
    		}
    	},
    	&quot;required&quot;: [
    		&quot;header&quot;
    	]
    }

In certain cases, I would like the *messageVersion* field not to be mandatory. Is there any way to make the mandatory-ness of the this field conditional?

jsonSchema attribute conditionally required

Hopefully this isn&#39;t obvious to others because I find the docs at https://json-schema.org/ to be lacking in finer details. I&#39;m getting a block of JSON with some properties that can be `null` or a `string`. How do you specify, in a JSON Schema (to be parsed by Json.NET&#39;s `JsonSchema.Parse` method), that a value can be of type `null` or type `string`?

Is there something simple I&#39;m missing like supplying an array for the type? For example;

    &quot;member_region&quot;: { &quot;type&quot;: [ &quot;string&quot;, null ] } // this throws an exception

Also, does anyone have a better source for JSON Schema details than json-schema.org? Where can I find a larger selection of examples? I don&#39;t want to read a big document/specification to find something that can easily be demonstrated in a 10 line example.

Specify a value can be a string or null with JSON Schema

Is there any naming convention for a json schema file extension? XML has .xsd (XML Schema Definition), what should json schema files have, .jsd (JSON Schema Definition)?

Json Schema file extension

I want to describe with JSON schema array, which should consist of zero or more predefined values. To make it simple, let&#39;s have these possible values: `one`, `two` and `three`. 

Correct arrays (should pass validation):

    []
    [&quot;one&quot;, &quot;one&quot;]
    [&quot;one&quot;, &quot;three&quot;]

Incorrect:

    [&quot;four&quot;]

Now, I know the `&quot;enum&quot;` property should be used, but I can&#39;t find relevant information where to put it.

Option A (under `&quot;items&quot;`):
    
    {
        &quot;type&quot;: &quot;array&quot;,
        &quot;items&quot;: {
            &quot;type&quot;: &quot;string&quot;,
            &quot;enum&quot;: [&quot;one&quot;, &quot;two&quot;, &quot;three&quot;]
        }
    }

Option B:

    {
        &quot;type&quot;: &quot;array&quot;,
        &quot;items&quot;: {
            &quot;type&quot;: &quot;string&quot;
        },
        &quot;enum&quot;: [&quot;one&quot;, &quot;two&quot;, &quot;three&quot;]
    }

Correct way to define array of enums in JSON schema

I am using json-schema and wanting to only allow properties that are declared in this file to pass validation. For instance if a user passes a &quot;name&quot; property in their json object it will fail this schema because &quot;name&quot; is not listed here as a property.

Is there some function similar to &quot;required&quot; that will only allow the listed properties to pass?

    {
    &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
    &quot;title&quot;: &quot;Accounting Resource - Add Item&quot;,
    &quot;type&quot;: &quot;object&quot;,
    &quot;properties&quot;: {
        &quot;itemNumber&quot;: {
            &quot;type&quot;:&quot;string&quot;,
            &quot;minimum&quot;: 3
        },
        &quot;title&quot;: {
            &quot;type&quot;:&quot;string&quot;,
            &quot;minimum&quot;: 5
        },
        &quot;description&quot;: {
            &quot;type&quot;:&quot;string&quot;,
            &quot;minimum&quot;: 5
        }
    },
    &quot;required&quot;: [
        &quot;itemNumber&quot;,
        &quot;title&quot;,
        &quot;description&quot;
    ]
    }

Only allow properties that are declared in JSON schema

I am having trouble coming up with a JSON schema that will validate if the JSON contains either:

- one field only
- another field only
- (one of two other fields) only

but not to match when multiples of those are present.

In my case specifically, I want one of 

- `copyAll`
- `fileNames`
- `matchesFiles` and/or `doesntMatchFiles`

to validate but I don&#39;t want to accept when more than that is there.


Here&#39;s what I&#39;ve got so far:

    {
        &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
        &quot;type&quot;: &quot;object&quot;,
        &quot;required&quot;: [ &quot;unrelatedA&quot; ],
        &quot;properties&quot;: {
    	&quot;unrelatedA&quot;: {
    	    &quot;type&quot;: &quot;string&quot;
    	},
    	&quot;fileNames&quot;: {
    	    &quot;type&quot;: &quot;array&quot;
    	},
    	&quot;copyAll&quot;: {
    	    &quot;type&quot;: &quot;boolean&quot;
    	},
    	&quot;matchesFiles&quot;: {
    	    &quot;type&quot;: &quot;array&quot;
    	},
    	&quot;doesntMatchFiles&quot;: {
    	    &quot;type&quot;: &quot;array&quot;
            }
        },
        &quot;oneOf&quot;: [
             {&quot;required&quot;: [&quot;copyAll&quot;], &quot;not&quot;:{&quot;required&quot;:[&quot;matchesFiles&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;doesntMatchFiles&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;fileNames&quot;]}},
             {&quot;required&quot;: [&quot;fileNames&quot;], &quot;not&quot;:{&quot;required&quot;:[&quot;matchesFiles&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;doesntMatchFiles&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;copyAll&quot;]}},
             {&quot;anyOf&quot;: [
                   {&quot;required&quot;: [&quot;matchesFiles&quot;], &quot;not&quot;:{&quot;required&quot;:[&quot;copyAll&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;fileNames&quot;]}},
                   {&quot;required&quot;: [&quot;doesntMatchFiles&quot;], &quot;not&quot;:{&quot;required&quot;:[&quot;copyAll&quot;]}, &quot;not&quot;:{&quot;required&quot;:[&quot;fileNames&quot;]}}]}
        ]
    } ;

This matches more than I want to. I want this to match all of the following:

    {&quot;copyAll&quot;: true, &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;fileNames&quot;: [&quot;aab&quot;, &quot;cab&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;matchesFiles&quot;: [&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;doesntMatchFiles&quot;: [&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;matchesFiles&quot;: [&quot;a*&quot;], &quot;doesntMatchFiles&quot;: [&quot;*b&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}

but not to match:

    {&quot;copyAll&quot;: true, &quot;matchesFiles&quot;:[&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;fileNames&quot;: [&quot;a&quot;], &quot;matchesFiles&quot;:[&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;copyAll&quot;: true, &quot;doesntMatchFiles&quot;: [&quot;*b&quot;], &quot;matchesFiles&quot;:[&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;fileNames&quot;: [&quot;a&quot;], &quot;matchesFiles&quot;:[&quot;a*&quot;], &quot;unrelatedA&quot;:&quot;xxx&quot;}
    {&quot;unrelatedA&quot;:&quot;xxx&quot;}


I&#39;m guessing there&#39;s something obvious I&#39;m missing - I&#39;d like to know what it is.

How do I require one field or another or (one of two others) but not all of them?

Does anybody know how to generate a [JSON schema][1] from a existing XML schema (XSD file)?
Are there any tools available for this?



  [1]: http://json-schema.org/

Generate Json schema from XML schema (XSD)

I have Swagger API Declaration for services using [Swagger v 1.2](https://github.com/wordnik/swagger-spec/blob/master/versions/1.2.md).

My original feeling about Swagger was that it is very close to JSON Schema (Draft 3 and lately Draft 4) and it shall be relatively easy to generate JSON Schema for request and response objects.

However, while part of the Swagger reuses JSON Schema structures, it turned out that it uses only a subset of features, and it also introduces its own inheritance in Models (using `subTypes` and `discriminator`).

Question: Is there any existing project or piece of code which can **generate usable JSON Schema from Swagger API Declaration**?

Optimally JSON Schema Draft 4 and using Python (but I will be happy to find anything).

How to generate JSON-Schema from Swagger API Declaration

I&#39;m creating a C# WCF Web Service that return a lot of data in a JSON format.
The client is an iPad application that is currently being developped by another team, So I&#39;m working on specifications, without example data.  
Currently the JSON string is created by the .net framework, my Web Service is returning a C# object containing all the information that are then serialized by the framework using DataContracts.

My problem is that the communication specifications only contain JSON Schema files (based on http://json-schema.org/). In order to facilitate the development I&#39;d like to generate the corresponding classes in C# but as the files contain quite a lot of information and there are a dozen of files, I don&#39;t really want to create those classes manually.

So I&#39;m looking for a tool that would allow me either :

 - To generate C# classes from a JSON Schema.
 - To convert a JSON Schema to an XSD file. Then it would be easy to create the classes as there are plenty of tool to generate classes from XSD.

I found a lot of tools to validate a JSON string against a JSON Schema or to generate classes from the JSON string but nothing that seem to help me.  
There is [JSON.NET][1] but it seems to be a library and not a tool and I didn&#39;t found any information about generating classes with it.

So if anyone knows a tools or has an idea on how I could generate those classes (I tried a tool that create the classes in Java but I couldn&#39;t make it work).


  [1]: http://json.codeplex.com/

Generate C# classes from JSON Schema

Suppose we have schema following schema (from tutorial [here][1]): 

    {
      &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
    
      &quot;definitions&quot;: {
        &quot;address&quot;: {
          &quot;type&quot;: &quot;object&quot;,
          &quot;properties&quot;: {
            &quot;street_address&quot;: { &quot;type&quot;: &quot;string&quot; },
            &quot;city&quot;:           { &quot;type&quot;: &quot;string&quot; },
            &quot;state&quot;:          { &quot;type&quot;: &quot;string&quot; }
          },
          &quot;required&quot;: [&quot;street_address&quot;, &quot;city&quot;, &quot;state&quot;]
        }
      },
    
      &quot;type&quot;: &quot;object&quot;,
    
      &quot;properties&quot;: {
        &quot;billing_address&quot;: { &quot;$ref&quot;: &quot;#/definitions/address&quot; },
        &quot;shipping_address&quot;: {
          &quot;allOf&quot;: [
            { &quot;$ref&quot;: &quot;#/definitions/address&quot; },
            { &quot;properties&quot;:
              { &quot;type&quot;: { &quot;enum&quot;: [ &quot;residential&quot;, &quot;business&quot; ] } },
              &quot;required&quot;: [&quot;type&quot;]
            }
          ]
        } 
        
      }
    }

And here is valid instance: 


    {
          &quot;shipping_address&quot;: {
            &quot;street_address&quot;: &quot;1600 Pennsylvania Avenue NW&quot;,
            &quot;city&quot;: &quot;Washington&quot;,
            &quot;state&quot;: &quot;DC&quot;,
            &quot;type&quot;: &quot;business&quot;
          }
    }


I need to ensure that any additional fields for `shipping_address` will be invalid. I know for this purpose exists `additionalProperties` which should be set to &quot;false&quot;. But when I&#39;m setting `&quot;additionalProprties&quot;:false` as in the following: 

    &quot;shipping_address&quot;: {
              &quot;allOf&quot;: [
                { &quot;$ref&quot;: &quot;#/definitions/address&quot; },
                { &quot;properties&quot;:
                  { &quot;type&quot;: { &quot;enum&quot;: [ &quot;residential&quot;, &quot;business&quot; ] } },
                  &quot;required&quot;: [&quot;type&quot;]
                }
              ],
              &quot;additionalProperties&quot;:false
            } 

I get a validation error (checked [here][2]):

    [ {
      &quot;level&quot; : &quot;error&quot;,
      &quot;schema&quot; : {
        &quot;loadingURI&quot; : &quot;#&quot;,
        &quot;pointer&quot; : &quot;/properties/shipping_address&quot;
      },
      &quot;instance&quot; : {
        &quot;pointer&quot; : &quot;/shipping_address&quot;
      },
      &quot;domain&quot; : &quot;validation&quot;,
      &quot;keyword&quot; : &quot;additionalProperties&quot;,
      &quot;message&quot; : &quot;additional properties are not allowed&quot;,
      &quot;unwanted&quot; : [ &quot;city&quot;, &quot;state&quot;, &quot;street_address&quot;, &quot;type&quot; ]
    } ] 

The question is: how should I to limit fields for the `shipping_address` part only?  Thanks in advance.

  [1]: http://spacetelescope.github.io/understanding-json-schema/structuring.html#structuring
  [2]: http://json-schema-validator.herokuapp.com/index.jsp

JSON schema : &quot;allof&quot; with &quot;additionalProperties&quot;

When using [JSON Schema](http://json-schema.org/) and [Open API specification (OAS)](https://github.com/OAI/OpenAPI-Specification) to document a REST API, how do I define the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) property?

How to define UUID property in JSON Schema and Open API (OAS)

I created an API spec from some JSON files and I am trying to test if the files validate against the API spec. 

There are some good tools to validate against JSON Schema, but I did not have chance to find a tool to validate against specs created in the Swagger (tool for creating API schema). The only solution I found is generating a client/server in the Swagger-Editor, it is quite cumbersome.

Is there already an existing tool to validate JSON against Swagger Schema?

Validating JSON against Swagger API schema

I want to make a schema of json file.It&#39;s for an array of products.

The json schema is similar as below:

    {
    &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;,
    &quot;title&quot;: &quot;Product set&quot;,
    &quot;type&quot;: &quot;array&quot;,
    &quot;items&quot;: {
        &quot;title&quot;: &quot;Product&quot;,
        &quot;type&quot;: &quot;object&quot;,
        &quot;properties&quot;: {
            &quot;id&quot;: {
                &quot;description&quot;: &quot;The unique identifier for a product&quot;,
                &quot;type&quot;: &quot;number&quot;
            },
            &quot;name&quot;: {
                &quot;type&quot;: &quot;string&quot;
            },
            &quot;price&quot;: {
                &quot;type&quot;: &quot;number&quot;,
                &quot;minimum&quot;: 0,
                &quot;exclusiveMinimum&quot;: true
            },
            &quot;tags&quot;: {
                &quot;type&quot;: &quot;array&quot;,
                &quot;items&quot;: {
                    &quot;type&quot;: &quot;string&quot;
                },
                &quot;minItems&quot;: 1,
                &quot;uniqueItems&quot;: true
            },
            &quot;dimensions&quot;: {
                &quot;type&quot;: &quot;object&quot;,
                &quot;properties&quot;: {
                    &quot;length&quot;: {&quot;type&quot;: &quot;number&quot;},
                    &quot;width&quot;: {&quot;type&quot;: &quot;number&quot;},
                    &quot;height&quot;: {&quot;type&quot;: &quot;number&quot;}
                },
                &quot;required&quot;: [&quot;length&quot;, &quot;width&quot;, &quot;height&quot;]
            },
            &quot;warehouseLocation&quot;: {
                &quot;description&quot;: &quot;Coordinates of the warehouse with the product&quot;,
                &quot;$ref&quot;: &quot;http://json-schema.org/geo&quot;
            }
        },
        &quot;required&quot;: [&quot;id&quot;, &quot;name&quot;, &quot;price&quot;]
    }
    }

The array should at least one item in it. How can I define the minimum of the array?

Do I need to add the minimun defination?


All Jsonschema Solutions on Gang of Coders

Total of 20 Jsonschema Solutions