Scenario:
If I DELETE a container, I expect all children of the container to be
deleted also, but not aggregate members. In order for the server to have
the logic to do that, I need some indication of what's a direct "real"
member of the container and what is only a reference. What other indication
or technique might I use, if not for ldp:contains ?
- Cody
On Fri, Apr 19, 2013 at 2:32 PM, Steve Speicher <sspeiche@gmail.com> wrote:
> On Fri, Apr 19, 2013 at 2:47 PM, Cody Burleson <cody.burleson@base22.com>
> wrote:
> > 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?
> >
>
> What is the scenario where this distinction is needed?
>
> --
> - Steve Speicher
>
--
Cody Burleson
Enterprise Web Architect, Base22
Mobile: +1 (214) 702-6338
Skype: codyburleson
Email: cody@base22.com
Blog: codyburleson.com
* <http://base22.com>*
*
*
*Check my free/busy
time.<http://www.google.com/calendar/embed?src=cody.burleson%40base22.com&ctz=America/Chicago%20>
*
