Extension naming differences due to IG build process - 2016-09 qicore #7

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US QI Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • QI-Core Profiles
    • Hide

      We agree it's helpful to be able to quickly find extensions based on filenames. But we note that the naming conventions aren't just relevant for extensions; other nice-to-haves would be:

      • datatypes (simple vs complex)
        * logical models
        * base resources
        * constrained resources (profiles)

      ... and given this complexity, a convention to cover all use cases becomes hard to define; and an incomplete convention would make other use cases more difficult.

      (Several of us use "grep" for this purpose, looking for a contexttype of "extension" across structuredefinition*).

      Show
      We agree it's helpful to be able to quickly find extensions based on filenames. But we note that the naming conventions aren't just relevant for extensions; other nice-to-haves would be: datatypes (simple vs complex) * logical models * base resources * constrained resources (profiles) ... and given this complexity, a convention to cover all use cases becomes hard to define; and an incomplete convention would make other use cases more difficult. (Several of us use "grep" for this purpose, looking for a contexttype of "extension" across structuredefinition*).
    • Chris Grenz / Marten Smits: 4-0-0
    • Enhancement

      Comment:

      In the previous FHIR build process, when the FHIR source spreadsheet were processed, extension definitions at the resource or global levels were generated as separate structure definition files prefixed with the name 'extension-' (e.g., extension-patient-clinicaltrial.xml) and file names followed a clear name convention. Such conventions made it easy for tooling to use file filters to quickly identify extensions and process them accordingly. Now, the new tooling prefixes all the files with 'StructureDefinition-'. These filename thus no longer distinguish between extensions and other structure definitions forcing tooling to open the files, parse them, and check the type of structuredefinition first. I would like to suggest a naming convention such as the current one for the FHIR build tool that clearly distinguishes the type of structure definition in the file name.

      Summary:

      Extension naming differences due to IG build process

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Claude Nanjo (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: