Re: [Tzdist] How should tzdist support rscale?
Cyrus Daboo <cyrus@daboo.name> Tue, 06 January 2015 15:24 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 C39851A1AA1;
Tue, 6 Jan 2015 07:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001,
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 fbWHQDFzNd44; Tue, 6 Jan 2015 07:24:32 -0800 (PST)
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 214CB1A8850;
Tue, 6 Jan 2015 07:24:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
by daboo.name (Postfix) with ESMTP id 7251A809E32;
Tue, 6 Jan 2015 10:24:19 -0500 (EST)
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 K5ycJmj_fGTJ; Tue, 6 Jan 2015 10:24:19 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46])
by daboo.name (Postfix) with ESMTPSA id 0DD82809E25;
Tue, 6 Jan 2015 10:24:17 -0500 (EST)
Date: Tue, 06 Jan 2015 10:24:13 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Jonathan Lennox <lennox@cs.columbia.edu>, tzdist@ietf.org, calsify@ietf.org
Message-ID: <258A901779432BE2E9A929AD@caldav.corp.apple.com>
In-Reply-To: <21675.2462.186194.702206@compute03.cs.columbia.edu>
References: <21675.2462.186194.702206@compute03.cs.columbia.edu>
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=2026
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/lQ6Pe4u0JxTdQPIbfcHZ7UGe6eg
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 15:24:35 -0000
Hi Jonathan, --On January 5, 2015 at 5:01:02 PM -0500 Jonathan Lennox <lennox@cs.columbia.edu> wrote: > 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? If a time zone were indeed defined in terms of a non-Gregorian recurrence then it would seem reasonable to support that. > 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? If tz data publishers actually start wantint to produce data using non-Gregorian rules, then we can easily define an extension to the capabilities response to indicate that is an option. > 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? Actually the rscale document only mentions time zones once in Section 1 - and there it states that time zone rules (i.e., what comes from a publisher) is specified in terms of the Gregorian calendar - that does not imply VTIMEZONE itself is limited to Gregorian rules - just that no time zone data uses non-Gregorian. If you think that text needs re-wording to clarify that, I can certainly change it. At this point, I think the use of non-Gregorian rules in VTIMEZONE should not be ruled out, but tzdist does not need to support it until we have publishers actually wanting to use it. Of course at that point things will get tricky for the publisher as they will want to keep the Gregorian rules around for backwards compatibility. -- Cyrus Daboo
- [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