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://tools.oasis-open.org/issues/browse/EMERGENCY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37645#comment-37645 ] 

Art Botterell commented on EMERGENCY-28:

But what if the alert/event spans a timezone boundary?  The client will still need to be able to deal with UTC and other timezones.

This seems like more a client UI concern than a CAP standard issue.  We've achieved unambiguous representation of times... customizing them to individual recipients' context needs to be done individually by their client tools.

> Recommend specifying a time zone in all DateTime fields
> -------------------------------------------------------
>                 Key: EMERGENCY-28
>                 URL: https://tools.oasis-open.org/issues/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]