Stream: IG creation
Topic: IHE naming
John Moehrke (Jan 17 2022 at 14:59):
@Grahame Grieve Can we separate the IHE discussion from the IG release procedure discussion. IHE is happy using the current cloud ci-build... So, I am not wanting to follow that.. but I would like to get guidance on IHE naming. I had asked before, so maybe now is a better time.
John Moehrke (Jan 17 2022 at 15:02):
I recently learned that an IG id value should be lowercase, so I have started to change to that. Is this a correct fact? Or am I misguided? I had not seen any rules for canonical URI that they also had to be all lowercase.
John Moehrke (Jan 17 2022 at 15:03):
"The IHE naming pattern creates a challenge for me. At present, in the publication process, everything is inferred from the package name. canonicals, urls, folder layouts.
But the scheme you've outlined, where the canonical is https://profiles.ihe.net/${domain}/${profile}... well, that's not quite true, since the domain and profile name are partially uppercased. There's no algorithm for that, since it's based on the name of the profile."
John Moehrke (Jan 17 2022 at 15:04):
why does something need to be inferred from the package name?
Grahame Grieve (Jan 17 2022 at 19:38):
well, there's two answers to that. It's how the code does it, but it's not how it needs to be done.
Grahame Grieve (Jan 17 2022 at 19:39):
so I can change how I'm doing it, but do I need to? What server is the IHE web server, and does the server itself use a case sensitive file system?
Vassil Peytchev (Jan 17 2022 at 22:01):
My two cents:
- Canonical URIs are identifiers first, URLs second
- The generic URI syntax assumes that the path is case sensitive.
A simple to follow and simple to check requirement that canonical URIs are always lower case seems to not be very burdensome.
Grahame Grieve (Jan 17 2022 at 22:03):
I would prefer that they are lowercase and will ensure that HL7 follows that, but it's not technically necessary, so I'm not going to impose that on IHE.
But whether the host webserver file system is case sensitive or not is a process issue, not something that matters to anyone but me
John Moehrke (Jan 18 2022 at 13:30):
yes the web server is case sensitive
John Moehrke (Jan 18 2022 at 13:30):
so, your "preference" is that the canonical URI is also lowercase.
John Moehrke (Jan 18 2022 at 13:31):
I can promote this, just have not seen a preference before, and doing what I have done seems to work. So I didn't know why it should be different, or how I would have known not to do what I have done.
Jose Costa Teixeira (Jan 18 2022 at 13:50):
Perhaps we can restart the tooling discussions for IHE
Grahame Grieve (Jan 18 2022 at 19:13):
you haven't used the publication tooling before. So that bit hasn't worked before and that's what we're talking about. But I can change that bit. I just didn't want to if IHE was going to change it's mind
John Moehrke (Jan 18 2022 at 19:15):
been using the IG publisher and publishing on the IHE profiles.ihe.net for a year.
John Moehrke (Jan 18 2022 at 19:15):
didn't use uppercase until a few months ago.
John Moehrke (Jan 18 2022 at 19:16):
what doesn't work?
Vassil Peytchev (Jan 18 2022 at 19:29):
I see no reason to use anything but lower case. I also don't see an actual issue.
If I am not mistaken with the above, can we simply agree that IHE canonicals will always be lower case?
Grahame Grieve (Jan 18 2022 at 19:33):
the IG publisher does two different things: it generates an IG, which is what most people do with it, and it maintains a web site of published IGs. It's the second that we're concerned with here - I don't think that you've been using that before.
John Moehrke (Jan 18 2022 at 20:02):
Grahame, I think I have.
John Moehrke (Jan 18 2022 at 20:02):
I am fine with being advised to go to lowercase for canonical. I simply didn't know better.
John Moehrke (Jan 18 2022 at 20:04):
https://profiles.ihe.net/ITI/PDQm/history.html
John Moehrke (Jan 18 2022 at 20:07):
I am using the -publish-update rather than the -go-publish... no idea why, just the parameter I first was made aware of. I now see the -go-publish and have no idea if IHE should switch. https://github.com/IHE/supplement-template/wiki/IG-build-for-Publication
Jose Costa Teixeira (Jan 18 2022 at 20:12):
Jose Costa Teixeira said:
Perhaps we can restart the tooling discussions for IHE
Jose Costa Teixeira (Jan 18 2022 at 20:28):
(it's much easier if we align to see what everyone is thinking)
Grahame Grieve (Jan 18 2022 at 20:35):
hmm. ok. my apologies. you may have used it. yes. As part of refactoring for the affiliates, I tightened up on the rules and cross-checks, and that included making the QA rules for IHE. So that parts new. I was trying to codify the rules that you described above, and ran into the fact that I can't without building new infrastructure.
Of course, I don't have to codify the rules - but I've found it really useful for HL7 because it prevents administrative accidents, people publishing things in the wrong place because of a typo or a copy/paste error
John Moehrke (Jan 18 2022 at 21:41):
im all for that.
John Moehrke (Jan 18 2022 at 21:42):
Jose Costa Teixeira said:
(it's much easier if we align to see what everyone is thinking)
The IHE-FHIR workgroup continues to meet, and make decisions based on proposals and consensus.
Jose Costa Teixeira (Jan 19 2022 at 13:14):
please bring this topic there, we can discuss and then decide (I think last meeting was cancelled, or I missed it). I don't see an urgency on this.
Last updated: Apr 12 2022 at 19:14 UTC
