...
How each of these nodes is peristed in the database is discussed in
the DLM Data Model page. Lets now look at each of the defined directive nodes used in the PLF and how their use during the merge process causes such changes to appear for a user in the UI.
cp:delete
...
Directives
Any nodes in incorporated fragments that are not marked with a cp:deleteAllowed='false' attribute can be deleted from a user's layout. Such action is recorded in a top level cp:deleteSet element that contains a single cp:delete node for each node deleted from the incorporated fragments. This does not mean one entry for each node contained in the node deleted. It only represents the pruning point node.
For example, suppose that we have a fragment targeted at all users that has a "All User's Sample" tab in it having a global node ID of 'u11l1s8' and the fragment owner allowed users to delete that tab. If a user deleted that node then the PLF portion recording such a change would look like this. Notice that only the node ID for the tab is represented not everything below the tab even though the tab and all of its contents will be removed upon log-in for this user.
...
If instead the "All User's Sample" tab had three columns two of which having node IDs of 'u1l1s14' and 'u1l1s22' were deleted by the user, the delete set would look like this.
For example, suppose that an "All Users" fragment contained an "All Users Sample" tab with some helpful content.
For example It also contains to by this user
cp:editSet
TBD:mboyd: user id 23 has edit set ready for capture for this section's description.