What does a delete operation imply?

[csarven]

[Question was raised in https://github.com//pull/157#discussion_r405219429 .]

The read, write and append operations ( #149 #126 #118 ) are aligned with WAC access modes. Write covers delete in both access mode and definition. Given that context, would it be useful to introduce the notion of delete as a separate operation?

"A delete operation entails that information can be removed."

Without discussing atomicity or recursion in the definition, I'm not sure how useful it'll be, but it may support the phrase "delete operation". Tautology.

It may help to revisit this after existing requirements involving write and delete are drafted and accepted. Ditto "update" and possibly other operations that could be argued to be distinct but I don't think we want to go over board or worse redefine CRUD or something.

[csarven]

Removing a resource from a container entails: i) delete resource, ii) remove containment statement about the deleted resource, iii) delete associated resources.