[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: SKI Presentation in Oslo
> From: Frank_Dawson@lotus.com
> Date: Wed, 18 Aug 1999 13:25:27 GMT
>
> Greg:
> In the following case:
> >case:
> >
> >James is definitely going to have a birthday party. We have planed it for
> >some time between the 2nd and the 4th of June.
> >
> >STATUS:CONFIRMED
> >Time property=Scheduled between the dates of June 2nd and June 4th
>
> If the DTSTART and DTEND are not fixed, then the STATUS can not be
> CONFIRMED. By definition, a confirmed event would have to have a precise
> start date/time. Hence, the more appropriate way to define this case would
> be:
I don't think your example (below) solves their problem. If I get all
appointments for June 3rd via CAP, this will not show up.
They could do it with an x-property. I think they are asking for
a standard way to do this. And again I go back to saying that
they need to propose some text and submit it to this list. And
then I think it must be a separate RFC.
> STATUS:NOT-YET-SCHEDULED
> DTSTART;VALUE=DATE:19990602
> X-NEW-DTSTART-FLEX;VALUE=PERIOD:19990602/19990604
> This would make use of a new enumeration for STATUS that _does not_
> ambiguate the existing values for this property. In addition, it would
> introduce a new property that is valid for VEVENTs with the
> "NOT-YET-SCHEDULED" status to indicate the range for the possible DTSTART
> (and another for the DTEND and DUE properties) or start of the calendar
> component.
> Creating a new calendar component is _not_ the right approach, given the
> requirements tendered todate. Also, we would not be adding a single new
> component, but rather three new ones. After all, this same "fuzzy"
> scheduling can apply to both VTODO and VJOURNAL calendar components also.
> -- Frank
-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM http://playground.sun.com/~dougr
Pager: Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131 Work: (650)786-7599
Mountain View, CA 94040 Ham Radio: N6AAW, Aviation: PP-ASEL