Potential Integration: The panta rhei perspective

Below we sketch the current situation in KWARC regarding the three research projects TNTBase, JOBAD, and panta rhei. Please don't take any box titles or colouring too serious, it is only an initial infrastructure and tries to emphasis on the focus of our research projects. We tried to leave out details to keep our discussion on a very abstract level. Naturally, we are biased, so please excuse any misplacements of your work (tell us, we'll fix it immediately)! This is all up for discussion!

Focus of the three projects:

  •  TNTBase: Intelligent Storage of OMDoc Documents
    (keywords: ???)
  •  JOBAD: Integration of Web Service into web documents (generated from OMDoc), implementing (inter)active documents
    (keywords: elisions, folding, unit conversion, notation-on-the-fly)
  • p|j project: proof-of-concept prototype for document generation and configuration; including authentication and permission management
    (keywords: notation, variants, narcons)

The projects have specified three different RESTful APIs

and implemented these in the following components, each with different purpose:

  • The TNTBase frontend demonstrates the functionality of the TNTBase core system
  • The JOBAD server demonstrates the backend support of services provided by the Javascript Framework for Active Document (JOBAD)
  • The janta mediator provides a proof-of-concept implementation of context-aware document generation and configuration

Please note: We support integration! However, all projects are on-going research, focus differs and continuously changes. Also, three PhD thesis are connected to them (two of them need to be completed this year). Integration means depending on each other, potentially finding synergies but possibly slowing down progresses.

Further Information

Auxiliary Libraries and Tools for OMDoc:

 TNTBase project:

 JOBAD:

The panta | janta project (p|j):

  • panta rhei is maintained for  GenCS only (currently no further extensions to the E-Learning Release, interface features will eventually be integrated into panta)
  • panta developments are on hold, we don't do interface tasks, panta is only developed for demonstration, we don't do CoPs?, we don't do Forums, we don't do user modelling or system-driven automation
  • Focus of the project: document generation, we don't do backend tasks (no storage) but only process documents in-memory, for the document generation we will not use XSLT (XSLT/ CSS is used for demo purpose to generate human-readable XHTML output for panta)

Attachments