The dateTime package exists to abstract dates and times.

The Range Class is a collection Class for DateTime instances. Range should be used even if a single, or no, instance of a dateTime Class is expected. Any Class that implements the repeat interface may be stored in a Range.

Enums in the package all have a public String getDisplayString() method that allows a UI to display only the values that have an implementation in the core system. If extra functionality is added to the core, UIs will be automatically updated with the new functionality. For classes The toString() method should be used for display in UIs.

Now that we have the graph database, non-composed Enums are a problem. So TimeSlot has been changed to a Class,a Time Class has been added and Session has been removed.This will involve a lot of updates but should not affect functionality.

• Repeat

• Date
• Range
• TimeSlot

• RepeatRange
• Session

Is the RepeatRate Enum a problem? Should it be an inner class of Range? -- neo