Move "self" link security bit to last subsection

The other parts flow much more naturally from the mention of
RFC 8288 in the introductory part of the security section.

Author: handrews

jsonschema-hyperschema.xml

@@ -2389,21 +2389,6 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
                 also apply, with appropriate adjustments (e.g. "anchor" as an LDO keyword rather
                 than an HTTP Link header attribute).
             </t>
-            <section title='"self" Links'>
-                <t>
-                    When link relation of "self" is used to denote a full representation of an
-                    object, the user agent SHOULD NOT consider the representation to be the
-                    authoritative representation of the resource denoted by the target URI if
-                    the target URI is not equivalent to or a sub-path of the URI used to request
-                    the resource representation which contains the target URI with the "self"
-                    link.
-                    <cref>
-                        It is no longer clear what was intended by the "sub-path" option in
-                        this paragraph.  While paths are defined as a hierarchical system
-                        by RFC 3986, there semantics of the hierarchy are not defined.
-                    </cref>
-                </t>
-            </section>
             <section title="Target Attributes">
                 <t>
                     As stated in <xref target="targetAttributes"/>, all LDO keywords describing
@@ -2442,6 +2427,21 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
                     match the link's "targetHints" values.
                 </t>
             </section>
+            <section title='"self" Links'>
+                <t>
+                    When link relation of "self" is used to denote a full representation of an
+                    object, the user agent SHOULD NOT consider the representation to be the
+                    authoritative representation of the resource denoted by the target URI if
+                    the target URI is not equivalent to or a sub-path of the URI used to request
+                    the resource representation which contains the target URI with the "self"
+                    link.
+                    <cref>
+                        It is no longer clear what was intended by the "sub-path" option in
+                        this paragraph.  While paths are defined as a hierarchical system
+                        by RFC 3986, there semantics of the hierarchy are not defined.
+                    </cref>
+                </t>
+            </section>
         </section>
 <!--
         <section title="IANA Considerations">