> >> Meaning what? If you mean common address book and mail clients then > >> you'd better stick to the standard or repeatedly/constantly explain to > >> your users why "no, I know that is what the field is labeled, but that > >> isn't what goes there". > >> Stick to the standard, don't cheat. > > Which standard says 'cn' is the fullname?
It is a defacto standard for contact information. > You can choose to populate 'cn' with a common name associated with a > person. If this includes the title (e.g. composing from 'title' and > 'sn') there is no reason why you should not do it. Because he mentions the use of PIM software like M$-Outlook. Every off-the-shelp PIM package will display the CN as "Name" and title as "Title" etc. Yes, you *SHOULD* be able to put anything you want as the CN (within reason), but in practice it doesn't work because the LDAP support is most every PIM is lousy. Not putting the name in CN will confuse users, and you'll certainly end up with name in CN if you allow user's to write to the Dit (assuming you can find PIM clients that support modifying the Dit). If you think you are going to use clients like M$-Oulook then you have to live by the constraints of how they see/use data, because you can't change it. --- You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
