IETF Logo Mail Archive

Re: centroid propagation

Hiroaki Kashima <kashima@csce.kyushu-u.ac.jp> Mon, 25 October 1993 14:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00230; 25 Oct 93 10:55 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00222; 25 Oct 93 10:55 EDT
Received: from ucdavis.ucdavis.edu by CNRI.Reston.VA.US id aa06692; 25 Oct 93 10:54 EDT
Received: by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA10956; Mon, 25 Oct 93 07:32:19 PDT
X-Orig-Sender: ietf-wnils-request@ucdavis.edu
Received: from inunaki.csce.kyushu-u.ac.jp ([133.5.18.3]) by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA10448; Mon, 25 Oct 93 07:17:50 PDT
Received: from hakozaki.csce.kyushu-u.ac.jp (hakozaki) by inunaki.csce.kyushu-u.ac.jp (5.67+1.6W/6.4JAIN-2.0-MX) id AA06169; Mon, 25 Oct 93 23:19:27 JST
Return-Path: <kashima@csce.kyushu-u.ac.jp>
Received: by hakozaki.csce.kyushu-u.ac.jp (4.1/6.4J.6-1.1) id AA26365; Mon, 25 Oct 93 23:19:26 JST
Message-Id: <9310251419.AA26365@hakozaki.csce.kyushu-u.ac.jp>
To: Mark Prior <mrp@itd.adelaide.edu.au>
Cc: ietf-wnils@ucdavis.edu
Subject: Re: centroid propagation
In-Reply-To: Your message of "Tue, 19 Oct 1993 09:25:03 +0930." <9310182355.AA11032@jarrah.itd.adelaide.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Date: Mon, 25 Oct 1993 23:19:24 +0900
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Hiroaki Kashima <kashima@csce.kyushu-u.ac.jp>

# I wonder how much I understand what you said... Sorry.

On Tue, 19 Oct 1993 09:25:03 +0930,
     Mark Prior <mrp@itd.adelaide.edu.au> said:

>    >  I don't support centroids since it is too difficult to do a complete
>    >  implementation when you are constrained by another system that doesn't
>    >  map into whois++ cleanly. I would attempt to do a partial

>     What type of constraints can be there? I can't image concretely. For
>     example?

>  Well I have another API to deal with and for all whois++ concepts I
>  must try to translate them into X.500 concepts. Whois++ is designed
>  with a WAIS style indexing facility in mind but X.500 doesn't provide
>  access in this way. I must issue typed searches against X.500 so there
>  is no easy way for me to get at all the possible values of items so
>  they may be provided to an index server.

I'm sure there are many types of attribute but is it needed to get
"all" of the values?

>                                           I also have a system that can
>  (and does) defend itself from people trying to "trawl" data from it,
>  so if you send it a whois query like "*" it will return nothing, even
>  though it has had thousands of matches. You must be must more specific.

Is there any problem to arrow "trawl"ing data?

>      >  implementation but unless whois++ supported "maybe" style responses
>      >  this would be too confusing for the user.

>       Is "maybe style" {vague,fuzzy,...?} searching?

>  No, I can do fuzzy searching easily enough via a soundex match. What I
>  am trying to drive at is that I might be able to pseudo index some
>  parts of my data. This means that if I implemented this and my server
>  was asked if it supported indexing it would respond "maybe", if it was
>  asked does it support indexing of surnames it could say "yes" but if
>  it was asked did it support indexing of personal titles it would say
>  "no".

--
	Hiroaki Kashima
the master's course
Computer Science and Communication Engineering,
Kyushu University
	E-mail: kashima@csce.kyushu-u.ac.jp

v2.23.0 | Report a Bug | By Email