Skip to content

Allow "headerSchema" for content negotiation #426

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
Oct 9, 2017
Merged

Allow "headerSchema" for content negotiation #426

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
15 changes: 12 additions & 3 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1235,9 +1235,18 @@ GET /foo/
</t>

<t>
If this property's value is not specified, then the value should be taken to be
"application/json". Hyper-Schema authors SHOULD NOT use a protocol-specific
value in <xref target="targetHints">"targetHints"</xref> for this purpose.
For protocols supporting content-negotiation, implementations MAY choose to
describe possible target media types using protocol-specific information in
<xref target="headerSchema">"headerSchema"</xref>. If both protocol-specific
information and "mediaType" are present, then the value of "mediaType" MUST
be compatible with the protocol-specific information, and SHOULD indicate
the media type that will be used in the absence of content negotiation.

</t>
<t>
When no such protocol-specific information is available, or when the
implementation does not recognize the protocol involved, then the value
SHOULD be taken to be "application/json".
</t>

<figure>
Expand Down