Ooooh - That's a good enlightenment.
Actually, now I gotta go back and correct
a whole bunch of RDN usage in the documentation
so maybbbe not so gooddd. Ignorance is bliss :-)
I'll make sure I qualify which RDN I'm talking
about in the documentation then, unless I
specify the relative context.
And since you use "name component" (Which sounds pretty standard)
I'll use that as well...so I'll say rightmost name component...cooooolll.
Thanks Alex,
- Ole
Alex Karasulu wrote:
Ole,
Also note that an RDN can be more than one name component in the DN. It
can be multiple name components as long as it is relative to some
context. For example if your context is dc=example,dc=com then you can
have an RDN of cn=oersory,ou=users. This is two name components but
it's still relative hence it's an RDN.
The terminology is a bit weird this way.
Alex
On 4/10/07, *Ole Ersoy* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Stefan,
Cool - I'll just use rightmost segment then.
Here's the Design Guide Snipped where I'm using it,
in case I some other terminology makes more sense:
-----------------------------------------------------------------
Then the last object on the list is capitalized, such that it matches
the name of the root DataObject's Type. Using the created list
the string that is the base DN is written. Note that the
rightmost segment <i>ou=com</i> of the DN uses the attribute label
<i>ou</i>. Thus when a new server partition for <i>com</i> is
added, it must use the attribute label <i>ou</i>.
-----------------------------------------------------------------
Thanks,
- Ole
SNIP
