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] Updated: (ODATA-11) date/time values without explicit time zones need further investigation


     [ http://tools.oasis-open.org/issues/browse/ODATA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-11:
----------------------------

       Proposal: 
CSDL
-Remove Edm.DateTime (with no offset).
-Clarify that Edm.DateTimeOffset MUST have offset. i.e. has type xs:dateTimeStamp(http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp). 

URL Conventions
-add a maxdatetime() function to return the "last point in time" (i.e., used by temporal)
-also define a mindatetime() function to return the earliest point in time (for symmetry)

Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47764/latest/odata-meeting-19_on-20121220-minutes.html

  was:
-Remove Edm.DateTime (with no offset).
-Clarify that Edm.DateTimeOffset MUST have offset. i.e. has type xs:dateTimeStamp(http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp). Servers SHOULD attempt to preserve offset, but MUST preserve the correct normalized value. 
(Impl note: if underlying store doesn't have offset, normalize (i.e., to some database offset or UTC).
-add a maxdatetime() function to return the "last point in time" (i.e., used by temporal)
-also define a mindatetime() function to return the earliest point in time (for symmetry)

Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47764/latest/odata-meeting-19_on-20121220-minutes.html

    Component/s: OData URL Conventions v1.0

The proposal part 

    Servers SHOULD attempt to preserve offset, but MUST preserve the correct normalized value. 
    (Impl note: if underlying store doesn't have offset, normalize (i.e., to some database offset or UTC).

seems to be covered by ODATA-121 and only affects the Protocol part

> date/time values without explicit time zones need further investigation
> -----------------------------------------------------------------------
>
>                 Key: ODATA-11
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-11
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Andrew Eisenberg
>            Assignee: Michael Pizzo
>             Fix For: WD01
>
>
> The reflection in OData of date/time values without explicit time zones needs further investigation.
> One way in which this issue manifests itself is in the comparison of a datetime value with a timezone to a datetime value without a timezone.

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