[ https://issues.oasis-open.org/browse/ODATA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67943#comment-67943 ]
Michael Pizzo edited comment on ODATA-1123 at 10/26/17 4:11 PM:
----------------------------------------------------------------
In C#, PHP, and Java (at least) there is no representation for 24:00. PHP will accept 24:00 and store as 00:00 (https://stackoverflow.com/questions/13060467/difference-between-2400-and-0000).
I am worried about how timeofday values would be roundtripped with such clients.
Also curious how they compare. Is 24:00 > 00:00? In PHP they would presumably be compared equal.
Finally, do we support an hour value of 24 in DateTimeOffset?
see also: https://en.wikipedia.org/wiki/24-hour_clock
was (Author: mikep):
In C#, PHP, and Java (at least) there is no representation for 24:00. PHP will accept 24:00 and store as 00:00.
I am worried about how timeofday values would be roundtripped with such clients.
Also curious how they compare. Is 24:00 > 00:00? In PHP they are compared equal.
Finally, do we support an hour value of 24 in DateTimeOffset?
> Allow 24:00:00 for Edm.TimeOfDay (public review comment c201710e00003)
> ----------------------------------------------------------------------
>
> Key: ODATA-1123
> URL: https://issues.oasis-open.org/browse/ODATA-1123
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: CSDL JSON , CSDL XML
> Affects Versions: V4.01_CSD03, V4.01_CSD02
> Reporter: Ralf Handl
> Fix For: V4.01_CS01
>
>
> Public review comment https://lists.oasis-open.org/archives/odata-comment/201710/msg00003.html
> CSDL 4.01 permits Edm.TimeOfDay values to range from 00:00:00 to 23:59:59.999*.
> However existing systems (e.g. SAP backends) frequently utilize 24:00:00 to indicate end-of-day. Requiring these values to be transmitted (e.g. to clients) as 23:59:59.999* could result in round-trip data loss.
> In fact such SAP systems (for V2/V4) already will return PT24H or normalization-equivalent (for the V2 format of Edm.Time using XSD duration) or 24:00:00 (for the V4 format of Edm.TimeOfDay using XSD time), which is non-compliant with OData V2-V4 specifications.
> To improve interoperability, it would be preferable to standardize this behaviour.
> Note that the lexical format for XSD time permits 24:00:00, as it is the left-truncation of dateTime lexical representation, and dateTime lexical representation (see https://www.w3.org/TR/xmlschema-2/#dateTime) states:
> - hh is a two-digit numeral that represents the hour; '24' is permitted if the minutes and seconds represented are zero, and the dateTime value so represented is the first instant of the following day (the hour property of a dateTime object in the ·value space· cannot have a value greater than 23);
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
