[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: SUBCLASSING, again



Title: RE: SUBCLASSING, again

How can you make an abstract subclass from something that was concrete? Subclassing means refinement or specialization.

This defies Logic, Object-Oriented Programming, and Common Sense.


regards,
John

John C. Strassner
Chief Strategy Officer
Intelliden Inc.
90 South Cascade Avenue
Colorado Springs, CO  80906  USA
phone:  +1.719.785.0648
  fax:     +1.719.785.0644
email:    john.strassner@intelliden.com



> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
> Sent: Wednesday, February 11, 2004 8:04 PM
> To: Kathleen Dally
> Cc: IETF-LDAPbis@OpenLDAP.org
> Subject: Re: SUBCLASSING, again
>
>
> At 06:56 PM 2/11/2004, Kathleen Dally wrote:
> >I would have no trouble deleting the sentence from Models, section
> >2.4.3:
> >        " Auxiliary object classes cannot subclass structural object
> >classes."
>
> Even though the model makes no sense in face of such constructions?
>
> >However, I do not believe that the intent to permit Auxiliary object
> >classes to subclass Structural object classes is as clear in X.501.
>
> Why?  Since X.501 didn't explicitly disallow this, why do
> you think it clear that the intent was to disallow this?
>
> Kurt
>