Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] from Wilde, Erik on 2013-03-19 (public-ldp-wg@w3.org from March 2013)

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Tue, 19 Mar 2013 15:15:44 -0400
To: Henry Story <henry.story@bblfish.net>, Linked Data Platform Working Group <public-ldp-wg@w3.org>
CC: Steve Speicher <sspeiche@gmail.com>
Message-ID: <CD6E06FD.F8B0%erik.wilde@emc.com>

hello henry.

On 2013-03-19 8:01 , "Henry Story" <henry.story@bblfish.net> wrote:
>currently there is no way of knowing which members are contained objects
>that could be deleted if the container were deleted and which one are
>not.

good point, and this is where the simple proposal would be a simple and
clean model: whatever was POSTed to the container (as LDP resource or as
non-LDP content) will be DELETEd. whatever was linked remains unaffected.

cheers,

dret.

Received on Tuesday, 19 March 2013 19:16:27 UTC