[Date Prev][Date Next]
Here is an example of a structural object class that subclasses both one
structural object class and one auxiliary object class. I believe this
is an important capability, so that a new structural object class can be
defined by augmenting another. Using a content rule to add the
auxiliary to the original class is not always possible because of
needing two distinct types of entries. In the example, there may be
entries with applicationEntity as the structural class and other entries
with mLAgent as the structural class.
( 2.16.8126.96.36.199.2.3.64 NAME 'mLAgent'
SUP ( 188.8.131.52 $
MAY 184.108.40.206 )
; 220.127.116.11 = applicationEntity
; 18.104.22.168 = pkiUser, an auxiliary object class
; 22.214.171.124 = supportedAlgorithms
My problem is that this important case appears to be precluded by the
statement in Models-09, 2.4.2:
"Structural object classes cannot subclass auxiliary object
What am I missing?