- From: Joe Touch <touch@isi.edu>
- Date: Sun, 19 Mar 2017 10:57:51 -0700
- To: Cyrus Daboo <cyrus@daboo.name>
- Cc: "Walter H." <Walter.H@mathemainzel.info>, ietf-http-wg@w3.org
> On Mar 19, 2017, at 10:23 AM, Cyrus Daboo <cyrus@daboo.name> wrote: > > 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. Inside the protocol, it is certainly in scope. > It is up to a client to decide how best to present that to a user. Which includes how Outlook presents intervals - both of which are outside the scope of the IETF. Joe
Received on Sunday, 19 March 2017 17:58:44 UTC