OASIS Emergency Management TCIcon indicating the project type

OASIS Emergency Management TC

Uploaded image for project: 'OASIS Emergency Management TC'
  1. OASIS Emergency Management TC
  2. EMERGENCY-37

Add response options element

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: EDXL-CAP
    • Labels:
      None
    • Proposal:
      Hide

      Add an element called:
      <responseOptions>
      which will provide receiving system choices of responses to give the end recipients. For example

      <responseOptions>
      <response>I am safe</response>
      <response>I am in danger</response>
      </responseOptions>

      Show
      Add an element called: <responseOptions> which will provide receiving system choices of responses to give the end recipients. For example <responseOptions> <response>I am safe</response> <response>I am in danger</response> </responseOptions>
    • Resolution:
      Hide

      Use PFIF in EDXL wrapper

      Show
      Use PFIF in EDXL wrapper

      Description

      Often times, when sending an alert to humans, we seek to get responses back to know status of the person
      By optionally requesting responses in the standard CAP itself, we can encourage this interactivity.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          waidyanatha Nuwan Waidyanatha (Inactive) added a comment -

          A method we had trialed, with human instigated receipt acknowledgement, was using the msgType = “Ack” - Acknowledges receipt and acceptance of the message(s) identified in <references>. There were discussions about "Ack" being removed. If this recommendation is replacing the original "Ack" then the literature should recognize that and mention it to let the readers know of the new change. It's intuitive to someone consistent following the meetings but hard on use who can't make all the calls but receive bits and pieces.

          Show
          waidyanatha Nuwan Waidyanatha (Inactive) added a comment - A method we had trialed, with human instigated receipt acknowledgement, was using the msgType = “Ack” - Acknowledges receipt and acceptance of the message(s) identified in <references>. There were discussions about "Ack" being removed. If this recommendation is replacing the original "Ack" then the literature should recognize that and mention it to let the readers know of the new change. It's intuitive to someone consistent following the meetings but hard on use who can't make all the calls but receive bits and pieces.
          Hide
          Permalink
          waidyanatha Nuwan Waidyanatha (Inactive) added a comment -

          Another note, the response options listed in the example: I am safe are also seem in the PFIF standard for missing persons: http://zesty.ca/pfif/

          Show
          waidyanatha Nuwan Waidyanatha (Inactive) added a comment - Another note, the response options listed in the example: I am safe are also seem in the PFIF standard for missing persons: http://zesty.ca/pfif/
          Hide
          Permalink
          tpetel Tomer Petel (Inactive) added a comment -

          Use PFIF in EDXL wrapper

          Show
          tpetel Tomer Petel (Inactive) added a comment - Use PFIF in EDXL wrapper

            People

            • Assignee:
              Unassigned
              Reporter:
              tpetel Tomer Petel (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: