Re: Quipu's treeStructure attribute in oidtables

Colin Robbins <c.robbins@nexor.co.uk> Mon, 22 May 1995 18:10 UTC

X400-Received: by mta haig.cs.ucl.ac.uk in /PRMD=uk.ac/ADMD=gold 400/C=gb/; Relayed; Mon, 22 May 1995 16:33:18 +0100
Date: Mon, 22 May 1995 16:33:18 +0100
X400-Originator: osi-ds-request@cs.ucl.ac.uk
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=uk.ac/ADMD=gold 400/C=gb/; haig.cs.uc.646:22.04.95.15.33.18]
Priority: Non-Urgent
DL-Expansion-History: osi-ds@cs.ucl.ac.uk ; Mon, 22 May 1995 16:33:17 +0100;
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Colin Robbins <c.robbins@nexor.co.uk>
Message-ID: <"12875 Mon May 22 16:32:48 1995"@nexor.co.uk>
To: "Luis P. Caamano" <lpc@sware.com>
Cc: quipu <quipu@cs.ucl.ac.uk>, OSI-DS <osi-ds@cs.ucl.ac.uk>, ldap@umich.edu
In-Reply-To: <9505221425.AA25319@alehouse.sware.com>
Subject: Re: Quipu's treeStructure attribute in oidtables

   >Since the value of the treeStructure attribute is very static, wouldn't
   >it be nice if we had it in the oidtable.oc?  That way, we define it
   >once and not every time one creates a entry of an object class that
   >needs a treeStructure attribute.  I've been thinking about modifying
   >quipu to handle this as an exercise, but would like some opinions
   >before I go ahead.
   >
   >Does anybody have any info regarding this?


TreeStructure is an out of date component of QUIPU.  If you do any
modifications at all you should consider implementing the structure
rules as offered by X.500(93).  These are stored "out of the way" in
sub entries of the DIT, but have the advantage of being available to
DUAs over DAP if they need to be accessed for some reason.

Colin

Quipu's treeStructure attribute in oidtables Luis P. Caamano
Re: Quipu's treeStructure attribute in oidtables Colin Robbins
Re: Quipu's treeStructure attribute in oidtables Alan Wong