Skip to content

fix media type in examples #971

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.

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
Changes from all commits
Commits
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
10 changes: 5 additions & 5 deletions jsonschema-core.xml
Original file line number Diff line number Diff line change
Expand Up @@ -1950,7 +1950,7 @@
<figure>
<artwork>
<![CDATA[
Content-Type: application/json;
Content-Type: application/schema-instance+json;
schema="https://example.com/my-hyper-schema#"
]]>
</artwork>
Expand All @@ -1964,7 +1964,7 @@
<figure>
<artwork>
<![CDATA[
Content-Type: application/json;
Content-Type: application/schema-instance+json;
schema="https://example.com/alice https://example.com/bob"
]]>
</artwork>
Expand All @@ -1977,9 +1977,9 @@
<figure>
<artwork>
<![CDATA[
Accept: application/json;
Accept: application/schema-instance+json;
schema="https://example.com/qiang https://example.com/li",
application/json;
application/schema-instance+json;
schema="https://example.com/kumar"
]]>
</artwork>
Expand All @@ -1995,7 +1995,7 @@
indicate that the client can accept several media types.
In the above example, note that the two media types differ
only by their schema parameter values. This requests an
application/json representation that conforms to at least one
application/schema-instance+json representation that conforms to at least one
of the identified schemas.
</t>

Expand Down