>I'd like to hear input from others here, and then I'll tell you what I think.

Notice he never onced addressed security, privacy, or authentication.

That aside, I'm all for whatever's easier. And with the Google API, a URI route would definitly be easier. If you could be secure using the URI, it would make it slam dunk decision given the limited scope of Google's Web Service.

As far as industry wide use of HTTP over URI, well that all depends on one thing in my mind... how will discoverability play out? Will it really live up to its potential? If so, and if your service is banking on that, its probably important to start laying the ground work now. For the majority of services, its a nonissue at this time.

Otherwise, for any real applications, SOAP would simplify more the complex... uh... complexify (thats not a word is it) in my opinion.