Re: Meeting Minutes for the SMIng WG at the 49th IETF...

["John Strassner" <jstrassn@cisco.com>]

I agree with Randy. I've never heard of "partial"
inheritance (before the SMIng meeting, that is). It seems
very wrong, as inheriting only some, but not all,
attributes, methods, or relationships of a class doesn't
make sense. If you want to inherit just some attributes,
consider putting them in a capsule instead. For anyone not
familiar with this terminology, it is roughly equivalent to
an aux class in the directory world. The key point is that a
capsule is an object, but not a class.

regards,
John
----- Original Message -----
From: <rpresuhn-lists@dorothy.bmc.com>
To: <sming@ops.ietf.org>
Sent: Friday, December 29, 2000 11:24 AM
Subject: RE: Meeting Minutes for the SMIng WG at the 49th
IETF...


> Hi -
>
> > Message-ID:
<10C8636AE359D4119118009027AE998704F39C62@FMSMSX34>
> > From: "Durham, David" <david.durham@intel.com>
> > To: "'sming@ops.ietf.org'" <sming@ops.ietf.org>
> > Subject: Meeting Minutes for the SMIng WG at the 49th
IETF...
> > Date: Thu, 28 Dec 2000 22:12:30 -0800
> ..
>
> I think some bits got dropped:
>
> > Randy: Partial implementation of a class seems odd.
There may be a semantic
> > for the class that implies all the attributes are to be
used. Maybe this
> > comes from the CMIP world. CMIP allows partial
inheritance as a partial
> > implementation of a class.
> ..
>
> GDMO (CMIP's object definition language) supports
multiple,
> not partial, inheritance.  My point was that if attributes
> have been bundled in a class, there must be some
underlying
> semantic that motivates this bundling.  To then "partially
> inherit" from that class risks breaking whatever semantic
> it was that led to the creation of the class in the first
> place.
>
> GDMO's way of handling multiple inheritance and packages
> allows one to attain the same objectives without
bastardizing
> OO modeling with the kind of partial inheritance that's
being
> introduced here.
>
>  -------------------------------------------------------
>  Randy Presuhn           randy_presuhn@bmc.com
>  Voice: +1 408 546-1006  BMC Software, Inc.  1-3141
>  Fax:   +1 408 965-0359  2141 North First Street
>  http://www.bmc.com/     San José, California 95131  USA
>  -------------------------------------------------------
>  My opinions and BMC's are independent variables.
>  -------------------------------------------------------
>
>