Skip to content

Commit 30ec437

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 f3727f1 commit 30ec437

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
@@ -2712,8 +2712,8 @@ https://example.com/schemas/common#/$defs/count/minimum
27122712
</artwork>
27132713
</figure>
27142714
<t>
2715-
This information MAY be omitted only if either the relative location contains
2716-
no references or if the schema does not declare an absolute URI as its "$id".
2715+
This information MAY be omitted only if either the dynamic scope did not pass over a reference
2716+
or if the schema does not declare an absolute URI as its "$id".
27172717
</t>
27182718
<t>
27192719
The JSON key for this information is "absoluteKeywordLocation".

0 commit comments

Comments
 (0)