I’ve been meaning to be more involved in this, but it’s been moving too fast, and I’ve been too busy with other things (like a job).
A comment by Tim Bray in today’s TAG meeting minutes, however, prompted me to check back;
over in son-of-RSS-land, we’re converging on using POST for entry creation/update/deletion for reasons that seem good
My concern with that is that the resulting API would not be RESTful, and I thought that the objective was that it should be (as the name RestEchoApi suggests!). It isn’t RESTful, because in the context of HTTP, tunneling methods over POST – even uniform ones – reduces visibility.
I added my two cents.