Merge pull request json-schema-org#472 from dlax/hyperschema-mailto-schema-up

Move up the JSON Hyper Schema in "mailto:" example

Author: handrews

jsonschema-hyperschema.xml

@@ -1667,7 +1667,7 @@ Link: <https://schema.example.com/entry> rel=describedBy
                     described by "submissionSchema" and "submissionMediaType".
                 </t>
                 <t>
-                    Therefore, we use "submissionMediaType" to indicate a multipart/alternative
+                    We use "submissionMediaType" to indicate a multipart/alternative
                     payload format, providing two representations of the same data (HTML and
                     plain text).  Since a multipart/alternative message is an ordered sequence
                     (the last part is the most preferred alternative), we model the sequence as
@@ -1680,32 +1680,6 @@ Link: <https://schema.example.com/entry> rel=describedBy
                     each part and are not ordered, should be modeled as JSON objects rather than
                     arrays.
                 </t>
-                <t>
-                    For the URI parameters, each of the three demonstrates a different way of
-                    resolving the input:
-                    <list style="hanging">
-                        <t hangText="email:">
-                            This variable's presence in "templateRequired" means that it must be
-                            resolved for the template to be used.  Since the "false" schema
-                            assigned to it in "hrefSchema" excludes it from the input data set,
-                            it must be resolved from the instance.
-                        </t>
-                        <t hangText="title:">
-                            The instance field matching this variable is required, and it is also
-                            allowed in the input data.  So its instance value is used to
-                            pre-populate the input data set before accepting the client's input.
-                            The client can opt to leave the instance value in place.  Since
-                            this field is required in "hrefSchema", the client cannot delete it
-                            (although it could set it to an empty string).
-                        </t>
-                        <t hangText="cc:">
-                            The "false" schema set for this in the main schema prevents this field
-                            from having an instance value.  If it is present at all, it must come
-                            from client input.  As it is not required in "hrefSchema", it may not
-                            be used at all.
-                        </t>
-                    </list>
-                </t>
                 <figure>
                     <preamble>
                         Note that some lines are wrapped to fit this document's width restrictions.
@@ -1768,6 +1742,32 @@ Link: <https://schema.example.com/entry> rel=describedBy
 }]]>
                     </artwork>
                 </figure>
+                <t>
+                    For the URI parameters, each of the three demonstrates a different way of
+                    resolving the input:
+                    <list style="hanging">
+                        <t hangText="email:">
+                            This variable's presence in "templateRequired" means that it must be
+                            resolved for the template to be used.  Since the "false" schema
+                            assigned to it in "hrefSchema" excludes it from the input data set,
+                            it must be resolved from the instance.
+                        </t>
+                        <t hangText="title:">
+                            The instance field matching this variable is required, and it is also
+                            allowed in the input data.  So its instance value is used to
+                            pre-populate the input data set before accepting the client's input.
+                            The client can opt to leave the instance value in place.  Since
+                            this field is required in "hrefSchema", the client cannot delete it
+                            (although it could set it to an empty string).
+                        </t>
+                        <t hangText="cc:">
+                            The "false" schema set for this in the main schema prevents this field
+                            from having an instance value.  If it is present at all, it must come
+                            from client input.  As it is not required in "hrefSchema", it may not
+                            be used at all.
+                        </t>
+                    </list>
+                </t>
                 <t>
                     So, given the following instance retrieved from "https://api.example.com/stuff":
                 </t>