[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=31642#action_31642 ] Michael Pizzo commented on ODATA-107: ------------------------------------- The current Edm.Time really is clock time; it's defined to be valid values are between 0-23:59.fffffff. The only slightly strange part is that the serialization form is defined as a subset of xs:dateTimeDuration. > 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 ATOM Format v1.0, OData Protocol v1.0 > Reporter: Michael Pizzo > Priority: Minor > > 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]