[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-calendar] Is there a difference?
That is my sense, Bill, but I am trying to make sure. For this conversation, assume UTC, leaving out DST and related issues. I’m looking for whether there should be a deeper meaning when applied to services. For people, if a CalConnect meeting starts at 12:00 and goes for an hour, one could argue that since they always start at 12:05, this means that it is scheduled until 1:05…. For services, I am interested in what is the required / expected state of the service at 3:01. Let’s say I schedule a room for 78 degrees between 2-3. Let’s say I schedule the same room for 72 degrees between 3-4. Let’s say that I know it takes 10 minutes to go between the temperatures. If the first schedule is in response to DR for Energy, then I am committed to not setting the thermostat *until* 3:00 If the second schedule is in response to CEO arriving for a meeting, then I am committed to getting the room temperature down *by* 3:00 "If something is not worth doing, it`s not worth doing well" - Peter Drucker
From: William Cox [mailto:wtcox@CoxSoftwareArchitects.com] I think that "support" and "the profile says use this" are two different things. What’s the difference in *actions*, and in *performance* between Do X beginning at 2:00 for an hour duration Do X beginning at 2:00 for and ending at 3:00 Do X for an hour ending at 3:00 All are possible using the VTODO data structure. One (C) is not allowed if I understand correctly Within any interaction, it would be simpler, cleaner to allow only (A) or (B) Do we need to allow both? Does B have a finite stop and A does not? Why would we support both? tc “It is difficult to get a man to understand something, when his salary depends upon his not understanding it” -- Upton Sinclair.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]