The use-case granted, here's another: I'm a CMS blasting out deltas to a feed, where I know something's been updated and I own the data and the feed and I just want to damn well update it and not waste cycles doing a GET.
So all I'm saying is that the language which explains how you'd reasonably use PUT and GET, should also make it clear that PUT does what PUT does, and there's no compulsory preceding GET. -Tim
How about stating that the client SHOULD do a GET before editing?