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-28) Recommend specifying a time zone in all DateTime fields

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

Steve Hakusa commented on EMERGENCY-28:

From https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/53640/Aproved%20CAP%20SC%20Meeting%20Notes%207-14-14.doc


Consensus was that the client should be the one to determine time.  We would recommend to the EM-TC that there be no change in the CAP Specification.  Discussion continued regarding making a note about this in the Best Practices guide and how do we track such.

> Recommend specifying a time zone in all DateTime fields
> -------------------------------------------------------
>                 Key: EMERGENCY-28
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-28
>             Project: OASIS Emergency Management TC
>          Issue Type: Bug
>          Components: CAP 
>            Reporter: Steve Hakusa
> Specifically for sent, expires, and onset, I suggest a Note to the effect of
> "If the location cited in the area block falls within a single timezone, effective SHOULD specify time in that zone, including allowance for Daylight Savings when applicable."
> The rationale is that times in the correct time zone are easier for users to understand and take action on, but frequently alerts use UTC.  Alert disseminators aren't always in the best position to know the time zone of the user to which they are disseminating the alert.

This message was sent by Atlassian JIRA

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