[OASIS Issue Tracker] Commented: (ODATA-11) date/time values without explicit time zones need further investigation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31157#action_31157 ] 

Evan Ireland commented on ODATA-11:
-----------------------------------

Although zone-offset qualified dateTimes are often suitable/preferred for past events, they may not be applicable to future events.

Suppose the current date is sometime in February 2007 and I record an appointment. My pseudo-schema is:

when : dateTime (zoneless)
where : string

I then create an appointment

var a = new Apppointment();
a.when = dateTime("2007-10-01T10:00:00");
a.where = "WLG"; // IATA code for Wellington, New Zealand

In other words, I want the event to occur at 10 a.m. local time in Wellington on 1 October, 2007. And I am identifying the intended time zone by location, not zone name or offset.

If dateTime cannot be zoneless, then a system propagating or storing this value may mess up, because in March 2007, the NZ government will decree that DST will come into effect on the last Sunday of September rather than (previously) the first Sunday in October.

Some other good examples are out there. I would refer people to read "A Brief History of DateTime" (http://blogs.msdn.com/b/bclteam/archive/2007/06/18/a-brief-history-of-datetime-anthony-moore.aspx).


> date/time values without explicit time zones need further investigation
> -----------------------------------------------------------------------
>
>                 Key: ODATA-11
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-11
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>            Reporter: Andrew Eisenberg
>            Assignee: Michael Pizzo
>
> The reflection in OData of date/time values without explicit time zones needs further investigation.
> One way in which this issue manifests itself is in the comparison of a datetime value with a timezone to a datetime value without a timezone.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira