Commit 023ff76

committed

Explain "targetSchema" and HTTP PATCH.

This keeps coming up, and I believe that this clarifies the existing behavior (vs, say, using "schema" to describe PATCH input).

1 parent 6c3df61 commit 023ff76Copy full SHA for 023ff76

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -703,7 +703,7 @@ GET /foo/`
`703`	`703`
`704`	`704`	`<section title="targetSchema">`
`705`	`705`	`<t>`
`706`		`- This property provides a schema that is expected to describe the link target, including what a client can expect if it makes an HTTP GET request, and what it should send if it replaces the resource in an HTTP PUT request. This property is advisory only.`
	`706`	`+ This property provides a schema that is expected to describe the link target, including what a client can expect if it makes an HTTP GET request, and what it should send if it replaces the resource in an HTTP PUT request. The request structure for HTTP PATCH is described by the combination of this schema and the media type of the PATCH request payload. This property is advisory only.`
`707`	`707`	`</t>`
`708`	`708`
`709`	`709`	`<section title="Security Considerations for "targetSchema"">`

Comments

(0)