Versioning of schema documents with only code list updates
It is proposed to publish the new versions of schema documents, in which only the type of code list-valued properties is updated, as bug fix releases (i.e. to replace the current schema documents with new schema documents including the new code list type) rather than minor releases (in a new schema location).
Similar to the problem described in Versioning of importing schema documents, if these schema documents were published as minor revisions (rather than bug fixes), all schemas that import these schema documents would need to be updated too, and this would cause a cascade of schema updates.
RE: Versioning of schema documents with only code list updates - Added by Pawel Soczewski about 6 years ago
From a technical point of view, it seems that this is a good idea, but formally change encoding of codelists is not an error.
I suggested, that the modification of technical rules of encoding application schema to XML schema was recognized as a corrigendum levels of changes.