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-126) Q1: Widely used terms with naming conventions that conflict


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

Elysa Jones updated EMERGENCY-126:
----------------------------------
    Description: {color:#212121}A subtask is created for each commenters response to this question.{color}  (was: {color:#212121}The response is based on our implementation of CAP in cooperation with the Norwegian Broadcasting Company and the Norwegian {color}{color:#000000}Water Resources and Energy Directorate, and on using CAP in our weather portal {color}[Yr|https://www.yr.no/]{color:#000000}.{color:#212121}
 {color}{color}
{color:#000000} 1) Severity and certainty should be removed from the event term to make the list manageably short. The term “warning” is not an event, and should not be used in the event term.
 
 2) We would prefer consolidation under a single term. We would also prefer the geographic domain to be a separate, optional part of the CAP message, as the consequences of events may vary strongly between different domains and within a predefined area. Suggested domains are Land, Marine, Coastal and Aviation. We also suggest to add “Polar low” and “Marine cold air outbreak” to the event list. “Marine cold air outbreak” has many similarities with “Lake effect snow”, and may cause strong wind, heavy snow showers, polar lows and/or marine icing. 
 
 3) MET Norway: We suggest that an event should only have one applicable CAP category. If both “broad term” and “narrow term” should be kept, the broad term should be defined by the CAP category alone.{color})
    Environment: Question 1:  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?  (was: Answers to questions regarding CAP Event Terms List)

> Q1:  Widely used terms with naming conventions that conflict
> ------------------------------------------------------------
>
>                 Key: EMERGENCY-126
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-126
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>         Environment: Question 1:  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?
>            Reporter: Elysa Jones
>            Assignee: Jacob Westfall
>            Priority: Major
>
> {color:#212121}A subtask is created for each commenters response to this question.{color}



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


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