RE: BYDAY and YEARLY

[kiwong <ki.wong@xxxxxxx>]

> -----Original Message-----
> From: Dan Hickman [mailto:dhickman@xxxxxxxxxxxxxxxxxx]
> Sent: Monday, July 07, 2003 3:02 PM
> To: kiwong; ietf-calendar@xxxxxxx
> Subject: RE: BYDAY and YEARLY
> 
> 
> You miss my point.  For yearly events, the BYMONTH is also derived from
> DTSTART.  For the sample, it would derive BYMONTH=5 since BYMONTH is not
> included in the RRULE.
> 

I don't think I miss your point. The RFC you quoted below is valid if the
recurring instance cannot be obtained by the RRULE, then use the DTSTART.
But the example RRULE:FREQ=YEARLY;BYDAY=20MO clearly defines the date of
the recurring instances, which are 20th Monday yearly. Whether it is in
May or not is not relevant because the date is already defined by the
RRULE.

ki


> Dan
> 
> > -----Original Message-----
> > From: Dan Hickman [mailto:dhickman@xxxxxxxxxxxxxxxxxx]
> > Sent: Monday, July 07, 2003 2:05 PM
> > To: kiwong; ietf-calendar@xxxxxxx
> > Subject: RE: BYDAY and YEARLY
> >
> >
> > But the from the same section 4.3.10
> >    Information, not contained in the rule, necessary to determine the
> >    various recurrence instance start time and dates are derived from
the
> >    Start Time (DTSTART) entry attribute. For example,
> >    "FREQ=YEARLY;BYMONTH=1" doesn't specify a specific day within the
> >    month or a time. This information would be the same as what is
> >    specified for DTSTART.
> >
> > Using your logic, the following RRULE example from the RFC would assume
> May
> > as the BYMONTH and would mean the 20th Monday in May.
> >      DTSTART;TZID=US-Eastern:19970519T090000
> >      RRULE:FREQ=YEARLY;BYDAY=20MO
> >
> 
> But the day here is defined, which is the 20th Monday of the year.
> However, the time is not defined, so I will interpret it as 20th Monday
of
> the year at time 090000.
>