Re: Models: Schema references to undefined entities

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

Kurt D. Zeilenga writes:
>At 01:24 PM 1/31/2003, Michael Ströder wrote:
>>Hallvard B Furuseth wrote:

> Note that I use the term "published" here.  Schema is "defined"
> in technical specifications, servers publish descriptions they
> know (if they so choose).

Oh, right.  That was in a previous draft of [Models], but it's not in
version 06.  Could you put it back?

>>> For example, an attribute type defined by the server's standard
>>> setup may have to be omitted because of a name conflict with a
>>> locally defined attribute type.  One could edit the attribute out of
>>> the object class which uses it as well, but that's uglier since
>>> clients would receive an incorrect definition of that object class.
>>
>> If the object class references the attribute type by name isn't there
>> still a naming conflict? IMHO the 'locally defined attribute type'
>> gets referenced thus changing the object class definition. Maybe it's
>> me but this sounds rather strange to me.

Sorry, I forgot to mention that I thought of replacing the attribute's
name, if any, with its OID in the object class description.

-- 
Hallvard