I work with SOAP somewhat. That page explains/summarizes it better than I have seen anywhere else (I still struggle with the RPC vs doc/lit vs wrapped thing, and how to tell which one is being used), and it may be why I've never gotten a "warm & fuzzy" feeling of understanding about it. On the other hand, I feel comfortable with XML schemas, even though I don't know it all off the top of my head.
I don't mind schemas. But I prefer nice simple message passing - I construct a request, pass it over, get back a reply. Easy to understand, and you can do it without a huge amount of overhead.
S stands for Simple
Re: S stands for Simple