@@ -3130,20 +3130,6 @@ https://example.com/schemas/common#/$defs/count/minimum
31303130 <t >Type name: application</t >
31313131 <t >Subtype name: schema+json</t >
31323132 <t >Required parameters: N/A</t >
3133- <t >
3134- Optional parameters:
3135- <list style =" hanging"
3136- <t hangText =" schema:"
3137- A non-empty list of space-separated URIs, each identifying
3138- a JSON Schema resource. The instance SHOULD successfully
3139- validate against at least one of these meta-schemas.
3140- Non-validating meta-schemas MAY be included for purposes such
3141- as allowing clients to make use of older versions of
3142- a meta-schema as long as the runtime instance validates
3143- against that older version.
3144- </t >
3145- </list >
3146- </t >
31473133 <t >
31483134 Encoding considerations: Encoding considerations are
31493135 identical to those specified for the "application/json"
@@ -3174,20 +3160,7 @@ https://example.com/schemas/common#/$defs/count/minimum
31743160 <list >
31753161 <t >Type name: application</t >
31763162 <t >Subtype name: schema-instance+json</t >
3177- <t >
3178- Required parameters:
3179- <list style =" hanging"
3180- <t hangText =" schema:"
3181- A non-empty list of space-separated URIs, each identifying
3182- a JSON Schema resource. The instance SHOULD successfully
3183- validate against at least one of these schemas.
3184- Non-validating schemas MAY be included for purposes such
3185- as allowing clients to make use of older versions of a schema
3186- as long as the runtime instance validates against that
3187- older version.
3188- </t >
3189- </list >
3190- </t >
3163+ <t >Required parameters: N/A</t >
31913164 <t >
31923165 Encoding considerations: Encoding considerations are
31933166 identical to those specified for the "application/json"
0 commit comments