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-144) ETL: Re-written section 2.4

Jacob Westfall created EMERGENCY-144:

             Summary: ETL: Re-written section 2.4
                 Key: EMERGENCY-144
                 URL: https://issues.oasis-open.org/browse/EMERGENCY-144
             Project: OASIS Emergency Management TC
          Issue Type: Improvement
          Components: EDXL-CAP 
            Reporter: Jacob Westfall

Section 2.4 has been rewritten and here is the suggested new text:


When constructing alerts, identifying subject events and event types is often not enough. Using meaningful terms for communicating hazardous or concerning impacts to an audience, is just as important. This is the social science of alerting and this is where the concept of an alert type arises.

An alert type is usually just the type of event transposed to also being the type of alert. For example, a âblizzard eventâ, of event type âblizzardâ, would often lead to a âblizzard alertâ of alert type âblizzardâ. Since an alert message requires a subject event to center the message on, it is natural to make this simple transposition of event types to alert types. This transposition activity holds true for other event type schemes as well (i.e. a âred eventâ becoming a âred alertâ, etc.).

However, the practice of setting an alert type for alerting authorities is just as inconsistent around the world as is setting event types. For example, a âhot dry weatherâ event, conducive to the possibility of bush fires, may result in alerts with alert types of âbushfire emergencyâ or âred flag warningâ. These two alert types are not necessarily understood to mean similar things â especially across different communities.

Regardless of what event terms are already in use, and what they might truly signify, the overall social aspect of an alerting service has been established. Furthermore, for this exampled case, it should be pointed out that the alert terms âemergencyâ and âwarningâ are not uncommon variations for the choice of term for an âalertâ, or is it actually meant to be a âbushfire emergency alertâ of type âbushfire emergencyâ. Nevertheless, the conclusion is that the practice of using terms for naming events and alerts can vary considerably making comparisons difficult.

Ultimately, public alerting is not meaningful if the message is not understood. Regardless of the term assigned to the event or alert, the social responsibility of an alerting authority is to effectively communicate the hazards and concerns associated to a subject event. In each case, representatives of the alerting authorities that chose these terms felt the chosen term was the correct one for the situation.

This message was sent by Atlassian Jira

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