[OASIS Issue Tracker] (EMERGENCY-160) ETL: Modified 5.3.2

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

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

Rex Brooks commented on EMERGENCY-160:
--------------------------------------

Committed to etl.v1.0-cn01.wd02

Because these 'tweaks' are numerous, the SC did not formally record approval in any specific Meeting Notes.

> ETL: Modified 5.3.2
> -------------------
>
>                 Key: EMERGENCY-160
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-160
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>            Reporter: Jacob Westfall
>            Priority: Major
>              Labels: ETL
>
> Modify the content for 5.3.2
> Â
> {color:#4c4635}terms that are actually secondary event terms that are often mistaken as a primary event term. (i.e. âthunderstorm warningâ).{color}
> {color:#4c4635}The term âthunderstorm warningâ is a secondary event term that refers to the act of responding to a warning, not the real or anticipated presence of a thunderstorm event itself. With all possible secondary event terms making a long list of terms, it makes it difficult to manage a list of terms for comparison purposes. Furthermore, such secondary events are not what the CAP elements, <severity>, <onset>, etc. were designed to address, although many authorities just use a value representative of the primary event. However, in this case, the primary term âthunderstormâ will suffice as it makes comparisons and list management easier. {color}



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