OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (ODATA-124) For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?

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

Michael Pizzo updated ODATA-124:

From 2012-11-7 face to face: 
-Leap seconds are not supported; valid values are 0-59. 

For Precision:
-MUST be 12 or less, SHOULD be 7 or less. Services should be aware that some clients are unable to support a precision greater than 7. Such clients should be aware of the potential for data loss when round-tripping values of greater precision. Such data loss can be prevented by using PATCH for updates and specifying only modified properties. 
    Environment: [Proposed]

> For round-tripping values, what precision must agents support for DateTime(Offset), and are leap seconds permitted?
> -------------------------------------------------------------------------------------------------------------------
>                 Key: ODATA-124
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-124
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Task
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_WD01
> We should define a minimum precision that agents must support for DateTime(Offset) when progapating values or proxying requests, and be explicit about whether leap seconds can/must be supported.
> Assuming for a moment that OData DateTime(Offset) does not support leap seconds, then suppose a computer system that implements "leap smear" over a day, by 1,000,000 microseconds smeared evenly over a day. That is approximately 12 (11.57) microseconds per second. The point here is that allowing for microsecond precision in DateTime(Offset) values in this case would amount to a "false" precision (the value may be less "accurate" than it is "precise"), given the variable length of seconds from day to day (the day before the leap second is observed, and the day the leap second is observed).
> Now while I appreciate that the lexical representation of date/times in OData V3 allows seconds=60 and that therefore presumably the intention was to support leap seconds, OData is likely to be used frequently together with HTML5 (which does not permit leap seconds or sub-millisecond precision), so I would recommend that OData should align with HTML5 and disallow leap seconds and sub-millisecond precision.
> See also: http://blogs.msdn.com/b/ericlippert/archive/2010/04/08/precision-and-accuracy-of-datetime.aspx

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]