Stream: committers/announce
Topic: Changes to filenames produced by template
Lloyd McKenzie (Dec 09 2019 at 03:30):
The standard HL7 template has been updated to use a standard naming convention of [type]-[id] for all files generated as part of the build process. In the past, some (but not all) StructureDefinition files took on the name of [id] or extension-[id] (mirroring how the core build handles naming). This created inconsistency and confusion - and there were also discrepancies in that some profile filenames used the standard [type]-[id] naming convention and some didn't. The impact of this is that if you have narrative, markdown or XHTML text that hyperlinks to particular profile pages, you may find that these links are now broken when you build using the newest template. You'll need to change your hyperlinks to reflect the new naming convention. For those not using the new template publication approach, there will be no impact yet. (You'll need to worry about fixing your links when you move to the template.)
Richard Kavanagh (Dec 09 2019 at 19:22):
So just to check my understanding...
If previously I had Acme-Event-MessageHeader, this should now be StructureDefinition-Acme-Event-MessageHeader ?
Richard Kavanagh (Dec 09 2019 at 19:23):
Does the Structure Definition need any changes, or is it just the way that the tooling deals with it?
Lloyd McKenzie (Dec 09 2019 at 19:26):
Just the way the tooling deals with it. Only time your StructureDefinition would need changing is if you'd manually authored the narrative for it and included links to other artifacts impacted by the naming change.
Nagesh Bashyam (Dec 18 2019 at 16:12):
@Lloyd McKenzie @Grahame Grieve
The build is still creating without the type. For example, the build still creates the schematrons such as davinci-atr-coverage.sch instead of StructureDefinition-davinci-atr-coverage.sch where the id is "davinci-atr-coverage" .
The template uses "StructureDefinition-davinci-atr-coverage.sch" which becomes an invalid link / error in Qa.html.
Just wondering if we need to update the template or the tool ?
Lloyd McKenzie (Dec 18 2019 at 16:27):
I'll dig
Nagesh Bashyam (Dec 18 2019 at 16:38):
It is present in these files..
template/layouts/layout-ext.html: <p>Other representations of extension: <a href="{{[type]}}-{{[id]}}.sch">Schematron</a>
template/layouts/layout-profile.html: <p>Other representations of profile: <a href="{{[type]}}-{{[id]}}.sch">Schematron</a>
If template changes, then we just need to remove the type and it should work...
Last updated: Apr 12 2022 at 19:14 UTC
