|
Revision 50, 1.4 kB
(checked in by tv, 6 years ago)
|
Import version 0.0.24
|
| Line | |
|---|
| 1 |
<itemizedlist> |
|---|
| 2 |
<listitem> |
|---|
| 3 |
<para>An LDAP entry corresponds with an object.</para> |
|---|
| 4 |
</listitem> |
|---|
| 5 |
<listitem> |
|---|
| 6 |
<para>Whereas object are usually instances of a single class, |
|---|
| 7 |
LDAP entries can "implement" multiple objectClasses.</para> |
|---|
| 8 |
</listitem> |
|---|
| 9 |
<listitem> |
|---|
| 10 |
<para>objectClasses can inherit zero, one or many |
|---|
| 11 |
objectClasses, just like programming classes.</para> |
|---|
| 12 |
</listitem> |
|---|
| 13 |
<listitem> |
|---|
| 14 |
<para>objectClasses have a root class, known as |
|---|
| 15 |
<literal>top</literal>; many object oriented programming |
|---|
| 16 |
languages have a root class, e.g. named |
|---|
| 17 |
<literal>Object</literal>.</para> |
|---|
| 18 |
</listitem> |
|---|
| 19 |
<listitem> |
|---|
| 20 |
<para>objectClasses are either <literal>STRUCTURAL</literal> |
|---|
| 21 |
or <literal>AUXILIARY</literal>; entries can only implement |
|---|
| 22 |
one <literal>STRUCTURAL</literal> objectClass.</para> |
|---|
| 23 |
</listitem> |
|---|
| 24 |
<listitem> |
|---|
| 25 |
<para>The objectClasses of an entry can be changed at will; |
|---|
| 26 |
you only need to take care that the entry has all the |
|---|
| 27 |
<literal>MUST</literal> attribute types, and no attribute |
|---|
| 28 |
types outside of the ones that are <literal>MUST</literal> or |
|---|
| 29 |
<literal>MAY</literal>.</para> |
|---|
| 30 |
<para>Note that e.g. OpenLDAP doesn't implement this.</para> |
|---|
| 31 |
</listitem> |
|---|
| 32 |
<listitem> |
|---|
| 33 |
<para>Attributes of an entry closely match attributes of |
|---|
| 34 |
objects in programming languages; however, LDAP attributes may |
|---|
| 35 |
have multiple values.</para> |
|---|
| 36 |
</listitem> |
|---|
| 37 |
</itemizedlist> |
|---|
