Skip to content

Commit 91ad6fd

Browse files
Henry H. AndrewsHenry H. Andrews
Henry H. Andrews
authored and
Henry H. Andrews
committed
Fix typos in Hyper Schema spec.
Remove some stray words that somehow found their ways into the wrong sentences. Fixes old repo issues (filed by vanthome): json-schema/json-schema#89 json-schema/json-schema#100
1 parent bdb9ccc commit 91ad6fd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

jsonschema-hyperschema.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@
295295
</t>
296296

297297
<t>
298-
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="RFC5988">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").
298+
If the instance is described by a schema providing a link with "root" relation, or such a link is provided in using the <xref target="RFC5988">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").
299299
The only exception to this is the resolution of "root" links themselves.
300300
</t>
301301

@@ -420,7 +420,7 @@
420420
</t>
421421

422422
<t>
423-
The base URI to be used for relative URI resolution SHOULD is defined as follows:
423+
The base URI to be used for relative URI resolution is defined as follows:
424424
<list>
425425
<t>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"</t>
426426
<t>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</t>

0 commit comments

Comments
 (0)