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

3. Prioritisation and Integration

The previous section introduced the directory, agents, proxies, toolkits, etc. that will constitute the PRIDE demonstrator. It also described several scenarios for how these components fit together into an integrated system. The components themselves are flexible and can be deployed in different ways. This section provides a brief view of how the components will be used in the PRIDE demonstrator. In particular, we will consider which components are crucial to its success.

The critical core of the PRIDE demonstrator will be:

• The PRIDE Directory implemented using X.500.
• A set of schema for describing people, organisations, networked services, collections and catalogues, SDI profiles, authentication information and other objects as necessary.
• DAP and LDAP access to the PRIDE directory.
• The directory neutral (DAP/LDAP) SDK.
• The PRIDE Universal Client, providing administrative and end-user access to the PRIDE Directory. This will include support for client call-out to suitable existing clients.
• The PRIDE Agent Toolkit.
• The Curator Agent.

• Transparent access to LDAP servers from the X.500 PRIDE Directory.
• The Z39.50 Access Gateway.
• The Alerting Agent.
• The Z39.50 Explain Harvester.
• The RDF Harvester.
• The Z39.50 Proxy.

• The CORBA Access Gateway.
• The ILL Proxy.