forked from json-schema-org/json-schema-org.github.io
-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathjson-schema-core.html
979 lines (911 loc) · 50 KB
/
json-schema-core.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>JSON Schema: A Media Type for Describing JSON Documents</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents"/>
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction"/>
<link href="#rfc.section.2" rel="Chapter" title="2 Conventions and Terminology"/>
<link href="#rfc.section.3" rel="Chapter" title="3 Overview"/>
<link href="#rfc.section.3.1" rel="Chapter" title="3.1 Validation"/>
<link href="#rfc.section.3.2" rel="Chapter" title="3.2 Hypermedia and Linking"/>
<link href="#rfc.section.4" rel="Chapter" title="4 Definitions"/>
<link href="#rfc.section.4.1" rel="Chapter" title="4.1 JSON Document"/>
<link href="#rfc.section.4.2" rel="Chapter" title="4.2 Instance"/>
<link href="#rfc.section.4.3" rel="Chapter" title="4.3 Instance equality"/>
<link href="#rfc.section.4.4" rel="Chapter" title="4.4 JSON Schema documents"/>
<link href="#rfc.section.4.5" rel="Chapter" title="4.5 Root schema and subschemas"/>
<link href="#rfc.section.5" rel="Chapter" title="5 Fragment identifiers"/>
<link href="#rfc.section.6" rel="Chapter" title="6 General considerations"/>
<link href="#rfc.section.6.1" rel="Chapter" title="6.1 Range of JSON values"/>
<link href="#rfc.section.6.2" rel="Chapter" title="6.2 Programming language independence"/>
<link href="#rfc.section.6.3" rel="Chapter" title="6.3 Mathematical integers"/>
<link href="#rfc.section.6.4" rel="Chapter" title="6.4 Extending JSON Schema"/>
<link href="#rfc.section.7" rel="Chapter" title="7 The "$schema" keyword"/>
<link href="#rfc.section.8" rel="Chapter" title="8 Schema references with $ref"/>
<link href="#rfc.section.9" rel="Chapter" title="9 Base URI and dereferencing"/>
<link href="#rfc.section.9.1" rel="Chapter" title="9.1 Initial base URI"/>
<link href="#rfc.section.9.2" rel="Chapter" title="9.2 The "$id" keyword"/>
<link href="#rfc.section.9.2.1" rel="Chapter" title="9.2.1 Internal references"/>
<link href="#rfc.section.9.2.2" rel="Chapter" title="9.2.2 External references"/>
<link href="#rfc.section.10" rel="Chapter" title="10 Usage for hypermedia"/>
<link href="#rfc.section.10.1" rel="Chapter" title="10.1 Linking to a schema"/>
<link href="#rfc.section.10.2" rel="Chapter" title="10.2 Describing a profile of JSON"/>
<link href="#rfc.section.10.3" rel="Chapter" title="10.3 Usage over HTTP"/>
<link href="#rfc.section.11" rel="Chapter" title="11 Security considerations"/>
<link href="#rfc.section.12" rel="Chapter" title="12 IANA Considerations"/>
<link href="#rfc.references" rel="Chapter" title="13 References"/>
<link href="#rfc.references.1" rel="Chapter" title="13.1 Normative References"/>
<link href="#rfc.references.2" rel="Chapter" title="13.2 Informative References"/>
<link href="#rfc.appendix.A" rel="Chapter" title="A Acknowledgments"/>
<link href="#rfc.appendix.B" rel="Chapter" title="B ChangeLog"/>
<link href="#rfc.authors" rel="Chapter"/>
<meta name="generator" content="xml2rfc version 2.5.1 - http://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Wright, A., Ed. and H. Andrews, Ed." />
<meta name="dct.identifier" content="urn:ietf:id:draft-wright-json-schema-01" />
<meta name="dct.issued" scheme="ISO8601" content="2017-4-21" />
<meta name="dct.abstract" content="JSON Schema defines the media type "application/schema+json", a JSON-based format for describing the structure of JSON data. JSON Schema asserts what a JSON document must look like, ways to extract information from it, and how to interact with it, ideal for annotating existing JSON APIs that would not otherwise have hypermedia controls or be machine-readable. " />
<meta name="description" content="JSON Schema defines the media type "application/schema+json", a JSON-based format for describing the structure of JSON data. JSON Schema asserts what a JSON document must look like, ways to extract information from it, and how to interact with it, ideal for annotating existing JSON APIs that would not otherwise have hypermedia controls or be machine-readable. " />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left">Internet Engineering Task Force</td>
<td class="right">A. Wright, Ed.</td>
</tr>
<tr>
<td class="left">Internet-Draft</td>
<td class="right"></td>
</tr>
<tr>
<td class="left">Intended status: Informational</td>
<td class="right">H. Andrews, Ed.</td>
</tr>
<tr>
<td class="left">Expires: October 23, 2017</td>
<td class="right">Cloudflare, Inc.</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">April 21, 2017</td>
</tr>
</tbody>
</table>
<p class="title">JSON Schema: A Media Type for Describing JSON Documents<br />
<span class="filename">draft-wright-json-schema-01</span></p>
<h1 id="rfc.abstract">
<a href="#rfc.abstract">Abstract</a>
</h1>
<p>JSON Schema defines the media type "application/schema+json", a JSON-based format for describing the structure of JSON data. JSON Schema asserts what a JSON document must look like, ways to extract information from it, and how to interact with it, ideal for annotating existing JSON APIs that would not otherwise have hypermedia controls or be machine-readable. </p>
<h1>
<a>Note to Readers</a>
</h1>
<p>The issues list for this draft can be found at <span><</span><a href="https://github.com/json-schema-org/json-schema-spec/issues">https://github.com/json-schema-org/json-schema-spec/issues</a><span>></span>. </p>
<p>For additional information, see <span><</span><a href="http://json-schema.org/">http://json-schema.org/</a><span>></span>. </p>
<p>To provide feedback, use this issue tracker, the communication methods listed on the homepage, or email the document editors. </p>
<h1 id="rfc.status">
<a href="#rfc.status">Status of This Memo</a>
</h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on October 23, 2017.</p>
<h1 id="rfc.copyrightnotice">
<a href="#rfc.copyrightnotice">Copyright Notice</a>
</h1>
<p>Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a></li>
<li>2. <a href="#rfc.section.2">Conventions and Terminology</a></li>
<li>3. <a href="#rfc.section.3">Overview</a></li>
<ul><li>3.1. <a href="#rfc.section.3.1">Validation</a></li>
<li>3.2. <a href="#rfc.section.3.2">Hypermedia and Linking</a></li>
</ul><li>4. <a href="#rfc.section.4">Definitions</a></li>
<ul><li>4.1. <a href="#rfc.section.4.1">JSON Document</a></li>
<li>4.2. <a href="#rfc.section.4.2">Instance</a></li>
<li>4.3. <a href="#rfc.section.4.3">Instance equality</a></li>
<li>4.4. <a href="#rfc.section.4.4">JSON Schema documents</a></li>
<li>4.5. <a href="#rfc.section.4.5">Root schema and subschemas</a></li>
</ul><li>5. <a href="#rfc.section.5">Fragment identifiers</a></li>
<li>6. <a href="#rfc.section.6">General considerations</a></li>
<ul><li>6.1. <a href="#rfc.section.6.1">Range of JSON values</a></li>
<li>6.2. <a href="#rfc.section.6.2">Programming language independence</a></li>
<li>6.3. <a href="#rfc.section.6.3">Mathematical integers</a></li>
<li>6.4. <a href="#rfc.section.6.4">Extending JSON Schema</a></li>
</ul><li>7. <a href="#rfc.section.7">The "$schema" keyword</a></li>
<li>8. <a href="#rfc.section.8">Schema references with $ref</a></li>
<li>9. <a href="#rfc.section.9">Base URI and dereferencing</a></li>
<ul><li>9.1. <a href="#rfc.section.9.1">Initial base URI</a></li>
<li>9.2. <a href="#rfc.section.9.2">The "$id" keyword</a></li>
<ul><li>9.2.1. <a href="#rfc.section.9.2.1">Internal references</a></li>
<li>9.2.2. <a href="#rfc.section.9.2.2">External references</a></li>
</ul></ul><li>10. <a href="#rfc.section.10">Usage for hypermedia</a></li>
<ul><li>10.1. <a href="#rfc.section.10.1">Linking to a schema</a></li>
<li>10.2. <a href="#rfc.section.10.2">Describing a profile of JSON</a></li>
<li>10.3. <a href="#rfc.section.10.3">Usage over HTTP</a></li>
</ul><li>11. <a href="#rfc.section.11">Security considerations</a></li>
<li>12. <a href="#rfc.section.12">IANA Considerations</a></li>
<li>13. <a href="#rfc.references">References</a></li>
<ul><li>13.1. <a href="#rfc.references.1">Normative References</a></li>
<li>13.2. <a href="#rfc.references.2">Informative References</a></li>
</ul><li>Appendix A. <a href="#rfc.appendix.A">Acknowledgments</a></li>
<li>Appendix B. <a href="#rfc.appendix.B">ChangeLog</a></li>
<li><a href="#rfc.authors">Authors' Addresses</a></li>
</ul>
<h1 id="rfc.section.1"><a href="#rfc.section.1">1.</a> Introduction</h1>
<p id="rfc.section.1.p.1">JSON Schema is a JSON media type for defining the structure of JSON data. JSON Schema is intended to define validation, documentation, hyperlink navigation, and interaction control of JSON data. </p>
<p id="rfc.section.1.p.2">This specification defines JSON Schema core terminology and mechanisms, including pointing to another JSON Schema by reference, dereferencing a JSON Schema reference, and specifying the vocabulary being used. </p>
<p id="rfc.section.1.p.3">Other specifications define the vocabularies that perform assertions about validation, linking, annotation, navigation, and interaction. </p>
<h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> Conventions and Terminology</h1>
<p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <a href="#RFC2119">RFC 2119</a> <cite title="NONE">[RFC2119]</cite>. </p>
<p id="rfc.section.2.p.2">The terms "JSON", "JSON text", "JSON value", "member", "element", "object", "array", "number", "string", "boolean", "true", "false", and "null" in this document are to be interpreted as defined in <a href="#RFC7159">RFC 7159</a> <cite title="NONE">[RFC7159]</cite>. </p>
<h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> Overview</h1>
<p id="rfc.section.3.p.1">This document proposes a new media type "application/schema+json" to identify a JSON Schema for describing JSON data. JSON Schemas are themselves JSON documents. This, and related specifications, define keywords allowing authors to describe JSON data in several ways. </p>
<h1 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1.</a> Validation</h1>
<p id="rfc.section.3.1.p.1">JSON Schema describes the structure of a JSON document (for instance, required properties and length limitations). Applications can use this information to validate instances (check that constraints are met), or inform interfaces to collect user input such that the constraints are satisfied. </p>
<p id="rfc.section.3.1.p.2">Validation behaviour and keywords are specified in <a href="#json-schema-validation">a separate document</a> <cite title="NONE">[json-schema-validation]</cite>. </p>
<h1 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2.</a> Hypermedia and Linking</h1>
<p id="rfc.section.3.2.p.1">JSON Hyper-Schema describes the hypertext structure of a JSON document. This includes link relations from the instance to other resources, interpretation of instances as multimedia data, and submission data required to use an API. </p>
<p id="rfc.section.3.2.p.2">Hyper-schema behaviour and keywords are specified in <a href="#json-hyper-schema">a separate document</a> <cite title="NONE">[json-hyper-schema]</cite>. </p>
<h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> Definitions</h1>
<h1 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1.</a> JSON Document</h1>
<p id="rfc.section.4.1.p.1">A JSON document is an information resource (series of octets) described by the application/json media type. </p>
<p id="rfc.section.4.1.p.2">In JSON Schema, the terms "JSON document", "JSON text", and "JSON value" are interchangeable because of the data model it defines. </p>
<p id="rfc.section.4.1.p.3">JSON Schema is only defined over JSON documents. However, any document or memory structure that can be parsed into or processed according to the JSON Schema data model can be interpreted against a JSON Schema, including media types like <a href="#RFC7049">CBOR</a> <cite title="NONE">[RFC7049]</cite>. </p>
<h1 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2.</a> Instance</h1>
<p id="rfc.section.4.2.p.1">JSON Schema interprets documents according to a data model. A JSON value interpreted according to this data model is called an "instance". </p>
<p id="rfc.section.4.2.p.2">An instance has one of six primitive types, and a range of possible values depending on the type: </p>
<dl>
<dt>null</dt>
<dd style="margin-left: 8">A JSON "null" production</dd>
<dt>boolean</dt>
<dd style="margin-left: 8">A "true" or "false" value, from the JSON "true" or "false" productions</dd>
<dt>object</dt>
<dd style="margin-left: 8">An unordered set of properties mapping a string to an instance, from the JSON "object" production</dd>
<dt>array</dt>
<dd style="margin-left: 8">An ordered list of instances, from the JSON "array" production</dd>
<dt>number</dt>
<dd style="margin-left: 8">An arbitrary-precision, base-10 decimal number value, from the JSON "number" production</dd>
<dt>string</dt>
<dd style="margin-left: 8">A string of Unicode code points, from the JSON "string" production</dd>
</dl>
<p> </p>
<p id="rfc.section.4.2.p.3">Whitespace and formatting concerns are thus outside the scope of JSON Schema. </p>
<p id="rfc.section.4.2.p.4">Since an object cannot have two properties with the same key, behavior for a JSON document that tries to define two properties (the "member" production) with the same key (the "string" production) in a single object is undefined. </p>
<h1 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3.</a> Instance equality</h1>
<p id="rfc.section.4.3.p.1">Two JSON instances are said to be equal if and only if they are of the same type and have the same value according to the data model. Specifically, this means: </p>
<ul class="empty">
<li>both are null; or</li>
<li>both are true; or</li>
<li>both are false; or</li>
<li>both are strings, and are the same codepoint-for-codepoint; or</li>
<li>both are numbers, and have the same mathematical value; or</li>
<li>both are arrays, and have an equal value item-for-item; or</li>
<li>both are objects, and each property in one has exactly one property with a key equal to the other's, and that other property has an equal value.</li>
</ul>
<p> </p>
<p id="rfc.section.4.3.p.2">Implied in this definition is that arrays must be the same length, objects must have the same number of members, properties in objects are unordered, there is no way to define multiple properties with the same key, and mere formatting differences (indentation, placement of commas, trailing zeros) are insignificant. </p>
<h1 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4.</a> JSON Schema documents</h1>
<p id="rfc.section.4.4.p.1">A JSON Schema document, or simply a schema, is a JSON document used to describe an instance. A schema is itself interpreted as an instance. A JSON Schema MUST be an object or a boolean. </p>
<p id="rfc.section.4.4.p.2">Boolean values are equivalent to the following behaviors: </p>
<dl>
<dt>true</dt>
<dd style="margin-left: 8">Always passes validation, as if the empty schema {}</dd>
<dt>false</dt>
<dd style="margin-left: 8">Always fails validation, as if the schema { "not":{} }</dd>
</dl>
<p> </p>
<p id="rfc.section.4.4.p.3">Properties that are used to describe the instance are called keywords, or schema keywords. The meaning of properties is specified by the vocabulary that the schema is using. </p>
<p id="rfc.section.4.4.p.4">A JSON Schema MAY contain properties which are not schema keywords. Unknown keywords SHOULD be ignored. </p>
<p id="rfc.section.4.4.p.5">A schema that itself describes a schema is called a meta-schema. Meta-schemas are used to validate JSON Schemas and specify which vocabulary it is using. </p>
<p id="rfc.section.4.4.p.6">An empty schema is a JSON Schema with no properties, or only unknown properties. </p>
<h1 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5.</a> Root schema and subschemas</h1>
<p id="rfc.section.4.5.p.1">The root schema is the schema that comprises the entire JSON document in question. </p>
<p id="rfc.section.4.5.p.2">Some keywords take schemas themselves, allowing JSON Schemas to be nested: </p>
<pre>
{
"title": "root",
"items": {
"title": "array item"
}
}
</pre>
<p id="rfc.section.4.5.p.3">In this example document, the schema titled "array item" is a subschema, and the schema titled "root" is the root schema. </p>
<p id="rfc.section.4.5.p.4">As with the root schema, a subschema is either an object or a boolean. </p>
<h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a href="#fragments" id="fragments">Fragment identifiers</a></h1>
<p id="rfc.section.5.p.1">In accordance with section 3.1 of <a href="#RFC6839">[RFC6839]</a>, the syntax and semantics of fragment identifiers specified for any +json media type SHOULD be as specified for "application/json". (At publication of this document, there is no fragment identification syntax defined for "application/json".) </p>
<p id="rfc.section.5.p.2">Additionally, the "application/schema+json" media type supports two fragment identifier structures: plain names and JSON Pointers. The use of JSON Pointers as URI fragment identifiers is described in <a href="#RFC6901">RFC 6901</a> <cite title="NONE">[RFC6901]</cite>. Fragment identifiers matching the JSON Pointer syntax, including the empty string, MUST be interpreted as JSON Pointer fragment identifiers. </p>
<p id="rfc.section.5.p.3">Per the W3C's <a href="#W3C.WD-fragid-best-practices-20121025">best practices for fragment identifiers</a> <cite title="NONE">[W3C.WD-fragid-best-practices-20121025]</cite>, plain name fragment identifiers are reserved for referencing locally named schemas. All fragment identifiers that do not match the JSON Pointer syntax MUST be interpreted as plain name fragment identifiers. </p>
<p id="rfc.section.5.p.4">Defining and referencing a plain name fragment identifier in the <a href="#id-keyword">"$id" keyword</a> <cite title="NONE">[id-keyword]</cite> section. </p>
<p/>
<h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> General considerations</h1>
<h1 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1.</a> Range of JSON values</h1>
<p id="rfc.section.6.1.p.1">An instance may be any valid JSON value as defined by <a href="#RFC7159">JSON</a> <cite title="NONE">[RFC7159]</cite>. JSON Schema imposes no restrictions on type: JSON Schema can describe any JSON value, including, for example, null. </p>
<h1 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2.</a> <a href="#language" id="language">Programming language independence</a></h1>
<p id="rfc.section.6.2.p.1">JSON Schema is programming language agnostic, and supports the full range of values described in the data model. Be aware, however, that some languages and JSON parsers may not be able to represent in memory the full range of values describable by JSON. </p>
<h1 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3.</a> <a href="#integers" id="integers">Mathematical integers</a></h1>
<p id="rfc.section.6.3.p.1">Some programming languages and parsers use different internal representations for floating point numbers than they do for integers. </p>
<p id="rfc.section.6.3.p.2">For consistency, integer JSON numbers SHOULD NOT be encoded with a fractional part. </p>
<h1 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4.</a> Extending JSON Schema</h1>
<p id="rfc.section.6.4.p.1">Implementations MAY define additional keywords to JSON Schema. Save for explicit agreement, schema authors SHALL NOT expect these additional keywords to be supported by peer implementations. Implementations SHOULD ignore keywords they do not support. </p>
<p id="rfc.section.6.4.p.2">Authors of extensions to JSON Schema are encouraged to write their own meta-schemas, which extend the existing meta-schemas using "allOf". This extended meta-schema SHOULD be referenced using the "$schema" keyword, to allow tools to follow the correct behaviour. </p>
<h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> The "$schema" keyword</h1>
<p id="rfc.section.7.p.1">The "$schema" keyword is both used as a JSON Schema version identifier and the location of a resource which is itself a JSON Schema, which describes any schema written for this particular version. </p>
<p id="rfc.section.7.p.2">The value of this keyword MUST be a <a href="#RFC3986">URI</a> <cite title="NONE">[RFC3986]</cite> (containing a scheme) and this URI MUST be normalized. The current schema MUST be valid against the meta-schema identified by this URI. </p>
<p id="rfc.section.7.p.3">The "$schema" keyword SHOULD be used in a root schema. It MUST NOT appear in subschemas. </p>
<p><a id="CREF1" class="info">[CREF1]<span class="info">While this pattern is likely to remain best practice for schema authoring, implementation behavior is subject to be revised or liberalized in future drafts. </span></a> </p>
<p id="rfc.section.7.p.5">Values for this property are defined in other documents and by other parties. JSON Schema implementations SHOULD implement support for current and previous published drafts of JSON Schema vocabularies as deemed reasonable. </p>
<h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> Schema references with $ref</h1>
<p id="rfc.section.8.p.1">The "$ref" keyword is used to reference a schema, and provides the ability to validate recursive structures through self-reference. </p>
<p id="rfc.section.8.p.2">An object schema with a "$ref" property MUST be interpreted as a "$ref" reference. The value of the "$ref" property MUST be a URI Reference. Resolved against the current URI base, it identifies the URI of a schema to use. All other properties in a "$ref" object MUST be ignored. </p>
<p id="rfc.section.8.p.3">The URI is not a network locator, only an identifier. A schema need not be downloadable from the address if it is a network-addressable URL, and implementations SHOULD NOT assume they should perform a network operation when they encounter a network-addressable URI. </p>
<p id="rfc.section.8.p.4">A schema MUST NOT be run into an infinite loop against a schema. For example, if two schemas "#alice" and "#bob" both have an "allOf" property that refers to the other, a naive validator might get stuck in an infinite recursive loop trying to validate the instance. Schemas SHOULD NOT make use of infinite recursive nesting like this; the behavior is undefined. </p>
<h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> Base URI and dereferencing</h1>
<h1 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1.</a> Initial base URI</h1>
<p><a href="#RFC3986">RFC3986 Section 5.1</a> <cite title="NONE">[RFC3986]</cite> defines how to determine the default base URI of a document. </p>
<p id="rfc.section.9.1.p.2">Informatively, the initial base URI of a schema is the URI at which it was found, or a suitable substitute URI if none is known. </p>
<h1 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2.</a> <a href="#id-keyword" id="id-keyword">The "$id" keyword</a></h1>
<p id="rfc.section.9.2.p.1">The "$id" keyword defines a URI for the schema, and the base URI that other URI references within the schema are resolved against. The "$id" keyword itself is resolved against the base URI that the object as a whole appears in. </p>
<p id="rfc.section.9.2.p.2">If present, the value for this keyword MUST be a string, and MUST represent a valid <a href="#RFC3986">URI-reference</a> <cite title="NONE">[RFC3986]</cite>. This value SHOULD be normalized, and SHOULD NOT be an empty fragment <#> or an empty string <>. </p>
<p id="rfc.section.9.2.p.3">The root schema of a JSON Schema document SHOULD contain an "$id" keyword with a URI (containing a scheme). This URI SHOULD either not have a fragment, or have one that is an empty string. <a id="CREF2" class="info">[CREF2]<span class="info">How should an "$id" URI reference containing a fragement with other components be interpreted? There are two cases: when the other components match the current base URI and when they change the base URI. </span></a> </p>
<p id="rfc.section.9.2.p.4">To name subschemas in a JSON Schema document, subschemas can use "$id" to give themselves a document-local identifier. This is done by setting "$id" to a URI reference consisting only of a fragment. The fragment identifier MUST begin with a letter ([A-Za-z]), followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons (":"), or periods ("."). </p>
<p id="rfc.section.9.2.p.5">The effect of defining an "$id" that neither matches the above requirements nor is a valid JSON pointer is not defined. </p>
<pre>
{
"$id": "http://example.com/root.json",
"definitions": {
"A": { "$id": "#foo" },
"B": {
"$id": "other.json",
"definitions": {
"X": { "$id": "#bar" },
"Y": { "$id": "t/inner.json" }
}
},
"C": {
"$id": "urn:uuid:ee564b8a-7a87-4125-8c96-e9f123d6766f"
}
}
}
</pre>
<p id="rfc.section.9.2.p.6">For example: </p>
<p id="rfc.section.9.2.p.7">The schemas at the following URI-encoded <a href="#RFC6901">JSON Pointers</a> <cite title="NONE">[RFC6901]</cite> (relative to the root schema) have the following base URIs, and are identifiable by either URI in accordance with Section <a href="#fragments">5</a> above: </p>
<p/>
<dl>
<dt># (document root)</dt>
<dd style="margin-left: 8">http://example.com/root.json#</dd>
<dt>#/definitions/A</dt>
<dd style="margin-left: 8">http://example.com/root.json#foo</dd>
<dt>#/definitions/B</dt>
<dd style="margin-left: 8">http://example.com/other.json</dd>
<dt>#/definitions/B/definitions/X</dt>
<dd style="margin-left: 8">http://example.com/other.json#bar</dd>
<dt>#/definitions/B/definitions/Y</dt>
<dd style="margin-left: 8">http://example.com/t/inner.json</dd>
<dt>#/definitions/C</dt>
<dd style="margin-left: 8">urn:uuid:ee564b8a-7a87-4125-8c96-e9f123d6766f</dd>
</dl>
<p> </p>
<h1 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1.</a> Internal references</h1>
<p id="rfc.section.9.2.1.p.1">Schemas can be identified by any URI that has been given to them, including a JSON Pointer or their URI given directly by "$id". </p>
<p id="rfc.section.9.2.1.p.2">Tools SHOULD take note of the URIs that schemas, including subschemas, provide for themselves using "$id". This is known as "Internal referencing". </p>
<p id="rfc.section.9.2.1.p.3">For example, consider this schema: </p>
<pre>
{
"$id": "http://example.net/root.json",
"items": {
"type": "array",
"items": { "$ref": "#item" }
},
"definitions": {
"single": {
"$id": "#item",
"type": "integer"
}
}
}
</pre>
<p id="rfc.section.9.2.1.p.4">When an implementation encounters the <#/definitions/single> schema, it resolves the "$id" URI reference against the current base URI to form <http://example.net/root.json#item>. </p>
<p id="rfc.section.9.2.1.p.5">When an implementation then looks inside the <#/items> schema, it encounters the <#item> reference, and resolves this to <http://example.net/root.json#item> which is understood as the schema defined elsewhere in the same document. </p>
<h1 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2.</a> External references</h1>
<p id="rfc.section.9.2.2.p.1">To differentiate schemas between each other in a vast ecosystem, schemas are identified by URI. As specified above, this does not necessarily mean anything is downloaded, but instead JSON Schema implementations SHOULD already understand the schemas they will be using, including the URIs that identify them. </p>
<p id="rfc.section.9.2.2.p.2">Implementations SHOULD be able to associate arbitrary URIs with an arbitrary schema and/or automatically associate a schema's "$id"-given URI, depending on the trust that the validator has in the schema. </p>
<p id="rfc.section.9.2.2.p.3">A schema MAY (and likely will) have multiple URIs, but there is no way for a URI to identify more than one schema. When multiple schemas try to identify with the same URI, validators SHOULD raise an error condition. </p>
<h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> Usage for hypermedia</h1>
<p id="rfc.section.10.p.1">JSON has been adopted widely by HTTP servers for automated APIs and robots. This section describes how to enhance processing of JSON documents in a more RESTful manner when used with protocols that support media types and <a href="#RFC5988">Web linking</a> <cite title="NONE">[RFC5988]</cite>. </p>
<h1 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1.</a> Linking to a schema</h1>
<p id="rfc.section.10.1.p.1">It is RECOMMENDED that instances described by a schema/profile provide a link to a downloadable JSON Schema using the link relation "describedby", as defined by <a href="#W3C.REC-ldp-20150226">Linked Data Protocol 1.0, section 8.1</a> <cite title="NONE">[W3C.REC-ldp-20150226]</cite>. </p>
<p id="rfc.section.10.1.p.2">In HTTP, such links can be attached to any response using the <a href="#RFC5988">Link header</a> <cite title="NONE">[RFC5988]</cite>. An example of such a header would be: </p>
<pre>
Link: <http://example.com/my-hyper-schema#>; rel="describedby"
</pre>
<h1 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2.</a> <a href="#profile" id="profile">Describing a profile of JSON</a></h1>
<p id="rfc.section.10.2.p.1">Instances MAY specify a "profile" as described in <a href="#RFC6906">The 'profile' Link Relation</a> <cite title="NONE">[RFC6906]</cite>. When used as a media-type parameter, HTTP servers gain the ability to perform Content-Type Negotiation based on profile. The media-type parameter MUST be a whitespace-separated list of URIs (i.e. relative references are invalid). </p>
<p id="rfc.section.10.2.p.2">The profile URI is opaque and SHOULD NOT automatically be dereferenced. If the implementation does not understand the semantics of the provided profile, the implementation can instead follow the "describedby" links, if any, which may provide information on how to handle the profile. Since "profile" doesn't necessarily point to a network location, the "describedby" relation is used for linking to a downloadable schema. However, for simplicity, schema authors should make these URIs point to the same resource when possible. </p>
<p id="rfc.section.10.2.p.3">In HTTP, the media-type parameter would be sent inside the Content-Type header: </p>
<pre>
Content-Type: application/json;
profile="http://example.com/my-hyper-schema#"
</pre>
<p id="rfc.section.10.2.p.4">Multiple profiles are whitespace separated: </p>
<pre>
Content-Type: application/json;
profile="http://example.com/alice http://example.com/bob"
</pre>
<p id="rfc.section.10.2.p.5">HTTP can also send the "profile" in a Link, though this may impact media-type semantics and Content-Type negotiation if this replaces the media-type parameter entirely: </p>
<pre>
Link: </alice>;rel="profile", </bob>;rel="profile"
</pre>
<h1 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3.</a> Usage over HTTP</h1>
<p id="rfc.section.10.3.p.1">When used for hypermedia systems over a network, <a href="#RFC7231">HTTP</a> <cite title="NONE">[RFC7231]</cite> is frequently the protocol of choice for distributing schemas. Misbehaving clients can pose problems for server maintainers if they pull a schema over the network more frequently than necessary, when it's instead possible to cache a schema for a long period of time. </p>
<p id="rfc.section.10.3.p.2">HTTP servers SHOULD set long-lived caching headers on JSON Schemas. HTTP clients SHOULD observe caching headers and not re-request documents within their freshness period. Distributed systems SHOULD make use of a shared cache and/or caching proxy. </p>
<pre>
User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
</pre>
<p id="rfc.section.10.3.p.3">Clients SHOULD set or prepend a User-Agent header specific to the JSON Schema implementation or software product. Since symbols are listed in decreasing order of significance, the JSON Schema library name/version should precede the more generic HTTP library name (if any). For example: </p>
<p id="rfc.section.10.3.p.4">Clients SHOULD be able to make requests with a "From" header so that server operators can contact the owner of a potentially misbehaving script. </p>
<h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a href="#security" id="security">Security considerations</a></h1>
<p id="rfc.section.11.p.1">Both schemas and instances are JSON values. As such, all security considerations defined in <a href="#RFC7159">RFC 7159</a> <cite title="NONE">[RFC7159]</cite> apply. </p>
<p id="rfc.section.11.p.2">Instances and schemas are both frequently written by untrusted third parties, to be deployed on public Internet servers. Validators should take care that the parsing of schemas doesn't consume excessive system resources. Validators MUST NOT fall into an infinite loop. </p>
<p id="rfc.section.11.p.3">Servers need to take care that malicious parties can't change the functionality of existing schemas by uploading a schema with an pre-existing or very similar "$id". </p>
<p id="rfc.section.11.p.4">Individual JSON Schema vocabularies are liable to also have their own security considerations. Consult the respective specifications for more information. </p>
<h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> IANA Considerations</h1>
<p id="rfc.section.12.p.1">The proposed MIME media type for JSON Schema is defined as follows: </p>
<ul class="empty">
<li>Type name: application</li>
<li>Subtype name: schema+json</li>
<li>Required parameters: N/A</li>
<li>Encoding considerations: Encoding considerations are identical to those specified for the "application/json" media type. See <a href="#RFC7159">JSON</a> <cite title="NONE">[RFC7159]</cite>. </li>
<li>Security considerations: See Section <a href="#security">11</a> above. </li>
<li>Interoperability considerations: See Sections <a href="#language">6.2</a> and <a href="#integers">6.3</a> above. </li>
<li>Fragment identifier considerations: See Section <a href="#fragments">5</a> </li>
</ul>
<p> </p>
<h1 id="rfc.references"><a href="#rfc.references">13.</a> References</h1>
<h1 id="rfc.references.1"><a href="#rfc.references.1">13.1.</a> Normative References</h1>
<table>
<tbody>
<tr>
<td class="reference">
<b id="RFC2119">[RFC2119]</b>
</td>
<td class="top"><a>Bradner, S.</a>, "<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC3986">[RFC3986]</b>
</td>
<td class="top"><a>Berners-Lee, T.</a>, <a>Fielding, R.</a> and <a>L. Masinter</a>, "<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC6839">[RFC6839]</b>
</td>
<td class="top"><a>Hansen, T.</a> and <a>A. Melnikov</a>, "<a href="http://tools.ietf.org/html/rfc6839">Additional Media Type Structured Syntax Suffixes</a>", RFC 6839, DOI 10.17487/RFC6839, January 2013.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC6901">[RFC6901]</b>
</td>
<td class="top"><a>Bryan, P.</a>, <a>Zyp, K.</a> and <a>M. Nottingham</a>, "<a href="http://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>", RFC 6901, DOI 10.17487/RFC6901, April 2013.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC7159">[RFC7159]</b>
</td>
<td class="top"><a>Bray, T.</a>, "<a href="http://tools.ietf.org/html/rfc7159">The JavaScript Object Notation (JSON) Data Interchange Format</a>", RFC 7159, DOI 10.17487/RFC7159, March 2014.</td>
</tr>
<tr>
<td class="reference">
<b id="W3C.REC-ldp-20150226">[W3C.REC-ldp-20150226]</b>
</td>
<td class="top"><a>Speicher, S.</a>, <a>Arwe, J.</a> and <a>A. Malhotra</a>, "<a href="http://www.w3.org/TR/2015/REC-ldp-20150226">Linked Data Platform 1.0</a>", World Wide Web Consortium Recommendation REC-ldp-20150226, February 2015.</td>
</tr>
</tbody>
</table>
<h1 id="rfc.references.2"><a href="#rfc.references.2">13.2.</a> Informative References</h1>
<table>
<tbody>
<tr>
<td class="reference">
<b id="RFC5988">[RFC5988]</b>
</td>
<td class="top"><a>Nottingham, M.</a>, "<a href="http://tools.ietf.org/html/rfc5988">Web Linking</a>", RFC 5988, DOI 10.17487/RFC5988, October 2010.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC6906">[RFC6906]</b>
</td>
<td class="top"><a>Wilde, E.</a>, "<a href="http://tools.ietf.org/html/rfc6906">The 'profile' Link Relation Type</a>", RFC 6906, DOI 10.17487/RFC6906, March 2013.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC7049">[RFC7049]</b>
</td>
<td class="top"><a>Bormann, C.</a> and <a>P. Hoffman</a>, "<a href="http://tools.ietf.org/html/rfc7049">Concise Binary Object Representation (CBOR)</a>", RFC 7049, DOI 10.17487/RFC7049, October 2013.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC7231">[RFC7231]</b>
</td>
<td class="top"><a>Fielding, R.</a> and <a>J. Reschke</a>, "<a href="http://tools.ietf.org/html/rfc7231">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>", RFC 7231, DOI 10.17487/RFC7231, June 2014.</td>
</tr>
<tr>
<td class="reference">
<b id="W3C.WD-fragid-best-practices-20121025">[W3C.WD-fragid-best-practices-20121025]</b>
</td>
<td class="top"><a>Tennison, J.</a>, "<a href="http://www.w3.org/TR/2012/WD-fragid-best-practices-20121025">Best Practices for Fragment Identifiers and Media Type Definitions</a>", World Wide Web Consortium LastCall WD-fragid-best-practices-20121025, October 2012.</td>
</tr>
<tr>
<td class="reference">
<b id="json-schema-validation">[json-schema-validation]</b>
</td>
<td class="top"><a>Wright, A.</a> and <a>G. Luff</a>, "<a href="http://tools.ietf.org/html/draft-wright-json-schema-validation-00">JSON Schema Validation: A Vocabulary for Structural Validation of JSON</a>", Internet-Draft draft-wright-json-schema-validation-00, October 2016.</td>
</tr>
<tr>
<td class="reference">
<b id="json-hyper-schema">[json-hyper-schema]</b>
</td>
<td class="top"><a>Wright, A.</a> and <a>G. Luff</a>, "<a href="http://tools.ietf.org/html/draft-wright-json-schema-hyperschema-00">JSON Hyper-Schema: A Vocabulary for Hypermedia Annotation of JSON</a>", Internet-Draft draft-wright-json-schema-hyperschema-00, October 2016.</td>
</tr>
</tbody>
</table>
<h1 id="rfc.appendix.A"><a href="#rfc.appendix.A">Appendix A.</a> Acknowledgments</h1>
<p id="rfc.section.A.p.1">Thanks to Gary Court, Francis Galiegue, Kris Zyp, and Geraint Luff for their work on the initial drafts of JSON Schema. </p>
<p id="rfc.section.A.p.2">Thanks to Jason Desrosiers, Daniel Perrett, Erik Wilde, Ben Hutton, Evgeny Poberezkin, Brad Bowman, Gowry Sankar, Donald Pipowitch, and Dave Finlay for their submissions and patches to the document. </p>
<h1 id="rfc.appendix.B"><a href="#rfc.appendix.B">Appendix B.</a> ChangeLog</h1>
<p><a id="CREF3" class="info">[CREF3]<span class="info">This section to be removed before leaving Internet-Draft status.</span></a> </p>
<p/>
<dl>
<dt>draft-wright-json-schema-01</dt>
<dd style="margin-left: 8">
<ul>
<li>Updated intro</li>
<li>Allowed for any schema to be a boolean</li>
<li>"$schema" SHOULD NOT appear in subschemas, although that may change</li>
<li>Changed "id" to "$id"; all core keywords prefixed with "$"</li>
<li>Clarify and formalize fragments for application/schema+json</li>
<li>Note applicability to formats such as CBOR that can be represented in the JSON data model</li>
</ul>
<p> </p>
</dd>
<dt>draft-wright-json-schema-00</dt>
<dd style="margin-left: 8">
<ul>
<li>Updated references to JSON</li>
<li>Updated references to HTTP</li>
<li>Updated references to JSON Pointer</li>
<li>Behavior for "id" is now specified in terms of RFC3986</li>
<li>Aligned vocabulary usage for URIs with RFC3986</li>
<li>Removed reference to draft-pbryan-zyp-json-ref-03</li>
<li>Limited use of "$ref" to wherever a schema is expected</li>
<li>Added definition of the "JSON Schema data model"</li>
<li>Added additional security considerations</li>
<li>Defined use of subschema identifiers for "id"</li>
<li>Rewrote section on usage with HTTP</li>
<li>Rewrote section on usage with rel="describedBy" and rel="profile"</li>
<li>Fixed numerous invalid examples</li>
</ul>
<p> </p>
</dd>
<dt>draft-zyp-json-schema-04</dt>
<dd style="margin-left: 8">
<ul>
<li>Split validation keywords into separate document</li>
</ul>
<p> </p>
</dd>
<dt>draft-zyp-json-schema-00</dt>
<dd style="margin-left: 8">
<ul>
<li>Initial draft.</li>
<li>Salvaged from draft v3.</li>
<li>Mandate the use of JSON Reference, JSON Pointer.</li>
<li>Define the role of "id". Define URI resolution scope.</li>
<li>Add interoperability considerations.</li>
</ul>
<p> </p>
</dd>
</dl>
<p> </p>
<h1 id="rfc.authors">
<a href="#rfc.authors">Authors' Addresses</a>
</h1>
<div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Austin Wright</span> (editor)
<span class="n hidden">
<span class="family-name">Wright</span>
</span>
</span>
<span class="org vcardline"></span>
<span class="adr">
<span class="vcardline">
<span class="locality"></span>
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline"></span>
</span>
<span class="vcardline">EMail: <a href="mailto:[email protected]">[email protected]</a></span>
</address>
</div><div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Henry Andrews</span> (editor)
<span class="n hidden">
<span class="family-name">Andrews</span>
</span>
</span>
<span class="org vcardline">Cloudflare, Inc.</span>
<span class="adr">
<span class="vcardline">
<span class="locality"></span>
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline"></span>
</span>
<span class="vcardline">EMail: <a href="mailto:[email protected]">[email protected]</a></span>
</address>
</div>
</body>
</html>