It would be interesting to know what some X.500 vendors currently do. This seems to beg for some kind of 'ambiguousStructuralRule' error.
>>> "Steve McLain" <firstname.lastname@example.org> 2/22/04 8:28:10 PM >>>
What is the desired/proper behavior if when adding a new entry, there are two or more possible dITStructureRules that could equally be the governingStructureRule?
NameForm1 mandatory cn, optional ou, namedObjectClass orgPerson
NameForm2 mandatory cn, optional sn, namedObjectClass orgPerson
Attempting to add a orgPerson object with the rdn of "cn=ldapuser" to a parent object that has a governingStructureRule
What dITStructureRule is set for the governingStructureRule or should this error?
I have looked through X.500 and the current model draft, I have not found the answer yet.