We need to design 1. PHP and 2. REST API changes to allow deleting content object translation without deleting the whole object. And describe the behavior as proposed in the epic.

Open question is what customers need here.

What has been reported that they need is:

• Deleting a translation from all versions of a content (including published version, drafts and archives)
  • This is somewhat in contrast to how versions are treated today in the system, with exception of drafts the system normally don't allow editing/changing versions

What would make more technically sense:

• Deleting a translation from a version and return a draft (UI code can handle directly publishing if needed, it can also offer user to delete all prior versions with given language if user really want to wipe out history)

In both cases should probably throw if user tries to delete last remaining translation, for that content/version deletion is more suitable

Any input on this is welcome.