Initial Architecture Diagram

· development
The nice thing about a project like DATAMI, which is mostly being developed from scratch, is that we always get to start with a kind of architecture diagram. In my view, while it does not really get into the details of what’s going on, this is still the best way to do project planning: identify the individual components and tasks, the dependencies between them, and their requirements. We made one on a whiteboard a couple of weeks ago with Carlo and I though that translating it into a human readable form (turns out the DATAMI team, i.e., Carlo and I, are not exactly human) would be the right first ‘serious’ post here.
Architecture overview of DATAMI

Architecture overview of DATAMI

I won’t go into the details of it now, but the basic principle is that there are three main activities: recording, enhancing and visualising. Recording corresponds to capturing the online activities of the user, through a local web proxy. This tool already exists in an initial form and will be finalised soon. Enhancing is where the IKS Stanbol services are being used, extracting additional semantic information related to the online resources being encountered by the user through their online activities. Visualising is the last bit of the puzzle, where we will need to find a way to enable users to view, understand and explore their semantically enhanced web history. The whole data management and communication aspect of this architecture will be handled through the use of semantic technologies, with information being stored in RDF triple stores (Fuseki) and the exchange of information between components being tackled using the SPARQL and SPARQL-Update protocols.


Comments RSS

Leave a Comment