As per Relevance of the word representation, we have this rfc below:

---

Network Working Group T.
Request for Comments: 1960 University of
Obsoletes: 1558 June 1996
Category: Standards

A String Representation of LDAP Search

Status of this

This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited

1.

The Lightweight Directory Access Protocol (LDAP) [1] defines
network representation of a search filter transmitted to an
server. Some applications may find it useful to have a common way
representing these search filters in a human-readable form.
document defines a human-readable string format for representing
search filters

2. LDAP Search Filter

An LDAP search filter is defined in [1] as follows

Filter ::= CHOICE {
and [0] SET OF Filter
or [1] SET OF Filter
not [2] Filter
equalityMatch [3] AttributeValueAssertion
substrings [4] SubstringFilter
greaterOrEqual [5] AttributeValueAssertion
lessOrEqual [6] AttributeValueAssertion
present [7] AttributeType
approxMatch [8]
}

SubstringFilter ::= SEQUENCE {
type AttributeType
SEQUENCE OF CHOICE {
initial [0] LDAPString
any [1] LDAPString
final [2]
}
}



Howes Standards Track [Page 1]

RFC 1960 LDAP Search Filters June 1996


AttributeValueAssertion ::= SEQUENCE {
attributeType AttributeType
attributeValue
}

AttributeType ::=

AttributeValue ::= OCTET

LDAPString ::= OCTET

where the LDAPString above is limited to the IA5 character set.
AttributeType is a string representation of the attribute type
and is defined in [1]. The AttributeValue OCTET STRING has the
defined in [2]. The Filter is encoded for transmission over
network using the Basic Encoding Rules defined in [3],
simplifications described in [1].

3. String Search Filter

The string representation of an LDAP search filter is defined by
following grammar. It uses a prefix format

::= '(' ')'
::= | | | ::= '&' ::= '|' ::= '!' ::= | ::= | | ::= ::= | | | ::= '='
::= '~='
::= '>='
::= '<='
::= '=*'
::= '=' ::= NULL | ::= '*' ::= NULL | '*' ::= NULL |
is a string representing an AttributeType, and has the
defined in [1]. is a string representing an AttributeValue
or part of one, and has the form defined in [2]. If a
contain one of the characters '*' or '(' or ')', these
should be escaped by preceding them with the backslash '\' character



Howes Standards Track [Page 2]

RFC 1960 LDAP Search Filters June 1996


Note that although both the and productions
produce the 'attr=*' construct, this construct is used only to
a presence filter

4.

This section gives a few examples of search filters written
this notation

(cn=Babs Jensen
(!(cn=Tim Howes))
(&(objectClass=Person)(|(sn=Jensen)(cn=Babs J*)))
(o=univ*of*mich*)

5. Security

Security considerations are not discussed in this memo

6.

[1] Yeong, W., Howes, T., and S. Kille, "
Directory Access Protocol", RFC 1777, March 1995.

[2] Howes, R., Kille, S., Yeong, W., and C. Robbins, "The
Representation of Standard Attribute Syntaxes", RFC 1778,
March 1995.

[3] Specification of Basic Encoding Rules for Abstract
Notation One (ASN.1). CCITT Recommendation X.209, 1988.

7. Author's

Tim
University of
ITD Research
535 W William St
Ann Arbor, MI 48103-4943


Phone: +1 313 747-4454
EMail: tim@umich.










Howes Standards Track [Page 3]

---

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.



RFC documents can be found at I.E.T.F.



Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX

---