- From: Wilde, Erik <Erik.Wilde@emc.com>
- Date: Wed, 30 Jan 2013 12:05:55 -0500
- To: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
hello ashok. thanks for the concise write-up! On 2013-01-30 16:23 , "Ashok Malhotra" <ashok.malhotra@oracle.com> wrote: >Composition and Aggregation > >E. If you delete a container you delete everything it contains. >For nested containers this leads to a cascaded delete. > >F. If you do not want a member to be deleted when the container is >deleted, >do not include the member in the containers but rather include a link to >the >member in the container. > >E and F follow the AtomPub model. E for AtomPub means you DELETE everything you have POSTed. since AtomPub has no nested collections, there is no cascaded delete. F is not quite as henry was illustrating it. in the model he described, we clearly have to distinguish entries (the metadata stuff) and content (the "payload" of an entry). rephrased with these terms, it should read: if you do not want content to be deleted when a collection is deleted, do not embed the content in the entry; instead, include it by linking to it. cheers, dret.
Received on Wednesday, 30 January 2013 17:06:50 UTC