FSH tank part of shorthand?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 1.2.3
    • Hide

      FSH defines behavior around FSH projects. The FSH Tank as an embodiment of a FSH project is a SUSHI construct. The language specification should therefore use the language of FSH Projects, while SUSHI can continue to use FSH Tank. 

      We will change the language in the specification to reflect this distinction.

       

      Show
      FSH defines behavior around FSH projects. The FSH Tank as an embodiment of a FSH project is a SUSHI construct. The language specification should therefore use the language of FSH Projects, while SUSHI can continue to use FSH Tank.  We will change the language in the specification to reflect this distinction.  
    • Moesel/Rhodes 11-0-1
    • Correction
    • Non-substantive

      Is the directory structure and file naming convention a normative part of the spec or an implementation choice of SUSHI? I suggest that we leave it as a an implementation part of SUSHI.
      If IG generation is the scope of Shorthand (see previous comment), than this should be made part of the specificaiton

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: