Skip to content

Commit 6ca91fa

Browse files
committed
Attempt to justify and explain unevaluated keyword phrasing
Fixes #998
1 parent e8d37e1 commit 6ca91fa

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

jsonschema-core.xml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2576,6 +2576,14 @@
25762576
to contribute to whether or not the item or property has been evaluated.
25772577
Only successful evaluations are considered.
25782578
</t>
2579+
<t>
2580+
If an item in an array or an object property is "successfully evaluated", it
2581+
is logically considered to be valid in terms of the representation of the
2582+
object or array that's expected. For example if a subschema represents a car,
2583+
which requires between 2-4 wheeles, and the value of "wheeles" is 6, the instance
2584+
object is not "evaluated" to be a car, and the "wheeles" property is considerd
2585+
"unevaluated (successfully as a known thing)", and does not retain any annotations.
2586+
</t>
25792587
<t>
25802588
Recall that adjacent keywords are keywords within the same schema object,
25812589
and that the dynamic-scope subschemas include reference targets as well as

0 commit comments

Comments
 (0)