Merge pull request #496 from handrews/norm

Fix normative vs informative references

Author: handrews

jsonschema-hyperschema.xml

@@ -5,7 +5,6 @@
 <!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
 <!ENTITY rfc4151 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4151.xml">
 <!--<!ENTITY rfc4287 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml">-->
-<!--<!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">-->
 <!ENTITY rfc5789 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5789.xml">
 <!ENTITY rfc6068 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6068.xml">
 <!ENTITY rfc6570 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6570.xml">
@@ -2492,9 +2491,10 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
             &rfc3986;
             <!--&rfc4287;-->
             &rfc6570;
+            &rfc6573;
             &rfc6901;
+            &rfc8288;
             &I-D.luff-relative-json-pointer;
-            &I-D.reschke-http-jfv;
             <reference anchor="json-schema">
                 <front>
                     <title>JSON Schema: A Media Type for Describing JSON Documents</title>
@@ -2518,15 +2518,13 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
         </references>
         <references title="Informative References">
             &rfc2046;
-            <!--&rfc5226;-->
             &rfc4151;
             &rfc5789;
             &rfc6068;
-            &rfc6573;
             &rfc7230;
             &rfc7231;
             &rfc7807;
-            &rfc8288;
+            &I-D.reschke-http-jfv;
         </references>
         <section title="Using JSON Hyper-Schema in APIs" anchor="apis">
             <t>

jsonschema-validation.xml

@@ -1381,17 +1381,6 @@
         <!-- References Section -->
         <references title="Normative References">
             &RFC2119;
-            <reference anchor="json-schema">
-                <front>
-                    <title>JSON Schema: A Media Type for Describing JSON Documents</title>
-                    <author/>
-                    <date year="2016" month="October"/>
-                </front>
-                <seriesInfo name="Internet-Draft" value="draft-wright-json-schema-00" />
-            </reference>
-        </references>
-
-        <references title="Informative References">
             &RFC1034;
             &RFC2045;
             &RFC2046;
@@ -1400,15 +1389,13 @@
             &RFC3986;
             &RFC3987;
             &RFC4291;
-            &RFC4329;
+            &RFC5322;
             &RFC5890;
             &RFC5891;
             &RFC6570;
             &RFC6531;
             &RFC6901;
             &RFC7159;
-            &RFC5322;
-            &I-D.luff-relative-json-pointer;
             <reference anchor="ecma262"
             target="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf">
                 <front>
@@ -1417,6 +1404,19 @@
                     <date/>
                 </front>
             </reference>
+            &I-D.luff-relative-json-pointer;
+            <reference anchor="json-schema">
+                <front>
+                    <title>JSON Schema: A Media Type for Describing JSON Documents</title>
+                    <author/>
+                    <date year="2016" month="October"/>
+                </front>
+                <seriesInfo name="Internet-Draft" value="draft-wright-json-schema-00" />
+            </reference>
+        </references>
+
+        <references title="Informative References">
+            &RFC4329;
         </references>
 
         <section title="Acknowledgments">
@@ -1462,6 +1462,8 @@
                             <t>I18N formats: "iri", "iri-reference", "idn-hostname", "idn-email"</t>
                             <t>Clarify that "json-pointer" format means string encoding, not URI fragment</t>
                             <t>Fixed typo that inverted the meaning of "minimum" and "exclusiveMinimum"</t>
+                            <t>Move format syntax references into Normative References</t>
+                            <t>JSON is a normative requirement</t>
                         </list>
                     </t>
                     <t hangText="draft-wright-json-schema-validation-01">