When creating a schema for an enterprise directory server (ldap) is it a better practice to stay with the *standard* object classes which may require several and overlap to get all the attributes needed? Or, is it better to use inetOrgPerson | OrganizationalPerson | Person and then create one custom Auxilliary object class to pick up the miscellaneous attributes that are included in ePerson, cimLocation, eLocation, eContactPerson, and any other custom attributes for the organization?
I tend to lean towards keeping things as standard and consistent as possible, require 6 to 8 object classes for a person entry. A consultant is suggesting limiting the number of object classes. Any thoughts, or opinions? David S. Adams 785-575-1194 --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
