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

Clarify use of non-ASCII characters

XMLWordPrintableJSON

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

      FSH already states requirements for item names, but we will update it to specifically indicate that letters must be ASCII (which has always been the intent). We suggest:

      Names MUST begin with an uppercase ASCII letter and contain only ASCII letters, numerals, and underscores (“_”).

      FSH provides requirements regarding the length of ids, and recommendations regarding id content, but we will update the Item Identifiers section to indicate that ids must follow the same rules as FHIR ids. This has always been the intent since FSH ids translate directly to FHIR ids. We suggest:

      Ids MUST contain only ASCII letters, numerals, hyphens ("-"), and dots ("."), with a length limit of 64 characters (per the requirements of the FHIR id datatype).

      Rather than provide specific details about unicode and right-to-left markers for strings, we will update the discussion on strings in the Primitives section of the spec to indicate that FSH strings follow the same rules as FHIR strings. We suggest:

      FSH strings follow the same rules and support the same content as the FHIR string datatype, including the following special escape sequences: \r (unicode U+000D), \n (U+000A), and \t (U+0009).

      Show
      FSH already states requirements for item names, but we will update it to specifically indicate that letters must be ASCII (which has always been the intent). We suggest: Names MUST begin with an uppercase ASCII letter and contain only ASCII letters, numerals, and underscores (“_”). FSH provides requirements regarding the length of ids, and recommendations regarding id content, but we will update the Item Identifiers section to indicate that ids must follow the same rules as FHIR ids. This has always been the intent since FSH ids translate directly to FHIR ids. We suggest: Ids MUST contain only ASCII letters, numerals, hyphens ("-"), and dots ("."), with a length limit of 64 characters (per the requirements of the FHIR id datatype ). Rather than provide specific details about unicode and right-to-left markers for strings, we will update the discussion on strings in the Primitives section of the spec to indicate that FSH strings follow the same rules as FHIR strings. We suggest: FSH strings follow the same rules and support the same content as the FHIR string datatype , including the following special escape sequences: \r (unicode U+000D), \n (U+000A), and \t (U+0009).
    • Chris Moesel/Mark Kramer: 12-0-0
    • Correction
    • Non-substantive

      Clarify that FSH is Unicode (UTF-8?) and whether non-ASCII characters can be used (particularly outside of strings, such as in item names) and how they are encoded (direct use of UTF-8, \U+9999, &copy, etc.). Clarify use of right-to-left text and use of directional markers.

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

            jafeltra Julia Afeltra
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: