Previous Contents Index Next |
iPlanet Messaging and Collaboration Schema Reference |
Appendix A General Information
This appendix covers the following topics:
LDAP Overview
LDAP Overview
iPlanet Messaging and Collaboration products include object classes and attributes defined by the Lightweight Directory Access Protocol (LDAP) and extensions to the standard LDAP schema developed by iPlanet and by the Internet Engineering Task Force (IETF) that extend the basic functionality of LDAP.Initially developed at the University of Michigan, LDAP is a lightweight version of the X.500 Directory Access Protocol. LDAP has become an Internet standard for directory services running over TCP/IP.
One or more LDAP servers contain the data that make up the LDAP directory. An LDAP directory stores information in object-oriented hierarchies of entries. Each entry is uniquely identified by a distinguished name, or DN. The DN consists of the comma-separated sequence of attributes and values that specify the unique location of an entry within the directory information tree. This provides a path of names tracing the entry back to the top of the directory hierarchy.
Attribute Syntax
Directory data is represented as attribute-value pairs. Any specific piece of information is associated with a descriptive attribute.Each attribute has a corresponding syntax definition. The syntax definition describes the type of information provided by the attribute.
Syntax Method
Abbreviation
Definition
Telephone numbers (identical to cis, but blanks and dashes (-) are ignored
Required and allowed attributes for each object class are included in the object class listing.
Unless otherwise noted, attributes are assumed to be multi-valued, that is, more than one instance of the attribute can be specified. Attributes that are single-valued, that is, only one instance of the attribute can be specified, are noted as such in the Syntax heading, found in each attribute definition.
Object Identifiers
To meet LDAP and X.500 standards, all attributes and objects should have been assigned Object identifiers (OIDs). An OID is a sequence of integers, typically written as a dot-separated string. The OID identifies who first filed the name of the object or attribute with the standards committee.For example, all Netscape-defined attributes have the base OID of 2.16.840.1.113370.3.1, and all Netscape-defined object classes have the base OID of 2.16.840.1.113730.3.2
In some cases, objects and attributes listed in this document do not have an OID assigned to them yet.
ISO 8601 Time Zones
There are 92 time zones:Africa/Amman
Africa/Cairo
Africa/Casablanca
Africa/Johannesburg
Africa/Lagos
Africa/Tripoli
Africa/Windhoek
America/Adak
America/Anchorage
America/Buenos_Aires
America/Caracas
America/Chicago
America/Costa_Rica
America/Cuiaba
America/Denver
America/Godthab
America/Grand_Turk
America/Halifax
America/Havana
America/Indianapolis
America/Los_Angeles
America/Miquelon
America/New_York
America/Phoenix
America/Port-au-Prince
America/Santiago
America/Sao_Paulo
America/St_Johns
Asia/Alma-Ata
Asia/Anandyr
Asia/Aqtau
Asia/Aqtobe
Asia/Baku
Asia/Bangkok
Asia/Beirut
Asia/Bishkek
Asia/Calcutta
Asia/Dacca
Asia/Irkutsk
Asia/Jerusalem
Asia/Kabul
Asia/Kamchatka
Asia/Karachi
Asia/Katmandu
Asia/Krasnoyarsk
Asia/Magadan
Asia/Novosibirsk
Asia/Rangoon
Asia/Riyadh
Asia/Shanghai
Asia/Tehran
Asia/Tokyo
Asia/Ulan_Bator
Asia/Vladivostok
Asia/Yakutsk
Asia/Yekaterinburg
Asia/Yerevan
Atlantic/Azores
Atlantic/Cape_Verde
Atlantic/South_Georgia
Atlantic/Stanley
Australia/Adelaide
Australia/Brisbane
Australia/Darwin
Australia/Hobart
Australia/Lord_Howe
Australia/Sydney
Europe/Bucharest
Europe/Istanbul z
Europe/London
Europe/Minsk
Europe/Moscow
Europe/Paris
Europe/Riga
Europe/Samara
Europe/Simferopol
Europe/Warsaw
Pacific/Apia
Pacific/Auckland
Pacific/Chatham
Pacific/Easter
Pacific/Fiji
Pacific/Gambier
Pacific/Guadalcanal
Pacific/Honolulu
Pacific/Kiritimati
Pacific/Marquesas
Pacific/Norfolk
Pacific/Noumea
Pacific/Pitcairn
Pacific/Rarotonga
Pacific/Tongatapu.
Previous Contents Index Next
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated January 30, 2002