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

Steve Hakusa commented on EMERGENCY-17:


We've seen 3 separate definitions of expires used in practice:
- “The event will end at this time”
- “The next update for this alert is expected by”
- “This alert will cease to be valid after”

We would like to tell alert recipients the most accurate of:
- “Alert active for next X minutes” (if we have event end time)
- “Next update expected in Y minutes” (if we have next update time)
- “Alert sent Z minutes ago” (if we just have expires time)

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