Indicate indepency of ordering in formal spec.

XMLWordPrintableJSON

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

      Make sure that the formal specification documents the order of items (profiles, invariants, rule sets, value sets, etc.) shall not affect the meaning of FSH.

      Proposed change:

      "The items defined by FSH are: Aliases, Profiles, Extensions, Instances, Value Sets, Code Systems, Mappings, Rule Sets, and Invariants. Items can appear in any order within *.fsh files, and can be moved around within a file (or to other .fsh* files) without affecting the interpretation of the content."

      Show
      Make sure that the formal specification documents the order of items (profiles, invariants, rule sets, value sets, etc.) shall not affect the meaning of FSH. Proposed change: "The items defined by FSH are: Aliases, Profiles, Extensions, Instances, Value Sets, Code Systems, Mappings, Rule Sets, and Invariants. Items can appear in any order within * .fsh  files, and can be moved around within a file (or to other  .fsh * files) without affecting the interpretation of the content."
    • Moesel/Rhodes 11-0-1
    • Clarification
    • Non-substantive

      This is a specification element that should also be mentiond tin the formal specification part of the spec. I believe this is not the case. Definition of what an "item" is will also help.

      Existing Wording:

      The order of items doesn’t matter. In FSH, you can refer to items defined before or after the current item.

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

              Created:
              Updated:
              Resolved: