Skip to content

Commit ad91243

Browse files
committed
s/name/plain name/
1 parent adf96df commit ad91243

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

jsonschema-core.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -589,15 +589,15 @@
589589
</t>
590590
<t>
591591
To specify such a subschema identifier,
592-
the "$id" keyword is set to a URI reference with a name fragment (not a JSON Pointer fragment).
592+
the "$id" keyword is set to a URI reference with a plain name fragment (not a JSON Pointer fragment).
593593
This value MUST begin with the number sign that specifies a fragment ("#"),
594594
then a letter ([A-Za-z]),
595595
followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"),
596596
colons (":"), or periods (".").
597597
</t>
598598
<t>
599599
The effect of using a fragment in "$id" that isn't blank or doesn't follow the
600-
name syntax is undefined.
600+
plain name syntax is undefined.
601601
<cref>
602602
How should an "$id" URI reference containing a fragment with other components
603603
be interpreted? There are two cases: when the other components match

0 commit comments

Comments
 (0)