Stream: implementers
Topic: ig publisher directory case sensitivity
Sean McIlvenna (Apr 28 2017 at 16:42):
In the "resources" directory, does it matter anymore (to the IG Publisher tool) if the directories are case sensitive? Ex: do I have to have the directory named "StructureDefinition", or can it be "structuredefinition"?
Eric Haas (Apr 29 2017 at 00:09):
I never worried about the case for folders vis a vis the tool.
Josh Mandel (Apr 29 2017 at 01:14):
My guess is that you should design for case sensitivity. It's possible that on Windows it doesn't matter, but on other platforms it likely does.
Grahame Grieve (May 01 2017 at 03:36):
yes case sensitivity always matters eventually
Sean McIlvenna (May 01 2017 at 16:01):
Ok. Given that case sensitivity should matter, what is the correct case-sensitive format to use for these folders? Is it "structuredefinition" or "StructureDefinition"?
Lloyd McKenzie (May 01 2017 at 16:41):
They need to match what's in you IG config JSON file
Sean McIlvenna (May 01 2017 at 16:43):
that's fine. i can do that, but beyond that, are there requirements for case-sensitivity?
Sean McIlvenna (May 01 2017 at 16:43):
the ig publisher, I think, used to only function if it was all lowercase
Sean McIlvenna (May 01 2017 at 16:44):
(i.e. if the JSON and directory were "StructureDefinition", it would still fail)
Eric Haas (May 01 2017 at 17:51):
I am assuming you are referring to the file structure like it is here If not - ignore the rest of this post. I don't think you should be naming folders the same name as resources.
Sean McIlvenna (May 01 2017 at 18:42):
that's interesting @Eric Haas
in all other examples (at least from a while back) the resources were separated into their own categorized folders based on their resource type.
Ex: resources/StructureDefinition/myStrucDef1.xml
Ex: resources/ValueSet/myValueSet1.xml
Sean McIlvenna (May 01 2017 at 18:43):
and I know this works (or at least did), since that's how C-CDA on FHIR was published
Sean McIlvenna (May 01 2017 at 18:43):
sounds like maybe there isn't very clear guidance on how this should be done... not sure what the recommendations are from the ig-pubhlisher developers
Eric Haas (May 01 2017 at 18:47):
It works but my reasoning is that it can get confusing as in resource/structuredefinition/structuredefinition....
Sean McIlvenna (May 01 2017 at 18:51):
well, in implementation guides that have over 30 resources, I'd prefer to use the categorized directory structure to ease navigability
Sean McIlvenna (May 01 2017 at 18:52):
so, with that, I'm still not sure whether a specific case-sensitive approach should be used
Sean McIlvenna (May 01 2017 at 18:52):
:)
Grahame Grieve (May 01 2017 at 21:07):
the IG publisher doesn't make any rules about this for input - whatever you do. But there are things it predicts to make it easier. But none of those predictions involve sub-folders.
Grahame Grieve (May 01 2017 at 21:08):
I think it works better if you have higher level categories in sub-folders - terminology, profiles, examples.
Grahame Grieve (May 01 2017 at 21:08):
but there's no rules
Last updated: Apr 12 2022 at 19:14 UTC
