[OASIS Issue Tracker] Updated: (ODATA-287) Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-287:
-----------------------------

         Proposal: Defer to 5.0
      Environment: [Proposed]
    Fix Version/s: V5.0_WD01

Evan and I suggest defering this issue to 5.0

> Consider adding a primitive type that corresponds with JSR 310 (JDK 1.8 time API) ZonedDateTime
> -----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-287
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-287
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Evan Ireland
>             Fix For: V5.0_WD01
>
>
> Please refer to ZonedDateTime in the JSR 310 (JDK 1.8 time API) documentation:
>   http://threeten.sourceforge.net/apidocs/javax/time/calendar/ZonedDateTime.html
> OData does not permit such a value (essentially a DateTimeOffset together with a named time zone region) to be represented except by using string or complex types.
> We might reasonably expect that OData interoperability with the new Java time system will be impacted by the omission of a corresponding CSDL primitive type.

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