On Sun, 27 Jul 2003, Kurt Cagle wrote: > I've added the optional <endDateTime> element to the <scheduledTime> > element. <endDateTime> and <duration> are mutually exclusive, you cannot > have both simultaneously. If neither <endDateTime> or <duration> is > included, the assumption is made that the event will take place for 1 hour.
Hi, Kurt. Just some thoughts... Sorry to make trouble, but is it really necessary to have two different elements for expressing the same thing? I am generally wary of redundancy in protocols, especially where it is possible for redundant representations to be in conflict. Why not just stick to a single <duration> element and keep it simple? Some events might not last any length of time -- for example, a deadline -- or an unknown length of time -- such as a dinner party. Instead of defaulting to a duration of 1 hour, how about interpreting events with no <duration> as having no duration? -- ?!ng
