[OASIS Issue Tracker] (EMERGENCY-125) Q1 - widely used terms with naming conventions that conflict

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

     [ https://issues.oasis-open.org/browse/EMERGENCY-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elysa Jones updated EMERGENCY-125:
----------------------------------
    Summary: Q1 - widely used terms with naming conventions that conflict  (was: Comments by Pinkerton)

> Q1 - widely used terms with naming conventions that conflict
> ------------------------------------------------------------
>
>                 Key: EMERGENCY-125
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-125
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>         Environment: CAP Event Terms List
>            Reporter: Elysa Jones
>            Assignee: Jacob Westfall
>            Priority: Major
>
> # *+Question:+* There are widely used terms with naming conventions that conflict.  For example, Warning is used for some events and not for others in the actual term.  Or Severe Thunderstorm when the actual event is a Thunderstorm, which may or may not be severe, or Extreme Fire Danger versus just Fire Danger.  How do we reconcile this inconsistent naming?
> {color:#000000} {color}
> *_{color:#595959}Pinkerton Response:{color}_* _{color:#595959}Severe and Extreme are both values which can already be found in the “severity” parameter. To avoid confusion, we suggest preventing users from providing predefined variables from other parameters in the “event” parameter. 
>  
>  For example, in the instance provided above, the “event” would simply be Thunderstorm and the alert publisher would be compelled to define the “severity” of said event as Severe.{color}_
>  _{color:#595959}{color}_ 
>  # *+Question:+* There are some narrow terms that fall under several different broad terms.  For example, Gale under Air Hazard and Gale under Marine Weather.  Or Storm Surge on its own versus also part of a Tropical Storm.  What is the feedback on either consolidating under a single broad term or allowing for the same narrow term to be repeated in multiple locations?
> {color:#000000} {color}
> *_{color:#595959}Pinkerton Response:{color}_* _{color:#595959}We agree we should consolidate these narrow terms into one broad term.  
>  
>  For example, in the instance provided above, the “Gale” event would be consolidated within only one of the two broader event terms (“Air Hazard” or “Marine Weather”).  In the other example, the “Storm Surge” event would be consolidated under the “Tropical Storm” event.{color}_
>  _{color:#595959}{color}_ 
>  # *+Question:+* In attempting to develop the list we found there are a number of ambiguities between both the broad terms and narrow terms.  In addition there are also some ambiguities with the CAP categories.  For example, Air Quality in the Canadian list falls into 4 CAP categories.   How will the community address the problems of using a very short list of broad terms given these ambiguities?  How can the list be made most useful to achieve the goals of an event list?
> {color:#000000} {color}
> *_{color:#595959}Pinkerton Response:{color}_* _{color:#595959}This question is referring to the ‘Full Event Terms List” (OASIS website, CAP Subcommittee page), but it appears some development has been done since this question was originally posed.{color}_



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)