Date: Thu, 28 Mar 2024 21:52:25 +0000 (UTC) Message-ID: <1151784657.7065.1711662745243@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7064_1502790621.1711662745241" ------=_Part_7064_1502790621.1711662745241 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LDAP specification allows the use of attribute options. Attribute op= tions can provide metadata about values for the attribute. Multiple options= can be provided for a given attribute/value.
The classic example is language. displayName;lang-en
tells =
you that this is the English version of displayName. displayName;lang=
-jp
would be the Japanese version.
displayName;lang-en: Hideki Matsui
displayName;lang-jp: =E6=9D=BE=E4=BA=95=E7=A7=80=E5=96=9C
Generally, options behave intuitively. A query without specifying an opt=
ion should match all relevant attributes (ie: displayName
matc=
hes both displayName;lang-en
and displayName;lang-jp), while a more specific query matches only relevant attributes (so
would not match either of the above examples).=