Steve Maine is in the midst of the perennial debate between SOAP and REST, and I feel compelled to add my two cents...
At the XML DevCon last week I noticed that it continues to be fashionable to bash the existing Web Services standards as being too complex and unwieldy (which in several notable cases is true, but it's what we have to work with at this point) but that doesn't change the fact that they solve real problems. I've always had a sneaking suspicion that people heavily into REST as a concept favored it mostly out of laziness, since it is undeniably a much simpler model than the SOAP/WS-* stack. On the other hand, it fails to solve a bunch of real problems that SOAP/WS-* does. WS-Addressing is a good example.
I spent two years developing an application that involved hardware devices attached to large power transformers and industrial battery systems that needed to communicate back to a central data collection system. We used SOAP to solve that particular problem, since it was easy to get the data where it needed to go, and we could use WS-Security to provide a high level of data encryption to our customers. (Utility companies like that.) However, we had one customer who would only allow us to get data from the monitors on their transformers through a store-and-forward mechanism, whereby the monitors would dump their data to a server inside their firewall, and we could pick up the data via FTP. This is a great place for WS-Addressing, since all the addressing information staid inside the SOAP document, and it didn't matter if we stored it out to disk for a bit. There is no way that REST could have solved this particular problem. Or, at least, no way without coming up with some truly bizarre architecture that would never be anything but gross.
REST is great for solving very simple application scenarios, but that doesn't make it a replacement for SOAP. I agree that many of the WS-* standards are getting a bit out of hand, but I also agree with Don Box's assessment (in his "WS-Why?" talk last week) that given the constraints, WS-Addressing and WS-Security are the simplest solutions that solve the problem. There's a reason why these are non-trivial specs. They solve non-trivial problems.
So rather than focusing on REST vs. SOAP, it's more interesting and appropriate to look at the application scenarios and talk about which is the simplest solution that addresses all the requirements. I don't think they need to be mutually exclusive.