Chris Allen <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> short answer:
>
> typically, organization is used to define your company, and
> organizationalUnit is used to hold departments and main offices, so use
> organizationalUnit.
>
> long answer:
>
> again use organizationalUnit, but be careful how many OUs you create.
The directory at stake here is one for a provincial governement, and
it will be both internal-facing (for white pages and authentification
services) and external-facing (a searchable public services
directory).
My plan at this point is to:
1. Use the "organizationalUnit" class as a starting point
2. Create a "govOrganizationalUnit" sub-class under
"organizationalUnit" that would hold entries describing the main
governement departments ("energy", "environment", "transportation" ,
...).
3. Create a "govDepartment" sub-class under "govOrganizationalUnit"
that would hold all entries pertaining to smaller entities with
departments ("HR", "IT", "Propaganda"..).
My goal is three-fold:
1. Allow internal-facing object classes such as "govPerson" to include
a DN entry to its service ("HR"), the service itself being a sub-class
of a government department ("transportation").
2. Allow external-facing object classes ("public services") to link to
the proper department or office.
3. In the yet-to-be-designed namespace, each "govOrganizationalUnit"
is very likely to be a node, and smaller "govDepartment" might be
sub-nodes as well.
Paul.
