Better specify the process of validating a Compound Schema Document

Author: Relequestual

jsonschema-core.xml

@@ -1895,9 +1895,10 @@
                 <section title="Validating">
                     <t>
                         Given that a Compound Schema Document may have embedded resources which idenfiy as using different
-                        dialects, it is NOT RECOMMENDED that these documents are validated by applying a meta-schema
+                        dialects, these documents SHOULD NOT be validated by applying a meta-schema
                         to the Compound Schema Document as an instance. It is RECOMMENDED that an alternate
-                        validation process be provided in order to validate Schema Documents.
+                        validation process be provided in order to validate Schema Documents. Each Schema Resource
+                        SHOULD be separately validated against its associated meta-schema.
                         <cref>
                             If you know a schema is what's being validated, you can identify if the schemas
                             is a Compound Schema Document or not, by way of use of "$id", which identifies an
@@ -1906,7 +1907,8 @@
                     </t>
                     <t>
                         A Compound Schema Document in which all embedded resources idenfity as using the same
-                        dialect MAY be validated by applying the appropriate meta-schema.
+                        dialec, or in which "$schema" is omitted and therefore defaults to that of the enclosing resource,
+                        MAY be validated by applying the appropriate meta-schema.
                     </t>
                 </section>
             </section>