The p|j project

The p|j project was launched to re-implement the panta-rhei system into a client-server architecture, including two components: panta (user interface/ frontend application) and janta (backend service). panta provides the browsing, discussion, and assessment infrastructure, while janta takes over all user, permission, and content handling (including adaptation and document generation).

Architecture

The janta component consists of a request handler, a content handler, and a user data handler. It provides a content interface to various repositories (we can provide plugins for MySQL, RDF triple stores, XML DBs, or the file system).

The user data handler manages all user data: It retrieves, updates, deletes, and stores data in the respective storage (via the content interface). Moreover, it provides user-specific input parameters for the content handler.

The content handler manages all content (documents): It retrieves, updates, deletes, and stores data depending on the functionality of the underlying repository. In addition, it provides the adaptation of content based on user-specific input parameters (requested from the user handler). The first adaptation service can provide the conversion of  OMDoc content into XHTML as well as the adaptation of notations (drawing on  JOMDoc).

A web-application (e.g. the panta component) can request (adapted) content and user data from janta and send user information to janta.

Further readings & ongoing-discussions

•  milestones
• panta roadmap
• janta roadmap