Skip to content

Commit 9e96dda

Browse files
clarify "relative location" wording
keywordLocation does not always contain a relative location that actually exists in a schema - because of reference navigation, its path contains keywords from multiple locations
1 parent 713c353 commit 9e96dda

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

jsonschema-core.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2718,8 +2718,8 @@ https://example.com/schemas/common#/$defs/count/minimum
27182718
</artwork>
27192719
</figure>
27202720
<t>
2721-
This information MAY be omitted only if either the relative location contains
2722-
no references or if the schema does not declare an absolute URI as its "$id".
2721+
This information MAY be omitted only if either the dynamic scope did not pass
2722+
over a reference or if the schema does not declare an absolute URI as its "$id".
27232723
</t>
27242724
<t>
27252725
The JSON key for this information is "absoluteKeywordLocation".

0 commit comments

Comments
 (0)