2. General Description

2.1. Perspective of the Product

The donantonio client will interact with servers, by a protocol that will have to be defined.

2.2. Functions of the system

2.2.1. Resources access

The client will be able to obtain from the donantonio's servers the information that the administrator determines, in form of sets of descriptions of resources (metadata).

The metadata that the clients get describe the resource, and this will not be necessarily located in the server what have provided the description.

2.2.2. Local Library

The client will maintain, with the got descriptions of the servers, a local library that adjusts to the requirements of the administrator of the client.

2.2.3. Queries and replication of descriptions

The donantonio clients will include mechanisms or protocols to make a total or partial replication of the stored descriptions in a server.

The clients, for this aim, will elaborate queries in a certain language that will have to be defined. The query language will allow to get as answer one or more descriptions, based on the pattern of query used.

2.2.4. Access of the user to resources

The client or the library of the client will have to accept also queries of information that interactively an user makes, through an application of the kind of donantonio user interface..

2.2.5. Access of the user to configuration

The client could be configured from an user's interface. To configure a client must be understood to establish of what servers are going to obtain the data, and how (by of what queries).

2.3. User Features

The user's interfaces that can be required for this application will have to be intuitive for handling, easy to learn and simple to handle. The system will have to display a high degree of usability.

2.4. Restrictions

The system will be free software (in agreement with the GNU-GPL license or similar) and will have to be free those components that it reuses.

The system will be designed according to a client/server model.

The system will based its communications on standard Internet protocols.

The different subsystems must have a simple design and implementation, independent of the platform or the programming language.

Note: The requirement "the clients must be able to take care of several user requests simultaneously" seems more than a present requirement an interesting improvement...

2.5. Suppositions and dependencies

2.5.1. Suppositions

It is assumed that the requirements described in this document are stable once is approved by the design team taking care of suggestions of the community. Any request of changes in the specification must be approved by the design team and be managed by the same one.

2.5.2. Dependencies

The Donantonio client requires to communicate with servers to keep his library. Therefore there is a dependency of the functionality that offers these.