I suppose that boils down to prescriptivism vs descriptivism debate. I'm a prescriptivist in that case: there's Roy's thesis that defines what he meant by REST, and if an API (no matter how useful and successful) doesn't fit that description, it should be called something else.

I agree we need a good word for those HTTP-but-not-quite-REST APIs. I simply call them "HTTP APIs", but maybe SIMPLE, NoRPC or REST 2.0 will take off ;)