Stream: IG creation
Topic: IG Publisher 1.1.3 new error if validator.pack is referenced
Rob Hausam (Jul 18 2020 at 15:39):
Where is the documentation for how to use the "package system" as the alternative for validator.pack? @Grahame Grieve @Lloyd McKenzie @Mark Iantorno
Lloyd McKenzie (Jul 18 2020 at 15:57):
My understanding is that it should just 'happen' if the packages of interest are using the CI build. The validator will go look for the package in the local cache and if it doesn't find it there, will look for it in HL7's package repository. So no user action needed (and thus not really anything to document..
Rob Hausam (Jul 18 2020 at 16:01):
I'm trying to interpret what that means in connection with what I'm seeing. As an example (not the only one), there still is an issue with the downloads.html page here and the reference to the validator.pack download that IG Publisher is now (as of 1.1.3) complaining about. So is the answer just to remove that link and the associated text entirely from the downloads page and not replace it (that's what I'm assuming at this point)?
Rob Hausam (Jul 18 2020 at 17:41):
I just decided to replace validator.pack with package.tgz (and adjust the text accordingly).
Lloyd McKenzie (Jul 18 2020 at 19:19):
If you're using the CI build to produce the package.tgz, you shouldn't actually need to pass it as an argument
Grahame Grieve (Jul 18 2020 at 22:31):
people can download the package.tgz file if they want, and use it locally just like they would've used validator.pack, but for the package aware tools, there's no need to do that; just refer to the IG but it's package+version and bingo, it'll work.
At this point the package aware tools I know about are:
- torinox
- the java validator
- the IG publisher
- my server + the FHIR Toolkit
- sushi
Grahame Grieve (Jul 18 2020 at 22:31):
where as the validator.pack was only supported by the java validator. Hence I now call it an error for an IG to mention it.
Rob Hausam (Jul 19 2020 at 23:43):
OK. That makes sense. So maybe it would be good to have a general expectation of what's normally needed/appropriate/useful to have links for on the IG downloads page?
Grahame Grieve (Jul 20 2020 at 01:36):
well, the only thing it really makes sense to download is the IG itself.
Rob Hausam (Jul 20 2020 at 01:47):
Yes. I assume the definitions and examples (as in the sample IG) also still make sense.
Grahame Grieve (Jul 20 2020 at 07:12):
I don't know what you'd do with the definitions, but sure, why not. The examples, yes
John Moehrke (Jul 20 2020 at 13:44):
downloading the conformance resources in specific mimeType flavor is helpful (give me all the conformance resources in JSON). It might get ridiculous to have zip downloads per Actor per mimeType. Not clear to me that having independent examples download is as compelling, would rather these examples be in the same conformance resource downloads. Do these sub package zips include the provenance history as applicable?
Grahame Grieve (Jul 20 2020 at 19:07):
the only IG that has sub-packages that I know of is UTG
Last updated: Apr 12 2022 at 19:14 UTC
