Keep with standard Object classes and standard attributes as much as you can: they fullfill most of the real needs. Of course you may need custom attributes: the way that you describe is correct, to define the new attributes, put them in an auxiliary class. Add the auxiliary class to the structural (standard class) that you use to defin objects. It is customary to call custom attributes and classes using a small prefix just to distinguish the names. My company is Syntlogo and "our" attributes are of the type syTelephoneNumber, syGivenName and so on.
You may want to get an OID, even if your server doesn't require it: you can request it at http://www.iana.org/assignments/enterprise-numbers. Even the idea to group these attributes in homogeneous classes is correct: you hardls need more than few of them, if you perform an accurate modeling. 6 or 8 are ok, avoid 12-15... So even your consultant is right: no one objectClass more than exaclty needed. You can always define a new óne, so keep the design as clean as possible. Best regards, mit freundlichen Grüßen Giovanni Baruzzi [EMAIL PROTECTED] -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 17. Oktober 2006 16:49 An: [email protected] Betreff: [ldap] Fw: Object classes - A few custom or many *standard* 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. --- 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.
