Re: objectIdentifierMatch on ambiguous name

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Kurt D. Zeilenga writes:
>> All syntaxes that use OIDs that I can see come
>> with a definition which says which OID name space they apply to,
> 
> Really?  I think that most of the definitions of name space are
> actually quite ambiguous.  Consider the assertion (objectClass=foo) in
> a subtree search where different parts of the subtree are controlled
> by different subschemas, each with a different definition for foo.
> (Let's assume the server holds the whole subtree for now.) Is the
> server to map foo on a per entry basis, or once for the whole
> operation?

per entry, I think.

>> except
>> the OID syntax itself - and the core schema only uses that for the
>> objectClass attribute, which itself provides the namespace.
> 
> I think that an attribute type used in an attribute of a particular entry
> may actually be insufficient to clear specify a namespace.  Consider DNs.
> Are all names of attribute types appearing in a DN in the same name space,
> or could each RDN be in a separate name space?

Doesn't matter.  If the attribute names are not in the registry or the
table of short names or whatever in [DN], short names are not used.

The RDN 'objectClass=foo' could be a problem, though.

-- 
Hallvard