Resolve conflict

Author: Relequestual

jsonschema-core.xml

@@ -50,7 +50,7 @@
             </address>
         </author>
 
-        <date year="2021"/>
+        <date year="2022"/>
         <workgroup>Internet Engineering Task Force</workgroup>
         <keyword>JSON</keyword>
         <keyword>Schema</keyword>
@@ -1863,6 +1863,11 @@
                             no point in forbidding it, while others have argued that it complicates
                             schema identification and should be forbidden.  Feedback on this
                             topic is encouraged.
+                            After some discussion, we feel that we need to remove the use of
+                            "canonical" in favour of talking about JSON Pointers which reference
+                            across schema resource boundaries as undefined or even forbidden behavior
+                            (https://github.com/json-schema-org/json-schema-spec/issues/937,
+                            https://github.com/json-schema-org/json-schema-spec/issues/1183)
                         </cref>
                     </t>
                     <t>
@@ -3417,6 +3422,18 @@ https://example.com/schemas/common#/$defs/count/minimum
                     </t>
                 </list>
             </t>
+            <t>
+                Note: The fragment part of the URI does not make it canonical or non-canonical,
+                rather, the base URI used (as part of the full URI with any fragment) is what
+                determines the canonical nature of the resulting full URI.
+                <cref>
+                    Multiple "canonical" URIs? We Acknowledge this is potentially confusing, and
+                    direct you to read the CREF located in the
+                    <xref target="embedded">JSON Pointer fragments and embedded schema resources</xref>
+                    section for futher comments.
+                </cref>
+            </t>
+
         </section>
 
         <section title="Manipulating schema documents and references">