Stream: conformance
Topic: packages
Martijn Harthoorn (Apr 01 2019 at 13:07):
@Eric Haas , @Lloyd McKenzie , @Grahame Grieve , I see that the package specification contains edits with additions regarding to Implementation Guides. This are very valid additions to the Implementation Guide requirements, but not to the package specification.
Package Spec: http://wiki.hl7.org/index.php?title=FHIR_NPM_Package_Spec
Ig Requirements: http://wiki.hl7.org/index.php?title=FHIR_Implementation_Guide_Publishing_Requirements
Martijn Harthoorn (Apr 01 2019 at 13:07):
Not all packages are IG's.
Martijn Harthoorn (Apr 01 2019 at 13:08):
And so for example, the IG author can never be a mandatory field for packages in general.
Martijn Harthoorn (Apr 01 2019 at 13:08):
from the current page: "author - mandatory = ImplementationGuide.publisher"
Grahame Grieve (Apr 01 2019 at 13:08):
I think author should be mandatory but I agree it can only be the IG publisher if it's for an IG
Martijn Harthoorn (Apr 01 2019 at 13:10):
It would benefit to have a separate page of requirements for IG packages.
Martijn Harthoorn (Apr 01 2019 at 13:13):
A statement like this: "All FHIR Implementation Guides are published as NPM packages" - is a valid statement in the HL7 IG publishing requirements page. (as long as this is about ballotable ig's), but when read as a generic statement about IG's on the package spec, it is more untrue than true.
Grahame Grieve (Apr 01 2019 at 19:30):
I'll re-org the page to make the difference clearer
Grahame Grieve (Apr 01 2019 at 19:40):
k done
Last updated: Apr 12 2022 at 19:14 UTC
