Re: [Tzdist] Next step

Cyrus Daboo <cyrus@daboo.name> Mon, 19 October 2015 19:00 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01ACA1B2C75 for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 12:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cceJ-cqfe2n4 for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 12:00:17 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B76B01B2C4E for <tzdist@ietf.org>; Mon, 19 Oct 2015 12:00:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 21B78231A47A; Mon, 19 Oct 2015 15:00:13 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mIGHYsoh6wm; Mon, 19 Oct 2015 15:00:12 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 5729E231A46C; Mon, 19 Oct 2015 15:00:12 -0400 (EDT)
Date: Mon, 19 Oct 2015 15:00:10 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Doug Royer <douglasroyer@gmail.com>, tzdist@ietf.org
Message-ID: <316D3AAC6E4A5336C1784897@caldav.corp.apple.com>
In-Reply-To: <56253CCB.6010602@gmail.com>
References: <CADZyTkmO_PcfWTw-36U_6vo=EuDAnAmvUo6nvPZjkHjb_ALPSQ@mail.gmail.com> <40285_1445262970_t9JDu8BA043191_50DBD330DB51FDFC0C3E86D4@cyrus.local> <5624FAC4.5030008@andrew.cmu.edu> <B38549591D4FFBE5A83BF0BD@cyrus.local> <56253CCB.6010602@gmail.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=847
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/nida2W8_vIKjCa4tKB4uOY-H310>
Subject: Re: [Tzdist] Next step
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 19:00:19 -0000

Hi Doug,

--On October 19, 2015 at 12:56:11 PM -0600 Doug Royer 
<douglasroyer@gmail.com>; wrote:

>> I would prefer just geo URI -> tzid, and leave address->geo to some
>> other service (since that is useful in a number of other situations -
>> not just tzdist).
>
> The database should be separate, political boundaries change and who
> would keep up with (example) the city limits of Wells Nevada so the
> database can correctly map it to Mountain time when the rest of Nevada
> uses Pacific time?
>

It is true that there are already web services that do that kind of thing 
(see e.g., <http://www.geonames.org/export/web-services.html#timezone>). 
The question is whether that would be valuable for a client to do directly 
along side tzdist - or would we just let them rely on their existing 
"date-time/timezone" picker UI.

-- 
Cyrus Daboo