|
2 | 2 | <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
|
3 | 3 | <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
|
4 | 4 | <!ENTITY RFC3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
|
5 |
| -<!ENTITY RFC4627 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4627.xml"> |
6 | 5 | <!ENTITY RFC5988 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5988.xml">
|
7 | 6 | <!ENTITY RFC7231 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7231.xml">
|
| 7 | +<!ENTITY RFC7159 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7159.xml"> |
8 | 8 | ]>
|
9 | 9 | <?rfc toc="yes"?>
|
10 | 10 | <?rfc symrefs="yes"?>
|
|
93 | 93 | <t>
|
94 | 94 | The terms "JSON", "JSON text", "JSON value", "member", "element", "object", "array",
|
95 | 95 | "number", "string", "boolean", "true", "false", and "null" in this document are to
|
96 |
| - be interpreted as defined in <xref target="RFC4627">RFC 4627</xref>. |
| 96 | + be interpreted as defined in <xref target="RFC7159">RFC 7159</xref>. |
97 | 97 | </t>
|
98 | 98 | </section>
|
99 | 99 |
|
100 | 100 | <section title="Core terminology">
|
101 | 101 |
|
102 | 102 | <section title="Property, item">
|
103 | 103 | <t>
|
104 |
| - When refering to a JSON Object, as defined by <xref target="RFC4627"/>, the |
| 104 | + When refering to a JSON Object, as defined by <xref target="RFC7159"/>, the |
105 | 105 | terms "member" and "property" may be used interchangeably.
|
106 | 106 | </t>
|
107 | 107 |
|
108 | 108 | <t>
|
109 |
| - When refering to a JSON Array, as defined by <xref target="RFC4627"/>, the terms |
| 109 | + When refering to a JSON Array, as defined by <xref target="RFC7159"/>, the terms |
110 | 110 | "element" and "item" may be used interchangeably.
|
111 | 111 | </t>
|
112 | 112 | </section>
|
|
259 | 259 |
|
260 | 260 | <section title="Applicability to all JSON values">
|
261 | 261 | <t>
|
262 |
| - It is acknowledged that an instance may be any valid JSON value as defined by <xref target="RFC4627"/>. |
| 262 | + It is acknowledged that an instance may be any valid JSON value as defined by <xref target="RFC7159"/>. |
263 | 263 | As such, JSON Schema does not mandate that an instance be of a particular type: JSON Schema can describe any JSON value, including null.
|
264 | 264 | </t>
|
265 | 265 | </section>
|
266 | 266 |
|
267 | 267 | <section title="Programming language independence">
|
268 | 268 | <t>
|
269 | 269 | JSON Schema is programming language agnostic. The only limitations are the ones
|
270 |
| - expressed by <xref target="RFC4627"/> and those of the host programming |
| 270 | + expressed by <xref target="RFC7159"/> and those of the host programming |
271 | 271 | language.
|
272 | 272 | </t>
|
273 | 273 | </section>
|
|
326 | 326 | <section title="Security considerations">
|
327 | 327 | <t>
|
328 | 328 | Both schemas and instances are JSON values. As such, all security considerations
|
329 |
| - defined in <xref target="RFC4627">RFC 4627</xref> apply. |
| 329 | + defined in <xref target="RFC7159">RFC 7159</xref> apply. |
330 | 330 | </t>
|
331 | 331 | </section>
|
332 | 332 |
|
@@ -628,10 +628,10 @@ Content-Type: application/my-media-type+json;
|
628 | 628 | <references title="Normative References">
|
629 | 629 | &RFC2119;
|
630 | 630 | &RFC3986;
|
| 631 | + &RFC7159; |
631 | 632 | </references>
|
632 | 633 |
|
633 | 634 | <references title="Informative References">
|
634 |
| - &RFC4627; |
635 | 635 | &RFC5988;
|
636 | 636 | &RFC7231;
|
637 | 637 | <reference anchor="json-schema-validation"
|
|
0 commit comments