Stream: implementers
Topic: GF#17015 - Backbone Specializations
Grahame Grieve (Jun 13 2018 at 02:55):
GF#17015 askes why we both publishing this list: http://hl7.org/fhir/2018May/backboneelement.html#summary
Grahame Grieve (Jun 13 2018 at 02:56):
The answer is, because @Brian Postlethwaite asked us to.
Grahame Grieve (Jun 13 2018 at 02:56):
in a previous ballot.
Grahame Grieve (Jun 13 2018 at 02:56):
though I think it's a very technical artifact that we could publish somewhere else.... does anyone have any opinions on this?
Lloyd McKenzie (Jun 13 2018 at 02:57):
"we both" = "we bother"?
Grahame Grieve (Jun 13 2018 at 02:59):
y
Brian Postlethwaite (Jun 25 2018 at 07:54):
This is used in the code generator to explicitly define the classname that is generated (where there are some really long ones, or the names clash when auto-generating)
Brian Postlethwaite (Jun 25 2018 at 07:54):
And was a great location to be able to see all these names.
(I believe that the JAVA generator also uses the values)
Lloyd McKenzie (Jun 25 2018 at 09:18):
Does it need to be rendered for readers of the spec?
Brian Postlethwaite (Jun 25 2018 at 09:21):
Can be a handy reference for those doing code generations. (doen't have to be normative though)
Lloyd McKenzie (Jun 25 2018 at 09:30):
I'm fine with producing it - just lean towards a link to a file rather than putting that noise in the rendered spec
Grahame Grieve (Jun 25 2018 at 10:28):
I can make it a .... text... file?
Brian Postlethwaite (Jun 25 2018 at 10:58):
with html as the content?
(just don't link to it from anything)
:tongue:
Last updated: Apr 12 2022 at 19:14 UTC