the scenario is as follows: there is an schema/dtd online, which is used by the parsers to validated their documents. At one point one of the following happens: a bug is found in the schema/DTD or a new, unexpected element should be added in the document.
At this point the schema needs an updated. I guess this will impact all the standalone clients that have the schema locally cached, for example for being used in editors.
Is there a common practice for avoiding such schema modification scenarios? Phps by versioning the schema (different schema versions having different schema names). Or we should live with it, figers X-sed for users that have a cached snapshot of the schema