WS Calendar requirements

[Edward Koch <ed@akuacom.com>]

All,

My interest in WS calendar is in its application to DR signals and messages that contain information about upcoming DR events.  My requirements are fairly brief and include the following.

- Need for specifying a hierarchy of schedules and time slots. Probably three levels is sufficient.

- Need to be able to easily partition up a time period into time slots which fully cover the time period.

- Need to be able to specify time periods and their "sub-periods" in a manner which reduces the burden of validation and where possible done in such a manner that eliminates the possibility of invalid time specifications.  This requirement is to reduce the burden on lighter weight clients that may need to consume these schedules. For example given the above requirement of being able to completely partiion a time period into time slots that completely cover the period it should be possible to specify the time periods in such a way that it makes it impossible to define an illegal time slot.

- Need to be able to associate information with individual time slots, e.g. prices, shed levels, etc. that may be associated with a DR signal.  When you consider that all DR signals, whether they are based on price or grid reliability information, etc. contain schedules it is reasonable that there is defined the notion of a "DR Signal" that contains a schedule and then associate the appropriate information within the time slots of the schedule.  This is inverted from what some people may be considering wherein the fundamental data elements (e.g. price or shed level) has a schedule embedded within them.


I think this is it for now.


-ed koch