[OASIS Issue Tracker] (CMIS-773) Timezone support in browser binding

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

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

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

Here is a proposal for a CMIS extension that addresses the topic:
https://www.oasis-open.org/committees/document.php?document_id=53091&wg_abbrev=cmis


> Timezone support in browser binding
> -----------------------------------
>
>                 Key: CMIS-773
>                 URL: https://tools.oasis-open.org/issues/browse/CMIS-773
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Browser Binding
>         Environment: CMIS 1.1
>            Reporter: Peter Monks
>
> In CMIS 1.1, DateTime values in the Browser Binding use Unix epoch time, which doesn't provide any support for timezones.  This functionally cripples the Browser Binding and is inconsistent with the SOAP and AtomPub bindings, which both provide full timezone support (via ISO-8601 DateTime values).
> Amongst other problems, this issue manifests itself as:
> * loss of information when a client reads a timezone-specific DateTime value from a CMIS repository
> * inability for a client to write a timezone-specific DateTime value to a CMIS repository
> * incidental complexity for clients that make use of multiple bindings concurrently
> Note: proposed solutions must be fully functional regardless of the value of the Browser Binding's "succinct mode".  Specifically, it must _not_ be a requirement that succinct mode be disabled in order to gain this capability 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)