Valid Against oneOf the Subschemas (XOR)

When you want to ensure that an instance is valid against exactly one of the subschemas, you can use the oneOf keyword.

You can think of oneOf as an XOR operation between subschemas. If more than one subschema is valid, the instance is considered invalid.

Example

Let's add a new property dateOfBirth to the JSON document.

1{
2  "name": "John Doe",
3  "age": 25,
4  "dateOfBirth": "1999-01-01"
5}

Now you want to apply these conditions in the document:

• if age is present, dateOfBirth should not be present, and vice versa.
• both age and dateOfBirth should not be present at the same time.
• if none of them is present, the document should be invalid.

Schema Definition

To apply these conditions you can use oneOf keyword. oneOf ensures that exactly one of the specified subschemas is valid.

We will combine using oneOf and required, to ensure that only one of the properties is present in the JSON document.

1{
2  "type": "object",
3  "properties": {
4    ...
5    "dateOfBirth": { "type": "string", "format": "date" }
6  },
7  "oneOf": [
8    { "required": ["age"] },
9    { "required": ["dateOfBirth"] }
10  ]
11}

Task

1{
2  "name": "John Doe",
3  "age": 25,
4}

You are given a schema for the above JSON document in the side editor. Using oneOf keyword, update schema to ensure that the age follows one of the below conditions:

• Either between 18 and 60 (inclusive) or,
• Greater then 65 (inclusive).