- From: Cyrus Daboo <cyrus@daboo.name>
- Date: Sun, 19 Mar 2017 12:23:03 -0500
- To: Joe Touch <touch@isi.edu>, "Walter H." <Walter.H@mathemainzel.info>
- cc: ietf-http-wg@w3.org
Hi Joe, --On March 19, 2017 at 8:45:48 AM -0700 Joe Touch <touch@isi.edu> wrote: >> look at this image: >> https://cdn.pbrd.co/images/LkqU6dJCk.png >> there you see the end of the "appointment" is the beginning of the next >> day which is invalid ... > > That is correct if you interpret 'end' as the time when something ceases, > not the last instant inside the interval. > > But this is far out of scope for the ietf. > Actually the IETF does specify that in RFC5545 (iCalendar). iCalendar defines the time range <start, end> as start being "inclusive" and "end" being exclusive. It is up to a client to decide how best to present that to a user. When displaying timed events to users, it makes sense to show a 1 hour meeting at 10 am as "10 am -> 11 am". However, for all-day events, showing a 1 day event on Monday as "Monday -> Tuesday" is certainly "odd" as most users don't appreciate the difference between "inclusive" and "exclusive". In fact some clients will adjust the end date displayed to the user to the previous date specified in the iCalendar DTEND property, giving a display range that matches most users expectations. -- Cyrus Daboo
Received on Sunday, 19 March 2017 16:23:32 UTC