| |
Subclassing: How does LDAP object class grow? |
|
|
Subject: Subclassing: How does LDAP object class grow?
Author: eLDAP
In response to: Objectclass and Subclassing: Abstract, Structural and Auxiliary Object Class
Posted on: 08/02/2006 06:33:55 PM
An object class can be derived from an object class which is itself derived from an even more generic object class. This process stops at the most generic object class, top, which is an abstract object class used as a superclass of all structural object classes. This single chian of subclassing is commonly referred as inheritance.
An object class may be derived from two or more direct superclasses. This feature of subclassing is termed multiple inheritance.
>
> On 08/02/2006 01:27:29 PM eLDAP wrote:
Object Classes
In LDAP, an object class defines the set of attributes that can be used to define an entry.
An object class can be one of three types:
Structural: indicates the attributes that the entry may have and where each entry may occur in the DIT. This object class represents the corresponding real world object. Entries must belong to a structural object class, so most object classes are structural object classes.
Auxiliary: indicates the attributes that the entry may have. An auxiliary object class does not represent a real world object, but represents additional attributes that can be associated with a structural object class to supplement its specification. Each entry may belong to only a single structural object class, but may belong to zero or more auxiliary object classes.
Abstract: defined only as a superclass or template for other (structural) object classes. An abstract object class is a way of collecting a set of attributes that will be common to a set of structural object classes, so that these classes may be derived as subclasses of the abstract class rather than being defined from scratch. An entry may not belong to an abstract object class.
References:
|
|
|
|
