Re: ISSUE-106: Does having a timezone field make sense, should it be utfOffset or utcOffset and tz to better match vCard

Hi Christopher,

Le jeudi 20 janvier 2011 à 11:43 +1100, Christopher Hunt a écrit :
> utfOffset is not good enough alone given that has a temporal quality with regards to daylight savings time. A zoneinfo reference e.g. "Australia/Sydney" is much more meaningful as rules can be associated with this type of identifier.

We realize that, but one difficulty that appeared when we reviewed this
issue during our call yesterday is that the vCard RFC uses two
properties to denote the timezone of a given contact:
* a UTC-OFFSET property that is defined as hh:mm difference to UTC
* a TZ property, with an undefined format

Since compatibility with vCard is one of the design requirements of our
API, it's not clear yet whether we can usefully define a proper timezone
attribute (defined with a real timezone identifier), or if we are
reduced to use the less adequate but better defined utcOffset approach.

Dom

Received on Thursday, 20 January 2011 08:51:00 UTC