Change logs for draft-handrews-*-02

Author: handrews

jsonschema-core.xml

@@ -3273,9 +3273,22 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
                 <list style="hanging">
                     <t hangText="draft-handrews-json-schema-02">
                         <list style="symbols">
+                            <t>Update to RFC 8359 for JSON specification</t>
                             <t>Moved "definitions" from the Validation specification here as "$defs"</t>
                             <t>Moved applicator keywords from the Validation specification as their own vocabulary</t>
                             <t>Moved the schema form of "dependencies" from the Validation specification as "dependentSchemas"</t>
+                            <t>Formalized annotation collection</t>
+                            <t>Specified recommended output formats</t>
+                            <t>Defined keyword interactions in terms of annotation and assertion results</t>
+                            <t>Added "unevaluatedProperties" and "unevaluatedItems"</t>
+                            <t>Define "$ref" behavior in terms of the assertion, applicator, and annotation model</t>
+                            <t>Allow keywords adjacent to "$ref"</t>
+                            <t>Note undefined behavior for "$ref" targets involving unknown keywords</t>
+                            <t>Add recursive referencing, primarily for meta-schema extension</t>
+                            <t>Add the concept of formal vocabularies, and how they can be recognized through meta-schemas</t>
+                            <t>Additional guidance on initial base URIs beyond network retrieval</t>
+                            <t>Allow "schema" media type parameter for "application/schema+json"</t>
+                            <t>Better explanation of media type parameters and the HTTP Accept header</t>
                         </list>
                     </t>
                     <t hangText="draft-handrews-json-schema-01">

jsonschema-hyperschema.xml

@@ -2752,7 +2752,11 @@ Link: <https://example.com/api/trees/1/nodes/456>; rev="up"
                 <list style="hanging">
                     <t hangText="draft-handrews-json-schema-hyperschema-02">
                         <list style="symbols">
-                            <t></t>
+                            <t>Allow multiple values for "rel"</t>
+                            <t>Clarify that "headerSchema", like "targetHints", should use array values</t>
+                            <t>Clarified link behavior with conditional applicator keywords such as "if"</t>
+                            <t>Added and clarified various examples</t>
+                            <t>Avoid accidentally implying that only POST can be used to create in HTTP</t>
                         </list>
                     </t>
                     <t hangText="draft-handrews-json-schema-hyperschema-01">

jsonschema-validation.xml

@@ -1293,6 +1293,11 @@
                             <t>Moved "definitions" to the core spec as "$defs"</t>
                             <t>Moved applicator keywords to the core spec</t>
                             <t>Renamed the array form of "dependencies" to "dependentRequired", moved the schema form to the core spec</t>
+                            <t>Added "contentSchema" to allow applying a schema to a string-encoded document</t>
+                            <t>Also allow RFC 4648 encodings in "contentEncoding"</t>
+                            <t>Added "minContains" and "maxContains"</t>
+                            <t>Update RFC reference for "hostname" and "idn-hostname"</t>
+                            <t>Add "uuid" and "duration" formats</t>
                         </list>
                     </t>
                     <t hangText="draft-handrews-json-schema-validation-01">