Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-42310

Clarify non-space whitespace role

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Shorthand (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • Language Reference
    • 3
    • Hide

      We will clarify how various whitespace characters are (or are not) supported in FSH. We propose adding text similar to the following in section 3.3.3 Whitespace:

      FSH syntax is agnostic regarding the type of whitespace used (e.g., spaces, tabs, non-breaking spaces, etc.), with the following exceptions:

      • FSH rules must be separated using a standard newline and/or carriage return
      • indented rules must be indented using standard space characters
      • whitespace within strings will be preserved as-is, except as noted for triple-quoted strings
      Show
      We will clarify how various whitespace characters are (or are not) supported in FSH. We propose adding text similar to the following in section 3.3.3 Whitespace: FSH syntax is agnostic regarding the type of whitespace used (e.g., spaces, tabs, non-breaking spaces, etc.), with the following exceptions: FSH rules must be separated using a standard newline and/or carriage return indented rules must be indented using standard space characters whitespace within strings will be preserved as-is, except as noted for triple-quoted strings
    • Chris Moesel / Gino Canessa: 10-0-0
    • Clarification
    • Non-substantive

    Description

      Clarify throughout how non-space whitespace characters (including tabs, zero-width breaking space, etc. See https://unicode-explorer.com/articles/space-characters) are treated. Are they (or some subset of them) equivalent to space?

      (Comment 31 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            mathompson@mitre.org MintThompson
            Rongparker Ron G. Parker
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: