[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=31161#action_31161 ] 

Ralf Handl commented on ODATA-11:
---------------------------------

That's an excellent example for always requiring a timezone: to interpret the "when" property, a consumer needs to know that its values are relative to the "where" property. 

If OData only had DateTimeOffset, the publisher would have to apply its local knowledge when translating this internal storage model into an OData model and translate the local datetime value to UTC.

By offering both DateTime and DateTimeOffset data types, we give the publisher the chance to confuse clients and require out-of-band knowledge to interpret the "when" value.

> 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