odata message

Subject: [OASIS Issue Tracker] Created: (ODATA-281) Keep second() as integer, introduce FractionalSeconds

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Wed, 27 Feb 2013 02:07:50 -0500 (EST)

Keep second() as integer, introduce FractionalSeconds
-----------------------------------------------------

                 Key: ODATA-281
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-281
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData ABNF Construction Rules, OData Protocol , OData URL Conventions 
    Affects Versions: V4.0_WD01
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_WD01


ODATA-215 was originally intended to address the apparent overlap between hour, minute, and second functions for datetimeoffset and duration datatypes, and did so by replacing the not-terribly-useful hour/minute/second functions for duration with a totalseconds function.

Along the way we also noted that we had no way to represent fractional seconds, and so we changed the return type of the second function for datetimeoffset to return a decimal.

Upon further reflection, I think this is inconsistent; the second portion is a separate portion from fractional seconds, just as day is separate from hour is separate from minute is separate from second. I would instead like to keep second() an integer, and introduce a fractionalsecond function that returns the fractional seconds as a decimal value <1.

This is more consistent, for example, with how SQL and many programming languages handle parts of datetime functions.

-- 
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