Re: [Tzdist] Next step

Doug Royer <douglasroyer@gmail.com> Mon, 19 October 2015 19:10 UTC

Return-Path: <douglasroyer@gmail.com>
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 D218A1B2BCD for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 12:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 z2eUxOuk7ejO for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 12:10:40 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DFA51B2B46 for <tzdist@ietf.org>; Mon, 19 Oct 2015 12:10:40 -0700 (PDT)
Received: by pabrc13 with SMTP id rc13so198905339pab.0 for <tzdist@ietf.org>; Mon, 19 Oct 2015 12:10:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=jKNXL9+NX9zovoy8pqIVG8LBhH7yztkBz6X7oWqPQRk=; b=PeZTYS6t5yS2qoiSzFyHXs7qIwoaWVkru/M39WPShUaPE0TxLkkN1kX7v+LgzXiAdq mRgbP2sM906z8UQt/y5mw+nHXznsrrE0Fia+zYkqKKiEa4ED9ClA7+jaAF5KYha1ZsOb ANdMmGcU/cQ1NMcAhpbup4CrbBe+7w7KG6wMk2XODDa/wWXRcKcxWF+GWGRgfpqbOB9K lSkkozb9bAAbut7IWY6D5oD12Dc+8KvuhfgSG41dODAIB6nS6laVvUUduk3j24ovsZ7o c7US5hqtjuImUD0+rINHA71cR2fBtreePk1ZXAuHIrknI2JFABymEPqEMntC8OVQAfyV psRw==
X-Received: by 10.68.213.73 with SMTP id nq9mr31785382pbc.104.1445281839879; Mon, 19 Oct 2015 12:10:39 -0700 (PDT)
Received: from [192.168.1.4] ([71.209.29.59]) by smtp.googlemail.com with ESMTPSA id t9sm29368321pbs.17.2015.10.19.12.10.38 for <tzdist@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Oct 2015 12:10:38 -0700 (PDT)
To: tzdist@ietf.org
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> <316D3AAC6E4A5336C1784897@caldav.corp.apple.com>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <5625402D.9070409@gmail.com>
Date: Mon, 19 Oct 2015 13:10:37 -0600
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <316D3AAC6E4A5336C1784897@caldav.corp.apple.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040008060709070406080405"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/Gvhz3ETpQpFyNqEh6GuGTPQTqkE>
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:10:42 -0000

On 10/19/2015 01:00 PM, Cyrus Daboo wrote:
> 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.
> 

Postal codes don't always map to time zones. When you live way out in
the country, the postal code can be more than 20 miles away from the
city with the same name.  The postal code is designed to route
snail-mail to your home, not define your physical location.

I know postal codes can cross time zones, city boundaries and perhaps
county boundaries, not aware of any state boundary issue. I picked the
Wells Nevada example for that reason. Some rural residents that live out
of the city limits have Wells zip codes because it is the nearest post
office. And they are not in the same time zone as Wells NV.

That would make the database a real mess to keep up to date.

-- 

Doug Royer - (http://K7DMR.us / http://DougRoyer.US)
DouglasRoyer@gmail.com
714-989-6135