Re: [Specifications] Should we introduce a property to associate operations and their target directly to an entity?

>I know you're right about the spec but it only means that PUT is used to create or update a resource >identified by the requested URL. Otherwise nothing forbids new resources from being created by side >effects of a POST. In fact it's such a common pattern

This not a rule - it's just happens it is used in some circumstances. I imagine that POST'ing a resource to `/members` may end up with a `Location` header point to a URL that is not related to the newly created resource in any way - it may point client to a resource from which it can obtain i.e. status of the task submitted for processing. In case of members, it may be a process of user verification, etc.

-- 
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/3#issuecomment-336649121 using your GitHub account

Received on Saturday, 14 October 2017 17:06:34 UTC