W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2012

Re: ldp-ISSUE-30 (bugtrack): Hierarchical bugtracking service [Use Cases and Requirements]

From: Richard Cyganiak <richard@cyganiak.de>
Date: Wed, 7 Nov 2012 21:44:07 +0000
Cc: Arnaud Le Hors <lehors@us.ibm.com>, public-ldp-wg@w3.org
Message-Id: <F280D941-9A6F-466C-B564-0827D31DDBDC@cyganiak.de>
To: nathan@webr3.org
On 6 Nov 2012, at 19:25, Nathan wrote:
> All use cases, and all desired functionality (although less is more) can be done using GET/PUT/DELETE/PATCH, Why use, and moreover constrain, POST?

PATCH requires a new format. POST doesn't.

POST is the most appropriate method for adding to a collection, especially if the server is to choose the URI for the new item.

Do you feel that POST is being constrained when the target of the POST request is different from the resource whose properties/members are being managed through the POST request?

Received on Wednesday, 7 November 2012 21:44:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:33 UTC