Origin of the REST API pattern: PUT takes what GET returns

We use a pattern where a client (e.g. Angular) can get a set of resource representations (aka entities) using GET /things and return any one of those entities as the payload to PUT /things/{id}.

All well and good (as long as the id is in the uri and not in the payload) unless the GET response entities include summary information that makes no sense in a PUT.

Be that as it may, I'm looking for the origin or proponents of this GET-out, PUT-in pattern (with or without modification for reality) in order to clearly show that it is not part of the REST specification. I have found cases where purely idiomatic choices such as this have been beatified as being "RESTful", and exceptions -- by extension -- heretical. I think this process is called pseudepigrapha.

Any ideas?