exclusiveMaximum : Number
exclusiveMaximum
NumberValidation succeeds if the numeric instance is less 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 | Draft 7 | 
| Changed In | Draft 6 | 
| Introduced In | Draft 3 | 
| Vocabulary | Validation | 
| Specification | https://json-schema.org/draft-07/draft-handrews-json-schema-validation-01#rfc.section.6.2.3 | 
| Metaschema | http://json-schema.org/draft-07/schema# | 
| Official Tests | draft7/exclusiveMaximum.json | 
| Default | None | 
| Annotation | None | 
| Affected By | None | 
| Affects | None | 
| Also See | 
                  
  | 
              
The exclusiveMaximum keyword restricts number instances to be strictly less
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": "http://json-schema.org/draft-07/schema#",
  "exclusiveMaximum": 10
}9.9910.0011110.010"100000"{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "exclusiveMaximum": -2.1
}-2.2-3-2.01-2-2.1"100000"