From ece27e6b90a98d2447a9c94f268f8bd393b1dd7b Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Tue, 13 Dec 2016 11:56:18 -0800 Subject: [PATCH] Wording clarifications in general considerations. These are the leftover bits of Issue #55 and some clarifications requested in a comment on issue #101 that have not already been added in some other PR for some other issue. These specific chagnes were previously approved in #143, but so many other things have changed since #143 that most of it was no longer relevant, so I closed it and started these changes over. In particular, explaining {} and {"not": {}} is no longer needed as they are covered while introducing "true" and "false" schemas in the core specification, so that is no longer repeated in this change. Likewise, the parent/child validation descriptions have been modified in several PRs and no longer has the problems that were previously a concern. --- jsonschema-validation.xml | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 1ea5f54a..714f7ddd 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -184,7 +184,11 @@ -
+
+ + Each JSON Schema validation keyword adds constraints that + an instance must satisfy in order to successfully validate. + Validation keywords that are missing never restrict validation. In some cases, this no-op behavior is identical to a keyword that exists with certain values, @@ -192,13 +196,13 @@
-
- +
- Validation keywords typically operate independent of each other, without affecting each other. + Validation keywords typically operate independently, without + affecting each other's outcomes. - For author convenience, there are some exceptions: + For schema author convenience, there are some exceptions: "additionalProperties", whose behavior is defined in terms of "properties" and "patternProperties"; "additionalItems", whose behavior is defined in terms of "items"; and