File tree 1 file changed +18
-1
lines changed
1 file changed +18
-1
lines changed Original file line number Diff line number Diff line change 50
50
</address >
51
51
</author >
52
52
53
- <date year =" 2021 " />
53
+ <date year =" 2022 " />
54
54
<workgroup >Internet Engineering Task Force</workgroup >
55
55
<keyword >JSON</keyword >
56
56
<keyword >Schema</keyword >
1863
1863
no point in forbidding it, while others have argued that it complicates
1864
1864
schema identification and should be forbidden. Feedback on this
1865
1865
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)
1866
1871
</cref >
1867
1872
</t >
1868
1873
<t >
@@ -3417,6 +3422,18 @@ https://example.com/schemas/common#/$defs/count/minimum
3417
3422
</t >
3418
3423
</list >
3419
3424
</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
+
3420
3437
</section >
3421
3438
3422
3439
<section title =" Manipulating schema documents and references" >
You can’t perform that action at this time.
0 commit comments