Skip to content

Commit f78d397

Browse files
committed
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.
1 parent d951d88 commit f78d397

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

jsonschema-validation.xml

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -191,21 +191,25 @@
191191
</t>
192192
</section>
193193

194-
<section title="Missing keywords">
194+
<section title="Constraints and missing keywords">
195+
<t>
196+
Each JSON Schema validation keyword adds constraints that
197+
an instance must satisfy in order to successfully validate.
198+
</t>
195199
<t>
196200
Validation keywords that are missing never restrict validation.
197201
In some cases, this no-op behavior is identical to a keyword that exists with certain values,
198202
and these values are noted where known.
199203
</t>
200204
</section>
201205

202-
<section title="Linearity">
203-
<!-- I call this "linear" in the same manner e.g. waves are linear, they don't interact with each other -->
206+
<section title="Keyword independence">
204207
<t>
205-
Validation keywords typically operate independent of each other, without affecting each other.
208+
Validation keywords typically operate independently, without
209+
affecting each other's outcomes.
206210
</t>
207211
<t>
208-
For author convenience, there are some exceptions:
212+
For schema author convenience, there are some exceptions:
209213
<list>
210214
<t>"additionalProperties", whose behavior is defined in terms of "properties" and "patternProperties";</t>
211215
<t>"additionalItems", whose behavior is defined in terms of "items"; and</t>

0 commit comments

Comments
 (0)