Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual page 41

The Directory Server schema differs slightly from the LDAPv3 schema, as it uses its
own proprietary object classes and attributes. In addition, it uses a private field in
the schema entries called
defined originally. For example, if a schema entry is defined in the standard
LDAPv3 schema, the
Netscape for the Directory Server's use, the
Netscape Directory Server
For example, the standard person object class appears in the schema as follows:
objectclasses: ( 2.5.6.6 NAME 'person' DESC 'Standard Person Object
Class' SUP top MUST (objectlass $ sn $ cn) MAY (description $
seealso $ telephoneNumber $ userPassword) X-ORIGIN 'RFC 2252' )
This schema entry states the object identifier, or OID, for the class (
name of the object class (
then lists the required attributes (
attributes (
description
For more information about the LDAPv3 schema format, refer to the LDAPv3
Attribute Syntax Definitions document (RFC2252).
The differences between Directory Server 5.0 schema and Directory Server 4.x are
described in the following table:
Directory Server 4.x Syntax
bin
ces
cis
dn
int
tel
In addition, Directory Server 5.0 supports the following syntaxes:
Syntax
OctetString
URI
, which describes where the schema entry was
X-ORIGIN
field refers to RFC 2252. If the entry is defined by
X-ORIGIN
.
), a description of the class (
person
objectclass
, ,
seealso telephoneNumber
Equivalent Directory Server 5.0 Syntax
Binary
IA5String
DirectoryString
DN
INTEGER
TelephoneNumber
Description
Same behavior as Binary.
Same behavior as IA5String.
Netscape Standard Schema
field contains the value
X-ORIGIN
standard person
, , and ) and the allowed
sn cn
, and
userPassword
Chapter 3 How to Design the Schema
), the
2.5.6.6
),
).
41