[Tzdist] How should tzdist support rscale?
Mon, 05 January 2015 21:13 UTC
Return-Path: <lennox@cs.columbia.edu>
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 22A1D1A8A80;
Mon, 5 Jan 2015 13:13:32 -0800 (PST)
X-Quarantine-ID: <DYfy5lne31_G>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Missing required header field: "From"
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5
tests=[BAYES_50=0.8, MISSING_FROM=1, RCVD_IN_DNSWL_MED=-2.3]
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 DYfy5lne31_G; Mon, 5 Jan 2015 13:13:29 -0800 (PST)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
by ietfa.amsl.com (Postfix) with ESMTP id E082D1A8A6A;
Mon, 5 Jan 2015 13:13:28 -0800 (PST)
Received: from compute03.cs.columbia.edu (compute03.cs.columbia.edu
[128.59.11.33])
by mailbackend.panix.com (Postfix) with ESMTPA id 49C7D132E2;
Mon, 5 Jan 2015 16:13:28 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21674.65143.707505.318547@compute03.cs.columbia.edu>
Date: Mon, 5 Jan 2015 16:13:27 -0500
To: tzdist@ietf.org,calsify@ietf.org
X-Mailer: VM 8.1.0 under 23.3.1 (x86_64-pc-linux-gnu)
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/k_Bx7A7sNCp7cw4ebRd4DxGRjFM
X-Mailman-Approved-At: Tue, 06 Jan 2015 02:39:03 -0800
Subject: [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: Mon, 05 Jan 2015 21:13:32 -0000
(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.) A question recently occured to me about the interaction of rscale and tzdist. Should it be possible for a VTIMEZONE -- either inline in an iCalendar document, or distributed by tzdist -- to use an RSCALE? There are some natural use cases for this -- Iran uses the Persian calendar to set its DST observances, and Israel used the Hebrew calendar from 2005-2012. Right now the IANA tzdata just expands non-Gregorian rules to a list of dates, but in principle, RSCALE would be a much more natural (and compact) way of representing rules like these. However, tzdist has no way to negotiate the use of iCalendar extensions. Should one be defined? For that matter, the rscale draft doesn't talk about its use in VTIMEZONE at all (indeed, it asserts that VTIMEZONEs are always specified in Gregorian time). Should it? -- Jonathan Lennox lennox@cs.columbia.edu
- [Tzdist] How should tzdist support rscale? Jonathan Lennox
- Re: [Tzdist] How should tzdist support rscale? Doug Royer
- Re: [Tzdist] How should tzdist support rscale? Lester Caine
- [Tzdist] How should tzdist support rscale?
- Re: [Tzdist] How should tzdist support rscale? Cyrus Daboo
- Re: [Tzdist] How should tzdist support rscale? Lester Caine
- Re: [Tzdist] How should tzdist support rscale? Jonathan Lennox
- Re: [Tzdist] How should tzdist support rscale? Jonathan Lennox