Re: Re: dtend removed?

I don't think I really understand the Use Case.  Can you give me two
examples of nursing shifts that you cannot express in iCalendar?  (or maybe
not sure if you can express in iCalendar)

We (Notes) might be able to express this in our UI in release 6 going
forward if this is what I think it is...
Thanks-
CS


ietf-calsify-bounces@xxxxxxxxxxxxxxxxx wrote on 04/04/2005 01:26:16 AM:

> I'm curious, are there any clients with UIs that are capable of making
> the distinction between those two kinds of user intent?
>
> Lisa
>
> On Apr 3, 2005, at 8:18 PM, Sam Roberts wrote:
>
> > Quoting Doug@xxxxxxxxx, on Sun, Apr 03, 2005 at 07:02:15PM -0600:
> >> Tantek Çelik wrote:
> >>> +1
> >>>
> >>> I concur with Sam's examples and conclusions.
> >>>
> >>> If interoperability is the primary goal of this endeavor rather than
> >>> theoretical reductionist simplification, then we should keep DTEND.
> >>
> >> The only thing proved is that nether DTEND or DURATION solves
> >> the problem.
> >>
> >> The real problem he found was that there is no one way
> >> to solve the problem of floating time events that
> >> occur access a time zone change.
> >
> > DURATION is a good solution for fixed-duration events.
> >
> >> We need to define the TZ math rules in the spec. Even
> >> with DTEND, it sill does not work all of the time.
> >
> > DTEND is the beginning of the solution for fixed-end events. It has
> > problems, they should be fixed.
> >
> > Saying there is no way in iCalendar to represent very common event
> > occurences such as a work shift doesn't seem like it will broaden
> > acceptance.
> >
> > When a hospital wants to represent its nursing shifts as recurring
> > events, an iCalendar doesn't do it they have two choices:
> >
> >  - throw iCalendar away, which would be a pity
> >  - extend the meaning of iCalendars to support this
> >
> > This group should define the meaning of recurring events with DTEND, to
> > avoid ad-hoc implementations by implementors.
> >
> > Sam
> >
> >
> > _______________________________________________
> > Ietf-calsify mailing list
> > Ietf-calsify@xxxxxxxxxxxxxxxxx
> > http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>
> _______________________________________________
> Ietf-calsify mailing list
> Ietf-calsify@xxxxxxxxxxxxxxxxx
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify