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] (ODATA-1123) Allow 24:00:00 for Edm.TimeOfDay (public review comment c201710e00003)

    [ https://issues.oasis-open.org/browse/ODATA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67944#comment-67944 ] 

Michael Pizzo commented on ODATA-1123:

Note that ISO 8601 allowed 24:00 but seems to disallow it in the 2016 draft: https://www.loc.gov/standards/datetime/ISO_DIS%208601-1.pdf:

NOTE 2 The expression 00:00:00 denotes beginning of day; for Information Technology Interchange there is no
representation of end of day. Thus even though it is recognized that the expression 24:00:00 is used as a natural
language expression to denote end of a day, this expression is not used for Information Technology Interchange.

> 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

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