3.1.1 Abstract Data Model
This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.
Free/busy data is kept in a specific message in the public foldersmessage store. There is one message for each user for whom free/busy data is published. This message is called the free/busy message. It is contained in a folder that represents the administrative group to which the user belongs. There is one folder for each administrative group in the organization. All of these folders are descendants of the special folder SCHEDULE+ FREE BUSY. Each folder that represents an administrative group is a sibling of the folders that represent other administrative groups. An administrative group represents an organizational unit within an organization, as specified in [RFC1279]. The organizational unit is specified by the org-unit-rdn component of the distinguished name (DN) (1) of the Address Book object for the user, as defined in [MS-OXOABK] section 18.104.22.168.
The PidTagSchedulePlusFreeBusyEntryId property (section 22.214.171.124) is not persisted on any object but is temporarily cached in memory or computed on demand.