Skip to content

Commit c0373a3

Browse files
committed
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.
1 parent 8a27a0c commit c0373a3

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

jsonschema-hyperschema.xml

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2389,21 +2389,6 @@ Link: <https://api.example.com/trees/1/nodes/456> rev=up
23892389
also apply, with appropriate adjustments (e.g. "anchor" as an LDO keyword rather
23902390
than an HTTP Link header attribute).
23912391
</t>
2392-
<section title='"self" Links'>
2393-
<t>
2394-
When link relation of "self" is used to denote a full representation of an
2395-
object, the user agent SHOULD NOT consider the representation to be the
2396-
authoritative representation of the resource denoted by the target URI if
2397-
the target URI is not equivalent to or a sub-path of the URI used to request
2398-
the resource representation which contains the target URI with the "self"
2399-
link.
2400-
<cref>
2401-
It is no longer clear what was intended by the "sub-path" option in
2402-
this paragraph. While paths are defined as a hierarchical system
2403-
by RFC 3986, there semantics of the hierarchy are not defined.
2404-
</cref>
2405-
</t>
2406-
</section>
24072392
<section title="Target Attributes">
24082393
<t>
24092394
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
24422427
match the link's "targetHints" values.
24432428
</t>
24442429
</section>
2430+
<section title='"self" Links'>
2431+
<t>
2432+
When link relation of "self" is used to denote a full representation of an
2433+
object, the user agent SHOULD NOT consider the representation to be the
2434+
authoritative representation of the resource denoted by the target URI if
2435+
the target URI is not equivalent to or a sub-path of the URI used to request
2436+
the resource representation which contains the target URI with the "self"
2437+
link.
2438+
<cref>
2439+
It is no longer clear what was intended by the "sub-path" option in
2440+
this paragraph. While paths are defined as a hierarchical system
2441+
by RFC 3986, there semantics of the hierarchy are not defined.
2442+
</cref>
2443+
</t>
2444+
</section>
24452445
</section>
24462446
<!--
24472447
<section title="IANA Considerations">

0 commit comments

Comments
 (0)