|
530 | 530 | format attribute and instance SHOULD succeed. All format attributes defined |
531 | 531 | in this section apply to strings, but a format attribute can be specified |
532 | 532 | 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>. |
534 | 534 | <cref> |
535 | 535 | Note that the "type" keyword in this specification defines an "integer" type |
536 | 536 | which is not part of the data model. Therefore a format attribute can be |
|
1017 | 1017 | <t> |
1018 | 1018 | If the instance is a string, and if "contentMediaType" is present, this |
1019 | 1019 | 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>. |
1020 | 1022 | </t> |
1021 | 1023 | <t> |
1022 | 1024 | This keyword MAY be used with any media type that can be mapped into |
1023 | 1025 | JSON Schema's data model. |
1024 | 1026 | </t> |
1025 | 1027 | <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. |
1027 | 1030 | </t> |
1028 | 1031 | </section> |
1029 | 1032 |
|
|
0 commit comments