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.
An implementer should read [MS-ADTS] sections 220.127.116.11 and 18.104.22.168 to understand the data model in this specification. Specifically, the State Modeling Primitives and Notation Conventions in this document are per [MS-ADTS] section 22.214.171.124.2.
This protocol operates over an external directory instance that is composed of a set of named objects as described in [MS-ADTS] section 3.1.1.
Objects are retrieved from the directory database using the Active Directory Web Services: Custom Action Protocol Web Service Protocol by specifying attribute values that the object's attribute's values satisfy (for example, object!distinguishedName must match an input string). Sections 126.96.36.199 and 188.8.131.52 list the Active Directory attributes and classes that are relevant to this protocol.
When requesting or manipulating directory objects, the constraints on individual objects and their attributes MUST be honored as specified in [MS-ADTS].