Stream: IG creation
Topic: IG Maturity
Grahame Grieve (Mar 05 2019 at 00:05):
GF#18277 says that the IG publisher will provide support or maturity of artefacts (as well as IG).
Here's some ideas for the tool:
- generate lists with maturity appended to the links (per the entries on http://hl7.org/fhir/resourcelist.html)
- add maturity level to the summary table
- generate a special maturity header fragment
- generate special list fragments by maturity
- generate entries for [type]-[id]-maturity in the data file
Richard Townley-O'Neill (Mar 05 2019 at 00:22):
deleted
Lloyd McKenzie (Mar 05 2019 at 00:40):
Not following first bullet about maturity. How will you handle exposing page maturity?
Grahame Grieve (Mar 05 2019 at 00:42):
pages don't have maturity, only artefacts do
Lloyd McKenzie (Mar 05 2019 at 00:42):
True. I guess they just have ballot levels. Though we tend to expose those in the maturity lists.
Grahame Grieve (Mar 05 2019 at 00:44):
a given template might be able to map between artefacts and pages - hence I propose generation of a special maturity header fragment
John Moehrke (Mar 05 2019 at 13:49):
I like. We do this manually in IHE. We only expose this in a maturity chart in the throw-away section at the beginning. We have only exposed Resource and transport maturity. This minimalism view is all that we can manage manually, but it might be the right level of exposure. For example we didn't expose query parameter maturity or element within a resource maturity; which is important overall but too noisy. Too much and the maturity values start to become intrusive, and a distraction. Ultimately when the IG goes normative all things that it relies on will be normative, so the resulting specification would not have maturity listed at all (exceptions are possible).
Grahame Grieve (Mar 05 2019 at 20:18):
ok updated the doco, and in the next release
Last updated: Apr 12 2022 at 19:14 UTC
