Merge branch 'master' into issue-1019-known-vocabs-are-always-processed

Author: Relequestual

jsonschema-core.xml

@@ -45,13 +45,8 @@
 
         <author fullname="Greg Dennis" initials="G" surname="Dennis">
             <address>
-                <postal>
-                    <street></street>
-                    <city>Auckland</city>
-                    <region></region>
-                    <country>NZ</country>
-                </postal>
                 <email>[email protected]</email>
+                <uri>https://github.com/gregsdennis</uri>
             </address>
         </author>
 
@@ -103,7 +98,8 @@
                 This specification defines JSON Schema core terminology and mechanisms, including
                 pointing to another JSON Schema by reference,
                 dereferencing a JSON Schema reference,
-                specifying the vocabulary being used,
+                specifying the dialect being used,
+                specifying a dialect's vocabulary requirements,
                 and defining the expected output.
             </t>
             <t>
@@ -146,9 +142,10 @@
                 some sort of condition.
             </t>
             <t>
-                To facilitate re-use, keywords can be organized into vocabularies.  A vocabulary
+                To facilitate re-use, keywords can be organized into vocabularies. A vocabulary
                 consists of a list of keywords, together with their syntax and semantics.
-                A set of vocabularies identified by a meta-schema is known as a dialect.
+                A dialect is defined as a set of vocabularies and their required support
+                identified in a meta-schema.
             </t>
             <t>
                 JSON Schema can be extended either by defining additional vocabularies,
@@ -1198,9 +1195,10 @@
                         vocabularies available for use in schemas described by that meta-schema.
                         It is also used to indicate whether each vocabulary is required or optional,
                         in the sense that an implementation MUST understand the required vocabularies
-                        in order to successfully process the schema.  Any vocabulary that is
-                        understood by the implementation MUST be processed in a manner consistent
-                        with the semantic definitions contained within the vocabulary.
+                        in order to successfully process the schema. Together, this information forms
+                        a dialect. Any vocabulary that is understood by the implementation MUST be
+                        processed in a manner consistent with the semantic definitions contained
+                        within the vocabulary.
                     </t>
                     <t>
                         The value of this keyword MUST be an object.  The property names in the

jsonschema-validation.xml

@@ -1350,6 +1350,9 @@
                     <author initials="B." surname="Hutton">
                         <organization/>
                     </author>
+                    <author initials="G." surname="Dennis">
+                        <organization/>
+                    </author>
                     <date year="2020" month="November"/>
                 </front>
                 <seriesInfo name="Internet-Draft" value="draft-bhutton-json-schema-00" />