Re: [Specifications] Should we introduce a property to associate operations and their target directly to an entity? from Tomasz Pluskiewicz via GitHub on 2017-10-14 (public-hydra-logs@w3.org from October 2017)

From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
Date: Sat, 14 Oct 2017 09:07:55 +0000
To: public-hydra-logs@w3.org
Message-ID: <issue_comment.created-336621946-1507972060-sysbot+gh@w3.org>

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 to be created by side effects of a POST. In fact it's such a common pattern

POST a new representation to a collection
```
POST /members HTTP/1.1

{
  "name": "Tomasz",
  "description": "I wan to be a member"
}
```

The server returns a link to the **new** resource
```
HTTP/1.1 201 Created
Link: </members/tomasz>
```

There you go. I created a new resource using POST. 

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

Received on Saturday, 14 October 2017 09:07:43 UTC