I think we actually agree on most points, just use different words.
I agree.
My major problem has been associated with one of control. If I cannot decide
what my name is, and use that name irrespective of the particular directory
service, then I feel that I have lost control of my name. If I pick a stupid
name, and people can't find me, that is my problem. If the directory service
picks a stupid name, and people can't find me, that's a problem I can't even
fix.
You bet! But the solution isn't to let everyone build the heirarchy differently
using different schema just because they have differing needs. In other words,
both interoperability and flexibility are important, and there are tradeoffs
between the two that have to be taken into account.
I happen to think that this stuff is *so* flexible that these two goals should
not conflict unless someone is in fact doing something dumb. But I've dealt
with too many screwy notions from customers to think that everyone will do this
stuff sensibly.
Ned