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-17) Add event expiration element

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

Norm Paulsen commented on EMERGENCY-17:

+1 for Mike. Although we define stale slightly different. Stale is when the forecaster can't update the alert - they have to start a new one; but that is not when the Alert message comes off the display. That time is a little later which equates to the expires time in CAP.

For Steve I would add the following...
- for those that use if for the event end time, they are using it incorrectly unless they are using the SAME definition of event, not the CAP one.
- for the phrase... “Alert active for next X minutes” (if we have event end time)... 
your comments in brackets contradict the phrase. X should come from <expires> if it exists.

Event end time is nice to pass along if we have it but we don't always. I would like an optional element go with onset in the manner that expires goes with effective.

> Add event expiration element
> ----------------------------
>                 Key: EMERGENCY-17
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-17
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Should a new CAP element be added that represents the expected expiration of the event?

This message was sent by Atlassian JIRA

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