XML Schema Versioning

We are trying to come up with a sound mechanism for versioning XML schema.

This is currently a 'hot topic' in my organisation and there are (as usual)
a number of contradictory views. Some want to use version attributes and
others version information within namespace declarations. Some want to
utilise validating parsers as much as possible, others are content to
perform validation processing differently. Everyone is trying to come up
with a way of minimizing the impact of changes to both the schema(s) being
changed, instance documents and any other schemas or XSLTs, etc.. which may
'include/import' them or contain bindings. Of course versioning doesn't just
apply to schema's, we also need to version other artefacts (WSDLs, XSLTs,
etc.) but it is schemas which most people seem to want to discuss.

Can anyone offer some advice from their own experience which may help us
decide.

Regards

Fraser Goffin.

_________________________________________________________________
Unlimited Internet access for only $21.95/month.  Try MSN!
http://resourcecenter.msn.com/access/plans/2monthsfree.asp

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.