Skip to content

Commit ef14ca7

Browse files
committed
restate requirements for scheam location; remove note
1 parent 4e7be40 commit ef14ca7

File tree

1 file changed

+4
-10
lines changed

1 file changed

+4
-10
lines changed

jsonschema-core.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2104,16 +2104,10 @@ When represented in JSON, the key for this information MUST be "evaluationPath".
21042104

21052105
### Schema Location
21062106

2107-
The schema location is the absolute, dereferenced location of the schema object
2108-
that produced a result. The value MUST be expressed using the canonical IRI of
2109-
the relevant schema resource plus a JSON Pointer fragment that indicates the
2110-
schema object that produced the output. It MUST NOT include by-reference
2111-
applicators such as `$ref` or `$dynamicRef`.[^14]
2112-
2113-
[^14]: Note that "absolute" here is in the sense of "absolute filesystem path"
2114-
(meaning the complete location) rather than the "absolute-IRI" terminology from
2115-
RFC 3987 (meaning with scheme and without fragment). Schema locations will have
2116-
a fragment in order to identify the specific schema object.
2107+
The schema location is the canonical URI of the schema object plus a JSON
2108+
Pointer fragment indicating the subschema that produced a result. In contrast
2109+
with the evaluation path, the schema location MUST NOT include by-reference
2110+
applicators such as `$ref` or `$dynamicRef`.
21172111

21182112
```
21192113
https://example.com/schemas/common#/$defs/allOf/1

0 commit comments

Comments
 (0)