solid/specification

PATCH should not create resource

CxRes opened this issue · 2 comments

CxRes commented

Currently:

When a successful PUT or PATCH request creates a resource, the server MUST use the target URI to assign the URI to that resource.

This says PATCH can be used to create a resource. I believe this is inconsistent with RFC5789.

CxRes commented

Referring to #68, I am only objecting to doing with PATCH (and is not consistent with existing standards) what can be done with PUT. I have no issue, for example, with intermediate container creation.

CxRes commented

Sorry, I got that wrong (closing)!

Quoting RFC5789:

If the Request-URI does not
point to an existing resource, the server MAY create a new resource,
depending on the patch document type (whether it can logically modify
a null resource) and permissions, etc.