Directory Services |
The display specifier for an object class contains the following attributes that can be used to specify the localized display names used in the UI for objects of that class:
The attributeDisplayNames values are Unicode strings; each element consists of a comma-delimited name pair:
<attribute name>,<display text>
In this example, <attribute name> is the lDAPDisplayName of the attribute and <display text> is the text to display as the name of that attribute in the user interface.
Because many vendors may extend classes with new attributes or creating entirely new classes, it is important that the class and attribute display names are unambiguous and do not result in conflicts.
Each vendor should prefix the class display name with a unique friendly identifier based on the vendor name. For example, if the fictitious company, Fabrikam Inc., creates a new class derived from the "contact" class, they can have a unique class display name "Fabrikam Contact."
If a vendor extends an existing class with new attributes, they should again uniquely identify the attribute display name so that no conflicts occur with other attribute display names. Again, prefixing the attribute display name with unique friendly identifier based on the vendor name is good practice. For example, if the Fabrikam company extends the user class with a new HR attribute, they could uniquely display the attribute as "Fabrikam HR Information."
In addition, from a localization perspective, each vendor should localize the class and attribute display names into each language supported by Microsoft® Windows® 2000.
A name mapping value can be added to the attributeDisplayNames attribute.
To add a value to the attributeDisplayNames property
For more information about naming new classes and attributes, see Naming Attributes and Classes.