PRIDE Architecture and Interfaces &
PRIDE Logical Components and Integration Designs
Work Package 2 of Telematics for Libraries project PRIDE (LB 5624)
|
Title page
Table of Contents
Previous
-
Next
|
The
PRIDE project will implement and demonstrate the use of a combined directory
service that has integrated support for both Patron Information (e.g.
information about people and organisations) and Service Information
(e.g. information needed to contact remote networked services).
The PRIDE demonstrator will comprise:
- Directory Service - A combined directory service, the PRIDE Directory,
(offering both patron and service information) based on open standards.
- User Access - A WWW based user agent (in addition to client access
available as a result of the standard protocols supported).
- Harvesters and Agents - Software that provides automatic population of
the PRIDE Directory from existing information sources, automatic reformatting
and management of information in the directory and the generation of alerts for
end-users based on Selective Dissemination of Information (SDI)
profiles.
- Proxy Services - Services which mimic those already existing but make
use of the PRIDE Directory to offer an enhanced level of functionality.
This document provides a high level functional specification of the PRIDE
demonstrator, identifying the key architectural components and noting any
existing software that will be re-used and integrated. It builds on D2.2.1
- PRIDE Requirements & Success Factors to provide the baseline for
D3.1.1 - Consolidated PRIDE Design that will be written during Phase 2
of the project.
The
PRIDE demonstrator will investigate and demonstrate the following functional
areas:
- Directory enabling of existing applications.
- Access to directory systems via non-directory protocols.
- Schema design for patron and service directories.
- The application of harvesters to increase directory usefulness and to allow
automatic directory population.
- Agent toolkits and directory neutral access toolkits.
- Scaling up of LDAP using X.500 as a framework.
- Universal client as a gateway to many services.
- Authentication in association with directory services.
The demonstrator system will allow our initial premises and design decisions to
be assessed. This assessment will be undertaken later in the project, both
from a user point of view and from a technical point of view.
The
remainder of this document explores the listed functional areas by providing a
high level view of the functional units required for their implementation in
the demonstrator.
We begin with a discussion of the classes of component that will form the
system. These are: the directory itself; mechanisms to access the directory;
harvesters and agents; and directory enabled proxy applications.
This is followed by a system level view where the integration and
proritorization of the various components is considered.
|
1999-02-26
|
PRIDE Architecture and Interfaces &
PRIDE Logical Components and Integration Designs
|