Stream: fhir/infrastructure-wg
Topic: Package Specification problem
Grahame Grieve (Sep 01 2018 at 03:56):
The package specification says that resources in a package go in
Grahame Grieve (Sep 01 2018 at 03:56):
package/[resourceName]-[id].json
Grahame Grieve (Sep 01 2018 at 03:57):
tgz files have a length limit of 100 chars for the path. There's a POSIX extension to go longer than 100, but it's not clear how widely that's supported, or how to find out.
Grahame Grieve (Sep 01 2018 at 03:57):
sticking to a length limit of 100, that means that there's 22 characters left for the length of the resource name
Grahame Grieve (Sep 01 2018 at 03:58):
100 [limit] - (8 [package/] + 1 [-] + 5[.json] + 64 [id]) = 22
Grahame Grieve (Sep 01 2018 at 03:58):
the following resource names are > 22 chars long
Grahame Grieve (Sep 01 2018 at 03:58):
- TerminologyCapabilities
- OrganizationAffiliation
- MedicationAdministration
- MedicinalProductPackaged
- MedicinalProductClinicals
- BiologicallyDerivedProduct
- ImmunizationRecommendation
- CoverageEligibilityRequest
- MedicinalProductDeviceSpec
- MedicinalProductIngredient
- CoverageEligibilityResponse
- MedicinalProductAuthorization
- SubstanceReferenceInformation
- MedicinalProductPharmaceutical
Grahame Grieve (Sep 01 2018 at 03:59):
that may or many not be a problem; if they appear in a package, they can't have resources that have all 64 chars used in their id.
Grahame Grieve (Sep 01 2018 at 04:00):
We have some implementers frustrated by the 64 char limit - they want to use longer composites that include human meaningful names . But some of them would want more than 128 chars so they can get a whole narrative in the id....
Grahame Grieve (Sep 01 2018 at 04:01):
it seems to me that it really only matters for resources with a canonical URL (1 of them right now)
Grahame Grieve (Sep 01 2018 at 04:01):
anyone have any comments on this?
Lloyd McKenzie (Sep 01 2018 at 04:56):
So long as the publication tooling enforces the limit, we should be ok.
Michel Rutten (Sep 01 2018 at 11:56):
Uh oh, maxlength 100 is really tight... I'm worried that this limitation will keep bugging modellers for years to come. Should e.g. Forge try to verify that combination of resource type name + id doesn't exceed 88 chars? This seems very user-unfriendly. Do we really want to force this ancient 8-bit era limitation onto the HL7 FHIR community, for years and years to come?
Josh Mandel (Sep 01 2018 at 12:58):
As far as I can tell this should only be true for very old versions of tar. Where are you hitting this limitation?
Josh Mandel (Sep 01 2018 at 12:58):
I.e. the extension you mentioned, Grahame.
Grahame Grieve (Sep 01 2018 at 20:17):
the limitation is in the original format. There is a POSIX extension for extending it but the documentation is pretty unclear about how well it's supported
Grahame Grieve (Sep 01 2018 at 20:17):
we have not tried using it, so we don't know of any software that doesn't support it.
Grahame Grieve (Sep 01 2018 at 20:18):
do you have a way/criteria for us to find out whether we can safely use it?
Last updated: Apr 12 2022 at 19:14 UTC
