Stream: IG creation
Topic: Resource should declare it's [sic] jurisdiction
Jean Duteau (Jun 08 2020 at 19:21):
I upgraded to the latest publisher and I'm getting a new warning (well, it's new to me) of "Resource should declare it's jurisdiction..." a) that should be 'its' and not 'it's'. But I'm getting the warning on the ImplementationGuide resource which is generated by the publisher, so I'm struggling to find out where I should be putting the jurisdiction.
Grahame Grieve (Jun 08 2020 at 19:36):
It was introduced a couple of versions ago
Grahame Grieve (Jun 08 2020 at 19:37):
the publisher doesn't generate the IG resource from scratch - it always comes from somewhere
Giorgio Cangioli (Jun 09 2020 at 15:18):
Hi @Grahame Grieve I have an issue too with the jurisdictions..I'm working on some EU projects and I've a lot of errors due to this when I build the IGs
Giorgio Cangioli (Jun 09 2020 at 15:19):
if I use <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="150"/>
the message is
the resource should declare it's jurisdiction to match the package id (hl7.fhir.eu.gk, jurisdiction = urn:iso:std:iso:3166#EU
Giorgio Cangioli (Jun 09 2020 at 15:20):
If I use <system value="urn:iso:std:iso:3166"/><code value="EU"/>
the message is
Attempt to access unknown value "EU" from map tx.countrycode for "urn:iso:std:iso:3166#EU"
Giorgio Cangioli (Jun 09 2020 at 15:20):
A slightly different error with urn:iso:std:iso:3166-2 , but still an error..
Giorgio Cangioli (Jun 09 2020 at 15:22):
EU is a reserved code referring to the European Union https://www.iso.org/obp/ui/#iso:code:3166:EU
Giorgio Cangioli (Jun 09 2020 at 15:22):
suggestions ?
Grahame Grieve (Jun 09 2020 at 20:57):
EU may be reserved by ISO 3166 but I don't believe it's a valid code in 3166. We can discuss that on #terminology if you think I'm wrong and it matters.
Grahame Grieve (Jun 09 2020 at 20:58):
you should be using <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="150"/> but the code that checks the jurisdictions doesn't know about hl7.fhir.eu. Looking at that, though, I would say that should not be using hl7.fhir.eu.gk, just hl7.fhir.gk. At least, that's my rules for HL7 use of packages
Giorgio Cangioli (Jun 10 2020 at 09:34):
About ISO 3166 and EU, I don’t know what the right answer is and how “reserved codes” should be considered, i.e. if they are part or not of the Code System 😊.
Giorgio Cangioli (Jun 10 2020 at 09:35):
Concerning the "hl7.fhir.eu." root for npm-names it was adopted after a mail exchange we had on begin 2019 for another EU project (trillium II).
No problems on revising this choice for the new European initiatives, but I believe that something that allow to identify the EU governance space is in any case useful.
Giorgio Cangioli (Jun 10 2020 at 09:35):
If hl7.fhir.eu cannot be used anymore because eu is not a recognized 3166 code, would hl7.eu.fhir resolve this issue ?
Giorgio Cangioli (Jun 10 2020 at 10:39):
..additional question..if the third element of a hl7.fhir.xx.xyz npm name should be an ISO country code (if this is the rule) how does it work for hl7.fhir.uv.xyz packages ?
Alexander Henket (Jun 10 2020 at 10:50):
I think HL7 always has had the notion of realms. A realm was an alpha two ISO 3166 code, or "UV" for universal realm. UV never was a 3166 code to my knowledge, it was an exception that HL7 introduced.
If we are using reverse dns logic, why not use eu.fhir? eu is a valid IANA top level domain. I'm sure I'm too hasty with this suggestion, but just thought of putting it on the table
Alexander Henket (Jun 10 2020 at 10:53):
An alternative way of looking at this: UV may stand for "Universal" but why could an EU guide not aim for "universal"? Hence: why impose that every continent or collection of continent parts (Eurasia, EMEA, ...) is going this route?
Grahame Grieve (Jun 10 2020 at 12:01):
hl7.fhir.eu is good to use and future versions of the IG publisher can support it, no problems. Though we do need to figure out whether EU is a valid code before I sort that out.
But european affiliates should just use hl7.fhir.[cc] not hl7.fhir.eu.[cc]
Grahame Grieve (Jun 10 2020 at 12:02):
if the third element of a hl7.fhir.xx.xyz npm name should be an ISO country code (if this is the rule) how does it work for hl7.fhir.uv.xyz packages ?
it doesn't have to be a iSO country code, but the IG publisher wasn't expecting it to be EU and you shouldn't have a region unless the region is the owner
Giorgio Cangioli (Jun 10 2020 at 12:04):
Grahame Grieve said:
hl7.fhir.eu is good to use and future versions of the IG publisher can support it, no problems. Though we do need to figure out whether EU is a valid code before I sort that out.
Great ! Thank you.
Giorgio Cangioli (Jun 10 2020 at 12:06):
Grahame Grieve said:
But european affiliates should just use hl7.fhir.[cc] not hl7.fhir.eu.[cc]
Yes sure.
This is what I believe they/we are doing. e.g. hl7.fhir.it
Grahame Grieve (Jun 10 2020 at 12:09):
yes that's right
Jose Costa Teixeira (Jun 10 2020 at 12:09):
hmm. I had hl7.be.fhir?
Jose Costa Teixeira (Jun 10 2020 at 12:10):
There is no issue in changing - is hl7.fhir.be preferred?
Grahame Grieve (Jun 10 2020 at 12:11):
yes it is preferred but HL7 Belgium owns hl7.be so hl7.be.fhir is allowed
Jose Costa Teixeira (Jun 10 2020 at 12:16):
thank you
Last updated: Apr 12 2022 at 19:14 UTC
