[OASIS Issue Tracker] (EMERGENCY-153) ETL: Change title for 3.3 and rewrite section content

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

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

Rex Brooks commented on EMERGENCY-153:
--------------------------------------

Change: Section 3.3 committed to etl-v1.0-cn01-wd02

Minuted in SC Meeting Notes: Date-meeting-notes

> ETL: Change title for 3.3 and rewrite section content
> -----------------------------------------------------
>
>                 Key: EMERGENCY-153
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-153
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>            Reporter: Jacob Westfall
>            Assignee: Rex Brooks
>            Priority: Major
>              Labels: ETL
>
> Change the section title to "Impact Spectrum" for 3.3
> Â
> Replace the text with this rewritten content:
> Â
> Alerts can be used to alert audiences to events of interest that have impacts that are minor, major, or anywhere in between. Often, the desire of many alerting authorities is to express that degree of impact quickly and succinctly as possible. In CAP, this is what the <headline> element is designed for; however, another way to do this is to encapsulate the degree of impact into the event type term. If an event type has an additional adjunct in the term that infers some sense of impact, such as âconcernâ, âproblemâ, âissueâ, âhazardâ, âemergencyâ, etcâ then simply presenting the event type may be enough to get enough of the message across in presentation mediums where succinctness is key.
> Image
> Much like time-based terms, impact-based terms on their own are abstract. They convey the idea of an event and do not contravene the idea of a subject event in a CAP message. Impact-based terms come with the same advantages of time-based terms. For example, a âbeach hazardâ is an acceptable event type when âbeachâ on its own is vague for comparison purposes. Even the implied full event term âbeach eventâ is vague - it really only answers the question of where, as opposed to what. Adding in the impact term âhazardâ, as in âbeach hazardâ (or âbeach hazard eventâ - as implied) makes the term much more helpful.



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