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

Informative remark is not valid for synchronization section

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Triaged (View Workflow)
    • Highest
    • Resolution: Persuasive with Modification
    • FHIRCast (FHIR)
    • 2.1.0-ballot
    • Infrastructure & Messaging
    • STU
    • Synchronization considerations
    • Hide

      Update this informative remark to not only indicate that the page is informative, but also that implementers should carefully read and understand its content. So, something like:

      This page contains guidance to implementers and is not part of the normative-track; however, implementers are strongly encouraged to read and understand its content towards successful synchronization.

      Also, review and rephrase any normative verbs that exist on this page:
      1. Use editorial discretion to not use lower-case shall/should/may.
      2. Move this normative requirement to elsewhere in the spec (probably the syncerror definition page):

      A Client that initiates a context change and receives a syncerror related to a context change event it send, *_SHOULD _*resend this event at regular intervals until sync is reestablished or another, newer, event has been received

      Show
      Update this informative remark to not only indicate that the page is informative, but also that implementers should carefully read and understand its content. So, something like: This page contains guidance to implementers and is not part of the normative-track; however, implementers are strongly encouraged to read and understand its content towards successful synchronization. Also, review and rephrase any normative verbs that exist on this page: 1. Use editorial discretion to not use lower-case shall/should/may. 2. Move this normative requirement to elsewhere in the spec (probably the syncerror definition page): A Client that initiates a context change and receives a syncerror related to a context change event it send, *_SHOULD _*resend this event at regular intervals until sync is reestablished or another, newer, event has been received
    • Clarification
    • Compatible, substantive

    Description

      Although the section does not contain mandatory text, it is sufficiently important not to be skipped due to the sentence at the start. I suggest that we remove it.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bvdh Bas van den Heuvel
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: