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

Soften compatibility assertion

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Shorthand (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • FHIR Shorthand
    • 1.1
    • Hide

      Normative content should not change in incompatible ways, but incompatible changes are allowed in very rare circumstances. As such, we'll update the language to say something like the following:

      Designation as a normative standard does not mean that the FSH language will cease to evolve. Rather, it indicates that, except in very rare cases, future changes will be compatible with normative portions of the specification.

      Show
      Normative content should not change in incompatible ways, but incompatible changes are allowed in very rare circumstances. As such, we'll update the language to say something like the following: Designation as a normative standard does not mean that the FSH language will cease to evolve. Rather, it indicates that, except in very rare cases, future changes will be compatible with normative portions of the specification.
    • Chris Moesel/Mark Kramer: 12-0-0
    • Correction
    • Non-substantive

    Description

      Are we truly bound to be compatible, or is it a goal that we don't break without a really, really good reason? Consider relaxing from must to should.

      Existing Wording:

      only that any future changes must be compatible with the normative portions of the specification

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

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: