Deleted nodes don't exist anymore in the repository from any client's point of view.
They might still exist in other contexts (e.g. another branch), or physically within the repository for internal reasons (e.g. storage optimization, concurrent editing support).
After this call succeeds, the deleted nodes MUST NOT appear in any responses according to bulk API.
If we delete a node, we implicitly remove it from its parent's containment/annotation.
(Transitively) contained/annotation nodes of deleted nodes are also deleted.
After this call succeeds, a repository MAY consider the deleted node's id to be unused, and thus allow to re-use it.
A repository also MAY disallow re-using previously deleted node ids.
Rationale: Assume we disallowed re-using node ids. If the repo uses pseudo-random new node ids, it would need to store all node ids given out ever to fulfill this constraint.
Deleted nodes don't exist anymore in the repository from any client's point of view.
They might still exist in other contexts (e.g. another branch), or physically within the repository for internal reasons (e.g. storage optimization, concurrent editing support).
After this call succeeds, the deleted nodes MUST NOT appear in any responses according to bulk API.
If we delete a node, we implicitly remove it from its parent's containment/annotation.
(Transitively) contained/annotation nodes of deleted nodes are also deleted.
After this call succeeds, a repository MAY consider the deleted node's id to be unused, and thus allow to re-use it.
A repository also MAY disallow re-using previously deleted node ids.
Rationale: Assume we disallowed re-using node ids. If the repo uses pseudo-random new node ids, it would need to store all node ids given out ever to fulfill this constraint.