exclusiveMinimum : Number
exclusiveMinimum
NumberValidation succeeds if the numeric instance is greater than the given number.
| Value |
This keyword must be set to a number
Hint: Use the jsonschema metaschema and jsonschema lint commands to catch keywords set to invalid values
|
|---|---|
| Kind | Assertion |
| Applies To | Number |
| Base Dialect | 2019-09 |
| Changed In | Draft 6 |
| Introduced In | Draft 3 |
| Vocabulary | Validation |
| Specification | https://json-schema.org/draft/2019-09/draft-handrews-json-schema-validation-02#rfc.section.6.2.5 |
| Metaschema | https://json-schema.org/draft/2019-09/meta/validation |
| Official Tests | draft2019-09/exclusiveMinimum.json |
| Default | None |
| Annotation | None |
| Affected By | None |
| Affects | None |
| Also See |
|
The exclusiveMinimum keyword restricts number instances to be strictly
greater than the given number.
Remember that JSON Schema is a constraint-driven language.
Therefore, non-number instances successfully validate against this
keyword. If needed, make use of the type keyword to constraint
the accepted type accordingly.
Examples
{
"$schema": "https://json-schema.org/draft/2019-09/schema",
"exclusiveMinimum": 10
}10.1119.9910.010"100000"{
"$schema": "https://json-schema.org/draft/2019-09/schema",
"exclusiveMinimum": -2.1
}-2.09-2-2.11-3-2.1"100000"