Combining the Component Model and Core Modules into one
This is a long running discussion that I'd like to get some traction on and progress if possible. Basically having the 2 root modules is very confusing, and the original rationale for having them seems to no longer be justified. Therefore it would be best to amalgamate them into one Module.
However, would this impact anyone?
Would there be a large amount of work required to do so?
As always, all thoughts and opinions welcome!
Comments
For us there would be work. Not necessarily a massive amount of work, but some work would be required to our release testing framework and quite possibly our authoring tools, but that would take more analysis and probably running the updated data through our tests to look for impacts.
How will you represent a single module version in the module dependency reference set?
Perhaps renaming the modules would help with the confusion? Call one the Metadata module.
In Sweden, and probably many other countries that haven't started to use SNOMED CT that much, very few people know that the international release is divided into 2 different modules. I therefore expect the impact would be very low in these countries.