From 4a1035137f90ffff425bea257f48858dcd0d301c Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Sat, 26 Sep 2020 13:25:23 -0700 Subject: [PATCH] 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. --- jsonschema-core.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 6288e746..999009e8 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -2705,11 +2705,18 @@
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. + + 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. +