Re: [cmis-comment] browser binding timezone extension

["Mueller, Florian" <florian.mueller02@sap.com>]

Hi Michael,

Thank you for your suggestion. The CMIS TC discussed this in the last TC call and decided not change the extension.

Your proposal makes life easier for some clients, but more difficult for servers and other clients. To validate a DateTime value, servers and clients would have to have the resolution at hand when parsing to throw an appropriate exception. That would make the extension and the implementations more complex. It would be also a feature that doesn’t exist in the other bindings.

Values of the resolutions „year" and „date" are not ambiguous with this format, but - as you mentioned - more error-prone. If you want to be absolutely sure that there no misunderstandings between the client and the server, set the timezone to GMT or use the simple format. 

Best Regards,

Florian

From: Michael Brackx <michael.antispam+cmis@gmail.com>
Date: Montag, 2. Juni 2014 10:55
To: "cmis-comment@lists.oasis-open.org" <cmis-comment@lists.oasis-open.org>
Subject: [cmis-comment] browser binding timezone extension

Hi,

It would be nice to include support for DateTime resolution in the browser binding timezone extension. The combination of timezones and resolution is tricky to get right.

I would propose to use ISO8601 years, dates depending on the resolution.

resolution year: YYYY

resolution date: YYYY-MM-DD

resolution time: as proposed

no resolution: as proposed

Michael