Terminology
Terminology used in LDAP
- 
  
  
- 
  
  
- This object class consists of zero or more attributes
 
 - 
  
  
- This object class consists of zero or more attributes
 
 
 - 
  
  
 - 
  
  
- ObjectClass
 - ObjectClass
 
 
- 
Data is represented as hierarchy of objects,each of which is called entry.The resulting tree structure is called a Directory Information Tree (DIT). The top entry of the tree is called root.
 - 
Each entry in the tree has one parent entry and zero or more child entries.
 - 
Each entry is composed of one or more objectClasses. -> These objectClasses contain zero or more attributes.
 - 
These attributes have names just like values.
 
ObjectClasses.
Objectclasses is like a container of attributes,where each objectClass has a unique name.There exists a predefined set of ObjectClasses,each of which contains lot of attributes.
Characteristics of ObjectClasses:
- objectClasses defines whether the attribute member should be 
MUSTorMAYbe present. - objectClass types: 
STRUCTURAL,AUXILIARY,ABSTRACT, and there should be atleast oneSTRUCTURALobjectClass with zero or more AUXILIARY objectClasses. - objectClass inherits properties and characteristics from its parent objectClass (including its attributes).
 
Attributes.
Attributes contains values,which are present within the objectClass,each attribute define the data type.
Attributes are mostly defined in key=value pair.
- 
Attributes can be optional
MAYor mandatoryMUSTdefined in that object class.If it is inherited by multiple objectClasses, in one objectClass it can be mandatory in another object class it can be optional, this is defined by the objectClass. - 
Attributes can be
SINGLEorMUTLIvalued. 
some examples for attributes like cn aliased commonName which is within the objectClass person,organizationalPerson and so on..
Another example is dc aliased domainComponent which is present under the objectClass dcObject.
# Entry Level Hierarchy
dn: dc=example,dc=com
dc: example
description: The best company in the whole world
objectClass: dcObject
objectClass: organization
o: Example, Inc.
## FIRST Level hierarchy - people 
# this is an ENTRY sequence and is preceded by a BLANK line
dn: ou=people, dc=example,dc=com
ou: people
description: All people in organisation
objectClass: organizationalUnit
## SECOND Level hierarchy - people entries 
# this is an ENTRY sequence and is preceded by a BLANK line
dn: cn=Robert Smith,ou=people,dc=example,dc=com
objectclass: inetOrgPerson
cn: Robert Smith
cn: Robert
sn: Smith
uid: rsmith
mail: robert@example.com
mail: r.smith@example.com
ou: salesDN attribute is the sum of all the RDN (Root Distinguished Name)