Why is version a part of the include?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • Clinical Quality Language (FHIR)
    • 1.4 [deprecated]
    • Clinical Decision Support
    • Authors Guide
    • 1.3. Libraries
    • Hide

      The include declaration allows for version-specific binding, but does not require it. A more in-depth discussion of library versioning is provided in the Developer's Guide, Libraries topic.

      However, clearly the use of a version on the first appearance gives the impression that it is required. We will add an example declaration with the version, and then discuss versioning briefly in connection with the current example, and link to the Developer's Guide, Libraries topic (https://cql.hl7.org/2020May/03-developersguide.html#libraries-1) for more in-depth discussion.

      Show
      The include declaration allows for version-specific binding, but does not require it. A more in-depth discussion of library versioning is provided in the Developer's Guide, Libraries topic. However, clearly the use of a version on the first appearance gives the impression that it is required. We will add an example declaration with the version, and then discuss versioning briefly in connection with the current example, and link to the Developer's Guide, Libraries topic ( https://cql.hl7.org/2020May/03-developersguide.html#libraries-1) for more in-depth discussion.
    • Chris Moesel/Ricardo Quintano: 13-0-2
    • Clarification
    • Non-substantive

      It is very uncommon in software engineeting to include libraries of specific versions. It is typically assumed that libraries are backwards compatible and that the run-time linking to specific library versions is separate from the specification of a specific interface import on the level of the programing language.

      So using the concrete version in the import is to be very well motivated. I would strongly suggest to add this motivation here, and if there is no sufficient motivation than not to force includes with specific library versions.

      Existing Wording:

      include CMS153_Common version '2' called Common

      Proposed Wording:

      include CMS153_Common called Common

            Assignee:
            Bryn Rhodes
            Reporter:
            ivan_zapreev
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: