View Source

h3.Definition: Schema

The schema of a Directory Server defines a set of rules that govern the kinds of information that the server can hold. Directory schema is comprised of a number of different elements, including:

* [Attribute Syntaxes|Definition -- Attribute Syntax] -- Provide information about the kind of information that can be stored in an attribute.

* [Matching Rules|Definition -- Matching Rule] -- Provide information about how to make comparisons against attribute values.

* [Matching Rule Uses|Definition -- Matching Rule Use] -- Indicate which attribute types may be used in conjunction with a particular matching rule.

* [Attribute Types|Definition -- Attribute Type] -- Define an [OID|Definition -- Object Identifier] and a set of names that may be used to refer to a given attribute, and associates that attribute with a syntax and set of matching rules.

* [Object Classes|Definition -- Object Class] -- Define named collections of attributes and classify them into sets of required and optional attributes.

* [Name Forms|Definition -- Name Form] -- Define rules for the set of attributes that should be included in the [RDN|Definition -- Relative Distinguished Name] for an entry.

* [DIT Content Rules|Definition -- DIT Content Rule] -- Define additional constraints about the object classes and attributes that may be used in conjunction with an entry.

* [DIT Structure Rule|Definition -- DIT Structure Rule] -- Define rules that govern the kinds of subordinate entries that a given entry may have.

* [Attributes|Definition -- Attribute] are the elements responsible for storing information in a directory, and the schema defines the rules for which attributes may be used in an entry, the kinds of values that those attributes may have, and how clients may interact with those values.

Clients may learn about the schema elements that the server supports by retrieving an appropriate [subschema subentry|Definition -- Subschema Subentry].

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact