Skip to content

Commit 4a10351

Browse files
committed
Clarify what "absolute" means for kwd loc
It is like absolute filesystem paths, not like absolute-URI from RFC 3986. In fact, an absolute keyword location can never be an RFC 3986 absolute-URI because a fragment must always be present to identify the keyword.
1 parent d432786 commit 4a10351

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

jsonschema-core.xml

+8-1
Original file line numberDiff line numberDiff line change
@@ -2705,11 +2705,18 @@
27052705
<section title="Keyword Absolute Location">
27062706
<t>
27072707
The absolute, dereferenced location of the validating keyword. The value MUST
2708-
be expressed as an absolute URI using the canonical URI of the relevant
2708+
be expressed as a full URI using the canonical URI of the relevant
27092709
schema object, and it MUST NOT include by-reference applicators
27102710
such as "$ref" or "$dynamicRef" as non-terminal path components.
27112711
It MAY end in such keywords if the error or annotation is for that
27122712
keyword, such as an unresolvable reference.
2713+
<cref>
2714+
Note that "absolute" here is in the sense of "absolute filesystem path"
2715+
(meaning the complete location) rather than the "absolute-URI"
2716+
terminology from RFC 3986 (meaning with scheme but without fragment).
2717+
Keyword absolute locations will always have a fragment in order to
2718+
identify the keyword.
2719+
</cref>
27132720
</t>
27142721
<figure>
27152722
<artwork>

0 commit comments

Comments
 (0)