OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EMERGENCY-37) Add response options element

    [ https://issues.oasis-open.org/browse/EMERGENCY-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57441#comment-57441 ] 

Nuwan Waidyanatha commented on EMERGENCY-37:

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.

> Add response options element
> ----------------------------
>                 Key: EMERGENCY-37
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-37
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tomer Petel
> Often times, when sending an alert to humans, we seek to get responses back to know status of alert reception. 
> By optionally requesting responses in the standard CAP itself, we can encourage this interactivity. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]