ADSM NetWare development is looking into changing the naming convention
for specifying NDS objects.  Does anybody have any preferences on
how they would like the naming conventions?

For example, the user 'Spike' is part of Organizational Unit 'Development'
which is part of the organization 'IBM'.  The name of container 'Spike'
in the context of the current ADSM naming convention is:

   DIRECTORY:/.O=IBM/.OU=Development.O=IBM/.CN=Spike.OU=Development.O=IBM

This type of specification 'simulates' a DOS-like directory structure.

Do you . . .

1) prefer the current specification?
2) prefer to use a naming convention similar to those used in NDS utilities
   (NWADMIN, NETADMIN)?  For example:

   DIRECTORY:/.CN=Spike.OU=Development.O=IBM

3) prefer to use a naming convention using elements of both (ie having
   a similar specification as NWADMIN/NETADMIN but with the highest level
   on the left)?  For example:

   DIRECTORY:/.O=IBM.OU=Development.CN=Spike

4) have an even better idea ?

Please keep in mind factors such as wildcard specifications (eg. say you
wanted to list all of the containers in .OU=Development).  Any input
would be appreciated.

Also, if anybody would care to share thoughts on backing up and restoring
the NDS (do you use ADSM, do you rely on NDS replication ...), we would
enjoy hearing from you.

Thanks,
ADSM NetWare development