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-1) alert.info.event size restriction

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

Art Botterell commented on EMERGENCY-1:

Here again, the alert is not the event.  "Tornado" describes the event, "Tornado Warning" describes the alert.  

One could come close by simply appending the word "Warning" or "Alert" to the display of the <event> value.  However, the practical emphasis for consumers in near-realtime might better be on the protective action recommendation (<responseType>)... e.g., "Take Shelter."  Displaying the hazard type may be roughly equivalent for folks who are familiar with the hazard, but may not be all that useful

From an alert effectiveness perspective the best approach... and all this really goes to design of the UI rather than the message format... might be to combine both, e.g., "Take Shelter for Tornado" or "Evacuate for Lahar."  The required information is already in the alert, it just needs a bit of transformation for display.

> alert.info.event size restriction
> ---------------------------------
>                 Key: EMERGENCY-1
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-1
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP

This message was sent by Atlassian JIRA

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