From 1e579ad45cb5675c0b594a9dd90091798a4ac406 Mon Sep 17 00:00:00 2001 From: Austin Wright Date: Wed, 23 Nov 2016 15:40:21 -0700 Subject: [PATCH] Validation: Add note about removal of boolean forms of exclusiveMininum/exclusiveMaximum --- jsonschema-validation.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index fc248b1f..14ae5ee1 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -235,6 +235,9 @@ The value of "exclusiveMaximum" MUST be number, representing an exclusive upper limit for a numeric instance, or a boolean. Schemas SHOULD NOT use the boolean form. + + The boolean form of "exclusiveMaximum" is expected to be removed in the future. + If "exclusiveMaximum" is true, "maximum" is a number, and the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "maximum". Else if "exclusiveMaximum" is a number and the instance is a number, then the instance is valid only if it has a value strictly less than (not equal to) "exclusiveMaximum". @@ -255,6 +258,9 @@ The value of "exclusiveMinimum" MUST be number, representing an exclusive upper limit for a numeric instance, or a boolean. Schemas SHOULD NOT use the boolean form. + + The boolean form of "exclusiveMinimum" is expected to be removed in the future. + If "exclusiveMinimum" is true, "minimum" is a number, and the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "minimum". Else if "exclusiveMinimum" is a number and the instance is a number, then the instance is valid only if it has a value strictly greater than (not equal to) "exclusiveMinimum".