[OASIS Issue Tracker] (CMIS-708) Clarify Browser Binding DateTime property values

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

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

Florian Müller commented on CMIS-708:
-------------------------------------

I can't point you to meeting minutes, but the reason not to include the timezone was that JavaScript Date objects don't store timezones and the transport format should be as simple as possible.

> Clarify Browser Binding DateTime property values
> ------------------------------------------------
>
>                 Key: CMIS-708
>                 URL: https://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 Müller
>            Assignee: Gregory Melahn
>            Priority: Trivial
>             Fix For: V1.1
>
>
> 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 was sent by Atlassian JIRA
(v6.1.1#6155)