Make resource creation more exact and testable#263
Conversation
csarven
left a comment
There was a problem hiding this comment.
I think mention of client can be omitted altogether. Also focus on effective request URI.
Changing the requirement's focus (from clients) to servers is perhaps most useful for PATCH because it changes resource creation from MAY (RFC5789) to MUST. For PUT and POST, the requirement is actually not needed because it is already covered by RFC 7231.
Co-authored-by: Sarven Capadisli <[email protected]>
Co-authored-by: Sarven Capadisli <[email protected]>
|
Should we still guide (informative/note) the clients along the lines of: Clients can use PUT and PATCH requests to assign a URI to a resource. Clients can use POST requests to have the server assign a URI to a resource. |
|
Added commit. Have a look. Interesting that GitHub doesn't allow me to request a review from you (sort of obviously). |
No description provided.