Skip to content

Commit 3882a38

Browse files
committed
Clarify what is meant by JSON Pointer format.
Addresses issue #328. URI fragment-encoded JSON Pointers are already handled by the "uri-reference" format, plus "pattern" if the media type supports multiple fragment types that would need to be disambiguated. Guidance on using "uri-reference" plus "pattern" belongs on the web site, so I did not add it to the spec.
1 parent 737e718 commit 3882a38

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

jsonschema-validation.xml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -878,8 +878,10 @@
878878
This attribute applies to string instances.
879879
</t>
880880
<t>
881-
A string instance is valid against this attribute if it is a valid JSON Pointer,
882-
according to <xref target="RFC6901"/>
881+
A string instance is valid against this attribute if it
882+
is a valid JSON string representation of a JSON Pointer,
883+
according to
884+
<xref target="RFC6901">RFC 6901, section 5</xref>
883885
</t>
884886
</section>
885887
</section>

0 commit comments

Comments
 (0)