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-31) Clarify and standardize ways to cancel a CAP alert


Steve Hakusa created EMERGENCY-31:
-------------------------------------

             Summary: Clarify and standardize ways to cancel a CAP alert
                 Key: EMERGENCY-31
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-31
             Project: OASIS Emergency Management TC
          Issue Type: Bug
            Reporter: Steve Hakusa


From https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/54116/Sep15-2014-meeting-notes.doc and also discussed in https://issues.oasis-open.org/browse/EMERGENCY-4

There are multiple different ways to Cancel a CAP message, each with subtle meanings.

msgType Cancel is more akin to Revoke.  Consider renaming, and adding a requirement that Cancel messages do not have an info block.

msgType Cancel could apply to the “event” instead and may be part of the new event information construct for CAP

Current practice in widespread use is to use an info block with a Cancel to explain the reasons for the cancellation.  Clarify whether Cancel is appropriate for this case, or should msgType Alert be used.  Clarify how to specify expires times in these cases.

Clarify how to use Cancel with responseType AllClear, noting Cancel practices had evolved out of the lack of All Clear in prior CAP versions.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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