Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb format media type?
Lester Caine <lester@lsces.co.uk> Thu, 08 January 2015 10:08 UTC
Return-Path: <lester@lsces.co.uk>
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 7DA0A1ACCF8
for <tzdist@ietfa.amsl.com>; Thu, 8 Jan 2015 02:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5
tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 yJNu9PajScya for <tzdist@ietfa.amsl.com>;
Thu, 8 Jan 2015 02:08:05 -0800 (PST)
Received: from mail4.serversure.net (mail4-2.serversure.net [217.147.176.214])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 96ED91A89A6
for <tzdist@ietf.org>; Thu, 8 Jan 2015 02:08:04 -0800 (PST)
Received: (qmail 8158 invoked by uid 89); 8 Jan 2015 10:08:01 -0000
Received: by simscan 1.3.1 ppid: 8142, pid: 8151, t: 0.1461s
scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677
Received: from unknown (HELO ?10.0.0.8?)
(lester@rainbowdigitalmedia.org.uk@86.169.173.116)
by mail4.serversure.net with ESMTPA; 8 Jan 2015 10:08:01 -0000
Message-ID: <54AE5700.2010505@lsces.co.uk>
Date: Thu, 08 Jan 2015 10:08:00 +0000
From: Lester Caine <lester@lsces.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "tzdist@ietf.org >> Time Zone Data Distribution Service" <tzdist@ietf.org>
References: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
<54ADC723.60707@cs.ucla.edu> <54AE15C6.10807@cisco.com>
In-Reply-To: <54AE15C6.10807@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/MBsfLyJghDiBLQwGJw_ILBZrTuo
Subject: Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb
format media type?
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: <http://www.ietf.org/mail-archive/web/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: Thu, 08 Jan 2015 10:08:07 -0000
On 08/01/15 05:29, Eliot Lear wrote: > I stand corrected. Paul's right. I was thinking of the source file. Not having actually looked at the binary tz setup - I still work with the raw data files - I'm not sure if each TZid has it's own full expansion from the base generic rules? Is that the case Paul? With large areas of the world NOW using a generic rule, one of the American areas, or European time, I can envisage a 'distributor' that provides only a current subset of timezone data? Perhaps even truncated to 2010 and used for ICALENDAR/IEVENT current events. In much the same way that the mechanism for monitoring 'version' comes out in the wash, one that maps TZid to the core generic rules should also come out naturally? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
- [Tzdist] [tzdist] #34 (service): should we includ… tzdist issue tracker
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Eliot Lear
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Ken Murchison
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… tzdist issue tracker