In the DMA view, you've combined access control with versioning behavior. Personally, I think you'd better look at a richer scheme. By separating the two, I avoid confusion between the information management and the information maintenance activities. Many current products only support a single Editor, but a larger set of possible Editors. I am unclear how I can tell the difference between making a new person capable of editting versus his actually being in the process of editting and needing control over the document state.
Current implementations permit multiple branched versions.
Lock Ownership and Contact information cannot be required. This information is often privileged. The privilege may not be tied to who has access to the document. I am uncomfortable with your redefinition of delete. Versioning I don't understand your versioning model.