output - change property names in declarations

Author: gregsdennis

jsonschema-core.xml

@@ -2759,9 +2759,10 @@
 
                 <section title="Keyword Relative Location">
                     <t>
-                        The relative location of the validating keyword that follows the validation
-                        path.  The value MUST be expressed as a JSON Pointer, and it MUST include
-                        any by-reference applicators such as "$ref" or "$dynamicRef".
+                        The relative location of the validating keyword that follows the path
+                        traversed through the schema.  The value MUST be expressed as a JSON
+                        Pointer, and it MUST include any by-reference applicators such as
+                        "$ref" or "$dynamicRef".
                     </t>
                     <figure>
                         <artwork>
@@ -2775,7 +2776,7 @@
                     due to the inclusion of these by-reference applicator keywords.
                     </t>
                     <t>
-                        The JSON key for this information is "keywordLocation".
+                        The JSON key for this information is "evaluationPath".
                     </t>
                 </section>
 
@@ -2807,7 +2808,7 @@ https://example.com/schemas/common#/$defs/count/minimum
                         over a reference or if the schema does not declare an absolute IRI as its "$id".
                     </t>
                     <t>
-                        The JSON key for this information is "absoluteKeywordLocation".
+                        The JSON key for this information is "schemaLocation".
                     </t>
                 </section>
 
@@ -2841,13 +2842,15 @@ https://example.com/schemas/common#/$defs/count/minimum
 
                 <section title="Nested Results">
                     <t>
-                        For the two hierarchical structures, this property will hold nested errors
-                        and annotations.
+                        For "basic", this property will appear only at the root node and will hold
+                        all errors or annotations in a list.
                     </t>
                     <t>
-                        The JSON key for nested results in failed validations is "errors"; for
-                        successful validations it is "annotations".  Note the plural forms, as
-                        a keyword with nested results can also have a local error or annotation.
+                        For "detailed" and "verbose", this property will hold nested errors
+                        and annotations in a tree structure, mimicking that of the schema.
+                    </t>
+                    <t>
+                        The JSON key for nested results is "nested".
                     </t>
                 </section>
 
@@ -2857,19 +2860,14 @@ https://example.com/schemas/common#/$defs/count/minimum
                 <t>
                     The output MUST be an object containing a boolean property named "valid".  When
                     additional information about the result is required, the output MUST also contain
-                    "errors" or "annotations" as described below.
+                    "nested" as described below.
                     <list>
                         <t>
                             "valid" - a boolean value indicating the overall validation success or
                             failure
                         </t>
                         <t>
-                            "errors" - the collection of errors or annotations produced by a failed
-                            validation
-                        </t>
-                        <t>
-                            "annotations" - the collection of errors or annotations produced by a
-                            successful validation
+                            "nested" - the collection of errors or annotations produced by a keyword
                         </t>
                     </list>
                     For these examples, the following schema and instance will be used.