Technologically, the programming will be based on a central system, or basic technological infrastructure, and on a set of modules or services that can be developed separately and independently of the central system. Communication between the central system and the modules will be done through calls based on OKI/OSID specifications (http://www.okiproject.org).
The central system will manage all the transversal aspects of the process, for example, security and session control. The individual modules will be responsible for managing their own functions and module specific information. The central system could use either Moodle or Sakai platforms as a base, as the project guarantees compatibility with both platforms, using OKI.
It is a Service Oriented Architecture (SOA) with an open technological base that will allow interoperability between heterogenic modules. Communication with the central system will be principally based on web services, and each module will be able to choose its own internal architecture and base technology. The architecture proposed will be made up of four main layers:
1. Basic Platform: The platform used will depend on the service. It could be either Moodle or SAKAI.
2. OKI Adapter: This will allow the connection between the modules and the basic platform, using OKI/OSID specifications. Libraries will be provided using both Java and PHP.
3. OSIDs: The set of service programming interfaces that will be available, as proposed by the OKI specifications.
4. Services or Modules The modules or services themselves. These make up the project. The basic platform is chosen based on these services.