.Net Web Services

.Net is often praised for its tools and facilities to write a new web service. True I agree, it merely takes 5 minustes if u know .net to write a new service and publish it. But after that ????
.Net do WS in its own style. user does not even need to know the fact it is remote. SOAP, forget abt it, no body knows they use it.
But what if one programmer want to introduce some feature into it, say it want to support Addressing .. ? The the fun time starts. Basically you end up with rewriting whole Web Service stack to do this, I mean to support interoperability there after.
Its better to have something closed, rather than making one half open. Using a open standard and hiding its implementation is like stranded in the rd blind folded. Either take him off the road, or remove the blind