Stream: committers
Topic: Bindings.ini
Michelle (Moseman) Miller (Feb 10 2017 at 20:07):
I found that a number of coding system OIDs are being repurposed between releases and builds. Per https://chat.fhir.org/#narrow/stream/implementers/topic/OIDs, @Grahame Grieve said that bindings.ini should prevent that from happening. Today, after a local build that introduced new value set bindings, I committed bindings.ini, which looks like it had 60+ new bindings auto generated from my local build that were not previously committed. That leads me to believe that we (committers) are not checking in bindings.ini like we should when a new binding is created. I wonder if that is the root of the issue behind why OIDs are getting re-assigned between builds and published versions of the spec.
Grahame Grieve (Feb 10 2017 at 22:55):
this is strange. you should not get updates to bindings.ini unless the build tool is told that it's doing a final build for hl7.org. That's why you don't usually get changes in bindings.ini - I would get them at publication time
Grahame Grieve (Feb 10 2017 at 22:55):
I will investigate
Michelle (Moseman) Miller (Feb 10 2017 at 23:13):
For whatever it is worth, I did a full local build using -nopartial
Last updated: Apr 12 2022 at 19:14 UTC
