[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-107) Should OData support a "clock time" (xs:time) datatype?
[ http://tools.oasis-open.org/issues/browse/ODATA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32168#action_32168 ]
Stefan Drees commented on ODATA-107:
------------------------------------
I second Mike's proposal (from his 2013-01-23-comment) since it simplifies a lot and also covers the backward compatibility issues that arise.
> Should OData support a "clock time" (xs:time) datatype?
> -------------------------------------------------------
>
> Key: ODATA-107
> URL: http://tools.oasis-open.org/issues/browse/ODATA-107
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData ABNF Construction Rules v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Priority: Minor
> Fix For: WD01
>
>
> Edm.Time was intended to be xs:duration ("P1Y1M1DT1H1M1S"). On Sept 6, 2012 we approved ODATA-70 to consistently treat Edm.Time as xs:duration, but this led to discussion as to whether we should have a datatype for "clock time" separate from xs:duration, and whether that time should have an optional or required timezone.
> At that same meeting we agreed to repurpose this issue, which was originally somewhat a duplicate of ODATA-70, to track the possibly support for xs:Time.
--
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]