[Ietf-calsify] DTEND clarification in
PStephenson at gw.novell.com
Thu Nov 17 08:37:46 PST 2005
In section 7.1 Event Component, it states:
The "DTEND" property for a "VEVENT" calendar component specifies
the non-inclusive end of the event.
In section 7.4 Free/Busy Component, it states:
the "DTSTART" and "DTEND" properties specify an inclusive time
that surrounds the busy time information;
It would seem that this implies DTEND is inclusive not
Isn't DTEND non-inclusive in this case?
In section 22.214.171.124 Date/Time End, it states:
Description: Within the "VEVENT" calendar component, this
defines the date and time by which the event ends. The value MUST
later in time than the value of the "DTSTART" property.
but in section 7.1. Event Component it states:
For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE-TIME data type but no
"DTEND" property, the event ends on the same calendar date and
of day specified by the "DTSTART" property.
and also section 10. Recommended Practices it states:
2. A calendar entry with a "DTSTART" property but no "DTEND"
property does not take up any time. It is intended to represent
event that is associated with a given calendar date and time of
such as an anniversary. Since the event does not take up any
it MUST NOT be used to record busy time no matter what the value
the "TRANSP" property.
If not having a DTEND, it is defined to be the same as DTSTART,
why can't DTEND be defined to be the same as DTEND?
Or is it a matter of clarifying that you either have a DTEND
or you can't have a DTEND, if DTEND is the same as DTSTART?
Just my two bits.
More information about the Ietf-calsify