Re: adding url attribute to Organization or Organizational unit

["Graeme Joyce" <openldap-list@jade.co.nz>]

> That is, each entry should be of one structural objectclass.  You
> should list derived classes as values of the objectclasses values.
> Once created, you should never change, add, modify, delete the
> objectclasses which affect the "structure" of the entry.  That is,
> you shouldn't change a person to an inetOrgPerson (or vica versa)
> after initial creation.
>

Just wondering how to correctly define the objectclass values for an
"inetOrgperson" entry:

1)
objectclass: top
objectclass: person
objectclass: organizationalperson
objectclass: inetorgperson

OR

2)
objectclass: top
objectclass: inetorgperson

Does 1) meet the criteria: "entry should be of one structural class" ?

Is 2) acceptable, assuming you have no clients that require the "person" or
"organizationalperson" objectclasses on the entry?

Thanks
Graeme