[OASIS Issue Tracker] Issue Comment Edited: (CMIS-708) ClarifyBrowser Binding DateTime property values

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

    [ http://tools.oasis-open.org/issues/browse/CMIS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24722#action_24722 ] 

Florent Guillaume edited comment on CMIS-708 at 2/28/11 11:54 AM:
------------------------------------------------------------------

My use case is just that the timezone is part of the domain model so we'll have applications expecting to find out what's the timezone of a date, and expecting to get it back unchanged when it stores a date.


      was (Author: florent.guillaume):
    My use case is just that the timezone is part of the domain model so we'll have applications expecting to find out what's the timezone of a date is, and expecting to get it back unchanged when it stores a date.

  
> Clarify Browser Binding DateTime property values
> ------------------------------------------------
>
>                 Key: CMIS-708
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-708
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Browser Binding
>    Affects Versions: V1.1
>            Reporter: Florian Mueller
>            Priority: Trivial
>
> The current draft defines that DateTime property values are transmitted as milliseconds since 1970/01/01. It doesn't define a time zone, though.
> We should pin it down to UTC.

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