2704
2704
2705
2705
<section title =" Keyword Relative Location" >
2706
2706
<t >
2707
- The relative location of the validating keyword that follows the validation
2708
- path. The value MUST be expressed as a JSON Pointer, and it MUST include
2709
- any by-reference applicators such as "$ref" or "$dynamicRef".
2707
+ The relative location of the validating keyword that follows the path
2708
+ traversed through the schema. The value MUST be expressed as a JSON
2709
+ Pointer, and it MUST include any by-reference applicators such as
2710
+ "$ref" or "$dynamicRef".
2710
2711
</t >
2711
2712
<figure >
2712
2713
<artwork >
2720
2721
due to the inclusion of these by-reference applicator keywords.
2721
2722
</t >
2722
2723
<t >
2723
- The JSON key for this information is "keywordLocation ".
2724
+ The JSON key for this information is "evaluationPath ".
2724
2725
</t >
2725
2726
</section >
2726
2727
@@ -2752,7 +2753,7 @@ https://example.com/schemas/common#/$defs/count/minimum
2752
2753
over a reference or if the schema does not declare an absolute IRI as its "$id".
2753
2754
</t >
2754
2755
<t >
2755
- The JSON key for this information is "absoluteKeywordLocation ".
2756
+ The JSON key for this information is "schemaLocation ".
2756
2757
</t >
2757
2758
</section >
2758
2759
@@ -2786,13 +2787,15 @@ https://example.com/schemas/common#/$defs/count/minimum
2786
2787
2787
2788
<section title =" Nested Results" >
2788
2789
<t >
2789
- For the two hierarchical structures , this property will hold nested errors
2790
- and annotations.
2790
+ For "basic" , this property will appear only at the root node and will hold
2791
+ all errors or annotations in a list .
2791
2792
</t >
2792
2793
<t >
2793
- The JSON key for nested results in failed validations is "errors"; for
2794
- successful validations it is "annotations". Note the plural forms, as
2795
- a keyword with nested results can also have a local error or annotation.
2794
+ For "detailed" and "verbose", this property will hold nested errors
2795
+ and annotations in a tree structure, mimicking that of the schema.
2796
+ </t >
2797
+ <t >
2798
+ The JSON key for nested results is "nested".
2796
2799
</t >
2797
2800
</section >
2798
2801
@@ -2802,19 +2805,14 @@ https://example.com/schemas/common#/$defs/count/minimum
2802
2805
<t >
2803
2806
The output MUST be an object containing a boolean property named "valid". When
2804
2807
additional information about the result is required, the output MUST also contain
2805
- "errors" or "annotations " as described below.
2808
+ "nested " as described below.
2806
2809
<list >
2807
2810
<t >
2808
2811
"valid" - a boolean value indicating the overall validation success or
2809
2812
failure
2810
2813
</t >
2811
2814
<t >
2812
- "errors" - the collection of errors or annotations produced by a failed
2813
- validation
2814
- </t >
2815
- <t >
2816
- "annotations" - the collection of errors or annotations produced by a
2817
- successful validation
2815
+ "nested" - the collection of errors or annotations produced by a keyword
2818
2816
</t >
2819
2817
</list >
2820
2818
For these examples, the following schema and instance will be used.
0 commit comments