[OASIS Issue Tracker] Issue Comment Edited: (ODATA-14) add Edm.Date to the OData primitive data types

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

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

Evan Ireland edited comment on ODATA-14 at 9/5/12 11:52 PM:
------------------------------------------------------------

I would like to add my support for the addition of a Date data type, as distinct from DateTime.
I recently requested some real-life data models from enterprise mobility customers, and collected statistics for utilization of the various data types used (which in our enterprise mobility data models, are based on XML schema data types).

Model 1 {boolean=1, date=13, dateTime=1, decimal=35, int=172, long=5, string=1318, time=2}

Model 2 {long=24, string=164}

Model 3 {date=2, dateTime=1, long=9, string=38, time=1}

Model 4 {date=25, decimal=1, double=1, long=30, string=489, time=12}

Model 5 {date=14, decimal=7, long=15, string=167, time=8}

Model 6 {byte=1, date=2, decimal=10, long=11, string=161, time=2}

You will note that in most cases, the "date" data type is far more prevalent than dateTime (also note that "time" is more prevalent than dateTime).

Such a significant prevalence of "date" in real-life customer data models calls for recognition of this in OData Models as a separate type from DateTime.

Note that in all the above models  the data types (date, time and dateTime) are without zone offset.

Given the complexity associated with handling DateTime values that have no zone offset specified (are they interpreted as UTC, or as "Time Zone Independent Field-Based Time"  as defined in http://www.w3.org/TR/2005/NOTE-timezone-20051013/), it is particularly troublesome if there is no Date type. We have seen situations where it is extremely difficult when passing data across multiple tiers to a mobile device, and back again, people's birth dates can end up being unintentionally changed in the back-end system.


      was (Author: evan.ireland):
    I would like to add my support for the addition of a Date data type, as distinct from DateTime.
I recently requested some real-life data models from enterprise mobility customers, and collected statistics for utilization of the various data types used (which in our enterprise mobility data models, are based on XML schema data types).

Model 1 {boolean=1, date=13, dateTime=1, decimal=35, int=172, long=5, string=1318, time=2}

Model 2 {long=24, string=164}

Model 3 {date=2, dateTime=1, long=9, string=38, time=1}

Model 4 {date=25, decimal=1, double=1, long=30, string=489, time=12}

Model 5 {date=14, decimal=7, long=15, string=167, time=8}

Model 6 {byte=1, date=2, decimal=10, long=11, string=161, time=2}

You will note that in most cases, the "date" data type is far more prevalent than dateTime (also note that "time" is more prevalent than dateTime).

Such a significant prevalence of "date" in real-life customer data models calls for recognition of this in OData Models as a separate type from DateTime.

Note that in all the above cases the data types (date, time and dateTime) are without zone offset. I will comment on that in a separate issue.
  
> add Edm.Date to the OData primitive data types
> ----------------------------------------------
>
>                 Key: ODATA-14
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-14
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>            Reporter: Andrew Eisenberg
>            Assignee: Ralf Handl
>
> The addition of Edm.Date to the OData primitive data types might be considered. 
> Date values are widely used. SQL supports the DATE data type. XML Schema supports the xs:date data type. 
> Example:
>       <ComplexType Name="DeliveryFormatAvailability">
>         <Property Name="Available" Type="Edm.Boolean" Nullable="false" />
>         <Property Name="AvailableFrom" Type="Edm.Date" Nullable="true" />
>         <Property Name="AvailableTo" Type="Edm.Date" Nullable="true" />
>         <Property Name="Rating" Type="Edm.String" Nullable="true" MaxLength="Max" Unicode="true" FixedLength="false" />
>         <Property Name="Runtime" Type="Edm.Int32" Nullable="true" />
>       </ComplexType>

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