What does the eDirectory schema use to define the types of objects that are allowed to exist within a container object?

Partitions are logical segments of the eDirectory tree used for distributing and replicating data, not schema components that control where object classes may be placed.

Object values are the actual data stored within a property of an object, not a schema mechanism used to define structural containment.

Object classes define the mandatory and optional properties an object may have, but it is specifically containment rules - not object classes themselves - that govern where those objects may reside in the tree.

Containment rules are a specific schema construct that explicitly define which object classes are allowed to be placed inside a particular container class. For example, containment rules specify that User and Printer objects may reside inside an Organizational Unit, ensuring the directory tree conforms to a valid and predictable hierarchical structure.

Object properties (attributes) describe the data that can be stored within an object, not the rules governing which object types can exist inside a container.