Stream: implementers
Topic: Versioned change log?
Sean McIlvenna (Nov 24 2021 at 16:21):
I thought it used to be that at the bottom of every IG that has been versioned, in the footer, there was a link to "Change Log". I don't see that anymore. How do I see the changes in an IG from one version to another, now?
John Moehrke (Nov 24 2021 at 17:29):
that is up to the author of each IG, and thus the governance body to enforce.
Sean McIlvenna (Nov 24 2021 at 17:30):
what's up to the author of the IG?
Sean McIlvenna (Nov 24 2021 at 17:30):
whether to create a change log or not?
Sean McIlvenna (Nov 24 2021 at 17:30):
my point was: I thought the IG publisher automated this for us
Sean McIlvenna (Nov 24 2021 at 17:30):
manually creating a change log could be a nightmare
John Moehrke (Nov 24 2021 at 17:32):
not sure how the IG publisher could automate that, especially when the changes are in narrative
Grahame Grieve (Nov 24 2021 at 17:58):
look in the version history
Sean McIlvenna (Nov 24 2021 at 19:42):
was looking at that earlier... seems broken
Sean McIlvenna (Nov 24 2021 at 19:42):
ex: http://hl7.org/fhir/us/ecr/history.html
Sean McIlvenna (Nov 24 2021 at 19:42):
clicked on "change notes"
Sean McIlvenna (Nov 24 2021 at 19:43):
got error: A potentially dangerous Request.Path value was detected from the client (:).
Sean McIlvenna (Nov 24 2021 at 19:43):
it tried sending me to http://hl7.org/fhir/us/ecr/2021Jan/http://hl7.org/fhir/us/ecrhistory.html
Sean McIlvenna (Nov 24 2021 at 19:43):
@Grahame Grieve
John Moehrke (Nov 24 2021 at 19:52):
yes the history.html is part of the publication processing step.
John Moehrke (Nov 24 2021 at 19:54):
the change note column comes from your package-list.json
John Moehrke (Nov 24 2021 at 19:55):
so you seem to have some odd markdown in the "desc" in the package-list.json
John Moehrke (Nov 24 2021 at 19:57):
there is no automatically generated "desc" or html page describing the history. You can author an html, and point to it from the package-list.json "desc" element.
Grahame Grieve (Nov 24 2021 at 19:59):
ecr package list is wrong and misleading
Grahame Grieve (Nov 24 2021 at 20:00):
there is no change history for the ecr specification.
Grahame Grieve (Nov 24 2021 at 20:01):
the package-list.json contains a reference to a page that is supposed to contain change details, but it's just a reference back to the history page that contains the link in the first place. And the infrastructure doesn't know to check for that, and it renders it wrongly
Grahame Grieve (Nov 24 2021 at 20:06):
fixed. let me know if you find other instances like this
Sean McIlvenna (Nov 24 2021 at 20:32):
"fixed"... the history page seems to still have broken links @Grahame Grieve . what did you change/fix??
Grahame Grieve (Nov 24 2021 at 20:36):
if you're still seeing 'see changes' thne you haven't got the updated version
Sean McIlvenna (Nov 24 2021 at 21:01):
ahhh ok, cleared cache and it's different
Sean McIlvenna (Nov 24 2021 at 21:01):
now there's nothing about the change history
Sean McIlvenna (Nov 24 2021 at 21:01):
:)
Grahame Grieve (Nov 24 2021 at 21:10):
right. because as near as I can find, there is no change history at all, and the procedural requirements that there be one were met by providing a reference to the page that should contain or reference the history.
tl;dr: for the history, see the history
Last updated: Apr 12 2022 at 19:14 UTC
