Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior

I prefer Henry's proposal of using ldp:contains in addition to
ldp:membershipPredicate
or ldp:membershipPredicateInverse because it provides a clear mechanism for
properly managing resources.

Without that, how would I be able to distinguish between resources that a
container actually owns and those which it simply refers to? I would have
to come up with some mechanism and this seems to be a reasonable one, so
why not just go with it and make it standard?

-- 
Cody