FHIR Chat · capabilityStatement narrative · IG creation

Stream: IG creation

Topic: capabilityStatement narrative


view this post on Zulip John Moehrke (Feb 22 2021 at 14:33):

Given the intro and notes support that the IG builder has for StructureDefinitions... is there similar for CapabilityStatement?

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 14:58):

Yes - for all resources

view this post on Zulip Eric Haas (Feb 22 2021 at 16:51):

.... and examples too

view this post on Zulip Eric Haas (Feb 22 2021 at 16:52):

i considered proposing extension for intro and notes for resources but I remained unconvinced of the cost/benefit.

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 17:05):

Examples are resources :)

view this post on Zulip Eric Haas (Feb 22 2021 at 17:06):

I mentally inserted "conformance"

view this post on Zulip John Moehrke (Feb 22 2021 at 19:42):

thanks. this is going to help alot

view this post on Zulip Jose Costa Teixeira (Feb 22 2021 at 19:43):

Eric Haas said:

i considered proposing extension for intro and notes for resources but I remained unconvinced of the cost/benefit.

If you mean "the behaviour we have on intro and notes should be defined in an extension, instead of code and documentation", then I was thinking the same thing a few weeks ago

view this post on Zulip John Moehrke (Feb 22 2021 at 19:44):

oh, sorry... I simply like the method we already have.

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 19:46):

I really don't want intro and notes as extensions inside examples

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 19:47):

The example file should be the example content. You don't want extensions in there that are documentation and aren't part of the example.

view this post on Zulip Eric Haas (Feb 22 2021 at 19:49):

from a practical aspect I am not sure it would be any easier to manage than separate files

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 19:53):

  1. We don't want the extensions to be included in the example files in the published content - so we'd have to find a way to strip the extensions before the examples were processed
  2. The authoring environments for examples aren't terribly great for editing markdown or HTML. No preview editors or ability to test rendering
  3. Examples may be created by different people than those who provide the documentation around them

view this post on Zulip Jose Costa Teixeira (Feb 22 2021 at 19:55):

my idea was not to add the intro and notes as contents of the extension.

view this post on Zulip Jose Costa Teixeira (Feb 22 2021 at 19:56):

I was thinking of an extension that points to the filename.

view this post on Zulip Lloyd McKenzie (Feb 22 2021 at 19:56):

Ok, but why? Is there a reason we need the filenames to be flexible instead of fixed like they are now?

view this post on Zulip Jose Costa Teixeira (Feb 22 2021 at 20:00):

I was looking at different fragments. In that case I'd like to have this as repeatable behaviour

view this post on Zulip Jose Costa Teixeira (Feb 22 2021 at 20:00):

For only these two I don't see a need to change (except it is one more "nice to know" that we need to explain to people if we are telling them how to make an IG)

view this post on Zulip Eric Haas (Feb 22 2021 at 20:01):

Like I said re the extensions idea ... I don't think the juice is worth the squeeze


Last updated: Apr 12 2022 at 19:14 UTC