extending existing object classes vs deriving new classes
"Luis P. Caamano" <lpc@sware.com> Tue, 21 February 1995 20:24 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07081; 21 Feb 95 15:24 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07076; 21 Feb 95 15:24 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa12158; 21 Feb 95 15:24 EST
Received: from bastion.sware.com by haig.cs.ucl.ac.uk with Internet SMTP id <g.04133-0@haig.cs.ucl.ac.uk>; Tue, 21 Feb 1995 18:47:05 +0000
Received: from shlep.sware.com (shlep.sware.com [139.131.1.14]) by bastion.sware.com (8.6.5/8.6.5) with SMTP id NAA00613; Tue, 21 Feb 1995 13:28:23 -0500
Received: by shlep.sware.com (5.65/2.0) from alehouse.sware.com id AA22683; Tue, 21 Feb 95 13:37:54 -0500
Received: by alehouse.sware.com (5.65/2.1) from localhost id AA00761; Tue, 21 Feb 95 13:26:34 -0500
X-Orig-Sender: "Luis P. Caamano" <lpc@sware.com>
Message-Id: <9502211826.AA00761@alehouse.sware.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Luis P. Caamano" <lpc@sware.com>
X-Mailer: InterMail [2.0 pre-alpha]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: osi-ds@cs.ucl.ac.uk
Subject: extending existing object classes vs deriving new classes
Cc: edmund@sware.com
Date: Tue, 21 Feb 1995 13:26:34 -0500
hello. We need some opinions, pointers, lessons, hints, whatever you have. :) We are defining a new X.500 schema that among other things will include unix administration support. We still haven't decided about the DSA implementation, that is, we still have the option to implement our own DSA which could have our view of the directory schema. Of course, whatever we do will be X.500 compliant. While discussing the information that we would need to store/retrieve in the directory, we have hit an impasse in deciding if we should extend standard object classes with new attributes or derive new objects from the standard object classes. For instance, if we need to store some special attribute in say, the Application Process object class, do we simply define in our private schema the extra attributes as MAY CONTAIN or do we derive MyApplication Process as a subclass of Application Process? One of our goals is for our DSA to support as many DUAs as possible. If we extend, other DUAs will query our DSA and get an ASN.1 encoded object that will have strange attributes. However, the DUA will know about the object class. Thus, it's possible that the DUA will simply skip the unknown attribute while displaying the other ones. However, we are not sure if this is allowed by the standard. After all, Application Process has an object identifier and that in itself might carry the object semantics for some DUAs. On the other hand, if we derive, we are afraid that the DUA might not be able to find out that MyApplication Process is just a derivation of Application Process and then reject the whole object class. We are not sure how polymorphism works in the directory or how DUAs find about new object semantics when using the 1993 extensions. Does anybody know about any other sources that talk about the new extensions to X.500 (1993) for schema support other than the X.500 document itself or Sara Radicati's X.500 book? Are there any X.500 implementations that support subtrees, operational attributes, and the like? thanks a lot for your time on this, any help will be greatly appreciated. ---------------------------------------------------------------- Luis P. Caamano (LC2385) | lpc@sware.com SecureWare, Inc. Atlanta, GA | (404) 315-6296
- extending existing object classes vs deriving new… Luis P. Caamano
- RE: extending existing object classes vs deriving… Debasish Biswas
- Re: extending existing object classes vs deriving… Paul Barker
- RE: extending existing object classes vs deriving… PGUPTA
- Re: extending existing object classes vs deriving… Andrew Waugh