use YAML

XMLWordPrintableJSON

    • Type: Comment
    • Resolution: Considered - No action required
    • Priority: Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 1.5
    • Hide

      This comment relates to future possibilities for FSH and relates to non-normative content. The gist of this comment relates to the suggestion in the Future section of the  possibility of using something YAML-like to deal with nested paths. So far, FSH does not treat repeated white space as meaningful. Some shorter syntax should be considered for nested paths, but it is not clear what that syntax should be. FSH certainly will not become YAML, which seems to be the suggestion.  We will clarify this in the "Futures" section of the Overview.

      Show
      This comment relates to future possibilities for FSH and relates to non-normative content. The gist of this comment relates to the suggestion in the Future section of the  possibility of using something YAML-like to deal with nested paths. So far, FSH does not treat repeated white space as meaningful. Some shorter syntax should be considered for nested paths, but it is not clear what that syntax should be. FSH certainly will not  become  YAML, which seems to be the suggestion.  We will clarify this in the "Futures" section of the Overview.

      Moving SUSHI to YAML is a good idea and should be considered (as additional representation?) for STU1 as well.

      Existing Wording:

      A syntax like YAML is much more concise in this type of situation. Additional syntax is under consideration.

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

              Created:
              Updated:
              Resolved: