Re: Models: Structural Object Class

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 11:08 AM 1/27/2003, Jim Sermersheim wrote:
>>2.4.2. Structural Object Classes
>
>It may be good to note (as X.501 does) that an entry's
>structuralObjectClass attribute may be interrogated to discover which
>value of the entry's objectClass attribute is the structural object
>class.

And 'governingStructureRule', too?

 3.4.5. 'structuralObjectClass'            
  
 The attribute indicates the structural object class of the entry.

     ( 2.5.21.9 NAME 'structuralObjectClass'                   
       EQUALITY objectIdentifierMatch
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.38
       SINGLE-VALUE NO-USER-MODIFICATION
       USAGE directoryOperation )

 The 'objectIdentifierMatch' matching rule and OBJECT IDENTIFIER
 (1.3.6.1.4.1.1466.115.121.1.38) syntax is defined in [Syntaxes].
  

 3.4.6. 'governingStructureRule'
         
 The attribute indicates the structure rule governing the entry.

     ( 2.5.21.10 NAME 'governingStructureRule'                
       EQUALITY integerMatch
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
       SINGLE-VALUE NO-USER-MODIFICATION
       USAGE directoryOperation )

 The 'integerMatch' matching rule and INTEGER
 (1.3.6.1.4.1.1466.115.121.1.27) syntax is defined in [Syntaxes].


Personally, I don't have a problem adding both of these as they
address technical omissions.  One, however, could consider the
above to be 'LDAP non-"core" schema' [LDAPBIS charter].  This
charter issue I defer to Bob (who acts as sole chair in regards
to this I-D).

Kurt