Skip to content

Commit 8f10646

Browse files
committed
Resolve conflict
2 parents 9ee6ee4 + db65da8 commit 8f10646

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

jsonschema-core.xml

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@
5050
</address>
5151
</author>
5252

53-
<date year="2021"/>
53+
<date year="2022"/>
5454
<workgroup>Internet Engineering Task Force</workgroup>
5555
<keyword>JSON</keyword>
5656
<keyword>Schema</keyword>
@@ -1863,6 +1863,11 @@
18631863
no point in forbidding it, while others have argued that it complicates
18641864
schema identification and should be forbidden. Feedback on this
18651865
topic is encouraged.
1866+
After some discussion, we feel that we need to remove the use of
1867+
"canonical" in favour of talking about JSON Pointers which reference
1868+
across schema resource boundaries as undefined or even forbidden behavior
1869+
(https://github.com/json-schema-org/json-schema-spec/issues/937,
1870+
https://github.com/json-schema-org/json-schema-spec/issues/1183)
18661871
</cref>
18671872
</t>
18681873
<t>
@@ -3417,6 +3422,18 @@ https://example.com/schemas/common#/$defs/count/minimum
34173422
</t>
34183423
</list>
34193424
</t>
3425+
<t>
3426+
Note: The fragment part of the URI does not make it canonical or non-canonical,
3427+
rather, the base URI used (as part of the full URI with any fragment) is what
3428+
determines the canonical nature of the resulting full URI.
3429+
<cref>
3430+
Multiple "canonical" URIs? We Acknowledge this is potentially confusing, and
3431+
direct you to read the CREF located in the
3432+
<xref target="embedded">JSON Pointer fragments and embedded schema resources</xref>
3433+
section for futher comments.
3434+
</cref>
3435+
</t>
3436+
34203437
</section>
34213438

34223439
<section title="Manipulating schema documents and references">

0 commit comments

Comments
 (0)