Lines Matching refs:matching

30    specifications did not precisely define how character string matching
33    algorithms for character-based matching rules defined for use in
40    A Lightweight Directory Access Protocol (LDAP) [RFC4510] matching
46       True      - the attribute contains a matching value,
48       False     - the attribute contains no matching value,
51                   a matching value.
63    For instance, the caseIgnoreMatch matching rule may be used to
70    things) value syntaxes and matching rules for comparing values
74    The caseIgnoreMatch matching rule [X.520], for example, is simply
80    insensitive matching implementation that folded lowercase characters
88    The lack of precise specification for character string matching has
92    preparing character strings for matching.
110       characters insignificant to the matching rule.
119    Hence, preparation of character strings for X.500 [X.500] matching
144    specifications defining LDAP syntaxes and/or matching rules.
190    attribute value in preparation for character string matching rule
205    expected matching behavior.  Implementations are free to use
206    alternative processes so long as the matching rule evaluation
259    For case ignore, numeric, and stored prefix string matching rules,
308    characters insignificant to the matching rule.  This modification
309    differs from matching rule to matching rule.
311    Section 2.6.1 applies to case ignore and exact string matching.
312    Section 2.6.2 applies to numericString matching.
313    Section 2.6.3 applies to telephoneNumber matching.
601    In the absence of substrings matching, the insignificant space
602    handling for case ignore/exact matching could be simplified.
608    In the presence of substrings matching, this simplified space
609    handling would lead to unexpected and undesirable matching behavior.
626    Note to readers not familiar with LDAP substrings matching: the LDAP
644    substrings matching, one must study key aspects of X.500 case
645    exact/ignore matching.  X.520 [X.520] says:
714    partitioning and matching, the anomaly is considered acceptable.