When To Extend Your Schema; Getting And Assigning Object Identifiers - Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual

/usr/netscape/servers/slapd-
The following sections describe customizing the directory schema in more detail:
•

When to Extend Your Schema

•

Getting and Assigning Object Identifiers

• Naming Attribute and Object Classes
• Strategies for Defining New Object Classes
• Strategies for Defining New Attributes
• Deleting Schema Elements
• Creating Custom Schema Files
• Custom Schema Best Practices
When to Extend Your Schema
While the object classes and attributes supplied with the Directory Server should
meet most of your needs, you may find that a given object class does not allow you
to store specialized information about your organization. Also, you may need to
extend your schema to support the object classes and attributes required by an
LDAP-enabled application's unique data needs.
Getting and Assigning Object Identifiers
Each LDAP object class or attribute must be assigned a unique name and object
identifier (OID). When you define a schema, you need an OID unique to your
organization. One OID is enough to meet all of your schema needs. You simply
add another level of hierarchy to create new branches for your attributes and object
classes. Getting and assigning OIDs in your schema involves the following steps:
• Obtain an OID for your organization from the Internet Assigned Numbers
Authority (IANA) or a national organization.
In some countries, corporations already have OIDs assigned to them. If your
organization does not already have an OID, one can be obtained from IANA.
For more information, go to the IANA website at
http://www.iana.org/cgi-bin/enterprise.pl
serverID
/config/schema/99user.ldif
.
Chapter 3
Customizing the Schema
How to Design the Schema 47