Skip to content

Remove remaining media-type param references #1181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 17, 2022
Merged

Remove remaining media-type param references #1181

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 1 addition & 28 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3114,20 +3114,6 @@ https://example.com/schemas/common#/$defs/count/minimum
<t>Type name: application</t>
<t>Subtype name: schema+json</t>
<t>Required parameters: N/A</t>
<t>
Optional parameters:
<list style="hanging">
<t hangText="schema:">
A non-empty list of space-separated URIs, each identifying
a JSON Schema resource. The instance SHOULD successfully
validate against at least one of these meta-schemas.
Non-validating meta-schemas MAY be included for purposes such
as allowing clients to make use of older versions of
a meta-schema as long as the runtime instance validates
against that older version.
</t>
</list>
</t>
<t>
Encoding considerations: Encoding considerations are
identical to those specified for the "application/json"
Expand Down Expand Up @@ -3158,20 +3144,7 @@ https://example.com/schemas/common#/$defs/count/minimum
<list>
<t>Type name: application</t>
<t>Subtype name: schema-instance+json</t>
<t>
Required parameters:
<list style="hanging">
<t hangText="schema:">
A non-empty list of space-separated URIs, each identifying
a JSON Schema resource. The instance SHOULD successfully
validate against at least one of these schemas.
Non-validating schemas MAY be included for purposes such
as allowing clients to make use of older versions of a schema
as long as the runtime instance validates against that
older version.
</t>
</list>
</t>
<t>Required parameters: N/A</t>
<t>
Encoding considerations: Encoding considerations are
identical to those specified for the "application/json"
Expand Down