Skip to content

Commit 5794814

Browse files
require that $schema cannot contain a fragment (#1633)
* require that $schema cannot contain a fragment * Update specs/jsonschema-core.md Co-authored-by: Jason Desrosiers <jdesrosi@gmail.com> * add link to normalization requirements --------- Co-authored-by: Jason Desrosiers <jdesrosi@gmail.com>
1 parent 6d8d369 commit 5794814

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

specs/jsonschema-core.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -931,8 +931,9 @@ resources, unless such a resource itself declares a different dialect by
931931
including the `$schema` keyword with a different value.
932932

933933
The value of this keyword MUST be an
934-
[IRI](https://www.rfc-editor.org/info/rfc3987) (containing a scheme) and this
935-
IRI MUST be normalized.
934+
[absolute IRI](https://www.rfc-editor.org/info/rfc3987) (without a fragment).
935+
This IRI MUST be normalized, the rules for which can be found in the
936+
[next section](#dereferencing).
936937

937938
The `$schema` keyword SHOULD be used in the document root schema object, and MAY
938939
be used in the root schema objects of embedded schema resources. This keyword
@@ -943,7 +944,7 @@ schema resources.)
943944
Values for this property are defined elsewhere in this and other documents, and
944945
by other parties.
945946

946-
### Base IRI, Anchors, and Dereferencing
947+
### Base IRI, Anchors, and Dereferencing {#dereferencing}
947948

948949
To differentiate between schemas in a vast ecosystem, schema resources are
949950
identified by

0 commit comments

Comments
 (0)