emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Michael Brand <michael.ch.brand@gmail.com>,
	Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Adding support for limits and exclusions to iCal recurring events
Date: Sat, 27 Jul 2013 23:11:47 +0200	[thread overview]
Message-ID: <87wqob1ze4.fsf@gmail.com> (raw)
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")

Toke Høiland-Jørgensen <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,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-07-27 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 15:55 Adding support for limits and exclusions to iCal recurring events Toke Høiland-Jørgensen
2013-07-22 11:45 ` Nicolas Goaziou
2013-07-22 14:56   ` Toke Høiland-Jørgensen
2013-07-24  8:38     ` Nicolas Goaziou
2013-07-24 16:01       ` Michael Brand
2013-07-24 17:25         ` Toke Høiland-Jørgensen
2013-07-27 21:11           ` Nicolas Goaziou [this message]
2013-07-27 22:16             ` Toke Høiland-Jørgensen
2013-07-24 18:23       ` David Rogers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqob1ze4.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@gmail.com \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).