Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit cd4f1ad

Browse files
output - change property names in declarations
1 parent 86d5739 commit cd4f1ad

File tree

1 file changed

+15
-17
lines changed

1 file changed

+15
-17
lines changed

‎jsonschema-core.xml‎

Lines changed: 15 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -2704,9 +2704,10 @@
27042704

27052705
<section title="Keyword Relative Location">
27062706
<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".
27102711
</t>
27112712
<figure>
27122713
<artwork>
@@ -2720,7 +2721,7 @@
27202721
due to the inclusion of these by-reference applicator keywords.
27212722
</t>
27222723
<t>
2723-
The JSON key for this information is "keywordLocation".
2724+
The JSON key for this information is "evaluationPath".
27242725
</t>
27252726
</section>
27262727

@@ -2752,7 +2753,7 @@ https://example.com/schemas/common#/$defs/count/minimum
27522753
over a reference or if the schema does not declare an absolute IRI as its "$id".
27532754
</t>
27542755
<t>
2755-
The JSON key for this information is "absoluteKeywordLocation".
2756+
The JSON key for this information is "schemaLocation".
27562757
</t>
27572758
</section>
27582759

@@ -2786,13 +2787,15 @@ https://example.com/schemas/common#/$defs/count/minimum
27862787

27872788
<section title="Nested Results">
27882789
<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.
27912792
</t>
27922793
<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".
27962799
</t>
27972800
</section>
27982801

@@ -2802,19 +2805,14 @@ https://example.com/schemas/common#/$defs/count/minimum
28022805
<t>
28032806
The output MUST be an object containing a boolean property named "valid". When
28042807
additional information about the result is required, the output MUST also contain
2805-
"errors" or "annotations" as described below.
2808+
"nested" as described below.
28062809
<list>
28072810
<t>
28082811
"valid" - a boolean value indicating the overall validation success or
28092812
failure
28102813
</t>
28112814
<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
28182816
</t>
28192817
</list>
28202818
For these examples, the following schema and instance will be used.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /