Skip to content

Commit 45910eb

Browse files
committed
Updating fragmentResolution wording
1 parent 300600a commit 45910eb

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

proposals/json-schema-hypermedia.xml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -291,18 +291,17 @@
291291

292292
<section title="fragmentResolution">
293293
<t>
294-
This property indicates the fragment resolution protocol to use for resolving fragment identifiers in URIs within the instance representations.
295-
This applies to the instance object URIs and all children of the instance object's URIs.
296-
The default fragment resolution protocol is "json-pointer", which is defined below.
297-
Other fragment resolution protocols MAY be used, but are not defined in this document.
294+
When addressing a JSON document, the fragment part of the URI may be used to refer to a particular instance within the document, relative to the document root.
298295
</t>
299296

300297
<t>
301-
The fragment identifier is based on <xref target="RFC3986">RFC 3986, Sec 5</xref>, and defines the mechanism for resolving references to entities within a document.
298+
This keyword indicates the method to use for finding the appropriate instance within a document, given the fragment part.
299+
The default fragment resolution protocol is "json-pointer", which is defined below.
300+
Other fragment resolution protocols MAY be used, but are not defined in this document.
302301
</t>
303302

304303
<t>
305-
Note that if the instance is described by a schema providing the a link with "root" relation, or such a link is provided in using the <xref target="I-D.nottingham-http-link-header">HTTP Link header</xref>, then all fragment resolution should be resolved relative to the target of the root link.
304+
If the instance is described by a schema providing the a link with "root" relation, or such a link is provided in using the <xref target="I-D.nottingham-http-link-header">HTTP Link header</xref>, then the target of the "root" link should be considered the document root for the purposes of all fragment resolution methods that use the document structure (such as "json-pointer").
306305
The only exception to this is the resolution of "root" links themselves.
307306
</t>
308307

0 commit comments

Comments
 (0)