Stream: implementers
Topic: IG and individual versions
Jens Villadsen (Dec 13 2021 at 23:52):
What are the experiences NOT using the apply-version-parameter in the IG aka having all codesystems, valuesets and profiles holding individual versions.
Jens Villadsen (Dec 13 2021 at 23:53):
When is it a pain and when does it actually contribute
Grahame Grieve (Dec 14 2021 at 00:03):
the HL7 terminology package, for instance, doesn't use apply-version - the resources have their own versions
Grahame Grieve (Dec 14 2021 at 00:04):
the biggest downside is that most editors overlook the version and there's multiple releases with the same version
Grahame Grieve (Dec 14 2021 at 00:07):
and also, it's harder to figure out what the version should be when you're versioning the package, and hard to be disciplined about it when you do have a workable policy
Richard Townley-O'Neill (Dec 14 2021 at 01:55):
When apply-version is used, brand new resources get the same version number as resources carried over from previous versions.
Lloyd McKenzie (Dec 14 2021 at 05:54):
If you don't do it, you must manually track whether anything has changed and update the version number and do it consistently and right. That's very hard for humans to do correctly all the time. It also makes version-specific referencing miserable as you now need to know the specific version of the artifact rather than just the version of the IG.
Jens Villadsen (Dec 14 2021 at 23:10):
Rigth - and one also needs to consider what kind of change it is when a resource profile to a reference is changed within the referencing resource. That part is definetly hard. However, there also the downside that using apply-version EVERYTHING is bumped - and that especially might not make sense for eg. ValueSets and CodeSystems if they literally have not changed - @Erik Nielsen feel free to share your thoughts. If one can consider an IG as any other software library/component/package I guess that it is also the case that not all code is changed when a version is bumped - yet the software library/component/package is incremented in its entirety and that makes sense.
Last updated: Apr 12 2022 at 19:14 UTC
