2. General Description

2.2.1. Publication of resources

The system will allow to publish resources located in any place of Internet.

Each resource will be located by its description, that will be in the Donantonio servers, and therefore, it will not have why to coincide with the publication place of the resource.

2.2.2. Registry of descriptions

Each description will have a publication point, from which a donantonio server incorporates it to his library through the registry process.

2.2.3. Queries and replication of descriptions

The donantonio server will include mechanisms or protocols to admit the total or partial replication of the descriptions solicited by the clients.

For this aim, the servers will have to be able to attend queries of descriptions, for which will be defined the corresponding mechanisms or protocols.

The implanted mechanisms and languages of search in the servers will have to be compatible with those of the clients.

2.4.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.4.2. Dependencies

Although the server functionality is independent, because only it communicates with other clients when these do a request to him, can depend of other servers if, using the client functionality, it replicate from other server information for the maintenance of his own library.

Note: Review this. In fact there is communication

2.4.3. Specific requirements

In this section the it shows the functional requirements that will have to be satisfied by the system. All the requirements exposed here are ESSENTIAL, that is, a system would not be acceptable that does not satisfy some of the requirements presented here. These requirements have been specified considering, among others, the criterion of testing: given a requirement, it would have easily to be demonstrable if it is satisfied or not by the system.

Note: It is convenient to make the "requirements matrix", that confronts the requirements with the verification method.

2.5.1. REQ01: Registering descriptions

The server must register descriptions of resources (metadata and the corresponding URL).

2.5.2. REQ02: Visibility of the descriptions

All donantonio server will implement query's mechanisms that allow to select from a client a set of the descriptions that this one has.

2.5.3. REQ03: Transportability of the descriptions

All donantonio server will allow export a selected set of descriptions.

2.5.4. REQ04: Selection of descriptions

All server will implement mechanisms or languages that allow the clients to specify a consultation of their stored resources.

2.5.5. REQ05: Independence between servers

The servers will be independent to be able to give service independently to the clients.

2.5.6. REQ06: Unicity of the descriptions

The descriptions will have to be unique in each library maintained in each server.

2.6.1. User Interfaces

2.6.2. Interfaces hardware

Interfaces hardware

2.6.3. Software interfaces

2.6.4. Communication's interfaces

2.7.1. REQ10: Response time

The response times to the interactive queries will have to be reduced, considering a efficient communication network.

2.7.2. REQ11: Concurrency

The system will have to support concurrent attention to the queries.

2.8.1. REQ12: Life's Cicle.

The chosen life's cycle to develop the system will be the evolutionary prototype, so changes and new functions can be incorporated easily.

2.9.1. REQ13: Bibliographical norms

The bibliographical schemes to use in the system will be expressed in RDF.

2.10.1. REQ14: Free Software

The system will be free software and, therefore, any software component that it will be reused will have to be free.

2.10.2. REQ15: Portability

The system will be designed portable. It will have to be possible to implement applications donantonio in diverse languages and platforms.

2.10.3. REQ16: Maintenance

The system is susceptible to be extended. Therefore it will have to be designed easily supported, applying for his development the methodologies what it be precise for that.