[OASIS Issue Tracker] Created: (ODATA-314) CLONE -Please clarify the meaning of filter functions applied to DateTimeOffset values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

CLONE -Please clarify the meaning of filter functions applied to DateTimeOffset values
--------------------------------------------------------------------------------------

                 Key: ODATA-314
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-314
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Task
          Components: OData URL Conventions 
    Affects Versions: V4.0_WD01
         Environment: [Proposed]
            Reporter: Evan Ireland
            Assignee: Ralf Handl
             Fix For: V4.0_WD01


Consider for example the 'day' function applied to a DateTimeOffset.

Is this supposed to return the 'day' of the value when it is considered as UTC, or the 'day' component as it appears in the original literal value, which implies that the zone offset must be preserved when DateTimeOffset values are propagated?

If DateTimeOffset values are permitted to be 'normalized' by agents, but are not required to be, then the 'day' function applied to DateTimeOffset value would appear to be meaningless, unless it returns the UTC 'day'.


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