The SOAP tragedy was my first thought. In 2000, SOAP was just coming out and I had written an XML to Javabean mapper based on reflection that was much more lea

The SOAP tragedy was my first thought. In 2000, SOAP was just coming out and I had written an XML to Javabean mapper based on reflection that was much more lean and with much higher throughput than SOAP. At that time, Microsoft was the biggest SOAP proponent and was pushing it very hard. I thought it was bloated and unnecessarily complicated to integrate and conform to, so we skipped on it. I suspect most will skip on oData too unless it is simplified. It's an architect's abstract dream and I think some people need to wake up. I suspect the only people who will choose oData are the business managers running budget legitimizing projects.