null
New essay: Expect More.
I understand and accept Clemens Vasters stated requirements that For reasons of processing speed and efficiency I would like my stuff to stay very tightly coupled, early bound and with specialized, auto-generated parsers/serializers with a high degree of reliance on stable WSDL and XSD at all times; like RPC stubs/proxies. I am curious to see if he will accept mine, namely that Given the distributed nature of the internet, what is of paramount importance is that systems be designed and implemented in manners that enable change to be accommodated in both upwards and downwards compatible manners.
I believe that I have detailed an approach which satisfies both criteria (relying heavily on Dare's XML Schema Design Patterns document), but am open to discussion of other approaches which addresses both sets of requirements.