Cyrus Daboo wrote:
Hi Lisa,
--On April 3, 2005 22:26:16 -0700 Lisa Dusseault
<lisa@xxxxxxxxxxxxxxxxx> wrote:
I'm curious, are there any clients with UIs that are capable of making
the distinction between those two kinds of user intent?
I allow a user to choose whether to set an end time or a duration on an
event (the default for new events being duration).
I had remembered this conversation from years ago.
The real problem is that the RDATE's are invalid
for the example. Solution below:
This example shows that for DTEND events the
same problem exists. Here I took Sam's example and tweak
it a bit to show the real problem.
His original example was in effect:
DTSTART:20050402T150000 2-APR 3pm
DTEND:20050403T180000 3-APR 6pm
RDATE;VALUE-DATE:20060403
(Not sure you can mix dtstart:date-time with rrule:date,
I thought I read that, but lets assume you can).
Now change it to this and you will see the real issue:
Start off with:
DTSTART:20050402T150000 2-APR-2005 3pm
DTEND:20050403T180000 3-APR-2005 6pm
Now add 2-APR-2006 and with a time:
RDATE:20060402T154500
So at what time does the 2nd instance end ? Notice that
the RDATE value starts 45 minutes after the 1st instance.
I think the answer is - undocumented.
Solution:
If you want an explicit end time for a repeating floating event,
then RDATE's MUST always be a 'PERIOD' format.
RDATE;VALUE=PERIOD:20060402T154500/20060403T180000
or
RDATE;VALUE=PERIOD:20060402T154500/+PT14H15M
That is the only way that repeating floating events
can have a forced end time that is predictable.
If you use DURATION and all of them have the same
length, then RDATE of type PERIOD is not needed.
If you use DURATION and they do not have the same
length, the it also needs RDATEs of type PERIOD.
Again two ways to do exactly the same thing.
--
Doug Royer | http://INET-Consulting.com
-------------------------------|-----------------------------
We Do Standards - You Need Standards
Doug.vcf
Description: Vcard
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify@xxxxxxxxxxxxxxxxx
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
|
