Re: Widely distributed searching
clw@merit.edu Mon, 23 November 1992 20:02 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14208; 23 Nov 92 15:02 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14204; 23 Nov 92 15:02 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa01361; 23 Nov 92 15:03 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.03460-0@haig.cs.ucl.ac.uk>; Mon, 23 Nov 1992 18:32:34 +0000
Received: from merit.edu by bells.cs.ucl.ac.uk with Internet SMTP id <g.18330-0@bells.cs.ucl.ac.uk>; Mon, 23 Nov 1992 18:32:14 +0000
Return-Path: <clw@merit.edu>
Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA10927; Mon, 23 Nov 92 13:31:56 -0500
Received: by home.merit.edu (4.1/client-0.9) id AA24007; Mon, 23 Nov 92 13:31:55 EST
Date: Mon, 23 Nov 1992 13:31:55 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: clw@merit.edu
Message-Id: <9211231831.AA24007@home.merit.edu>
To: P.Barker@cs.ucl.ac.uk, directory-group@jnt.ac.uk, osi-ds@cs.ucl.ac.uk
Subject: Re: Widely distributed searching
Paul: One of the primary problems I have with the X.500 standard, irrespective of the various implementations, is that it locks the user into the X.500 namespace, and the user has to know a great deal about the layout of the namespace if she wants to issue more than local queries. So even the power search option is not sufficient for Yellow Pages type queries, and I have some *extreme* concerns about how this concept will scale. The Yellow Pages problem is actually extremely difficult to solve in X.500. Either one has to munge the namespace to contain all the relevant attributes for searching (as in @o=Internet@ou=K-12 Information) which is a horrible hack, even if everything under this subtree uses aliases, it's still next to imposs- ible to maintain, especially when the entry has been moved out from under the alias. The other way is to create relevant subtrees under each organization's entry (for example, for K-12 Educators who work for IBM) However, in either case, you are forcing the user to be aware of the layout of the name space to get at the information they really want. I think that the whois++ stuff solves these problems quite nicely, as many of the solutions fall right out of the architecture. Chris
- Widely distributed searching Paul Barker
- Re: Widely distributed searching OSI Directory Service
- Re: Widely distributed searching pays
- Re: Widely distributed searching Richard Letts
- Re: Widely distributed searching Alan.Young
- Re: Widely distributed searching Paul Barker
- Re: Widely distributed searching clw
- Re: getting oids Peter Furniss