directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ole Ersoy <>
Subject Re: Question on schema elements in documentation: OIDs for examples?
Date Fri, 20 Apr 2007 23:28:12 GMT
Hi Stefan,

It looks really good.  I'll probably we frequenting that when I need
reminders.  :-)

Also, I found Emmanuel's tip for browsing the Schema partition
(by adding an ou=schema connection) to LDAP studio really handy.

I'm not done reading yet, but I started with this:

The schema of an LDAP server is comprised of object classes, attributes, 
syntaxes and matching rules. Basically it defines which entries are 
allowed within the server and how the server should handle them. In 
contrast to the 1.0 release, ApacheDS 1.5.0 comes with a completely 
redesigned schema subsystem. It allows to dynamically update the schema, 
for instance it is possible to create new attribute types or object 
classes on the fly, i.e. without restarting the server.

Here's another attempt:

The schema of an LDAP server is a set of entries of the following types:
- ObjectClass
- AttributeType,
- Syntax
- MatchingRule

The first three types of entries are used to the schema rules / 
structure of other stored in the server.  ApacheDS 1.5.0 comes with a 
completely redesigned schema subsystem. It enables dynamic schema
updates, like the creation of new AttributeType or ObjectClass entries 
at runtime.

I still need to figure out MatchingRule entries...:-)

I think the only thing that needed grammatic fixing was this part:

It allows to dynamically update the schema,

The rest is just a suggestion.

- Ole

Stefan Zoerner wrote:
> Hi all!
> I have started a little text for newbies on how to add custom elements 
> to the schema with the help of the new schema subsystem of ApacheDS. 
> First of all: I works fine to add elements with standard JNDI methods, 
> well done, Alex!
> My first attempts for the text can be found here:

> I plan to make this an introduction section to the schema topic in the 
> Advanced User's Guide of ApacheDS 1.5, although there is obviously still 
> some work to do. Any feedback on the current structure and state of the 
> section is therefore highly appreciated! I am a newbie on this schema 
> subsystem as well.
> The section is build around an example of adding a custom attribute type 
> (numberOfGuns) and a custom object class (ship) to the schema in order 
> to add entries like this one for instance:
> dn: cn=HMS Victory,ou=ships,o=sevenSeas
> objectClass: top
> objectClass: ship
> cn: HMS Victory
> numberOfGuns: 104
> description: a ship of the line of the Royal Navy, built between 1759 
> and 1765
> For adding numberOfGuns and ship to the schema I have to use OIDs, but I 
> think it is not worth to register them officially below 
> Should I use obvious fun data like and, describe 
> the idea of OIDs and that a user should normally obtain a unique 
> starting point?
> Or should I use something which starts with and add 
> it on the list. Perhaps we can add a branch for documentation examples.
> What do you think?
> Greetings from Hamburg,
>     Stefan Zoerner (szoerner)

View raw message