Abstract: Systems that provide users with a model for designing, implementing, complying with, and proving compliance with, message life cycle management policies are disclosed. Such a model may be based on the notion of folders upon which policies are defined, new restrictions on such folders, mechanisms to assure that users have such folders, and mechanisms to establish how well users are complying with the policies by determining how they are filing items into the folders. The concept can be extended to other mutually exclusive grouping mechanisms.

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.

Abstract: DAP-IT is a new innovative method to achieve what has not been able to be accomplished in the concrete construction industry. The usual procedure to obtain what is commonly called a “dap out”, or step down in a newly placed concrete slab was to use any available material that in the majority of cases resulted in a poorly formed dap out that was unacceptable by the owner and architects. Using DAP-IT will without fail provide a clean, true recess in the concrete slab that will be a relief to, not only the owner/architects, but to the concrete finisher, who is ultimately responsible for producing a workmen like product. There is no other product in today's market that even comes close to achieving what my invention, DAP-OUT will accomplish.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for presenting different types of electronic messages at a common interface. Electronic message items are stored in an item database along with other types of items, such as, for example, contact items, folder items, document items, etc. Electronic message items have some common defined data fields and possibly other differently defined data fields that represent protocol and/or application specific properties. Computer systems can query the item database for message related data (e.g., from commonly defined data fields) and display links to message related data at a common messaging interface. Links to different types of electronic messages (as represented by protocol and/or application specific properties) may be displayed simultaneously at the common messaging interface.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for efficiently storing and accessing electronic messages. Generally, electronic messages are created and transformed in accordance with an electronic message schema hierarchy. Electronic messages can be created according to a general message schema that defines a format for data fields that are common to all types of electronic messages (e.g. electronic mail, instant message, fax message). Electronic messages can also be extended according to message extension schemas that define formats for adding protocol specific and/or or application specific data fields to an electronic message. Data fields added in accordance with message extension schemas can differ between electronic messages types.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for decoupling an attachment from an electronic message that included the attachment. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. Attachments are configured to have a data field indicating if the attachment is to persist when a corresponding electronic message is deleted. When an attachment persists, a user may be able to locate and use the attachment after a corresponding electronic message has been deleted (even if the attachment has not been expressly saved). Attachments are configured to include attachment metadata indicating properties of an electronic message that included the attachment. Accordingly, a user can access information (e.g., sender, subject, date, etc) associated with an electronic message (e.g., that included the attachment) even after the electronic message has been deleted.

Abstract: The principles of the present invention extend to efficiently and reliably providing message related data. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. An electronic message can include links to folder items that represent message folders. An electronic message can also include links to contact items that represent message participants. Message applications can register for folder spaces such that each message application is aware of folders that are primarily controlled by other message applications. A link to a contact item can be selected to access current contact related data for a message participant, even when the contact related data has changed since an electronic message containing the link was received.