[OASIS Issue Tracker] (EMERGENCY-1) alert.info.event size restriction

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

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

Norm Paulsen commented on EMERGENCY-1:
--------------------------------------

I agree with Steve in that there is no explicit element with >Tornado Warning< in CAP and that one should exist. Unfortunately, using <event> for this would be counter to the Alert/Event distinction in CAP. Tornado is the event, Tornado Warning is the alert. So a new optional element should exist that houses that free form Alert name text. So a single event that is multi hazard could spawn several alerts each with the same <event> but differnet <alert>s.

The NWS does recognize the warning and the associated products as the <event> and this can be seen in the history of the SAME code. But that interpretation is not shared everywhere.

<onset> goes to the <event> as <effective> goes to the alert message. They are attributes of two differnet things. I can have an event with an onset of noon tomorrow but the alert message is effective now meaning the message should be out there playing now to warn people.

Was just about to hit send and saw Art's comment come in. I agree with Art.

> alert.info.event size restriction
> ---------------------------------
>
>                 Key: EMERGENCY-1
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-1
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
>




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)