[OASIS Issue Tracker] Commented: (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=31400#action_31400 ] 

Evan Ireland commented on ODATA-14:
-----------------------------------

In further support of adding Date and also retaining DateTime (without Offset), please consider the precedent that has been set by IETF RFC 6321 (xCal: The XML Format for iCalendar), sections 3.6.4 (date), 3.6.5 (date-time) and 3.6.12 (time).

    http://tools.ietf.org/html/rfc6321

For date-time and time types, note how the xCal specification states:

"Note that while [W3C.REC-xmlschema-2-20041028] allows for a UTC offset to be included in date/time values, xCal does not use that, and instead follows the iCalendar behavior of using time zone definitions via the "TZID" property parameter."

The xCal specification then erroneously includes a "Z" suffix for some (but not all) date-time values in its examples section :-( 
Please ignore those errors for the sake of this discussion :-)

So the "gold-standard" for interoperability of information about future events uses zoneless values, as well as *separate* TZID values. Applications working with such values need some extra knowledge (for example an up-to-date TZID database). Correct behaviour of scheduling applications (built using OData technologies but perhaps *encapsulating* xCal data) cannot therefore simply be accomplished by requiring the use of zone-offset (i.e. eliminating DateTime and just retaining DateTimeOffset).



> 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