Abstract: The relationships between physical data store schema, object model, and end-user property may be encoded in the source of the object model using attributes. Reflection may be used to build the table of those relationships so that changes to the relationships between those three layers can be easily and quickly made without impacting higher levels in the software stack.

Abstract: Time-related properties may be modeled independent of a base object. Rather than storing time properties with the object, they may be stored independently. A given object may be stored once, even if it has a recurrent time property. The description of a “meeting,” for example, may be stored once. Each occurrence of that object over time may be stored in a “timeslot” (object <foo>occurs at time ‘t’ on day ‘d’). If it is a recurring property, recurrence information may be stored independently. “Exception” information may be stored independently as well.