XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot2
    • Clinical Decision Support
    • Content Lifecycle [deprecated]
    • 3.0.1.2
    • Hide

      Agreed, relax this requirement to state that the versioning scheme does not need to be applied to artifacts in draft state (though it can be, especially with the use of labels to indicate state (such as DRAFT), and provide a discussion of approaches (some systems allow only a single draft version of an artifact and that instance has no version element, other systems allow multiple draft versions and use a combination of versioning and labels to support this).

      Show
      Agreed, relax this requirement to state that the versioning scheme does not need to be applied to artifacts in draft state (though it can be, especially with the use of labels to indicate state (such as DRAFT), and provide a discussion of approaches (some systems allow only a single draft version of an artifact and that instance has no version element, other systems allow multiple draft versions and use a combination of versioning and labels to support this).
    • Jen Seeman/Greg White: 14-0-1
    • Clarification
    • Non-substantive

      The following is part of Conformance Requirement 3.1:

      3. For artifacts in draft status, the versioning scheme SHALL NOT apply, and there is no expectation that artifact contents are stable

      If versioning does not apply, then how does one know what version of a draft the artifact is on? Is this something that the meta tag should be used for (i.e., meta.versionId)? If so, can this section provide or reference a discussion on use of meta.versionId versus the resource's version (e.g., section 2.26.3.7.1 and how that applies?

       

            jen_seeman Jennifer Seeman
            stan_rankins Stan Rankins
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: