Skip to content

Move reference to RFC 7231 above sentence about "targetSchema" purpose #468

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

Closed
wants to merge 1 commit into from
Closed

Move reference to RFC 7231 above sentence about "targetSchema" purpose #468

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
8 changes: 4 additions & 4 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1330,13 +1330,13 @@ for varname in templateData:
</section>
<section title='"targetSchema" and HTTP' anchor="targetHTTP">
<t>
"targetSchema" suggests what a client can expect for the response to an HTTP
GET or any response for which the "Content-Location" header is equal to the
request URI, and what a client should send if it replaces the resource in an
HTTP PUT request.
The relationship between a resource's representation and HTTP requests and
responses is determined by <xref target="RFC7231">RFC 7231, section 4.3.1 -
"GET", section 4.3.4 "PUT", and section 3.1.4.2, "Content-Location"</xref>.
In particular, "targetSchema" suggests what a client can expect for the
response to an HTTP GET or any response for which the "Content-Location"
header is equal to the request URI, and what a client should send if it
replaces the resource in an HTTP PUT request.
</t>
<t>
The media type of the representation is given by the "targetMediaType"
Expand Down