Cite regular JSON Pointers separately.

json-schema-org · Sep 14, 2017 · 36ed6a1 · 36ed6a1
1 parent fca5fd5
commit 36ed6a1
Showing 1 changed file with 10 additions and 8 deletions.
diff --git a/jsonschema-hyperschema.xml b/jsonschema-hyperschema.xml
@@ -8,6 +8,7 @@
 <!ENTITY rfc5789 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5789.xml">
 <!ENTITY rfc5988 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5988.xml">
 <!ENTITY rfc6570 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6570.xml">
+<!ENTITY rfc6906 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6906.xml">
 <!ENTITY rfc7231 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7231.xml">
 <!ENTITY I-D.luff-relative-json-pointer SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-luff-relative-json-pointer-00.xml">
 <!ENTITY I-D.reschke-http-jfv SYSTEM "https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-reschke-http-jfv-06.xml">
@@ -561,7 +562,8 @@
                 <t>
                     The value of the "hrefPointers" link description property MUST be
                     an object.  Each property value in the object MUST be a valid
-                    <xref target="I-D.luff-relative-json-pointer">Relative JSON Pointer</xref>,
+                    <xref target="RFC6906">JSON Pointer</xref>, or a valid
+                    <xref target="I-D.luff-relative-json-pointer">Relative JSON Pointer</xref>
                     which is evaluated relative to the position in the instance from which
                     <xref target="href">"href"</xref> template variable resolution would
                     normally begin.
@@ -574,13 +576,12 @@
                 </t>
                 <figure>
                     <preamble>
-                        Recall that a Relative JSON Pointer which is not also a regular
-                        JSON Pointer begins with a number indicating how many levels
-                        up to move before applying the remainder of the pointer, if any, in the
-                        same manner as a regular JSON Pointer.  Consider the following schema
-                        for n-ary tree nodes, where a node is identified by its own id as well
-                        as the tree's root node id, and links are given for the IANA-registered
-                        "self" and "up" link relation types.
+                        Recall that a Relative JSON Pointer begins with a number indicating
+                        how many levels up to move before applying the remainder of the pointer,
+                        if any, in the same manner as a regular JSON Pointer.  Consider the
+                        following schema for n-ary tree nodes, where a node is identified by
+                        its own id as well as the tree's root node id, and links are given for
+                        the IANA-registered "self" and "up" link relation types.
                     </preamble>
                     <artwork>
 <![CDATA[{
@@ -1309,6 +1310,7 @@ GET /foo/
             &rfc3986;
             <!--&rfc4287;-->
             &rfc6570;
+            &rfc6906;
             &I-D.luff-relative-json-pointer;
             &I-D.reschke-http-jfv;
             <reference anchor="json-schema">