Description
(This issue has morphed from the original description of "trash a piece of content" because it's impossible to write one resource/service correctly, the first time, in isolation from other operations in the same context).
Basically: spike the basic shape of the trash spec to get good REST URIs, service interfaces/methods, and useful model objects.
Was:
Per the trash spec we'll be viewing the trashing of content as a state change rather than a location change.
To this end, it should be possible to trash a piece of content (that can be trashed) by updating it via a PUT to have a status of TRASHED. The contents of the PUT should not include any other changes to the content.