Re: [calsify] SKIP was Re: AD review of draft-ietf-calext-rscale-03

Barry Leiba <barryleiba@computer.org> Tue, 03 February 2015 03:41 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3101A1C02 for <calsify@ietfa.amsl.com>; Mon, 2 Feb 2015 19:41:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 XtJ6aOVcmDkM for <calsify@ietfa.amsl.com>; Mon, 2 Feb 2015 19:41:21 -0800 (PST)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 925671A1BBE for <calsify@ietf.org>; Mon, 2 Feb 2015 19:41:20 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id pn19so1558419lab.2 for <calsify@ietf.org>; Mon, 02 Feb 2015 19:41:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hnNQLKONT04T0mCDC2oaKyThHRugH6bp+YEtvkME3n0=; b=DN/SExXq+HWISKadFtm2ud+Xt95pG9H1vlvuEpTuo9+TsTQY0c5DGV1eFmylZJMws3 YY9/NKRCYKSJot+bA4WAuiABb6P9NjFYGu9004RyUHBsV65WAzDflGHuVtlgGw6Kb2SR 7PJ3kxApgcmKxzYmYq6wbiECp8gH6O5AEJtE+FcpJOmgteIVg65xZCuV1JY6P/T4+ca8 Kbu3+APzA32qb5bXsu+y2ESsUrXAlt3j/bZweLgN5bXlnm2OxNwto3tbta5LFWsAI38y 971I6nrVmMJGq95zu5jGXy86KiAm5XslVHk7YbNSC2GIZ8S35vuazVqXwKYxIPWSLlOV I6kQ==
MIME-Version: 1.0
X-Received: by 10.112.217.68 with SMTP id ow4mr22299120lbc.97.1422934878738; Mon, 02 Feb 2015 19:41:18 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Mon, 2 Feb 2015 19:41:18 -0800 (PST)
In-Reply-To: <68FCD7D11F934509267D5915@cyrus.local>
References: <68FCD7D11F934509267D5915@cyrus.local>
Date: Mon, 02 Feb 2015 22:41:18 -0500
X-Google-Sender-Auth: izn8Ex7KrOgB45bNQ4umuooo9io
Message-ID: <CALaySJKQP9WjRQV2qrgfLiGwj-SQAUCF6RVcQuRrUYNpfqp17A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary="001a1134c93efc5fb6050e26d7c0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/calsify/ajWIxlIi_IIJi18hLiaD9bLVOCA>
Cc: Calsify <calsify@ietf.org>
Subject: Re: [calsify] SKIP was Re: AD review of draft-ietf-calext-rscale-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 03:41:22 -0000

I think those descriptions are clear, and they look correct and complete to
me.  I'd be happy with them if the working group agrees.

But let me present an alternative formulation:

1. If the date is invalid because the month is not a valid month in the
currect year, the SKIP is to the next (forward) or previous (backward)
valid month.

2. Otherwise, the SKIP is to the next (forward) or previous (backward)
valid day.

I think that covers the situation.  If you think you need to explain the
different "day" situations further, which is never a bad thing, that can be
added as explanatory text.  Yes/no?

Barry

On Monday, February 2, 2015, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi,
> (Dealing with Barry's AD review issues #2 and #8 in a separate thread)
>
> OK, so I think you have identified a legitimate issue with SKIP. I would
> like to clarify the skip behavior as described below. I will propose
> concrete changes to the draft once we have agreed on the basic concepts.
>
> When a recurrence generates an invalid date, the following applies when
> SKIP is set to FORWARD or BACKWARD:
>
> 1) If the invalid date was generated from a rule starting on a leap day or
> a leap month: the SKIP value for forward/backward is then a day or a month,
> respectively.
>
> 2) If the invalid date was generated from a rule starting on a
> day-of-month not valid in the current month: the SKIP value for
> forward/backward is to the nearest valid day.
>
> 3) If the invalid date was generated from a rule with a BYMONTHDAY that
> results in a day-of-month not valid in the current month: the SKIP value
> for forward/backward is to the nearest valid day.
>
> Note that the above "rules" for SKIP are independent of the actual RSCALE
> value, which I believe is the correct approach (because otherwise we would
> need some kind of registry or an indicator from ICU as to what the behavior
> should be for each calendar scale).
>
> Can other RRULE experts please review the above and make sure those three
> descriptions are valid?
>
> --
> Cyrus Daboo
>
>