DeveloperWorks has a new article published on REST. Unfortunately I was able to find several significant problems with it in a matter of minutes.
The design is awful: methods in the URLs.
The "logic" on when to apply REST vs. "heavyweight" SOA is simply unfounded. Please: "As your application environment grows, it's likely you'll abstract away from the REST implementation details more and more... It shouldn't be too hard to extract the actual business logic behind the services and rewrap it in a SOAP package in the new environment."
Huh? That and the discussion at the beginning about large vs. small organizations using heavyweight SOA or REST. The author should follow his own advice:
"Take some time to think about this: it'll pay for itself in the long run!"