title: If I change a WSDL's targetNamespace, will it break existing consumers?
body: <p>I'm currently working on a SOA versioning strategy for my organization. I'm trying to determine where we should store the version number (Major.Minor) in the WSDL. There will be non-breaking changes made to the service interface (i.e. adding new operations) and for these non-breaking changes we'll just increment the minor number. We are considering using the WSDL's targetNamespace to store the version but we're afraid changing the WSDL's targetNamespace from something like 1.0 to 1.1 might result in a breaking change for some clients. </p>
  
  <p>Can anyone tell me the effects that changing the targetNamespace of a WSDL will have on existing consumers of that particular web service.  I've run some tests using WCF and I've found that it doesn't break existing applications that use the service.  However, I'm wondering if this will still be true from other non-.NET clients? </p>
  
  <p>Note: I do realize that changing the targetNamespace of a XSD referenced by the WSDL does result in a breaking change.</p>