Skip to content

Commit 78413ee

Browse files
authored
Merge pull request #999 from handrews/abs
Clarify what "absolute" means for keyword absolute location
2 parents 27f89d4 + 4a10351 commit 78413ee

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
@@ -2702,11 +2702,18 @@
27022702
<section title="Keyword Absolute Location">
27032703
<t>
27042704
The absolute, dereferenced location of the validating keyword. The value MUST
2705-
be expressed as an absolute URI using the canonical URI of the relevant
2705+
be expressed as a full URI using the canonical URI of the relevant
27062706
schema object, and it MUST NOT include by-reference applicators
27072707
such as "$ref" or "$dynamicRef" as non-terminal path components.
27082708
It MAY end in such keywords if the error or annotation is for that
27092709
keyword, such as an unresolvable reference.
2710+
<cref>
2711+
Note that "absolute" here is in the sense of "absolute filesystem path"
2712+
(meaning the complete location) rather than the "absolute-URI"
2713+
terminology from RFC 3986 (meaning with scheme but without fragment).
2714+
Keyword absolute locations will always have a fragment in order to
2715+
identify the keyword.
2716+
</cref>
27102717
</t>
27112718
<figure>
27122719
<artwork>

0 commit comments

Comments
 (0)