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=37299#comment-37299 ] 

Mike Gerber commented on EMERGENCY-17:

Yes and it should be optional.  NWS currently uses <expires> as the expiry date and time of the information in the alert message. This is the time at which the information in the message should be considered stale and no longer used. The NWS forecaster will update or cancel the alert by the <expires> time.  We also add an <eventEndingTime> parameter to the CAP message which is the expected end time of the event in the alert message.  That is, it is is the time at which the hazard conditions of the subject event are no longer expected.  For short duration events (e.g., less than 6 hours), the <expires> and <eventEndingTime> may be the same.  There are some events where we cannot provide an <eventEndingTime> such as long term River Flooding, Tsunamis, and others due to the nature of those events.

> 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]