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

On 2013-03-21 12:28 , "Andy Seaborne" <>
>I agree - links (bookmarks) are important.  Clients don't always start
>at the home page.

that's true, but if a bookmark broke, then starting from a home
page/resource, clients should be able to rediscover resources, by
repeating the process they used to discover them in the first place. by
removing all links to LDP resources, this is no longer possible, so these
resources are of no use to new clients. if the server keeps them around,
it would be nice to make them discoverable.

if we go with this strategy, we should at least add some language to the
deployment guide pointing out this consequence of the design, and list
possible strategies: create a magic (but not LDP-defined "deleted stuff"
container), or do some graceful garbage collection.



Received on Friday, 22 March 2013 05:03:20 UTC