From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Adding support for limits and exclusions to iCal recurring
 events
Date: Sat, 27 Jul 2013 23:11:47 +0200
Message-ID: <87wqob1ze4.fsf@gmail.com>
References: <87ehbaxt33.fsf@toke.dk> <87d2qa6cnh.fsf@gmail.com>
	<87y58yprs6.fsf@toke.dk> <87ip005p5b.fsf@gmail.com>
	<CALn3zoh9Y9QU3=o40Y-StN3W1SHB9dmDfXKM+wkf3ahHAHRRdA@mail.gmail.com>
	<87mwpbg9al.fsf@toke.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1V3Bm8-0006gm-OH
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 17:11:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1V3Bm3-0006Te-HU
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 17:11:40 -0400
Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:63436)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1V3Bm3-0006TQ-BP
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 17:11:35 -0400
Received: by mail-we0-f180.google.com with SMTP id p61so2726013wes.11
	for <emacs-orgmode@gnu.org>; Sat, 27 Jul 2013 14:11:34 -0700 (PDT)
In-Reply-To: <87mwpbg9al.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\=
	\=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of
	"Wed, 24 Jul 2013 19:25:06 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
Cc: Michael Brand <michael.ch.brand@gmail.com>, Org Mode <emacs-orgmode@gnu.org>

Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke.dk> writes:

> Michael Brand <michael.ch.brand@gmail.com> writes:
>
>> When implementing this, consider also whether the END_DATE should be
>> an agenda entry on its own and of which kind, warning period etc. I
>> tried to make an example that shows this issue.
>
> Adding to this, as mentioned previously, I interpret the iCal standard
> to really permit and end *time* rather than an end *date*. Which would
> make more sense in an org context? Going for an END_TIME parameter, and
> then comparing exactly to the scheduled time (i.e. if current iteration
> of the recurring entry > END_TIME, then filter it), or doing an END_DATE
> and then interpreting the actual cut-off to be at 00:00:00 on that
> date?

I think it would be less ambiguous to use ICALENDAR_UNTIL (or UNTIL),
and apply RFC 5545:

  The value of the UNTIL rule part MUST have the same value type as the
  "DTSTART" property. Furthermore, if the "DTSTART" property is
  specified as a date with local time, then the UNTIL rule part MUST
  also be specified as a date with local time. If the "DTSTART" property
  is specified as a date with UTC time or a date with local time and
  time zone reference, then the UNTIL rule part MUST be specified as
  a date with UTC time.


Regards,

--=20
Nicolas Goaziou