[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#4835) dyngroup.schema needs clarification

Full_Name: Howard Chu
Version: 2.3/HEAD
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (
Submitted by: hyc

Our current schema definition defines groupOfURLs as a structural objectclass.
This  matches the definition used by Netscape, where this schema originates.
However, the published documentation describes it as an auxiliary objectclass,
and indeed the Netscape/iPlanet/Sun/FDS/RHDS servers use it as if it were an


This ambiguity arises because Netscape/iPlanet/Sun/FDS/RHDS don't actually
implement the LDAP/X.500 data model correctly. There are many areas where they
fail to implement the model, but in this specific case they simply don't enforce
schema definitions.


And it appears that their developers didn't consider this a problem worthy of

But it's creating confusion for other users.


I think the right thing to do here is change our definition to AUXILIARY since
that matches its actual usage. It won't match the published definitions, but
those definitions are demonstrably wrong.