summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeorg Greve <greve@katana.(none)>2010-11-19 11:07:15 (GMT)
committerGeorg Greve <greve@katana.(none)>2010-11-19 11:07:15 (GMT)
commitccc12fce4d6b346484a0c65b1da44bc84399d966 (patch)
tree534959d033fac27f8630f25cc53536706648ea9e
parent6352c5dc3b292ed53530984d9ed92b190373b063 (diff)
downloadkeps-ccc12fce4d6b346484a0c65b1da44bc84399d966.tar.gz
Added reference to Douglass draft at IETF
-rw-r--r--KEP-0002.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/KEP-0002.txt b/KEP-0002.txt
index f7b031a..ed37e8d 100644
--- a/KEP-0002.txt
+++ b/KEP-0002.txt
@@ -118,6 +118,8 @@ The second case is slightly better because it is closer to what a user is likely
Usage of a database is also inevitable to keep the allowed selections synchronized between clients, ensuring a consistent user experience. While there is no officially recognized database that all applications refer to, the Olson database comes closest to being such a database, and the Olson timezone IDs are also used by the Unicode Common Locale Data Repository (CLDR) as well as the International Components for Unicode (ICU). The CLDR also provides mapping for Microsoft Windows time zone IDs to the standard Olson names.
+If and when the RFC Timezone Service Protocol<ref name="douglass">Douglass, http://tools.ietf.org/html/draft-douglass-timezone-service-00</ref> has matured further and sees implementation, it is likely to provide accurate data with mapping of aliases to DST data without local databases, thus resolving the primary weakness of the approach, and will likely support the Olson timezone database aliases, as they are already widely used.
+
So using references to the Olson timezone database is likely the best out of an imperfect set of choices.
=== How to retain backward compatibility and allow for smooth transition ===