Re: schema discrepencies (ITS#1175)

[dave@tamos.net]

Very wierd.  I guess I don't really have too much of a problem with an
attribute being listed in both MUST and MAY, but twice in one?  Ack!

thanks for the clear-up.

d!

Kurt@OpenLDAP.org wrote:
> 
> At 08:59 AM 5/26/01, dave@tamos.net wrote:
> >Full_Name: David E. Storey
> >Version: 2.x
> >OS: N/A
> >URL:
> >Submission from: (NULL) (216.254.88.83)
> >
> >
> >A little unsure about this one as I can't find any mention of it in the RFC's.
> >Can an objectclass list the same attribute as being both required and optional?
> 
> If listed in required, it is implicitly listed in optional.
> Hence, the listing in optional is extraneous.  But it is not
> illegal.
> 
> >Should the ldap_schema related functions check for this?
> >
> >in core.schema:
> >- residentialPerson has 'l' listed in both MUST and MAY.
> 
> As defined in RFC 2256.
> 
> >- organizationalRole has 'preferredDeliveryMethod' listed twice in MAY.
> 
> As defined in RFC 2256.
> 
> >in cosine.schema
> >- RFC822localPart has 'telephoneNumber' and 'telephonenumber' list under MAY.
> >- domain has 'streetAddress' listed twice in MAY.
> 
> As defined in RFC 1274 & X.520.
> 
> >in nis.schema
> >- oncRpc, ipProtocol have 'description' listed in both MUST and MAY.
> 
> As defined in RFC 2307
> 
> >These are all the discrepencies I could find among structural and auxiliary
> >objectclasses.
> >
> >d!