Skip to content

Commit 1a0d1d2

Browse files
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 1a0d1d2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

jsonschema-hyperschema.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -703,7 +703,7 @@ GET /foo/
703703

704704
<section title="targetSchema">
705705
<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.
707707
</t>
708708

709709
<section title="Security Considerations for &quot;targetSchema&quot;">

0 commit comments

Comments
 (0)