Skip to content

Commit 69b313c

Browse files
committed
Clarify examining for vs collecting annotations
You have to look at all subschemas in the cases in question, which may or may not result in actual collection of annotations, depending on the assertion outcomes of the individual subschemas.
1 parent 4050ae4 commit 69b313c

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

jsonschema-core.xml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -656,7 +656,7 @@
656656
subschemas have been evaluated, although in some circumstances evaluation
657657
may be short-circuited due to assertion results. When annotations are
658658
being collected, some assertion result short-circuiting is not possible
659-
due to the need to collect annotations from all subschemas, including
659+
due to the need to examine all subschemas for annotation collection, including
660660
those that cannot further change the assertion result.
661661
</t>
662662
<section title="Keyword Interactions">
@@ -1984,8 +1984,9 @@
19841984
<t>
19851985
An instance validates successfully against this keyword if it validates
19861986
successfully against at least one schema defined by this keyword's value.
1987-
Note that when annotations are being collected, they MUST be collected
1988-
from all subschemas if any subschema validates successfully.
1987+
Note that when annotations are being collected, all subschemas MUST
1988+
be examined so that annotations are collected from each subschema
1989+
that validates successfully.
19891990
</t>
19901991
</section>
19911992

0 commit comments

Comments
 (0)