Skip to content

Clarify what "absolute" means for keyword absolute location #999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 1, 2020
Merged

Clarify what "absolute" means for keyword absolute location #999

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2705,11 +2705,18 @@
<section title="Keyword Absolute Location">
<t>
The absolute, dereferenced location of the validating keyword. The value MUST
be expressed as an absolute URI using the canonical URI of the relevant
be expressed as a full URI using the canonical URI of the relevant
schema object, and it MUST NOT include by-reference applicators
such as "$ref" or "$dynamicRef" as non-terminal path components.
It MAY end in such keywords if the error or annotation is for that
keyword, such as an unresolvable reference.
<cref>
Note that "absolute" here is in the sense of "absolute filesystem path"
(meaning the complete location) rather than the "absolute-URI"
terminology from RFC 3986 (meaning with scheme but without fragment).
Keyword absolute locations will always have a fragment in order to
identify the keyword.
</cref>
</t>
<figure>
<artwork>
Expand Down