Skip to content

Commit 0dc74db

Browse files
committed
Clarify wording around fragid syntaxes
Only schema+json supports two syntaxes, so only it needs a rule for disambiguating them. schema-instance+json only supports one.
1 parent bdd5108 commit 0dc74db

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

jsonschema-core.xml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -332,9 +332,9 @@
332332
<t>
333333
The use of JSON Pointers as URI fragment identifiers is described in
334334
<xref target="RFC6901">RFC 6901</xref>.
335-
For "application/schema+json", fragment identifiers matching the JSON Pointer
336-
syntax, including the empty string, MUST be interpreted as JSON Pointer fragment
337-
identifiers.
335+
For "application/schema+json", which supports two fragment identifier syntaxes,
336+
fragment identifiers matching the JSON Pointer syntax, including the empty string,
337+
MUST be interpreted as JSON Pointer fragment identifiers.
338338
</t>
339339
<t>
340340
Per the W3C's

0 commit comments

Comments
 (0)