This page provides links to a number of works on enabling loosely coupled evolution of web and web service components using XML Schema, WSDL, WS-Policy and other languages authored by myself, then other authors.
W3C Web architecture XML Versioning finding for issue 41-XMLVersioning
- The W3C Architecture of the World-Wide Web, particularly in the areas of formal models, diagrams, extensibility, versioning.
- XML.com articles
- WSDL 2.0 Primer section on versioning
- Guide to Versioning using new Schema 1.1 features
- Google search of my blog
- Which Schema wildcard namespace value to use, ##other or ##any?
- Forwards compatibility with version #s requires version # mapping
- SOA Principles
- XML 2004 talk extending and versioning XML Languages( 200K PDF), a view of the previous articles.
- Providing Compatible Schema Evolution, a paper that examines todays and potential tomorrow solutions for compatible evolution
- Examining Element and Wildcards as siblings
- Four major constraints in achieving Loosely Coupled Web Services, an article about extensibility, versioning, asynchrony and standardization.
- Web Services or Distributed Objects looks at extensibility and whether Web services are "Webish" or Distributed Objects
- I've gradually come to the realization that versioning is all about substitubility, and substitutability really needs to be in V1 to achieve forwards compatibility.
- Compatibility and Evolution in an Asynch World
- Where substitution Rules can be found
- Why putting extra structure in V1.0 is good
- Protocol Extensibility and Versioning
- My ongoing attempt at defining a Formal Compatibility Definition.
There are numerous discussions on more tightly coupled evolution of services, particularly requiring some action on both sides.