You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 2, 2023. It is now read-only.
The base URI to be used for relative URI resolution SHOULD is defined as follows:
641
641
</p>
642
642
<blockquoteclass="text">
643
-
<p>if the data has a link defined, with a relation of "self", then the "href" value of that link is used
643
+
<p>if the data has a link defined, with a relation of "self", then the "href" value of that link is used, unless the relation of the link being resolved is also "self"
644
644
</p>
645
-
<p>if no such link exists, the URI should be resolved against the link with relation "self" belonging to the closest parent node in the JSON document
645
+
<p>otherwise, the URI should be resolved against the link with relation "self" belonging to the closest parent node in the JSON document, if it exists
646
646
</p>
647
-
<p>if no such links exist (the data and all its parents in the tree do not have a "self" link), the URI used to fetch the document should be used.
647
+
<p>otherwise, the URI used to fetch the document should be used.
648
648
</p>
649
649
</blockquote><p>
650
650
@@ -880,8 +880,7 @@ <h3>Table of Contents</h3>
880
880
<dd>
881
881
This relation indicates that the target of the link SHOULD be treated as the root or the body of the representation for the purposes of user agent interaction or fragment resolution.
882
882
All other properties of the instance objects can be regarded as meta-data descriptions for the data.
883
-
The URI of this link MUST be a fragment, specifying a location within the instance.
884
-
If it is not, this link should be ignored.
883
+
The URI of this link MUST refer to a location within the instance document, otherwise the link MUST be ignored.
885
884
886
885
</dd>
887
886
</dl></blockquote><p>
@@ -951,6 +950,12 @@ <h3>Table of Contents</h3>
951
950
952
951
<p>
953
952
The presence of a link with relation "root" alters what the root of the document is considered to be.
953
+
For fragment resolution methods (such as JSON Pointer fragments) that navigate through the document, the target of the "root" link should be the starting point for such methods.
954
+
955
+
</p>
956
+
<p>
957
+
The only exception is "root" links themselves.
958
+
When calculating the target of links with relation "root", existing "root" links MUST NOT be taken into consideration.
Because of the "root" link type's effect on URL resolution, it possible to create apparent paradoxes in URI resolution. For example, consider this response from a server:
The "profile" parameter in the "Content-Type" HTTP header defines the schema to be inside the data itself.
1038
-
But the schema defines a "root" link, which changes the document root, which seems like it should change the target of "#/schema".
1039
-
1040
-
</p>
1041
-
1042
-
1043
-
<p>
1044
-
To avoid this scenario, the following behaviour is defined: when resolving URIs for schemas, that schema MUST NOT be taken into account when calculating the document root.
This property value is advisory only, and is a schema that defines the expected structure of the JSON representation of the target of the link, if the target of the link is returned using JSON representation.
The interpretation of the data itself is performed by the news feed aggregator, which SHOULD reject any data that would not have also been interpreted as a news feed, had it been displayed in the main view.
The following properties also apply to link definition objects, and provide functionality analogous to HTML forms, in providing a means for submitting extra (often user supplied) information to send to a server.
@@ -1336,12 +1292,12 @@ <h3>Table of Contents</h3>
1336
1292
It is also separate from the "targetSchema" property, which provides a schema for the data that the client should expect to be returned when they follow the link.
<tdclass="author-text">Hors, A., Raggett, D., and I. Jacobs, “<ahref="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a>,” World Wide Web Consortium Recommendation REC-html401-19991224, December 1999 (<ahref="http://www.w3.org/TR/1999/REC-html401-19991224">HTML</a>).</td></tr>
0 commit comments