[Date Prev][Date Next]
RE: Substrings any match on an empty string
Ok, after re-reading the [Protocol] statement, it only says:
The matching rule for AssertionValues in a substrings filter item
is defined by the SUBSTR matching rule for the attribute type.
(nothing about the syntax of those AssertionValues)
And after reading Section 5.1 of [Syntaxes] further, I see:
SubstringFilter is converted into an assertion value of the
substrings matching rule prior to applying the rule.
So, I see a few issues:
1) [Protocol] should likely specify the bit about which syntax is to be
used in SubstringFilter AssertionValues.
2) [Protocol] should likely talk about the conversion into the
substrings matching rule syntax (as [Syntaxes] does).
3) The answer to Ron's original question is that it's *always* invalid
to have an empty _any_ part--correct? This is because even though an
equality assertion syntax might allow zero octets, the Substring
Assertion syntax (which we need to convert to) never allows a
>>> "Steven Legg" <firstname.lastname@example.org> 7/8/03 1:29:42 AM >>>
Jim Sermersheim wrote:
> It depends on the Assertion Value for the matching rule being used.
> Which brings up an issue:
> In Section 5.1 of [Syntaxes], there is a statement
> "Note that the AssertionValue in a SubstringFilter
> [PROT] MUST conform to the assertion syntax of the equality
> rule for the attribute type rather than the assertion syntax of
> substrings matching rule for the attribute type. "
> This does not align with [Protocol]. Steven, is this a historical
> artifact, or did I screw the protocol up?
Well it's historical in the sense that it is analogous to
what X.500 defines, but it remains appropriate. If an AssertionValue
in a SubstringFilter were of the Substring Assertion syntax then we
would have something which contains initial, any and final substrings
embedded in something (the SubstringFilter) which also has initial,
any and final parts. That would be silly. For example, what would be
the point of the Substring Assertion syntax value "*foo" in the
Given that the AssertionValue conforms to the assertion syntax of
the equality matching rule then for most attributes an "any" with
a zero-length string would be an invalid syntax. For those where
it is valid the result depends on the way string prep deals with empty
strings (each substring is prepared in isolation by the substring
> >>> "Ramsay, Ron" <Ron.Ramsay@ca.com> 7/7/03 11:04:23 PM >>>
> Hi all,
> Does anyone have an answer to this question:
> If I specify a filter of type 'substrings' where the
> substrings contain
> only an 'any' with a zero-length value, should I return all entries
> containing the attribute?
> It seems to me that the empty string is a substring of all strings.
> I've looked in RFC 2251, X.511 and X.520 but have not seen a
> which I could interpret as answering this question.
> Thanks for your help,