FHIR Chat · package-list.json

Up to now, it hasn't been clear how we intend to maintain the history page for igs. I've been doing it by hand. well, there's a change of policy. From now on, any new IGs submitted for publication must include an updated package-list.json to publish. This file is documented here:
http://wiki.hl7.org/index.php?title=FHIR_IG_PackageList_doco

For an example, see http://hl7.org/fhir/us/core/package-list.json

Grahame Grieve (Nov 22 2018 at 04:47):

the updated package-list.json must be in the root folder in github (and so not in the output folder)

Grahame Grieve (Nov 22 2018 at 04:58):

for guides published on hl7.org, the history page will be history.cfml, not history.html

Grahame Grieve (Nov 24 2018 at 01:21):

ok this is all complete now; all IGs on HL7.org publish their directory based off package-list.json

Eric Haas (Mar 20 2019 at 00:02):

these requirements for package-list.json don't make sense for a non hl7 balloted IG. e.g. something that may be published in fhir.org ?

{
  version" : "[version]",   // mandatory
...

  ====>   "status" : "[status]",   // mandatory
 ====>   "sequence" : "[sequence]",   // mandatory, except for ci-build entry
..
 }
Doco:

status: the status of the publication - one of 'draft', 'ballot', 'trial-use', or 'normative'
sequence: which group to publish this as part of (typically, 'STU 1' etc). Groups all the ballot publications and the final publication for the ballot sequence

I think they should be optional