I'm not sure what you're thinking of. What I've see is where a transaction resource is expressed as a collection of modified documents. E.g., in pseudo JSON:

I'm not sure what you're thinking of. What I've see is where a transaction resource is expressed as a collection of modified documents. E.g., in pseudo JSON: [ doc1, doc2, doc3 ] Usually each doc consists of some metadata (at least the doc URI, probably a revision number of the base document, maybe more depending) and the modified document content. (actually, it might be better like this: { "uri1": doc1, "uri2": doc2, "uri3": doc3 }) I'm not sure what your objection is, but this seems pretty generic to me. So the client GETs documents. It modifies some, puts them in a collection to form the transaction and POSTs them back to the store.