Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]

On 3/19/2013 10:51 AM, Steve Speicher wrote:
> Proposal:
> >>a) Remove the concepts of AggregateContainer and CompositeContainer. Leaving the only kind of container to be ldp:Container
> >>b) Have DELETE on a container only delete the container itself, not its members.  Introduce a "recursive delete" mechanism, that deletes the container and issues a DELETE on all its members (if the members are also containers, it recurses the delete).  The server may not be able to successfully delete the members but will at least attempt the DELETE.  It would seem unreasonable for the errors on deletion of members to be composed into a error report in that it would be infrequently used and come at a cost to produce.  Clients that need to know, could know based on some condition or minimal error response, then attempting to access member resources.
We could add a boolean recursive delete property on the container. This is sort of what SQL does.
Ashok

Received on Wednesday, 20 March 2013 20:38:15 UTC