Update JSON RFC reference

redaktor · Mar 18, 2016 · bdb9ccc · bdb9ccc
1 parent c75c528
commit bdb9ccc
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 13 deletions.
diff --git a/jsonschema-core.xml b/jsonschema-core.xml
@@ -2,9 +2,9 @@
 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
 <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
 <!ENTITY RFC3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
-<!ENTITY RFC4627 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4627.xml">
 <!ENTITY RFC5988 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5988.xml">
 <!ENTITY RFC7231 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7231.xml">
+<!ENTITY RFC7159 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7159.xml">
 ]>
 <?rfc toc="yes"?>
 <?rfc symrefs="yes"?>
@@ -93,20 +93,20 @@
             <t>
                 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 <xref target="RFC4627">RFC 4627</xref>.
+                be interpreted as defined in <xref target="RFC7159">RFC 7159</xref>.
             </t>
         </section>
 
         <section title="Core terminology">
 
             <section title="Property, item">
                 <t>
-                    When refering to a JSON Object, as defined by <xref target="RFC4627"/>, the
+                    When refering to a JSON Object, as defined by <xref target="RFC7159"/>, the
                     terms "member" and "property" may be used interchangeably.
                 </t>
 
                 <t>
-                    When refering to a JSON Array, as defined by <xref target="RFC4627"/>, the terms
+                    When refering to a JSON Array, as defined by <xref target="RFC7159"/>, the terms
                     "element" and "item" may be used interchangeably.
                 </t>
             </section>
@@ -259,15 +259,15 @@
 
             <section title="Applicability to all JSON values">
                 <t>
-                    It is acknowledged that an instance may be any valid JSON value as defined by <xref target="RFC4627"/>.
+                    It is acknowledged that an instance may be any valid JSON value as defined by <xref target="RFC7159"/>.
                     As such, JSON Schema does not mandate that an instance be of a particular type: JSON Schema can describe any JSON value, including null.
                 </t>
             </section>
 
             <section title="Programming language independence">
                 <t>
                     JSON Schema is programming language agnostic. The only limitations are the ones
-                    expressed by <xref target="RFC4627"/> and those of the host programming
+                    expressed by <xref target="RFC7159"/> and those of the host programming
                     language.
                 </t>
             </section>
@@ -326,7 +326,7 @@
             <section title="Security considerations">
                 <t>
                     Both schemas and instances are JSON values. As such, all security considerations
-                    defined in <xref target="RFC4627">RFC 4627</xref> apply.
+                    defined in <xref target="RFC7159">RFC 7159</xref> apply.
                 </t>
             </section>
 
@@ -628,10 +628,10 @@ Content-Type: application/my-media-type+json;
         <references title="Normative References">
             &RFC2119;
             &RFC3986;
+            &RFC7159;
         </references>
 
         <references title="Informative References">
-            &RFC4627;
             &RFC5988;
             &RFC7231;
            <reference anchor="json-schema-validation"

diff --git a/jsonschema-schema.xml b/jsonschema-schema.xml
@@ -6,8 +6,8 @@
 <!ENTITY RFC2673 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2673.xml">
 <!ENTITY RFC3339 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3339.xml">
 <!ENTITY RFC3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
-<!ENTITY RFC4627 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4627.xml">
 <!ENTITY RFC5322 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5322.xml">
+<!ENTITY RFC7159 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7159.xml">
 ]>
 <?rfc toc="yes"?>
 <?rfc symrefs="yes"?>
@@ -158,7 +158,7 @@
 
                     <list>
                         <t>individual Unicode characters, as defined by the <xref
-                        target="RFC4627">JSON specification</xref>;</t>
+                        target="RFC7159">JSON specification</xref>;</t>
                         <t>simple character classes ([abc]), range character classes ([a-z]);</t>
                         <t>complemented character classes ([^abc], [^a-z]);</t>
                         <t>simple quantifiers: "+" (one or more), "*" (zero or more), "?" (zero or
@@ -315,7 +315,7 @@
 
                         <t>
                             The length of a string instance is defined as the number of its
-                            characters as defined by <xref target="RFC4627">RFC 4627</xref>.
+                            characters as defined by <xref target="RFC7159">RFC 7159</xref>.
                         </t>
                     </section>
 
@@ -338,7 +338,7 @@
 
                         <t>
                             The length of a string instance is defined as the number of its
-                            characters as defined by <xref target="RFC4627">RFC 4627</xref>.
+                            characters as defined by <xref target="RFC7159">RFC 7159</xref>.
                         </t>
                     </section>
 
@@ -1323,7 +1323,7 @@
             &RFC2673;
             &RFC3339;
             &RFC3986;
-            &RFC4627;
+            &RFC7159;
             &RFC5322;
             <reference anchor="ecma262"
             target="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf">