Re: [Tzdist] How should tzdist support rscale?

Lester Caine <lester@lsces.co.uk> Tue, 06 January 2015 00:20 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 E29651A90A1 for <tzdist@ietfa.amsl.com>; Mon, 5 Jan 2015 16:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Pxl7tq2Fof9r for <tzdist@ietfa.amsl.com>; Mon, 5 Jan 2015 16:20:39 -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 D1E231A9097 for <tzdist@ietf.org>; Mon, 5 Jan 2015 16:20:38 -0800 (PST)
Received: (qmail 29396 invoked by uid 89); 6 Jan 2015 00:20:37 -0000
Received: by simscan 1.3.1 ppid: 29390, pid: 29393, t: 0.0554s 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; 6 Jan 2015 00:20:37 -0000
Message-ID: <54AB2A54.4030509@lsces.co.uk>
Date: Tue, 06 Jan 2015 00:20:36 +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
References: <21675.2462.186194.702206@compute03.cs.columbia.edu> <54AB231A.9020107@gmail.com>
In-Reply-To: <54AB231A.9020107@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/6e-KDmuw1kjPrVJZz-c19VN8K84
Subject: Re: [Tzdist] How should tzdist support rscale?
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: Tue, 06 Jan 2015 00:20:42 -0000

On 05/01/15 23:49, Doug Royer wrote:
>> (Cc'ing both tzdist and calsify because the issue is about the
>> interaction
>> of specs defined by the two groups...please trim to one or the other
>> if the
>> topic ends up being unique to that group.)
> That's such a complex topic, as you have been thinking about it, perhaps
> you should compose and send a draft?

Since TZ is already truncated to a Gregorian calendar I'd view better
calendar support in the same extension as pre-1970 data. Something that
many people need, but which is not 'tasked' to be provided via TZ. We do
need better support for a whole range of material relating to calendar
and time but currently TZ is not the place to provide that core data :(
We need a base to maintain everything which is not specifically within
the narrow window that TZ provides.

-- 
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