Taking away fundamental rights in an 'open' and 'free' society tends to be hard to do in big chunks. Pull away too many rights at one time and you risk awakening the populace. So generally things tend to happen quietly, slowly, in small pieces and always for "good reasons". It's not so much a conspiracy but the inevitable 'function creep' of all governments. The only way to stop this creeping loss of freedom is to publicly identify it and fight to have our freedoms restored.
John Gilmore, founder of the EFF amongst other accomplishments, carefully explains just how many of our freedoms of travel, association and employment have been made subject to the U.S. government's whim. I've read a lot about Mr. Gilmore's efforts to fight this most recent theft of liberty, but I still found his latest missive compelling for its stark and simple presentation of the facts. Well worth reading.
The official schema namespace for WSDL 1.1 is http://schemas.xmlsoap.org/wsdl/. But, and here is the fun part, the schema for that namespace given in the official W3C WSDL 1.1 note and the schema for that namespace given at the actual XML namespace URL are different. But wait, it gets better. Not only are the two schemas different, they aren't even compatible with each other! I'll give the gory details below but the bottom line is that there exist two incompatible versions of the WSDL 1.1 schema, one in the W3C note and one at the actual XML namespace URL which use the same XML namespace and the same element names. Just to add to the fun the WS-I has officially approved the schema at the actual namespace URL in contradiction to the schema in the W3C WSDL 1.1 note. So now implementers get to pick which industry body they favor since they have competing, incompatible, definitions for the WSDL 1.1 schema. I suppose errors like this make it more understandable why versioning in Web Services is such a disaster.