2 commits - KEP-0002.txt

[Georg Greve]

 KEP-0002.txt |    1 +
 1 file changed, 1 insertion(+)

New commits:
commit 878aa2256b23f28c5d0be88eb3dc4eb6f767b576
Merge: 33ef34a... cf46085...
Author: Georg C. F. Greve <greve at kolabsys.com>
Date:   Wed Jan 26 19:01:20 2011 +0100

    Merge branch 'master' of ssh://git.kolabsys.com/git/keps



commit 33ef34a26ce2d07aeaa85e7ab8c0f7f7a4114ddc
Author: Georg C. F. Greve <greve at kolabsys.com>
Date:   Wed Jan 26 18:56:10 2011 +0100

    Included suggestion by Jeroen van Meeuwen

diff --git a/KEP-0002.txt b/KEP-0002.txt
index 3e4f78f..f2ca5bd 100644
--- a/KEP-0002.txt
+++ b/KEP-0002.txt
@@ -39,6 +39,7 @@ The type for datetime storage in Kolab XML is modified as follows:
 * All datetime storage fields '''MAY''' carry up to one 'tz' attribute describing the time zone in the uniform naming convention designed by Paul Eggert, specifying time zones from the Olson database, a.k.a. tz database, a.k.a. zoneinfo database <ref>[[wikipedia:Zoneinfo | Wikipedia: Zoneinfo]]</ref>.
 * All fields that store future dates at the time of writing an entry, e.g. the 'start-date' and 'end-date' fields, '''MUST''' define the 'tz' attribute. Where the event should be calculated strictly against UTC, emulating previous behaviour, the value of the 'tz' field must be set to 'UTC' (all caps) explicitly.
 * All clients '''MUST''' be capable of parsing datetime fields according to {{rfc|3339}} <ref name="rfc3339">{{rfc|3339|title=Date and Time on the Internet: Timestamps}}</ref> format and '''SHOULD''' support loose parsing according to the superset provided by ISO 8601 <ref name="iso8601">ISO 8601: https://secure.wikimedia.org/wikipedia/en/wiki/ISO_8601</ref>.
+* When parsing a datetime field with 'tz' attribute, clients '''MUST''' treat this attribute as the most authoritative field and the stored time written as local time in this time zone, regardless of which offset the stored time specifies. Where this offset contradicts the 'tz' attribute, the 'tz' attribute '''MUST''' prevail. It is therefore recommended to ignore the offset where a 'tz' attribute exists and only fall back to it where it does not.
 
 It is recommended that all clients '''SHOULD''' check the Olson database at least once every three months against the locally cached version, '''OR''' suggest update policies for their respective operating systems that ensure the Olson database gets updated regularly. As far as is known, all commonly used and supported GNU/Linux distributions do this already.