From c11eab495839bdaab5f51e06bc153c1260d51611 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Tue, 30 Jun 2020 00:51:36 +0200 Subject: [PATCH] Specify delete container without recursion --- main/resource-access.bs | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/main/resource-access.bs b/main/resource-access.bs index e62ac650..5724d27e 100644 --- a/main/resource-access.bs +++ b/main/resource-access.bs @@ -70,16 +70,9 @@ When a contained resource is deleted, the server MUST also delete the associated To delete an ACL resource (see [[#ar-wac]]), an `acl:agent` MUST have `acl:Control` privileges per the ACL inheritance algorithm on the resource directly associated with it. [[Source](https://github.com/solid/specification/issues/145)] -[[Source](https://github.com/solid/specification/issues/41)] -A container can only be deleted if it contains no resources ([[#resource-containment]]). When a `DELETE` method request is made to a container, the server MUST delete the contained resources except containers. To recursively delete a container, server MUST accept client's `DELETE` request including the HTTP `Prefer` header with `return="representation"; include="http://www.w3.org/ns/ldp#PreferContainment"` (see [[!LDP]]'s Preferences on the Prefer Request Header). Server MUST respond with the `409` status code and response body including containment triples about unaffected resources of the delete request for agents with `acl:Read` privilege per the ACL inheritance algorithm. -[[Source](https://github.com/solid/specification/issues/132#issuecomment-562314633)] -[[Source](https://github.com/solid/specification/issues/41#issuecomment-580212776)] -[[Source](https://github.com/solid/specification/issues/41#issuecomment-582154098)] - -Server MAY omit the `DELETE` method in the HTTP response header `Allow` in response to safe method requests to a container, if `acl:agent` does not have the `acl:Write` privilege to a resource under its URI path. - -[[Source](https://github.com/solid/specification/issues/41)] +When a `DELETE` method request is made to a container, the server MUST delete the container if it contains no resources. If the container contains resources, the server MUST respond with the `409` status code and response body describing the error. +[[Source](https://github.com/solid/specification/pull/187/files/b7426e95a1613e08195a853a4d0a403b7030f494#r447130915)] This section is non-normative.