Skip to content

Commit c63e873

Browse files
committed
contentSchema: type MUST be a schema and instance SHOULD follow the data model
1 parent 5ebe3ca commit c63e873

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

jsonschema-validation.xml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -530,7 +530,7 @@
530530
format attribute and instance SHOULD succeed. All format attributes defined
531531
in this section apply to strings, but a format attribute can be specified
532532
to apply to any instance types defined in the data model defined in the
533-
<xref target="json-schema">core JSON Schema.</xref>
533+
<xref target="json-schema">core JSON Schema</xref>.
534534
<cref>
535535
Note that the "type" keyword in this specification defines an "integer" type
536536
which is not part of the data model. Therefore a format attribute can be
@@ -1017,13 +1017,16 @@
10171017
<t>
10181018
If the instance is a string, and if "contentMediaType" is present, this
10191019
property contains a schema which describes the structure of the string.
1020+
The string SHOULD be in a format compatible with the data model defined in the
1021+
<xref target="json-schema">core JSON Schema</xref>.
10201022
</t>
10211023
<t>
10221024
This keyword MAY be used with any media type that can be mapped into
10231025
JSON Schema's data model.
10241026
</t>
10251027
<t>
1026-
The value of this property SHOULD be ignored if "contentMediaType" is not present.
1028+
The value of this property MUST be a valid JSON schema. It SHOULD be ignored if
1029+
"contentMediaType" is not present.
10271030
</t>
10281031
</section>
10291032

0 commit comments

Comments
 (0)