|
Having been an ardent XSLT programmer for some time, I've been more than a resentful of the push being made by the software vendors to make the SOAP/RPC model the one true religion. XSLT 1.0 has been built around a model in which content was accessible through a URI interface (via the document() function). XSLT 2.0 mitigates this somewhat with the use of the <xsl:result-document> element, which makes it possible to send SOAP messages which can in turn be processed through a different XSLT object in an asynchronous thread, but even here, the amount of boilerplate necessary to send such content begins to become mind-numbing.
I agree with both Paul's thesis and Edd's call to jetison the SOAP specification, especially given the degree to which it has sent other, more significant efforts spinning out of control. No doubt we're about to see the fractionalization of the web standards bodies into the older W3C and the more brash WS-I, but I predict that ultimately the WS-I will end up falling apart of its own poorly designed architectures and the greed of its charter members. I was excited when the W3C was formed, and even more excited when the RAND debacle resolved in favor of Royalty Free licensing. That the WS-I formed shortly thereafter was no accident, but I think that all of the objections that people raised about the danger of RAND technology will in fact manifest themselves very soon.
|
Previous Message
