Content deleted Content added
→Schema: added uniqueMember and memberOf attributes |
|||
Line 153:
The contents of the entries in a subtree is governed by a [[schema]].
The schema defines the ''attribute types'' that directory entries can contain. An attribute definition includes a ''syntax'', and most non-binary values in LDAPv3 use [[UTF-8]] string syntax. For example, a "mail" attribute might contain the value "user@example.com". A "jpegPhoto" attribute would contain photograph(s) in binary [[JPEG]]/JFIF format. A "uniqueMember", "memberOf", or "member" attribute contains the DNs of other directory entries. Attribute definitions also specify whether the attribute is single-valued or multi-valued, how to search/compare the attribute (e.g. case-sensitive vs. case-insensitive and whether substring matching is supported), etc.
The schema defines ''object classes''. Each entry must have an objectClass attribute, containing named classes defined in the schema. The schema definition of the classes of an entry defines what kind of object the entry may represent - e.g. a person, organization or ___domain. The object class definitions also list which attributes the entry MAY and MUST contain. For example, an entry representing a person might belong to the classes "top" and "person". Membership in the "person" class would require the entry to contain the "sn" and "cn" attributes, and allow the entry also to contain "userPassword", "telephoneNumber", and other attributes. Since entries may belong to multiple classes, each entry has a complex of optional and mandatory attribute sets formed from the union of the object classes it represents.
| |||