Request.method definition makes no sense. - 2018-May Core Norm Infrastructure #235

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Bundle
    • Hide

      Change to "In a <code>transaction</code> or <code>batch</code>, this is the HTTP action to be executed for this entry. In a <code>history</code> bundle, this indicates the HTTP action that occurred."

      Show
      Change to "In a <code>transaction</code> or <code>batch</code>, this is the HTTP action to be executed for this entry. In a <code>history</code> bundle, this indicates the HTTP action that occurred."
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Correction
    • Non-substantive
    • STU3

      Existing Wording: The HTTP verb for this entry in either a change history, or a transaction/ transaction response.

      Proposed Wording: This indicates the HTTP action to be executed as part of this particular step in the batch or transaction.

      Comment:

      In addition to having an incorrect comma, this definition makes no sense. This is a request, not a response. I don't know what a "change history" is either.

      Summary:

      Request.method definition makes no sense.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: