White.Pages.txt.Z,
containing some of the original ideas in Netfind and measurements of
the system. The Netfind.Gathering paper contains an up-to-date
description of the data gathering and integration algorithms.
The third source of information focuses particularly on the URL-based
remote site customization mechanism, and is available in
ftp://ftp.cs.colorado.edu/pub/cs/distribs/netfind/Netfind.WP.URLs
-----------------------------------------------------------------------
Bibliography:
Netfind is one prototype developed by the Networked Resource Discovery
Project, at the University of Colorado - Boulder. A bibliography and
set of project papers is available by anonymous FTP from
ftp.cs.colorado.edu, in pub/cs/techreports/schwartz. This directory
contains a file called "README" that contains a project overview and
bibliography. The files in this directory are also available via an
electronic mail interface. For more information, send a mail message
to infosrv@ftp.cs.colorado.edu, containing the message body (not
subject line) "send HELP" (without quotes).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
PROSPERO
Date template updated or checked: 1 March, 1994
By: Name: Steven Augart
Email address: info-prospero@isi.edu
-----------------------------------------------------------------------
NIR Tool Name: Prospero
Brief Description of Tool:
The Prospero directory service supports a user centered view of files
scattered across the Internet. It can be used to organize references
to files as if they were on your local system, without the need to
physically move them.
Prospero provides access to existing directories and indices that can
be used to find files of interest that are available from Internet
archive sites. Among the indices available is the archie database
and a gateway to all Gopher menus, files, and searches. We hope to
have WAIS indices and World Wide Web documents online in the near
future.
Prospero also provides a mechanism to make directories and indices
available to end-users and applications in a format that allows
information from different sources to be integrated into a coherent
whole.
Prospero does not interpret the data that it organizes. It does
provide mechanisms to retrieve the data, but the display and use of
the data is up to the user's application. Prospero is intended to
serve as infrastructure that integrates information from a variety of
sources and supports a variety of user applications.
Prospero allows fine grained authorization of requests to all
objects, including directories and indices. Prospero supports the
authentication of clients through four mechanisms: (a) simple client
assertion of the user's identity; (b) a trusted port mechanism
similar to that used by the Berkeley UNIX R commands; (c) a simple
cleartext passwording mechanism; (d) Kerberos (version 5). The
maintainer of an ACL chooses which of these mechanisms he or she
wishes to accept as proof of the client's identity.
-----------------------------------------------------------------------
Primary Contact(s):
Name: Info Prospero (preferred contact address)
Email address: info-prospero@isi.edu
--------------------------
Name: Clifford Neuman
Email address: bcn@isi.edu
Postal Address: U.S.C. Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
U.S.A.
Telephone: +1-310-822-1511
------------------------
Name: Steven Augart
Email address: swa@isi.edu
Postal Address: U.S.C. Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695
U.S.A.
Telephone: +1-310-822-1511
-----------------------------------------------------------------------
Help Line:
Name: Info Prospero
Email address: info-prospero@isi.edu
-----------------------------------------------------------------------
Related Working Groups:
IETF IAFA WG
IETF IIIR WG
IETF URI WG
IETF NIR WG
IRTF Resource Discovery WG
-----------------------------------------------------------------------
Sponsoring Organisation / Funding source:
Information Sciences Institute, University of Southern California
The design and implementation was supported in part by the National
Science Foundation (Grant No. CCR-8619663), the Washington Technology
Center, Digital Equipment Corporation, and the Advanced Research
Projects Agency under NASA Cooperative Agreement NCC-2-539.
-----------------------------------------------------------------------
Mailing Lists:
Address: info-prospero@ISI.EDU
Administration: info-prospero-request@ISI.EDU
Description: This mailing list is really two one-way mailing
lists. Send mail to INFO-PROSPERO to obtain
information about Prospero, papers, or the
release. Mail to INFO-PROSPERO will not be
passed on to subscribers. INFO-PROSPERO is also
the list to which we will send status updates
and information on how to obtain new releases.
Archive: Via anonymous FTP to PROSPERO.ISI.EDU as
/pub/prospero/mail/info-prospero.arc
Via Prospero in the "#/INET/EDU/ISI/GUEST/prototype" virtual
system as /sites/isi.edu/pub/prospero/mail/info-prospero.arc
--------------------------
Address: prospero@ISI.EDU
Administration: prospero-request@ISI.EDU
Description: This mailing list is for general discussion of
Prospero, for announcements of new sites that
have come on board, and for announcements of
directories that people have created to organize
the information already accessible.
Archive: Via anonymous FTP to PROSPERO.ISI.EDU as
/pub/prospero/mail/prospero.arc
Via Prospero in the "#/INET/EDU/ISI/GUEST/prototype" virtual
system as /sites/isi.edu/pub/prospero/mail/prospero.arc.
-----------------------------------------------------------------------
News groups:
NONE
-----------------------------------------------------------------------
Protocols:
What is supported:
Prospero directory service requests are formatted
according to the Prospero protocol.
Prospero does not have its own file retrieval
protocol. Files may be automatically retrieved using
FTP, NFS, AFS, and GOPHER. Loginable services may also be
accessed via TELNET.
What it runs over:
Directory service requests are layered on top of
UDP, with our own (included) reliable message delivery
layer.
Other NIR tools this interworks with:
Archie, Gopher, Wais, WWW
Future plans:
-----------------------------------------------------------------------
Servers:
Date completed or updated: 1 November, 1993
Platform: UNIX
Primary Contact:
Name: Clifford Neuman and Steven Augart
Email address: info-prospero@isi.edu
Telephone: +1-310-822-1511
Server software available from:
Via anonymous FTP: PROSPERO.ISI.EDU, /pub/prospero/prospero.tar.Z
Via Prospero: /releases/prospero/prospero.tar.Z, in the
"#/INET/EDU/ISI/GUEST/prototype" virtual system.
Note that the name prospero.tar.Z refers to the most stable release
(currently Beta version 5.1). If you want the latest version of
the server (which includes the Gopher gateway), you should retrieve
it by version number; the name for the latest version is
prospero-alpha.5.2.tar.Z
Location of more information:
Contained within the release.
Latest version number:
Alpha Version 5.3
Brief Scope and Characteristics:
The server allows the maintainer to make directory information
available about selected portions of the server's filesystem, such as
anonymously FTPable files. The server also is used to publish
information from other databases, such as Archie. The server also
allows users and maintainers to store their own customized organizing
views of the namespace. Release Alpha.5.2 of the server includes a
gateway feature which treats all Gopher servers as a Prospero
database.
Approximate number of such servers in use:
50
General comments:
Future plans:
We have a prototype NFS server that makes Prospero queries, but it is
not yet ready to release. We plan to develop a gateway similar to
the existing Gopher gateway feature for World Wide Web. There is
also active work being done on exporting WAIS indices through
Prospero in a way similar to the way the archie database is exported.
-----------------------------------------------------------------------
Clients:
Date completed or updated: 1st November, 1993
Platform: UNIX
Primary Contact
Name: Clifford Neuman and Steven Augart
Email address: info-prospero@isi.edu
Telephone: +1-310-822-1511
Client software available from:
Via anonymous FTP: PROSPERO.ISI.EDU, /pub/prospero/prospero.tar.Z
Via Prospero: /releases/prospero/prospero.tar.Z, in the
"#/INET/EDU/ISI/swa" virtual system.
Note that the name prospero.tar.Z refers to the most stable release
(currently Beta version 5.1). If you want the latest version of
the clients (which includes the Prospero menu browser), you should
retrieve it by version number; the name for the latest version is
prospero-alpha.5.2.tar.Z
Latest Version number:
Alpha Version 5.2
Brief Scope and Characteristics:
We provide two client interfaces. The older one is a command-line
client, which can be configured to use the same syntax to navigate
through the Prospero namespace that a user uses to navigate through
the UNIX filesystem. ("cd", "ls", etc.) The newer one is a menu-
based file and directory browser similar to the UNIX Gopher client.
General comments:
Archie clients also make queries in the Prospero namespace, so all
Archie clients are Prospero clients too. They are better described
in the Archie report.
Future plans:
We are working on enhancing the menu browser client to allow users to
remotely customize and update virtual systems. We plan to develop a
Prospero hypertext browser.
-----------------------------------------------------------------------
Demonstration sites:
A guest virtual system is available on PROSPERO.ISI.EDU. However, to
use it, you must compile the Prospero command-line client on your own
machine. Instructions for using it come with the Prospero
distribution.
-----------------------------------------------------------------------
Documentation:
All of these papers are available via anonymous FTP from
PROSPERO.ISI.EDU. They may additionally be obtained through
Prospero itself by preceding the 'Full file name:' given below with
'/sites/isi.edu' and looking in the '#/INET/EDU/ISI/GUEST/prototype'
virtual system.
Document Title: The Prospero Protocol, version 5
Location details:
Site: PROSPERO.ISI.EDU
Full file name: /pub/prospero/doc/prospero-protocol.PS.Z
Document Title: Prospero User's Manual
Location details:
Site: PROSPERO.ISI.EDU
Full file name: /pub/prospero/doc/prospero-user-manual.PS.Z
Document Title: Prospero Library Manual
Location details:
Site: PROSPERO.ISI.EDU
Full file name: /pub/prospero/doc/prospero-library-manual.PS.Z
Document Title: Prospero Menu-based Browser API Manual
Location details:
Site: PROSPERO.ISI.EDU
Full file name: /pub/prospero/doc/prospero-menu-api.PS.Z
Document Title: Description of Prospero Documents and Papers
Location details:
Site: PROSPERO.ISI.EDU
Full file name: /pub/prospero/papers/README-prospero-documents
-----------------------------------------------------------------------
Bibliography:
A bibliography listing all publicly available Prospero documents and
papers is available via anonymous FTP from PROSPERO.ISI.EDU as
/pub/prospero/README-prospero-documents The following papers are also
available via anonymous FTP from PROSPERO.ISI.EDU:
Prospero:/papers/subjects/operating-systems/prospero/prospero-bii.ps.Z
Anonymous FTP: /pub/papers/prospero/prospero-bii.ps.Z
(POSTSCRIPT)
@INPROCEEDINGS{prosperobii,
AUTHOR = "Neuman, B. Clifford and Augart, Steven Seger",
TITLE = "Prospero: A Base for Building Information
Infrastructure",
BOOKTITLE = "Proceedings of INET'93",
YEAR = 1993,
MONTH = "August"}
For the readers of this report, this is the first paper you probably
want to read about Prospero. This paper describes how Prospero can
be used to integrate internet information services, including
Gopher, WAIS, Archie, and World Wide Web. The paper was
presented at INET'93 in August.
Prospero:/papers/subjects/operating-systems/prospero/prospero-oir.ps.Z
Anonymous FTP: /pub/prospero/papers/prospero-oir.ps.Z
(POSTSCRIPT)
@ARTICLE{oir,
AUTHOR = "Neuman, B. Clifford",
TITLE = "Prospero: A Tool for Organizing {I}nternet Resources",
JOURNAL = "Electronic Networking: Research, Applications and
Policy",
MONTH = "Spring",
YEAR = 1992,
VOLUME = 2,
NUMBER = 1}
This is the first paper we give to more general computer science
audiences to read. It's also a good first paper to look at. It
gives a good overview of Prospero and what it does. It also
describes a bit about the Virtual System model, of which Prospero is
a prototype implementation. Describes what Prospero does, not how
it does it.
Anonymous FTP: /pub/prospero/papers/prospero-gfsvsm.ps.Z
(POSTSCRIPT)
@INPROCEEDINGS{gfsvsm,
AUTHOR = "Neuman, B. Clifford",
TITLE = "The {P}rospero {F}ile {S}ystem: A Global File System
based on the {V}irtual {S}ystem {M}odel",
BOOKTITLE = "Proceedings of the Workshop on File Systems",
YEAR = 1992,
MONTH = "May"}
This is a good third paper to read about Prospero. This one is
targeted more toward system implementors. It provides more
implementation details than the paper on organizing Internet
resources, but less of the vision of how Prospero can be used together
with other systems.
Prospero:
/papers/subjects/operating-systems/prospero/prospero-smlic.ps.Z
Anonymous FTP: /pub/papers/prospero/prospero-smlic.ps.Z
(POSTSCRIPT)
@INPROCEEDINGS{prosperosmlic,
AUTHOR = "Neuman, B. Clifford and Augart, Steven Seger and
Upasani, Shantaprasad",
TITLE = "Using Prospero to Support Integrated
Location-Independent Computing",
BOOKTITLE = "Proceedings of the Usenix Symposium on Mobile and
Location-Independent Computing",
YEAR = 1993,
MONTH = "August"}
This paper describes how the Prospero Directory Service can be used to
solve the server selection problem and the user location problem. The
paper was presented in August at the Usenix Symposium on Mobile
and Location-Independent Computing.
Anonymous FTP: /pub/prospero/papers/UW-CS-89-01-07.PS.Z
(POSTSCRIPT)
@TECHREPORT{vsmldos,
AUTHOR = "Neuman, B. Clifford",
TITLE = "The {V}irtual {S}ystem {M}odel for Large Distributed
Operating Systems",
INSTITUTION = "Department of Computer Science, University of
Washington",
YEAR = 1989,
MONTH = "April",
NUMBER = "89-01-07"}
This describes the initial vision for the Virtual System
Model, the model on which Prospero is based. Much of the material in
this paper appears in greater detail in other papers.
Anonymous FTP: /pub/prospero/papers/UW-CSE-90-05-01.PS.Z
(POSTSCRIPT)
@TECHREPORT{vsmtp,
AUTHOR = "Neuman, B. Clifford",
TITLE = "The {V}irtual {S}ystem {M}odel: A Scalable Approach
to Organizing Large Systems (A Thesis Proposal)",
INSTITUTION = "Department of Computer Science and Engineering,
University of Washington",
YEAR = 1990,
MONTH = "May",
NUMBER = "90-05-01"}
for a long time this was the best description of Prospero, but
all the information in this document appears in more recent papers and
the dissertation itself.
Anonymous FTP: /pub/prospero/papers/prospero-closure.ps.Z
(POSTSCRIPT)
@ARTICLE{nfclosure,
AUTHOR = "Neuman, B. Clifford",
TITLE = "The Need for Closure in Large Distributed Systems",
JOURNAL = "Operating Systems Review",
MONTH = "October",
YEAR = 1989,
VOLUME = 23,
NUMBER = 4,
PAGES = "28--30"}
This paper describes the reasons that operating systems need to
support closure, that is they need to make it clear which name space
is to be used when resolving names. While closure is one of the
important features of Prospero, the concept should be applied in other
operating systems too.
Prospero:
/papers/subjects/operating-systems/prospero/prospero-neuman-thesis.ps.Z
Anonymous FTP: /pub/prospero/papers/prospero-neuman-thesis.ps.Z
(POSTSCRIPT)
@PHDTHESIS{phdneuman,
AUTHOR = "Neuman, B. Clifford",
TITLE = "The {V}irtual {S}ystem {M}odel: A Scalable Approach
to Organizing Large Systems",
SCHOOL = "University of Washington",
MONTH = "June",
YEAR = 1992,
NOTE = "Department of Computer Science and Engineering
Technical Report 92-06-04"}
This is Clifford Neuman's Ph.D. Dissertation. It is currently the
definitive work on Prospero and the Virtual System Model. Includes
an obsolete version of the Prospero User's Manual and of the Prospero
Protocol Specification.
-----------------------------------------------------------------------
Other Information:
We provide three documented library interfaces to Prospero in order to
make client writing easy.
The PFS and PCOMPAT libraries are documented in the library reference
manual. The PFS library allows one to directly make Prospero requests
and parse the results and to manipulate Prospero objects as
abstractions. The PCOMPAT library is an interface to the PFS library
which uses the same interface as the UNIX filesystem; one can link
many existing programs with the PCOMPAT library in order to get it to
resolve names in the Prospero namespace. It is not as portable as the
PFS library and does not provide as much functionality.
The third library interface is the menu-browser API library. It is
documented in the menu-based browser API manual and is used by our
menu-based browser.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
VERONICA
Date template updated or checked: 28 February, 1994
By: Name: Steven Foster
Email address: foster@veronica.scs.unr.edu
-----------------------------------------------------------------------
NIR Tool Name: veronica
Brief Description of Tool:
veronica: Very Easy Rodent-Oriented Net-wide Index to Computerized
Archives.
veronica is the comprehensive title-index of the world's gopher
servers. Because of veronica, the Gopher web is a search-and-
retrieval system as well as a browsing system. veronica is popular
because the ubiquitous Gopher client can both access the search
server, and provide immediate access to the discovered resources.
Taking advantage of Gopher's linked menus, and of the policy of open
access at most gopher sites, veronica finds and indexes almost all
items on publicly-accessible gopher servers.
As of February, 1994, veronica holds indexes to more than 3200 gopher
servers on approximately 2500 internet hosts. In February 1994 the
public-access veronica sites served an estimated 1,200,000 queries.
Most queries are resolved in less than twenty seconds. Eight server
sites offer searches to the internet community, and several other
institutions run servers for internal access.
veronica is easily accessed via any Gopher client. It offers various
types of searches, ranging from single-keyword searches to boolean
queries of indefinite complexity.
A veronica search originates with a user's request for a search,
submitted from a gopher client. The searches may include boolean
operators ( AND, OR, NOT, and parentheses ) and several options to
control the number of items returned, and to restrict the search to
certain gopher types. The result of a veronica search is a set of
gopher-type data items, which is returned to the gopher client as a
gopher menu. Each item on this menu contains the user's desired
keyword or keywords in the item title.
The user can access any of the gopher items by selecting from the
returned menu. Items on this menu may be drawn from many gopher
servers. Because veronica is accessed through gopher clients, it
provides immediate access to all types of data supported by the
gopher protocol and the client implementation.
The veronica service comprises two functions:
1) Harvesting menu data from gopher servers, and preparing it for
use;
2) Offering searches of that database to gopher clients.
These two functions are not necessarily provided by the same host
computer. Currently collection and preparation of data are done at
University of Nevada, and datasets are distributed to the other
veronica servers.
The veronica service infrastructure has been fairly stable since
July, 1993, with eight server sites offering searches for the
internet community (March 1994). These servers are supported by the
participating institutions: NYSERNET, PSI, SERRA, CNIDR, University
of Koeln, SUNET, University of Bergen and the University of Nevada
System Computing Services. Several additional servers offer searches
with access limited to internal users; in this class are servers at
MSU, SUNET, and the Australian University system.
An auxiliary tool to build a locally held menu of Public available
has been created. Called "maltshop", it has been distributed since
January, 1994. It appears that maltshop is rapidly being accepted,
but its long-term effect on loading of the servers may be
problematic.
-----------------------------------------------------------------------
Primary Contact(s):
Name: veronica development team
Email address: veronica@veronica.scs.unr.edu
Postal Address: VERONICA development team
SCS Computer Center Building mailstop 270
University of Nevada, Reno
Reno,
NV 89557-0023
Telephone: +1-702-784-4292 or +1-702-784-6557
Fax: +1-702-784-1108
Name: Fred Barrie
Email address: barrie@cs.unr.edu
Postal Address: SCS Computer Center Building mailstop 270
University of Nevada, Reno
Reno,
NV 89557-0023
Telephone: +1-702-784-4292 or +1-702-784-6557
Fax: +1-702-784-1108
Name: Steven Foster
Email address: foster@nevada.edu
Postal Address: SCS Computer Center Building mailstop 270
University of Nevada, Reno
Reno,
NV 89557-0023
Telephone: +1-702-784-4292 or +1-702-784-6557
Fax: +1-702-784-1108
-----------------------------------------------------------------------
Help Line:
Name: veronica development team
Email address: veronica@veronica.scs.unr.edu
Telephone: no telephone support available
Level of support offered: all users
Hours available: irregular response latencies to email queries,
based on schedule of developers.
-----------------------------------------------------------------------
Related Working Groups: GOPHER, FACETS
-----------------------------------------------------------------------
Sponsoring Organisation / Funding source:
University and Community College System of Nevada Computer Services,
and University of Nevada, Reno. Additional support has been
provided by CNIDR, Pandora Systems, Inc., and Pacific Bell Co.
Server hosts have been provided by the sites listed above in
the Description section.
-----------------------------------------------------------------------
Mailing Lists:
Address: gopher-news@boombox.micro.umn.edu
Address: veronica-news@veronica.scs.unr.edu
-----------------------------------------------------------------------
News groups:
Name: veronica discussion happens on comp.infosystems.gopher
-----------------------------------------------------------------------
Protocols:
What is supported: Gopher protocol, Gopher+ protocol
What it runs over: TCP
Other NIR tools this interworks with: Gopher, WAIS, ftp
Future plans: Implement extensions with Gopher+.
Support for URN/URL standards.
Per-site updates of indexes.
Subject-area-specific indexes.
Indexes for USENET news and LISTSERV articles.
Automated server load-levelling.
-----------------------------------------------------------------------
Servers:
Date completed or updated: February 28, 1994
By: Name: Steven Foster
Email address: foster@nevada.edu
Platform: UNIX
Primary Contact:
Name: veronica development team
Email address: veronica@veronica.scs.unr.edu
Telephone: +1-702-784-4292 or +1-702-784-6557
Server software available from:
Via ftp: veronica.scs.unr.edu
veronica-code/
veronica-data/
veronica-data.tar.Z
Location of more information:
Via Gopher: veronica.scs.unr.edu
veronica/
veronica-faq
how-to-compose-veronica-queries
Via Gopher: gopher.cnidr.org
veronica
veronica-faq
how-to-compose-veronica-queries
Via ftp: veronica.scs.unr.edu
veronica-code/
veronica-docs/
Latest version number: 0.6.5
Next planned version: 0.7b (March 1994)
Brief Scope and Characteristics:
Two modules: a data-collection module and a data-server module.
1. Data-collector runs on any Unix computer that does TCP
and compiles perl. This has not been distributed yet.
Data collection, data preparation, and indexing are being
done at veronica.scs.unr.edu. The harvester "walks" all
advertised gopher servers, and any newly-discovered servers.
Almost all redundant links are removed, leaving the
( hopefully ) canonical reference for each item.
Indexes are built at Nevada, and the indexed dataset is
distributed to server sites.
2. Server module.
Servers run on unix computers and answer to gopher-type-7
requests. Boolean keyword logic is implemented. See file
"how-to-compose-veronica-queries". Several options allow
retrieval of items with specified gopher-types, retrieval
of a file of links containing the search results, and
override for the default limit on number of results returned,
which is 200 items.
Server software runs on most flavors of unix, requires dbm
and perl, and requires about 1.4 GB of data on disk, with
considerable /tmp space available.
Server software is available to any site which wants to run
a server. Server sites are encouraged to offer the service
to the net at large.
Approximate number of such servers in use: twelve.
Auxiliary tool: Maltshop v. 0.2d
Maltshop builds a menu of Public Gopher Servers for the local
gopher menu.
Maltshop software available from:
Via ftp: veronica.scs.unr.edu
veronica-code/
menu-builder-0.2d
Via Gopher: veronica.scs.unr.edu, port 70
11/Search ALL of Gopherspace
12/Script to automate your local
Veronica menu
General comments:
Basic veronica service has been fairly stable since July 1993.
Indexing is quite efficient, and most queries are resolved in ten
seconds or quicker. More than 1,000,000 queries were resolved in
February, 1994.
Though veronica is well-accepted at this level of service, we are
undertaking significant upgrade efforts during Winter 93-94.
-----------------------------------------------------------------------
Clients:
Date completed or updated: October 19, 1993
By: Name: Steven Foster
Email address: foster@nevada.edu
Platform: veronica is accessed through any of the
gopher clients.
Primary Contact: As for gopher clients.
Client software available from: As for gopher clients.
Location of more information:
Via Gopher: gopher.tc.umn.edu, port 70
1/Information About Gopher
Future plans: veronica will interoperate with Gopher+
clients, allowing queries to be
composed by ASK blocks.
-----------------------------------------------------------------------
Demonstration sites:
Site name: UCCSN veronica server
Access details: gopher to veronica.scs.unr.edu, port 70.
Open "veronica" folder; choose one of
the search types available.
Site name: University of Minnesota Gopher server
Access details: gopher to gopher.tc.umn.edu, port 70.
Other Gopher and Information Servers
Search Gopherspace with veronica.
choose one of the search types available.
Site name: NYSERNET veronica server
Access details: gopher to nysernet.org, port 70.
Open "Search the Internet" folder;
choose one of veronica searches.
Site name: SERRA veronica server
Access details: gopher to gopher.unipi.it, port 70.
Open "University of Pisa - Services" folder;
choose the veronica search.
-----------------------------------------------------------------------
Documentation:
Document Title: veronica FAQ: Common Questions and answers
about veronica, a title search and retrieval
system for use with the internet gopher.
Location details:
Via Gopher:
Site: veronica.scs.unr.edu, port 70.
veronica
veronica FAQ
Full file name: veronica-faq
Site: gopher.micro.umn.edu, port 70.
Other Gopher and Information services
Search Gopherspace with veronica
veronica FAQ
Full file name: veronica-faq
Site: gopher.cnidr.org, port 70.
veronica
veronica FAQ
Full file name: veronica-faq
Via anonymous ftp:
Site: veronica.scs.unr.edu
veronica-docs/veronica-faq
Document Title: How to Compose veronica Search Queries.
Location details:
Via Gopher:
Site: veronica.scs.unr.edu, port 70.
veronica
How to Compose veronica Search Queries.
Full file name: how-to-query-veronica
Site: gopher.cnidr.org, port 70.
veronica
How to Compose veronica Search Queries.
Full file name: how-to-query-veronica
Via anonymous ftp:
Site: veronica.scs.unr.edu
veronica-docs/how-to-query-veronica
Document Title: About veronica.
Location details:
Via Gopher:
Site: veronica.scs.unr.edu, port 70.
veronica
About veronica
Full file name: veronica-about
Site: gopher.micro.umn.edu, port 70.
Other Gopher and Information services
Search Gopherspace with veronica
About veronica
Full file name: veronica-about
Site: gopher.cnidr.org, port 70.
veronica
About veronica
Full file name: veronica-about
-----------------------------------------------------------------------
Bibliography: none
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
WAIS (WAIS, Inc.)
Date template updated or checked: 1 March 1994
By: Name: Nathaniel Lee
Email address: than@wais.com
freeWAIS (CNIDR)
Date template updated or checked: 1 March 1994
By: Name: Jane Smith and Jim Fullton
Email address: Jane.Smith@CNIDR.org and Jim.Fullton@CNIDR.org
-----------------------------------------------------------------------
NIR Tool Name: WAIS
Brief Description of Tool:
WAIS - The Wide Area Information Servers system - is an electronic
publishing software set which allows you to search out and retrieve
multimedia information from databases anywhere in the world. WAIS
databases may be accessed by WAIS, gopher, and WWW clients (such as
Mosaic), and via online services such as Delphi and America OnLine.
WAIS software includes user interfaces for most platforms, and server
software that provides automatic indexing of databases.
WAIS was developed by Thinking Machines Corporation of Cambridge,
Massachusetts in collaboration with Apple Computer, Inc., Dow Jones &
Company, and KPMG Peat Marwick. With over 100 databases and 5,000
users worldwide, WAIS is rapidly becoming a standard for information
distribution within the Internet environment.
WAIS is a client-server application. Most of the clients remain
freely available with a few exceptions. WAIS, Inc. develops and
sells commercial versions of WAIS and the Clearinghouse for Networked
Information Discovery and Retrieval (CNIDR) develops freeWAIS, a
version free for distribution and use. A few freely distributable
versions remain available from Thinking Machines, Inc. and other
organizations.
What does WAIS do?
WAIS allows multimedia information to be stored anywhere on any
platform. Using your interface of choice, WAIS enables you to
find personal, corporate and public information. The information
is accessible regardless of format: text, formatted documents,
pictures, spreadsheets, graphics, sound, or video.
WAIS recognizes natural language queries. The search and retrieval
of relevant information is made using your native language. To
date, we have used English, French, Italian, and Latin! The most
relevant documents, regardless of size, can be sent back to the
server in their entirety to further refine your search (telling
the server, "Find me more like this document.") Proven searches
can be automatically repeated, monitoring and alerting you to new
information as it becomes available.
How does WAIS work?
WAIS uses a single computer-to-computer protocol (NISO Z39.50-
1988). Each WAIS server reads your question and based on its
words, searches the full text of the database for the most
relevant documents, and ranks them using automatic word weighting.
Servers need not fully understand your query; the retrieval
process is based on a search method called relevance feedback.
-----------------------------------------------------------------------
Primary Contact(s) (WAIS, Inc.):
Name: Than Lee
Email address: info@wais.com
Postal Address: 1040 Noel Drive, Suite 102, Menlo Park CA 94025
(USA)
Telephone: +1-415-617-0444
Fax: +1-415-327-6513
-----------------------------------------------------------------------
Primary Contact(s) (CNIDR):
Name: George Brett
Email address: George.Brett@CNIDR.org
Postal Address: 3021 Cornwallis Rd., Research Triangle Park
NC 27709 (USA)
Telephone: +1-919-248-1499
Fax: +1-919-248-1101
-----------------------------------------------------------------------
Help Line (WAIS, Inc.):
Name:
Email address: support@wais.com
Telephone:
Level of support offered: commercial customers only
Hours available: anytime
-----------------------------------------------------------------------
Help Line (CNIDR):
Name: Kevin Gamiel
Email address: Kevin.Gamiel@CNIDR.org
Telephone: +1-919-248-1499
Level of support offered: developers only
Hours available: 9-5 EST
-----------------------------------------------------------------------
Related Working Groups (WAIS, Inc.):
Z39.50 protocol group
-----------------------------------------------------------------------
Related Working Groups (CNIDR):
NISO: Z39.50 Implementor's Group (ZIG)
IETF: IIIR (Integrating Internet Information Resources) Working Group
URI (Uniform Resource Identifiers) Working Group
-----------------------------------------------------------------------
Sponsoring Organisation / Funding source (WAIS, Inc.):
WAIS, Inc.
-----------------------------------------------------------------------
Sponsoring Organisation / Funding source (CNIDR):
National Science Foundation Cooperative Agreement MCNC University of
North Carolina at Chapel Hill Other U.S. Government agencies
-----------------------------------------------------------------------
Mailing Lists (WAIS, Inc. and CNIDR):
Address: wais-discussion@wais.com
Administration: wais-discussion-request@wais.com
Description: Moderated, digested biweekly posting about WAIS
and Electronic publishing subjects. Please
submit interesting material.
Archive: /pub/mail-archives/wais-discussion/issue-*@wais.com
and wais-discussion-archive WAIS server
-----------------------------------------------------------------------
Mailing Lists (WAIS, Inc. and CNIDR):
Address: wais-talk@wais.com
Administration: wais-talk-request@wais.com
Description: Implementors forum on WAIS/freeWAIS. This is
for talking about nitty gritty details of
protocols and implementations.
Archive: /pub/mail-archives/wais-talk@wais.com
-----------------------------------------------------------------------
News groups (WAIS, Inc. and CNIDR):
Name: comp.infosystems.wais
Description: Variable quality information on WAIS/freeWAIS.
Archive: wais-talk-archive WAIS server
-----------------------------------------------------------------------
Protocols (WAIS, Inc. and CNIDR):
What is supported: z39.50-1988
What it runs over:
The freeware runs over tcp/ip. Production versions have worked
over x.25 and modems as well.
Other NIR tools this interworks with:
Gopher and WWW have been used as front ends to WAIS.
Future plans:
freeWAIS: Z39.50-1992 compliance, search engine independence
-----------------------------------------------------------------------
Servers (WAIS, Inc.): Connection Machine WAIS server
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: Brewster@wais.com
Platform: Connection Machine Model 2
Primary Contact:
Name: Ottavia Bassetti
Email address: ottavia@wais.com
Telephone: +1-617-234-1000
Server software available from: Thinking Machines Corp.
245 First Street
Cambridge, MA 02145 Location of more
information:
Latest version number:
Brief Scope and Characteristics:
Software that runs on CM2 Connection Machines to make them into WAIS
servers.
Approximate number of such servers in use:
10
General comments: Requires CM2 super computer.
-----------------------------------------------------------------------
Servers (CNIDR): freeware for most UNIX platforms
Date completed or updated: 13th December, 1993
By: Name: Jane Smith
Email address: Jane.Smith@CNIDR.org
Platform: Most Unix variations
Primary Contact:
Name: George Brett
Email address: George.Brett@CNIDR.org
Telephone: +1-919-248-1499
Server software available from:
ftp://pub/NIDR.tools/freewais @ftp.cnidr.org
gopher://gopher.cnidr.org
http://cnidr.org
Location of more information: info@CNIDR.org
Latest version number: freeWAIS 0.202
Brief Scope and Characteristics:
server and client code for freeWAIS.
Approximate number of such servers in use:
Unknown. ~568 databases are registered and freely accessible.
General comments:
Source code freely available for use and modification. Internet
community contributes to the software development, CNIDR incorporates
these developments into the freeWAIS releases.
-----------------------------------------------------------------------
Clients (CNIDR): many varied for most platforms
Date completed or updated: 13th December, 1993
By: Name: Jane Smith
Email address: Jane.Smith@CNIDR.org
Platform: varied
Primary Contact:
Name: Kevin Gamiel
Email address: Kevin.Gamiel@CNIDR.org
Telephone: +1-919-248-1499
Client software available from:
URL:ftp://pub/NIDR.tools/freewais @ftp.cnidr.org
Location of more information:
phone or e-mail CNIDR
Latest version number: N/A
Brief Scope and Characteristics:
Many clients of varying capability available for most popular
computing platforms
General comments:
Clients developed and updated regularly; check mailing lists or ftp
sites for latest information
Future plans:
New clients when freeWAIS 1.0 (Z39.50-1992 version) is released
-----------------------------------------------------------------------
Clients:
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: brewster@wais.com
Platform: NeXT
Primary Contact:
Name: Paul Burchard
Email address: burchard@math.utah.edu
Telephone:
Client software available from:
/pub/freeware/next@wais.com via anonymous FTP
Location of more information:
Latest version number: WAIStation-NeXT-1.9.6
Brief Scope and Characteristics:
General comments: NeXT client and server
Future plans:
------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: brewster@wais.com
Platform: EIWAIS 1.55
Primary Contact:
Name: Kevin Gourley
Email address: pc-shareware@einet.net
Telephone:
Client software available from:
/pub/freeware/windows@wais.com via anonymous FTP
/einet/pc@ftp.einet.net via anonymous FTP
Location of more information:
Latest version number: Version 1.55
Brief Scope and Characteristics:
WAIS client for Windows and Windows Sockets
General comments: Windows WAIS Client for Windows Sockets
- supporting multiple source queries
- advanced program/viewer launching
- embedded (any file size) text viewer
- auto-keyword highlighting
- graphics viewers included
- auto-browse mode for redirected source queries
- auto-parsing of WAIS catalogs returned by servers
- runs on wide range of winsock TCP/IP stacks
Future plans:
--------------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: Brewster@wais.com
Platform: telnet access (vt100)
Primary Contact:
Name: John Curran
Email address: jcurran@nnsc.nsf.net
Telephone:
Client software available from:
/pub/freeware/unix-src/wais-8-b5.1-swais-patches @wais.com
Location of more information:
telnet to quake.think.com log in as wais.
Latest version number:
Brief Scope and Characteristics:
General comments:
Future plans:
------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: brewster@wais.com
Platform: MacWAIS 1.28
Primary Contact:
Name: John Hardin
Email address: mac-shareware@einet.net
Telephone:
Client software available from:
/pub/freeware/mac@wais.com via anonymous FTP
Location of more information:
Latest version number: 1.28
Brief Scope and Characteristics:
General comments:
Future plans:
------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: Brewster@wais.com
Platform: Mac Hypercard
Primary Contact:
Name: Francois Schiettecatte
Email address: francois@wais.com
Telephone:
Client software available from:
/pub/freeware/mac/HyperWais* @wais.com
Location of more information: contact author
Latest version number: 1.9
Brief Scope and Characteristics:
HyperWais is a hypercard implementation of a WAIS client.
Its main characteristic is that it allows the user to remodel
the interface completely to their liking.
General comments: Requires approximately 1.7Mb to run
(including Hypercard).
Requires system 7.0 or greater.
Requires Hypercard 2.1
Requires Mac TCP
Future plans: None at present
------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: Brewster@wais.com
Platform: VMS
Primary Contact:
Name: Jim Fullton
Email address: Jim.Fullton@cnidr.org
Telephone:
Client software available from:
Location of more information:
Latest version number:
Brief Scope and Characteristics:
General comments:
Future plans:
------------------
Date completed or updated: 13th December, 1993
By: Name: Brewster Kahle
Email address: Brewster@wais.com
Platform: DOS
Primary Contact:
Name: Jim Fullton
Email address: Jim.Fullton@cnidr.org
Telephone:
Client software available from: /pub/freeware/dos/pc.wais @wais.com
Location of more information:
Latest version number:
Brief Scope and Characteristics:
General comments:
Future plans:
------------------