[Date Prev][Date Next]
Re: objectIdentifierMatch on ambiguous name
>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
> per entry, I think.
...though I wish I didn't:-)
In any case, I think the answer to that question belongs in
4.5. Search Operation in [Protocol], not in [Models].