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

Not very intuitive grammar

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 3.2.8
    • Hide

      The space between the non-caret and caret path exists because there are really two paths. The first is the path to the element of interest in with respect to the profiled resource, and the second is the path to an element in the StructureDefinition or ElementDefinition that defines the profile. 

      The space also improves readability, helping to visually pick out the caret, which can be hard to see.

      Nor do we favor optionality (space or no space) because that creates unnecessary inconsistency between IGs.

      So we propose no change.

      Show
      The space between the non-caret and caret path exists because there are really two paths. The first is the path to the element of interest in with respect to the profiled resource, and the second is the path to an element in the StructureDefinition or ElementDefinition that defines the profile.  The space also improves readability, helping to visually pick out the caret, which can be hard to see. Nor do we favor optionality (space or no space) because that creates unnecessary inconsistency between IGs. So we propose no change.
    • Kramer/Rhodes: 14-0-0

    Description

      The space between "communication\.language" and "^binding\.description" does not feel natural\. I would prefer not having it so that the LHS of the assignment forms a complete path\.

      Existing Wording:

      • communication.language ^binding.description = …

      Proposed Wording:

      • communication.language^binding.description = …

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivan_zapreev Ivan Zapreev (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: