[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: schema
At 11:36 PM 4/9/2003, Michael Ströder wrote:
>Kurt D. Zeilenga wrote:
>>At 11:54 AM 4/9/2003, De Leeuw Guy wrote:
>>
>>>Why the attributes entryCSN and entryUUID does not appear in
>>>the schema of the server ? (openldap 2.1.16/17)
>>Because there isn't yet a formal specification (e.g., RFC)
>>defining these operational attributes.
>
>Hmm...
>
>>>is a this technical reason ?
>>It's more process than technical. We'll publish the
>>descriptions once the IETF specifies what they are.
>
>How about publishing an experimental schema description with OpenLDAP-specific OIDs in the mean time?
Doing such tends to cause far worse problems. It hinders our
ability to change the specification / implementation.
>Everyone at the IETF-LDAP lists is telling LDAP programmers to look at the schema for everything.
Well, it should be clear to most LDAP'ers that you cannot do much
without knowledge of schema.
>But if the application developers do it's far from complete. Oh, yeah. The next answer is you shouldn't expect the schema to be complete... :-(
Applications which ask for all user and operational attributes
(especially all operational attributes) should be able to do
safely handle (ignore?) elements they don't understand. Or
they should just ask for elements they understand.
>E.g. for every attribute type I'd like to see whether it's there and whether is has 'NO-USER-MODIFICATION' and/or 'USAGE directoryOperation'.
Such information will not always be made available to you. Deal with it.
- Follow-Ups:
- Re: schema
- From: Michael Ströder <michael@stroeder.com>
- References:
- Re: schema
- From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: schema
- From: Michael Ströder <michael@stroeder.com>