OGM-400

* `byte`s and `long`s are stored as JSON numbers
* `Calendar`s are stored as ISO8601 strings, including TZ information
* `Date`s are stored as ISO8601 strings, in UTC, without TZ information

Note there is no standardized date format in JSON and thus CouchDB. After some research, using ISO8601 Strings seems as the most commonly used approach to me.

That's how it looks like (assuming the time is 11:50 UTC):

    "updateTime": "11:50:40.193Z" //Date with @Temporal(TemporalType.TIME)
    "destructionDate": "2013-11-26T11:50:40.193Z" //Date with @Temporal(TemporalType.TIMESTAMP)
    "creationDate": "2013-11-26Z" //Date with @Temporal(TemporalType.DATE)
    "destructionCalendar": "2013-11-26T12:50:40.193+01:00" //Calendar with @Temporal(TemporalType.TIMESTAMP)
    "creationCalendar": "2013-11-26+01:00" //Calendar with @Temporal(TemporalType.DATE)