AKBKHOME Consulting Services Available : Linux, Embedded Linux, C, PHP and PHP-GTK, just Contact me at alan@akbkhome.com 
LDAP Schema | AKBK Home >>>
ldap objectclass
AKBK Home :: LDAP :: Attributes :: dITStructureRules

Attribute:  dITStructureRules 

Description:
These attributes are located in the subschema entry. All servers SHOULD recognize their name, although typically only X.500 servers will implement their functionality.

BNC Syntax: 2.5.21.1 NAME 'dITStructureRules' EQUALITY integerFirstComponentMatch Used By: subschema

Syntax: `DIT

ID : 1.3.6.1.4.1.1466.115.121.1.17
Values with this syntax are encoded according to the following BNF:

DITStructureRuleDescription = "(" whsp
ruleidentifier whsp ; DITStructureRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"FORM" woid whsp ; NameForm
[ "SUP" ruleidentifiers whsp ] ; superior DITStructureRules
")"

ruleidentifier = integer
ruleidentifiers = ruleidentifier |
"(" whsp ruleidentifierlist whsp ")"
ruleidentifierlist = [ ruleidentifier *( ruleidentifier ) ]

 
BNC Syntax:

Equality Matching: integerFirstComponentMatch

Description:

Servers which allow subschema entries to be modified by clients MUST support the following matching rules, as they are the equality matching rules for several of the subschema attributes.

Implementors should note that the assertion syntax of these matching rules, an INTEGER or OID, is different from the value syntax of attributes for which this is the equality matching rule.

If the client supplies an extensible filter using an objectIdentifierFirstComponentMatch whose matchValue is in the "descr" form, and the OID is not recognized by the server, then the filter is Undefined.

BNC Syntax: 






Contact me at alan@akbkhome.com - especially if you have some work for me :)