[Date Prev][Date Next]
Re: objectIdentifierMatch on ambiguous name
At 04:10 AM 1/2/2003, Hallvard B Furuseth wrote:
>What does filter component (oid=foo) applied to attribute oid=bar
>evaluate to if the schema defines the following?
> object class ( ... NAME 'foo' ... )
> object class ( ... NAME 'bar' ... )
> attribute type ( ... NAME ('foo' 'bar') ... )
It likely needs to be clarified that the meaning of 'foo' and
'bar' are context sensitive and MUST NOT be used where the
context is not provided.
> attribute type ( ... NAME 'oid'
> EQUALITY objectIdentifierMatch
> SYNTAX 188.8.131.52.4.1.14184.108.40.206.38 ) ; OID
If this attribute is intended to hold OIDs referring to any
kind of object, then short names cannot be used with it. That
is, the assertion (oid=foo) is Undefined.
I note that if the attribute is intended to hold OIDs referring
to a specific kind of object (e.g., attribute types, object
classes, matching rules), the server needs also to be aware of
this intent in order to map "foo" to the appropriate (numeric)