Use Collections to manage process state.
Related and Conflicting Proposals
Remove process state from documents (like PacePubStatusResource, unlike PacePubControl), improving their reusability in processes unknown to the Atom specifications, and enabling non-Atom representations (e.g. RSS, images) to participate in Atom processes.
Keep Atom process-neutral (unlike PacePubStatusResource).
Permit parties to participate in a process without knowledge of that process, in whole or in part.
Add a "type" attribute for collections in both atomcoll and atomserv, whose value is a string identifying the type of the collection (I'd prefer URIs for extensions because I expect them to be common place). Predefine standard types "published" and "draft". [Note: I'm unclear how "contents" would be used, but I wonder if "type" couldn't replace it?]
Add a section (Appendix?) describing how process state can be managed using collections. e.g. POST an entry to a draft collection makes it a draft entry, POSTing one to a "published" collection, publishes it, and for other extension collection types, POSTing an entry there puts it in the state associated with the collection.