[OASIS Issue Tracker] (EMERGENCY-154) ETL: Insert new section for 3.4

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Jacob Westfall commented on EMERGENCY-154:
------------------------------------------

During the Sep 3 2021 meeting, a motion, to approve the changes in issue 154, was put forward by Rex and seconded by Elysa. The motion was approved with all in favour.

> ETL: Insert new section for 3.4
> -------------------------------
>
>                 Key: EMERGENCY-154
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-154
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>            Reporter: Jacob Westfall
>            Assignee: Rex Brooks
>            Priority: Major
>              Labels: ETL
>
> Insert the following content for a new section 3.4
> Â
> 3.4 Action Spectrum
> On occasion, alerting authorities use alerts to engage an audience to take action as a secondary event in response to some primary triggering event. The action requested by the alerting authority can range from monitoring for more information; evacuating the area; sheltering in place; or engaging in specific actions intended for the well-being of the individual or community. These secondary events may be simple recommendations or mandated orders to do something specific.
> Â
> Image 
> Â
> The COVID-19 pandemic re-acquainted world to âstay-at-home orderâ alerts. These alerts were becoming common during the pandemic and alerting authorities were becoming very prescriptive in their alert naming to get the message across. Rather than issuing hundreds of alerts, all referred to as âCOVID-19â alerts or âinfectious diseaseâ alerts, authorities altered the wording and named the alerts to such things as âstay-at-home orderâ and âfake vaccine warningâ. As an alert type, their names directed the audience to the secondary event cited.
> The corresponding event type could still easily be âinfectious diseaseâ, but a modified situation occurs where authorities are instead inspired to cite the secondary event as the event type, but that argument is a based on the mis-conception that the event type and alert type should be the same thing.
> Other action spectrum examples are âadvisoryâ, as with âtravel advisoryâ, âalertâ as with âAMBER alertâ, âordersâ as with âboil water orderâ and âevacuation orderâ, etcâ Even âwarningâ as with âweather warningâ is an example of this. In this latter example, the word âweatherâ is an adjunct to warning, meaning the event of interest is the warning itself and the audience engagement of the information they have just received, not the real or anticipated weather that triggered the alert.
> The term âAMBER Alertâ is an alert type created to heighten the awareness of the secondary response event that involves the participation of the audience. There is no actual secondary event unless some or all of the audience takes part. NOTE: AMBER is an acronym for âAmericaâs Missing: Broadcast Emergency Responseâ where the idea is to illicit a response by the audience. The word âalertâ is added to distinguish the acronym from the color amber if heard or seen in a message.
> The recommended approach in CAP for secondary action events is to keep the <eventCode> element tied to the triggering event for comparison purposes; use the <headline> element for the alert type referencing the secondary event; and use either option for the <event> element as preferred by the alerting authority. Using the examples above, the text snippet âstay-at-home orderâ or âAMBER Alertâ would appear as part of the <headline>, with the âinfectious diseaseâ code or âmissing personsâ code indicated in the <eventCode> element. As for the <event> element, either âstay-at-home orderâ and âAMBER Alertâ as references to the secondary event, or âinfectious diseaseâ and âmissing personâ as references to the triggering event.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)