Stream: IG creation
Topic: Supporting multiple dependency IG versions
Lloyd McKenzie (Jan 10 2022 at 15:31):
Da Vinci was having a discussion this morning that, in part, comes down to a tooling/methodology challenge. US-Core has a specific version that's referenced in regulation. However, newer versions can be authorized for use and, from time to time, the 'minimum' version gets moved up. Da Vinci puts out IGs that depend on US-Core. Ideally what we want to do is put out one release of each IG and allow validation against the range of US-Core IG versions that are 'allowed'. E.g. it should be possible to validate against CDex version A and US-Core version B.1, B.2 or B.3. This is technically gnarly. Any thoughts on if/how this could be done without putting out a separate CDex release for each possible US-Core release?
Oliver Egger (Jan 10 2022 at 19:08):
extend the version references to include also minor versions (patch are supported with a .x notation)?
Grahame Grieve (Jan 10 2022 at 19:12):
none of the tools support anything but a single reference. And I have no idea how I could either
Grahame Grieve (Jan 10 2022 at 19:13):
though that answer is correct in principle
Elliot Silver (Jan 10 2022 at 19:21):
NPM supports dependency version references like >4.1.0 if I recall correctly. Perhaps we could bring that into our package spec?
(I think this ties in with my version question of how an IG or profile says it's valid against any R4 release.)
Lloyd McKenzie (Jan 10 2022 at 19:46):
Validation has to happen against specific versions. I'm not only talking about 'minor' version changes. In principle, regulations could authorize the use of versions where there are breaking changes. Maybe the only solution is a "please generate 3 copies of this IG, with the following dependency differences" and then have the different IG variations point to each other.
Last updated: Apr 12 2022 at 19:14 UTC
